Data acquisition method, device and system, and storage medium

Abstract

A data acquisition method, device and system, and a storage medium. The method comprises: a network management service consumption entity can send to a network management service providing entity a calculation formula for calculating communication efficiency data of a network element set; and the network management service providing entity can obtain the communication efficiency data of the network element set on the basis of the calculation formula provided by the network management service consumption entity, and send the communication efficiency data to the network management service consumption entity. Therefore, the communication efficiency data can be flexibly acquired on the basis of the requirement of the network management service consumption entity.

Description

Data acquisition method, device, system and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 15, 2023, with application number 202311733276.6 and invention name “Data Acquisition Method, Device, System and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a data acquisition method, device, system and storage medium. Background Art

[0003] Communication efficiency is an important metric for evaluating network energy-saving measures. By comparing the communication efficiency data of a set of network elements before and after energy conservation, an improvement in communication efficiency indicates that the energy-saving measure has achieved a positive effect.

[0004] Generally, the network management service providing entity stores a calculation formula for communication efficiency data defined by a standard, calculates the communication efficiency data according to the stored calculation formula, and returns the communication efficiency data to the network management service consuming entity.

[0005] However, the current standards allow for a single type of communication efficiency data to be measured, and communication efficiency data cannot be obtained flexibly.

[0006] Summary of the Invention

[0007] The present application provides a data acquisition method, device, system and storage medium to flexibly acquire communication efficiency data.

[0008] In a first aspect, a data acquisition method is provided. The method can be executed by a network management service consuming entity, or by a chip or circuit configured in the network management service consuming entity, or by a logic module or software capable of implementing all or part of the functions of the network management service consuming entity. This application is not limited to this.

[0009] The method includes: sending a request message, the request message including a first calculation formula for calculating the communication efficiency data of a network element set, the first calculation formula including a first calculation factor and a second calculation factor, the first calculation factor indicating the service measurement data associated with the network element set, the second calculation factor indicating the cost data associated with the network element set, the network element set including at least one communication network element; and receiving the communication efficiency data of the network element set obtained based on the first calculation formula.

[0010] Using this method, a network management service consuming entity can send a calculation formula for calculating communication efficiency data for a set of network elements to a network management service providing entity. The network management service providing entity can then obtain the communication efficiency data for the set of network elements based on the calculation formula provided by the network management service consuming entity and send this communication efficiency data to the network management service consuming entity. Thus, communication efficiency data can be flexibly obtained based on the needs of the network management service consuming entity.

[0011] In a possible implementation, the communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

[0012] In another possible implementation, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0013] In another possible implementation, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0014] In another possible implementation, the carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

[0015] With this implementation, carbon emission data can be real-time data collected from a set of network elements, predicted data based on historical carbon emission data associated with the set of network elements, or derived from energy consumption data. When the network management service provider is unable to obtain carbon emission data on time (for example, because the network element set has weak data processing capabilities or is performing other tasks), the network management service provider can utilize its prediction function to obtain predicted data based on historical carbon emission data associated with the set of network elements. This ensures the timeliness and accuracy of carbon emission data feedback.

[0016] In another possible implementation, the energy consumption data is real-time data collected from the set of network elements, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the set of network elements.

[0017] With this implementation, energy consumption data can be either real-time data collected from a collection of network elements or predicted data based on historical energy consumption data associated with the collection. When the network management service provider is unable to obtain energy consumption data on time (for example, due to low data processing capabilities of the collection or due to other tasks), the network management service provider can leverage its prediction capabilities to generate predicted data based on historical energy consumption data associated with the collection. This ensures the timeliness and accuracy of energy consumption data feedback.

[0018] In another possible implementation, the service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on historical service measurement data associated with the network element set.

[0019] With this implementation, service metric data can be either real-time data collected from a set of network elements or predicted data derived from historical service metric data associated with the set. When the network management service provider is unable to obtain service metric data on time (for example, due to low data processing capabilities of the set of network elements or due to other tasks), the network management service provider can leverage its prediction capabilities to derive predicted data based on historical service metric data associated with the set of network elements. This ensures the timeliness and accuracy of service metric data feedback.

[0020] In another possible implementation, the request message further includes an identifier of at least one communication network element in the network element set.

[0021] In another possible implementation, the request message further includes an identifier corresponding to the first calculation formula.

[0022] With this implementation, the identifier is used to uniquely identify the communication efficiency data, and the identifier has a one-to-one correspondence with the first calculation formula.

[0023] In yet another possible implementation, the method further includes: acquiring the identifier and / or the first calculation formula based on user input.

[0024] With this implementation, users can customize the identification and calculation formula of communication efficiency data, thereby being able to flexibly obtain communication efficiency data.

[0025] In yet another possible implementation, the method further includes: presenting the first calculation factor and / or the second calculation factor for selection by the user.

[0026] With this implementation, the user can flexibly select the first calculation factor and the second calculation factor, thereby flexibly constructing a calculation formula for communication efficiency data.

[0027] In another possible implementation, the method further includes: receiving the first calculation factor and / or the second calculation factor from an operation administration and maintenance (OAM) or a third-party server; or, obtaining the first calculation factor and / or the second calculation factor from a configuration file.

[0028] In another possible implementation, the identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

[0029] In this implementation, the network management service consumer entity may also request to update the calculation formula for the communication efficiency data, thereby obtaining the communication efficiency data it requires.

[0030] In a second aspect, a data acquisition method is provided. The method can be executed by a network management service provider, or by a chip or circuit configured in the network management service provider, or by a logic module or software capable of implementing all or part of the network management service provider's functions. This application is not limited to this.

[0031] The method includes: receiving a request message, the request message including a first calculation formula for calculating the communication efficiency data of a network element set, the first calculation formula including a first calculation factor and a second calculation factor, the first calculation factor indicating the service measurement data associated with the network element set, the second calculation factor indicating the cost data associated with the network element set, the network element set including at least one communication network element; and sending the communication efficiency data of the network element set obtained based on the first calculation formula.

[0032] Using this method, a network management service provider can receive a calculation formula for calculating communication efficiency data for a set of network elements from a network management service consumer. The network management service provider can then obtain the communication efficiency data for the set of network elements based on the calculation formula provided by the network management service consumer, and send the communication efficiency data to the network management service consumer. This allows for flexible acquisition of communication efficiency data based on the needs of the network management service consumer.

[0033] In a possible implementation, the communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

[0034] In another possible implementation, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0035] In another possible implementation, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0036] In another possible implementation, the carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

[0037] With this implementation, carbon emission data can be real-time data collected from a set of network elements, predicted data based on historical carbon emission data associated with the set of network elements, or derived from energy consumption data. When the network management service provider is unable to obtain carbon emission data on time (for example, because the network element set has weak data processing capabilities or is performing other tasks), the network management service provider can utilize its prediction function to obtain predicted data based on historical carbon emission data associated with the set of network elements. This ensures the timeliness and accuracy of carbon emission data feedback.

[0038] In another possible implementation, the energy consumption data is real-time data collected from the set of network elements, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the set of network elements.

[0039] With this implementation, energy consumption data can be either real-time data collected from a collection of network elements or predicted data based on historical energy consumption data associated with the collection. When the network management service provider is unable to obtain energy consumption data on time (for example, due to low data processing capabilities of the collection or due to other tasks), the network management service provider can leverage its prediction capabilities to generate predicted data based on historical energy consumption data associated with the collection. This ensures the timeliness and accuracy of energy consumption data feedback.

[0040] In another possible implementation, the service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on historical service measurement data associated with the network element set.

[0041] With this implementation, service metric data can be either real-time data collected from a set of network elements or predicted data derived from historical service metric data associated with the set. When the network management service provider is unable to obtain service metric data on time (for example, due to low data processing capabilities of the set of network elements or due to other tasks), the network management service provider can leverage its prediction capabilities to derive predicted data based on historical service metric data associated with the set of network elements. This ensures the timeliness and accuracy of service metric data feedback.

[0042] In another possible implementation, the request message further includes an identifier of at least one communication network element in the network element set.

[0043] In another possible implementation, the identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

[0044] In this implementation, the network management service consumer entity may also request to update the calculation formula for the communication efficiency data, thereby obtaining the communication efficiency data it requires.

[0045] In a possible implementation, the method further includes: parsing the first calculation formula; and verifying the first calculation formula.

[0046] With this implementation, since the calculation formula for the communication efficiency data in this application is user-defined, the network management service provider entity needs to parse and verify the calculation formula for the communication efficiency data after receiving the request message.

[0047] The custom calculation formula for communication efficiency data includes a number, a first calculation factor, a second calculation factor, and an operator. The network management service provider may pre-store multiple numbers, multiple first calculation factors, multiple second calculation factors, and multiple operators. Upon receiving a request message, the network management service provider may compare the pre-stored numbers, calculation factors, and operators with the calculation formula for communication efficiency data in the request message to parse the calculation formula for communication efficiency data.

[0048] The network management service providing entity verifies whether the calculation formula of the communication efficiency data is valid. If the identifier of the communication efficiency data and the calculation formula of the communication efficiency data meet the requirements, it is valid; otherwise, it is invalid.

[0049] In another possible implementation, the first calculation formula also includes an operator, which is used to calculate the first calculation factor and the second calculation factor; the verification of the first calculation formula includes at least one of the following operations: checking whether the first calculation factor and the second calculation factor conform to the standard definition; or checking whether the operator conforms to the standard definition.

[0050] With this implementation, the first calculation factor and the second calculation factor in the first calculation formula are checked to see if they comply with the standard definition. For example, the first calculation factor and the second calculation factor are checked to see if they can be found in the existing standard. If not, the first calculation formula is considered invalid; if they can be found, the first calculation formula is considered valid.

[0051] Check whether the operators in the first calculation formula comply with the standard definition. For example, check whether the operators in the first calculation formula entered by the user can be operated normally. For example, if special characters such as @, #, and % appear, which will cause the first calculation formula to fail to operate normally, the first calculation formula is considered invalid; if no such special characters appear, the first calculation formula is considered valid.

[0052] In another possible implementation, the request message further includes an identifier corresponding to the first calculation formula.

[0053] With this implementation, the identifier is used to uniquely identify the communication efficiency data, and the identifier has a one-to-one correspondence with the first calculation formula.

[0054] In yet another possible implementation, the method further includes: checking whether the identifier is repeated with an identifier defined in a standard.

[0055] In this implementation, since the communication efficiency data identifiers in this application are user-defined, it is necessary to verify whether the communication efficiency data identifiers are valid. If the communication efficiency data identifiers meet the requirements, they are valid; otherwise, they are invalid. The network management service provider can first check the communication efficiency data identifiers defined by existing standards. If no such identifiers are found, they can then check the user-defined communication efficiency data list. If no such identifiers are found, the verification is considered invalid.

[0056] In another possible implementation, the method further includes: storing the identifier and the first calculation formula correspondingly.

[0057] With this implementation, the network management service provider can store the identifier and the first calculation formula corresponding to the identifier locally or on a third-party server. If the network management service consumer requests the communication efficiency data again, it can include the identifier in the request message instead of the first calculation formula. The network management service provider can then search for the first calculation formula corresponding to the identifier locally or on a third-party server based on the identifier in the request message. This reduces request message overhead.

[0058] In yet another possible implementation, the identifier further corresponds to a second calculation formula used to calculate energy efficiency data of the communication network, and the request message is used to request that the second calculation formula be replaced with the first calculation formula.

[0059] With this implementation, the network management service provider entity can store the above-mentioned identifier and the first calculation formula locally or on a third-party server. If the network management service consumer entity requests to obtain the communication efficiency data again, and the calculation formula of the communication efficiency data is updated, the second calculation formula carrying the identifier and the update can be selected in the request message. After receiving the request message, the network management service provider entity searches for the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity based on the identifier of the communication efficiency data in the request message, and checks that the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity is partially or completely different from the second calculation formula carried in the request message. The network management service provider entity then uses the second calculation formula carried in the request message to update the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity.

[0060] In a third aspect, a data acquisition device is provided that can implement the method of a network management service consumption entity described in the first aspect or any implementation of the first aspect. For example, the network management service consumption entity can be a chip or circuit. The method can be implemented using software, hardware, or hardware executing corresponding software.

[0061] In one possible implementation, the device includes: a transceiver unit, and may also include a processing unit; wherein the transceiver unit is used to send a request message, the request message includes a first calculation formula for calculating the communication efficiency data of a network element set, the first calculation formula includes a first calculation factor and a second calculation factor, the first calculation factor indicates the service measurement data associated with the network element set, the second calculation factor indicates the cost data associated with the network element set, and the network element set includes at least one communication network element; and the transceiver unit is also used to receive the communication efficiency data of the network element set obtained based on the first calculation formula.

[0062] Optionally, the communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

[0063] Optionally, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0064] Optionally, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0065] Optionally, the carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

[0066] Optionally, the energy consumption data is real-time data collected from the network element set, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the network element set.

[0067] Optionally, the service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on historical service measurement data associated with the network element set.

[0068] Optionally, the request message further includes an identifier of at least one communication network element in the network element set.

[0069] Optionally, the request message further includes an identifier corresponding to the first calculation formula.

[0070] Optionally, the processing unit is used to obtain the identifier and / or the first calculation formula based on user input.

[0071] Optionally, the processing unit is further configured to present the first calculation factor and / or the second calculation factor for selection by the user.

[0072] Optionally, the transceiver unit is further used to receive the first calculation factor and / or the second calculation factor from OAM or a third-party server; or, the processing unit is further used to obtain the first calculation factor and / or the second calculation factor from a configuration file.

[0073] Optionally, the identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

[0074] In a fourth aspect, a data acquisition device is provided that can implement the method of the network management service provider entity described in the second aspect or any implementation of the second aspect. For example, the network management service provider entity can be a chip or circuit. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0075] In one possible implementation, the device includes: a transceiver unit, and may also include a processing unit; wherein the transceiver unit is used to receive a request message, the request message includes a first calculation formula for calculating the communication efficiency data of a network element set, the first calculation formula includes a first calculation factor and a second calculation factor, the first calculation factor indicates the service measurement data associated with the network element set, the second calculation factor indicates the cost data associated with the network element set, and the network element set includes at least one communication network element; and the transceiver unit is also used to send the communication efficiency data of the network element set calculated based on the first calculation formula in response to the request message.

[0076] Optionally, the communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

[0077] Optionally, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0078] Optionally, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0079] Optionally, the carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

[0080] Optionally, the energy consumption data is real-time data collected from the network element set, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the network element set.

[0081] Optionally, the service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on historical service measurement data associated with the network element set.

[0082] Optionally, the request message further includes an identifier of at least one communication network element in the network element set.

[0083] Optionally, the processing unit is used to parse the first calculation formula; and the processing unit is further used to verify the first calculation formula.

[0084] Optionally, the first calculation formula also includes an operator, which is used to calculate the first calculation factor and the second calculation factor; the processing unit is also used to check whether the first calculation factor and the second calculation factor meet the standard definition; or check whether the operator meets the standard definition.

[0085] Optionally, the request message further includes an identifier corresponding to the first calculation formula.

[0086] Optionally, the processing unit is further configured to check whether the identifier is repeated with an identifier defined in a standard.

[0087] Optionally, the identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

[0088] In combination with the third aspect to the fourth aspect or any aspect of the third aspect to the fourth aspect, in another possible implementation, the data acquisition device in the above-mentioned third aspect to the fourth aspect or any aspect of the third aspect to the fourth aspect includes a processor coupled to a memory; the processor is configured to support the device to perform the corresponding functions in the above-mentioned network management operation instruction synchronization method. The memory is used to couple with the processor, which stores the necessary programs (instructions) and / or data for the device. Optionally, the data acquisition device may further include a communication interface for supporting communication between the device and other network elements. Optionally, the memory may be located inside the data acquisition device or outside the data acquisition device.

[0089] In combination with the third aspect to the fourth aspect or any one of the third aspect to the fourth aspect, in another possible implementation, the data acquisition device in the third aspect to the fourth aspect or any one of the third aspect to the fourth aspect includes a processor and a transceiver device, the processor is coupled to the transceiver device, the processor is used to execute a computer program or instruction to control the transceiver device to receive and send information; when the processor executes the computer program or instruction, the processor is also used to implement the above method through a logic circuit or execute code instructions. The transceiver device can be a transceiver, a transceiver circuit or an input-output interface, which is used to receive signals from other devices outside the data acquisition device and transmit them to the processor or send signals from the processor to other devices outside the data acquisition device. When the data acquisition device is a chip, the transceiver device is a transceiver circuit or an input-output interface.

[0090] When the data acquisition device in any of the third and fourth aspects or the third and fourth aspects is a chip or chip module, the sending unit may be an output unit, such as an output circuit or a communication interface; and the receiving unit may be an input unit, such as an input circuit or a communication interface. When the data acquisition device is a terminal or access network device, the sending unit may be a transmitter or a transmitter; and the receiving unit may be a receiver or a receiver.

[0091] In a fifth aspect, a data acquisition system is provided, comprising the data acquisition device as described in the third aspect or any one implementation of the third aspect and the data acquisition device as described in the fourth aspect or any one implementation of the fourth aspect.

[0092] In the sixth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When a computer executes the computer program or instruction, the method described in the first aspect, the second aspect, or any possible implementation of the first aspect and the second aspect is implemented.

[0093] In a seventh aspect, a computer program product comprising instructions is provided, which, when executed on a data acquisition device, causes the data acquisition device to execute the method described in the first aspect, the second aspect, or any possible implementation of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] FIG1 is a flow chart of a data acquisition method provided in an embodiment of the present application;

[0095] FIG2 is a schematic diagram of the architecture of a data acquisition system provided in an embodiment of the present application;

[0096] FIG3 is a flow chart of a data acquisition method provided in an embodiment of the present application;

[0097] FIG4 is a flow chart of another data acquisition method provided in an embodiment of the present application;

[0098] FIG5 is a schematic structural diagram of a data acquisition device provided in an embodiment of the present application;

[0099] FIG6 is a schematic structural diagram of another data acquisition device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0101] In wireless energy-saving scenarios, communication efficiency is a key metric for evaluating network energy-saving measures. By comparing the communication efficiency data of a set of network elements before and after energy conservation, an improvement in communication efficiency indicates that the energy-saving measure has had a beneficial effect.

[0102] As shown in Figure 1, it is a flow chart of a data acquisition method provided in an embodiment of the present application. Exemplarily, the method may include the following steps:

[0103] S101. A network management service consuming entity sends a request message to a network management service providing entity. Correspondingly, the network management service providing entity receives the request message.

[0104] This request message is used to request communication efficiency data.

[0105] The request message includes a measurement category list (measurementCategoryList) and a measurement granularity period (granularityPeriod).

[0106] The measurement category list indicates the measurement type(s) or key performance indicator (KPI) name / identity (ID) to be measured for this measurement task. KPIs include communication efficiency, which is a subcategory of KPIs. Currently, KPI-class measurement tasks can only measure the communication efficiency defined in the standard.

[0107] The communication efficiency data is related to a ratio of service measurement data to cost data, where the service measurement data refers to service measurement data associated with the network element set, and the cost data refers to cost data associated with the network element set.

[0108] The measurement granularity period is used to indicate the time interval between two measurement data. For example, for KPI-type measurements, the maximum measurement frequency is once every 5 minutes.

[0109] S102. The network management service providing entity sends communication efficiency data to the network management service consuming entity. Correspondingly, the network management service consuming entity receives the communication efficiency data.

[0110] In this embodiment, the network management service provider internally stores a calculation formula currently defined in the standard for calculating communication efficiency data for a set of network elements. When the network management service provider receives a request message from a network management service consumer, the network management service provider can search for the corresponding calculation formula based on the name / identifier of the communication efficiency, obtain service metric data and cost data from the set of network elements, calculate the communication efficiency data based on the found calculation formula and the obtained service metric data and cost data, and finally send the communication efficiency data to the network management service consumer.

[0111] However, currently only the communication efficiency data defined in the standard is allowed to be obtained, and the communication efficiency data allowed to be obtained is single. The existing standards define the radio access network (RAN), network slicing (subdivided into enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC), metamorphic internet of things (MIoT) and other service types), the fifth generation core network (5 th The calculation formula for communication efficiency data in the 5GC (5th Generation Core) scenario is presented. However, further standards propose using communication efficiency data as a service standard to provide services to users, allowing users to select communication efficiency data based on their needs. However, current communication efficiency measurement tasks can only measure communication efficiency data defined in existing standards, and cannot flexibly obtain communication efficiency data.

[0112] To address the above issues, this application provides a data acquisition solution. A network management service consuming entity can send a communication efficiency data calculation formula to a network management service providing entity. The network management service providing entity can then obtain communication efficiency data for a set of network elements based on the communication efficiency data calculation formula provided by the network management service consuming entity and send this communication efficiency data to the network management service consuming entity. This allows for flexible acquisition of communication efficiency data based on the needs of the network management service consuming entity, rather than being limited to acquiring standard-defined communication efficiency data.

[0113] Figure 2 shows a schematic diagram of the architecture of a data acquisition system provided in an embodiment of the present application. System 2000 includes a network management service consumer 201 and a network management service provider 202, which can interact with each other. For example, network management service consumer 201 can be located in a data acquisition system (network management system, NMS); network management service provider 202 can be located in an element management system (EMS).

[0114] Among them, the network management service consumption entity 201 sends a request message to the network management service providing entity 202, and the request message includes a first calculation formula for calculating the communication efficiency data of a network element set, the first calculation formula includes a first calculation factor and a second calculation factor, the first calculation factor indicates the service measurement data associated with the network element set, and the second calculation factor indicates the cost data associated with the network element set, and the network element set includes at least one communication network element; and the network management service providing entity 202 responds to the request message and sends the communication efficiency data of the network element set obtained based on the first calculation formula to the network management service consumption entity 201.

[0115] In a possible implementation, the communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

[0116] In another possible implementation, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0117] In another possible implementation, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0118] In another possible implementation, the carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

[0119] With this implementation, carbon emission data can be real-time data collected from a set of network elements, predicted data based on historical carbon emission data associated with the set of network elements, or derived from energy consumption data. When the network management service provider is unable to obtain carbon emission data on time (for example, because the network element set has weak data processing capabilities or is performing other tasks), the network management service provider can utilize its prediction function to obtain predicted data based on historical carbon emission data associated with the set of network elements. This ensures the timeliness and accuracy of carbon emission data feedback.

[0120] In another possible implementation, the energy consumption data is real-time data collected from the set of network elements, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the set of network elements.

[0121] With this implementation, energy consumption data can be either real-time data collected from a collection of network elements or predicted data based on historical energy consumption data associated with the collection. When the network management service provider is unable to obtain energy consumption data on time (for example, due to low data processing capabilities of the collection or due to other tasks), the network management service provider can leverage its prediction capabilities to generate predicted data based on historical energy consumption data associated with the collection. This ensures the timeliness and accuracy of energy consumption data feedback.

[0122] In another possible implementation, the service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on historical service measurement data associated with the network element set.

[0123] With this implementation, service metric data can be either real-time data collected from a set of network elements or predicted data derived from historical service metric data associated with the set. When the network management service provider is unable to obtain service metric data on time (for example, due to low data processing capabilities of the set of network elements or due to other tasks), the network management service provider can leverage its prediction capabilities to derive predicted data based on historical service metric data associated with the set of network elements. This ensures the timeliness and accuracy of service metric data feedback.

[0124] In another possible implementation, the request message further includes an identifier of at least one communication network element in the network element set.

[0125] In another possible implementation, the request message further includes an identifier corresponding to the first calculation formula.

[0126] With this implementation, the identifier is used to uniquely identify the communication efficiency data, and the identifier has a one-to-one correspondence with the first calculation formula.

[0127] In yet another possible implementation, the method further includes: acquiring the identifier and / or the first calculation formula based on user input.

[0128] With this implementation, users can customize the identification and calculation formula of communication efficiency data, thereby being able to flexibly obtain communication efficiency data.

[0129] In yet another possible implementation, the method further includes: presenting the first calculation factor and / or the second calculation factor for selection by the user.

[0130] With this implementation, the user can flexibly select the first calculation factor and the second calculation factor, thereby flexibly constructing a calculation formula for communication efficiency data.

[0131] In another possible implementation, the method further includes: receiving the first calculation factor and / or the second calculation factor from an OAM or a third-party server; or obtaining the first calculation factor and / or the second calculation factor from a configuration file.

[0132] In another possible implementation, the identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

[0133] In this implementation, the network management service consumer entity may also request to update the calculation formula for the communication efficiency data, thereby obtaining the communication efficiency data it requires.

[0134] In a possible implementation, the method further includes: parsing the first calculation formula; and verifying the first calculation formula.

[0135] With this implementation, since the calculation formula for the communication efficiency data in this application is user-defined, the network management service provider entity needs to parse and verify the calculation formula for the communication efficiency data after receiving the request message.

[0136] The custom calculation formula for communication efficiency data includes a number, a first calculation factor, a second calculation factor, and an operator. The network management service provider may pre-store multiple numbers, multiple first calculation factors, multiple second calculation factors, and multiple operators. Upon receiving a request message, the network management service provider may compare the pre-stored numbers, calculation factors, and operators with the calculation formula for communication efficiency data in the request message to parse the calculation formula for communication efficiency data.

[0137] The network management service providing entity verifies whether the calculation formula of the communication efficiency data is valid. If the identifier of the communication efficiency data and the calculation formula of the communication efficiency data meet the requirements, it is valid; otherwise, it is invalid.

[0138] In another possible implementation, the first calculation formula also includes an operator, which is used to calculate the first calculation factor and the second calculation factor; the verification of the first calculation formula includes at least one of the following operations: checking whether the first calculation factor and the second calculation factor conform to the standard definition; or checking whether the operator conforms to the standard definition.

[0139] With this implementation, the first calculation factor and the second calculation factor in the first calculation formula are checked to see if they comply with the standard definition. For example, the first calculation factor and the second calculation factor are checked to see if they can be found in the existing standard. If not, the first calculation formula is considered invalid; if they can be found, the first calculation formula is considered valid.

[0140] Check whether the operators in the first calculation formula comply with the standard definition. For example, check whether the operators in the first calculation formula entered by the user can be operated normally. For example, if special characters such as @, #, and % appear, which will cause the first calculation formula to fail to operate normally, the first calculation formula is considered invalid; if no such special characters appear, the first calculation formula is considered valid.

[0141] In another possible implementation, the request message further includes an identifier corresponding to the first calculation formula.

[0142] With this implementation, the identifier is used to uniquely identify the communication efficiency data, and the identifier has a one-to-one correspondence with the first calculation formula.

[0143] In yet another possible implementation, the method further includes: checking whether the identifier is repeated with an identifier defined in a standard.

[0144] In this implementation, since the communication efficiency data identifiers in this application are user-defined, it is necessary to verify whether the communication efficiency data identifiers are valid. If the communication efficiency data identifiers meet the requirements, they are valid; otherwise, they are invalid. The network management service provider can first check the communication efficiency data identifiers defined by existing standards. If no such identifiers are found, they can then check the user-defined communication efficiency data list. If no such identifiers are found, the verification is considered invalid.

[0145] In the present application, operations such as data collection and prediction performed by the network management service providing entity 202 may be performed by the network twin in the network management service providing entity 202 .

[0146] Digital twins (DTs) are a technology increasingly relevant to system automation. DTs are virtual replicas of real-world systems—physical systems—on which operations can be performed. Faced with the ever-increasing types, scale, and complexity of services, communication networks also need to leverage digital twin technology to seek better solutions beyond physical networks. Network twins, the application of digital twin technology to communication networks, aim to develop a wide range of network applications and achieve efficient, data-driven network management and maintenance.

[0147] A network twin is a digital twin whose physical counterpart is a communication network or some part of a communication network. A communication network can include, for example, physical network elements and components, virtualized network functions (VNFs) (i.e., network function elements instantiated as software-based entities), physical hosts for such VNFs, services, and traffic flows.

[0148] Specifically, a network twin refers to a digital mirror image of a physical network established in a digital manner. With the help of the historical network data, real-time network data and algorithmic models of the physical network, the physical network is digitized to achieve synchronous analysis, prediction and improvement optimization of the physical network. That is, the network twin contains a digital expression of the physical network and is used to simulate the physical network. Among them, the digital expression includes algorithmic models and data, etc. The network twin can also be called a network twin entity, a digital twin or a digital twin entity, and this application does not limit it. Among them, the physical network is a network formed by connecting various physical devices or network elements (such as hosts, routers, switches, etc.) and media (optical cables, cables, twisted pairs, etc.) in the network. The physical network can be a mobile access network, a transmission network, a mobile core network, a backbone network, etc.; the physical network can also be a data center network, a campus network, an industrial Internet of Things, etc. Network data can also be called network operation data, which is used to represent the operating status of the physical network. It can be configuration parameters, alarm data, performance data, etc. of physical devices or network elements.

[0149] Based on the above system, the data acquisition method provided by the embodiment of the present application is further described in detail below:

[0150] As shown in Figure 3, it is a flow chart of a data acquisition method provided in an embodiment of the present application. Exemplarily, the method may include the following steps:

[0151] S301. A network management service consuming entity sends a request message to a network management service providing entity. Correspondingly, the network management service providing entity receives the request message.

[0152] The request message includes a first calculation formula for calculating communication efficiency data of a network element set.

[0153] The first calculation formula includes a first calculation factor and a second calculation factor. The first calculation factor indicates service measurement data associated with the network element set, and the second calculation factor indicates cost data associated with the network element set. The service measurement data is a measurement of the service data of the network element set and is an effective output provided based on the unit cost; the cost data is the cost of generating, processing, or transmitting the service data of the network element set. The first calculation factor and the second calculation factor are indicators defined in the standard.

[0154] Exemplarily, the communication efficiency data (or the first calculation formula) is related to the ratio of the first calculation factor to the second calculation factor.

[0155] The network element set includes at least one communication network element. Exemplarily, the network element set may be a network function (NF) entity mentioned in the TS28.310 protocol.

[0156] In one implementation, the cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

[0157] Among them, energy efficiency refers to the effective output provided based on unit energy consumption.

[0158] In the calculation formula of the energy efficiency data, the first calculation factor indicates the service measurement data associated with the network element set, and the second calculation factor indicates the energy consumption data associated with the network element set.

[0159] Service measurement data may include the number of users, bandwidth, number of sessions, throughput, etc. It is understood that service measurement data may be the data volume mentioned in the TS28.310 protocol, or other data used to measure services, and this application is not limited thereto. The service measurement data may be real-time data collected from a set of network elements, or may be predicted data based on historical service measurement data associated with the set of networks.

[0160] The energy consumption data may be the energy consumed by the network element set. It is understood that the energy consumption data associated with the network element set may include not only the energy consumption data of the network element set itself, but also the energy consumption data of the equipment associated with the network element set. The energy consumption data associated with the network element set may be real-time data collected from the network element set, or the energy consumption data may be predicted data derived from historical energy consumption data associated with the network element set.

[0161] For example, the calculation formula for energy efficiency defined in the TS28.310 protocol is as follows:

[0162] Among them, DV MN Refers to the data volume (DV) of the mobile network (MN); EC MN Refers to the energy consumption (EC) of a set of network elements in a mobile network. The data volume can be, for example, throughput, and the unit can be bits; the unit of energy consumption is joules (J). Therefore, EE MN,DV The unit is bit / J.

[0163] In another implementation, the cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

[0164] Among them, carbon efficiency refers to the effective output provided based on unit carbon emissions.

[0165] In the calculation formula of the carbon efficiency data, the first calculation factor indicates the service measurement data associated with the network element set, and the second calculation factor indicates the carbon emission data associated with the network element set.

[0166] The meaning of business measurement data can be found in the description above.

[0167] The carbon emission data may be carbon emission data associated with a set of network elements. The carbon emission data may be real-time data collected from the set of network elements; or, the carbon emission data may be predicted data obtained based on historical carbon emission data associated with the set of network elements; or, the above-mentioned carbon emission data may also be obtained based on energy consumption data. Specifically, the carbon emission amount may be equal to the energy consumption data multiplied by the carbon emission factor. The specific carbon emission factor may be calculated based on the proportion of non-green energy used in the communication system and the proportion of specific non-green energy power generation materials used (such as coal-fired power generation, oil-fired power generation, etc.).

[0168] In this embodiment, the network management service consuming entity can carry a calculation formula in a request message, instead of only using a calculation formula stored in a network management service providing entity to calculate communication efficiency data as in the prior art. The calculation formula can be user-defined.

[0169] Furthermore, the first calculation formula may also include numbers and operators. For example, the energy efficiency identifier is EE_RAN_RRC, and the calculation formula of the energy efficiency is 10000*(RRC.ConnEstabSucc / RRC.ConnEstabAtt) / PEE.Energy. Among them, 10000 is a number in the calculation formula, which is generally a constant; the calculation formula includes the following two first calculation factors: the number of successful radio resource control connection establishment attempts (RRC.ConnEstabSucc), the number of radio resource control connection establishment attempts (RRC.ConnEstabAtt), and the calculation formula includes the following second calculation factor: energy consumption (PEE.Energy); the operators in the calculation formula include multiplication (*) and division ( / ), which are used to calculate the first calculation factor and the second calculation factor.

[0170] RRC.ConnEstabSucc indicates the number of successful radio resource control (RRC) connection establishments. This data can be obtained from the base station. After receiving the RRC connection setup request from the terminal, the base station sends an RRC connection setup complete message. Each time the base station sends or the terminal receives an RRC connection setup complete message, RRC.ConnEstabSucc increments by 1.

[0171] RRC.ConnEstabAtt indicates the number of RRC connection establishment attempts. Each time the base station receives an RRC connection establishment request from the terminal, RRC.ConnEstabAtt increases by 1. This data can be obtained from the base station.

[0172] Among them, PEE.Energy indicates energy consumption data associated with the base station and the terminal.

[0173] S302. In response to the request message, the network management service providing entity sends the communication efficiency data of the network element set obtained based on the first calculation formula to the network management service consuming entity. Correspondingly, the network management service consuming entity receives the communication efficiency data.

[0174] After receiving the request message, the network management service provider obtains the first calculation formula carried in the request message and parses the first calculation formula. Based on the first and second calculation factors included in the parsed first calculation formula, the provider obtains service metric data and cost data associated with the network element set. Based on the first calculation formula and the obtained service metric data and cost data associated with the network element set, the provider calculates communication efficiency data. The provider then sends the communication efficiency data for the network element set to the network management service consumer.

[0175] It is understandable that the first calculation factor and the second calculation factor correspond to data of the same time period, that is, the acquired service metric data associated with the network element set and the communication efficiency data correspond to data of the same time period. For example, the start time and end time of the acquired data may be the same.

[0176] According to a data acquisition method provided in an embodiment of the present application, a network management service consuming entity can send a calculation formula for communication efficiency data to a network management service providing entity. The network management service providing entity can then obtain communication efficiency data for a set of network elements based on the calculation formula for communication efficiency data provided by the network management service consuming entity and send the communication efficiency data to the network management service consuming entity. Thus, communication efficiency data can be flexibly acquired based on the needs of the network management service consuming entity.

[0177] The above embodiment describes how to obtain communication efficiency data. The following embodiment will further describe how to obtain a user-defined calculation formula for communication efficiency data, and how to verify the user-defined identifier and the calculation formula for communication efficiency data.

[0178] FIG4 is a flow chart of another data acquisition method provided in an embodiment of the present application. Exemplarily, the method may include the following steps:

[0179] S401. The network management service consumption entity obtains an identifier and / or a first calculation formula based on user input.

[0180] In this embodiment, the network management service consumption entity may obtain the identifier input by the user and / or the first calculation formula corresponding to the identifier through some interactive means. The identifier and the first calculation formula are user-defined.

[0181] For example, the network management service consuming entity may receive at least one first calculation factor and / or at least one second calculation factor from the OAM or a third-party server, or obtain at least one first calculation factor and / or at least one second calculation factor from its own configuration file. The first calculation factor and / or the second calculation factor are then presented to the user for selection. The network management service consuming entity receives the first calculation factor and / or the second calculation factor selected by the user, generates a first calculation formula, and establishes a correspondence between the identifier and the first calculation formula.

[0182] For the meaning of the first calculation formula, please refer to the above description.

[0183] S402: The network management service consuming entity sends a request message to the network management service providing entity. Correspondingly, the network management service providing entity receives the request message.

[0184] The request message includes an identifier corresponding to the first calculation formula (the identifier has a one-to-one correspondence with the first calculation formula), a first calculation formula for calculating the communication efficiency data of a network element set, and an identifier of at least one communication network element in the network element set.

[0185] In one example, the request message may include an existing measurement category list. The identifier may be included in the existing measurement category list. The existing measurement category list is used to indicate the measurement types and KPIs specified by the standard and generally does not support the specification of unknown or invalid measurement types and KPIs. In this example, the logic of the existing measurement category list is modified to support the specification of identifiers input by users. In addition, the existing measurement category list may also include identifiers defined by the standard, and the network management service provider entity may obtain communication efficiency data defined by the standard according to the method shown in Figure 1. The request message may also include a user-defined communication efficiency list, which includes an identifier and a first calculation formula.

[0186] In another example, the identifier can be included in a user-defined measurement list. In this example, the logic of the existing measurement category list is not modified because the existing measurement category list is used to indicate the measurement types and KPIs specified by the standard and generally does not support the specification of unknown or invalid measurement types and KPIs. Instead, a user-defined measurement list is introduced to specify the measurement of user-defined communication efficiency. In addition, the request message may also include an existing measurement category list, which includes an identifier for energy efficiency defined by the standard. The network management service provider entity can obtain standard-defined communication efficiency data according to the method shown in Figure 1. The request message may also include a user-defined communication efficiency list, which includes an identifier and a first calculation formula.

[0187] In the above two examples, the user-defined communication efficiency list can include two attribute values, name and formula, which are used to define the identifier and the calculation formula of the communication efficiency data respectively. The details are shown in Table 1 below:

[0188] Table 1

[0189] S403. After receiving the request message, the network management service providing entity obtains the identifier and the first calculation formula included in the request message, parses the first calculation formula, and verifies the identifier and the first calculation formula.

[0190] As previously mentioned, the first calculation formula for communication efficiency data includes a number, a first calculation factor, a second calculation factor, and an operator. The first calculation factor and the second calculation factor are indicators defined in the standard. The network management service provider pre-stores a variety of numbers, first calculation factors, second calculation factors, and operators. Upon receiving a request message, the network management service provider compares the pre-stored numbers, first calculation factors, second calculation factors, and operators with the first calculation formula in the request message to parse the first calculation formula.

[0191] Since the calculation formula for the identifier and communication efficiency data in this embodiment is user-defined, the network management service provider entity needs to verify whether the identifier and the calculation formula for the communication efficiency data are valid. If the identifier and the calculation formula for the communication efficiency data meet the requirements, it is valid; otherwise, it is invalid.

[0192] To check whether the custom identifier is valid, you can use the following methods:

[0193] One approach is for the network management service provider to first check against existing standard-defined identifiers. If no such identifiers are found, the provider can then check against a user-defined communication efficiency list. If no such identifiers are found, the verification is deemed invalid.

[0194] Another way may be to check whether the identifier is repeated with the identifier defined by the standard. If repeated, the customized identifier is considered invalid; if not repeated, the customized identifier is considered valid.

[0195] The following methods can be used to verify whether the calculation formula for the customized communication efficiency data is valid:

[0196] One approach may be to check whether the first and second calculation factors included in the calculation formula for communication efficiency data comply with the standard's definition. For example, the first and second calculation factors included in the calculation formula for communication efficiency data may be checked to see whether they can be found in existing standards. If they cannot be found, the calculation formula is considered invalid; if they can be found, the calculation formula is considered valid.

[0197] Another approach is to check whether the operators included in the communication efficiency data calculation formula comply with the standard definition. For example, the operator in the communication efficiency data calculation formula entered by the user can be checked to see if it can be operated normally. For example, if special characters such as @, #, and % appear, which will cause the calculation formula to fail to operate normally, the calculation formula is considered invalid. If these special characters do not appear, the calculation formula is considered valid.

[0198] S404a. If the verification is invalid, the network management service providing entity feeds back to the network management service consuming entity that the creation of the measurement task has failed.

[0199] The network management service provides entity feedback that the creation of the measurement task fails and the process ends.

[0200] The above step S404a is optional (indicated by a dotted line in the figure). After verifying that the calculation formula of the identifier and communication efficiency data is invalid, the network management service providing entity can directly end the process, and the network management service consuming entity will consider that the creation of the measurement task has failed.

[0201] S404b. If the verification is valid, the network management service providing entity feeds back to the network management service consuming entity that the measurement task creation is successful.

[0202] The above step S404b is optional (indicated by a dotted line in the figure). After the network management service providing entity verifies that the identifier and the calculation formula of the communication efficiency data are valid, the network management service consuming entity considers that the creation of the measurement task is successful.

[0203] S405. The network management service providing entity checks whether there is a data collection task for the first calculation factor and the second calculation factor in the first calculation formula.

[0204] When the above request message is used to request energy efficiency data, the first calculation factor indicates the service measurement data associated with the network element set, and the second calculation factor indicates the energy consumption data associated with the network element set; when the above request message is used to request carbon efficiency data, the first calculation factor indicates the service measurement data associated with the network element set, and the second calculation factor indicates the carbon emission data associated with the network element set. Since the first calculation factor and the second calculation factor both indicate data associated with the network element set, after receiving the request message, the network management service provider entity needs to verify whether there is a data collection task for the first calculation factor and the second calculation factor in the first calculation formula, that is, whether the corresponding data needs to be obtained from the network element set.

[0205] If the network management service provider verifies that it has collected data indicated by the first calculation factor and / or the second calculation factor after receiving the request message, it is determined that there is no data collection task. For example, the digital twin of the network management service provider periodically or irregularly obtains data from the physical network. Therefore, after receiving the request message, the network management service provider can verify that it has collected data indicated by the first calculation factor and the second calculation factor included in the first calculation formula.

[0206] If the network management service providing entity receives the request message and checks that it has not previously collected the data indicated by the first calculation factor and the second calculation factor included in the first calculation formula, it determines that there is a data collection task.

[0207] S406a. If there is a data collection task, the network management service providing entity requests the network element to obtain data indicated by the first calculation factor and / or the second calculation factor.

[0208] If there is a data collection task for the first calculation factor and / or the second calculation factor in the first calculation formula, the network management service providing entity can send a collection request to the corresponding network element set to request the data indicated by the first calculation factor and / or the second calculation factor.

[0209] When the network management service provider determines that a data collection task exists, the network management service provider may selectively perform the following steps S407a or S407b based on whether the data indicated by the first calculation factor and / or the second calculation factor can be obtained on time:

[0210] S407a. The network element set sends the collected real-time data to the network management service provider entity.

[0211] After receiving the above collection request, the network element collects service metric data and / or cost data in real time, and sends the collected real-time data to the network management service providing entity.

[0212] The real-time data includes business metric data and / or cost data.

[0213] The service measurement data is real-time data collected from a set of network elements.

[0214] The cost data includes any one of energy consumption data and carbon emission data. The energy consumption data is real-time data collected from a set of network elements, or the carbon emission data is real-time data collected from a set of network elements.

[0215] S407b. The network management service provider obtains prediction data using the prediction model.

[0216] When the network management service provider entity is unable to obtain business measurement data and / or cost data from the network element set on time (for example, the data processing capability of the network element set is weak or it is performing other tasks), or the digital twin of the network management service provider entity has good prediction capabilities, in order to ensure the timeliness and accuracy of the feedback of communication efficiency data, or to reduce communication overhead, data prediction capabilities are introduced into the network management service provider entity.

[0217] The network management service provider can utilize a prediction model to obtain prediction data based on historical service measurement data associated with the network element set. The service measurement data is prediction data obtained based on historical service measurement data associated with the network element set. The network management service provider can utilize a prediction model to obtain prediction data based on cost data associated with the network element set. The cost data includes either energy consumption data or carbon emission data. The energy consumption data is prediction data obtained based on historical energy consumption data associated with the network element set. The carbon emission data is prediction data obtained based on historical carbon emission data associated with the network element set.

[0218] The above-mentioned carbon emission data can also be obtained based on energy consumption data. The energy consumption data can be real-time data collected from the network element set, or predicted data obtained based on historical energy consumption data associated with the network element set. Specifically, the carbon emission amount can be equal to the energy consumption data multiplied by the carbon emission factor. The specific carbon emission factor can be calculated based on the proportion of non-green energy used in the communication system and the proportion of specific non-green energy power generation materials used (such as coal-fired power generation, oil-fired power generation, etc.).

[0219] Exemplarily, the network management service provider may obtain predicted data by acquiring historical service metric data associated with the set of network elements within a first time period, and may also obtain predicted data by acquiring historical cost data associated with the set of network elements within the first time period. That is, the first calculation factor and the second calculation factor correspond to data for the same time period (e.g., the first time period).

[0220] The network management service provider entity is unable to obtain the business measurement data associated with the network element set and / or the cost data associated with the network element set from the network element set on time. For example, the network management service provider entity sends a collection request to the network element set and starts a timer when sending the collection request. If the timer expires and no data returned by the network element set is received, the prediction model can be used to obtain the predicted data.

[0221] S408. The network management service providing entity calculates the communication efficiency data according to the first calculation formula and the acquired service metric data and cost data.

[0222] After the network management service providing entity obtains the data indicated by the first calculation factor and the second calculation factor, it can substitute the data indicated by the first calculation factor and the second calculation factor into the first calculation formula to calculate and obtain the communication efficiency data.

[0223] The request message may request to obtain multiple communication rate data. For each communication efficiency data to be obtained, the steps S405 to S408 are executed cyclically.

[0224] S409. The network management service providing entity sends the communication efficiency data obtained based on the first calculation formula to the network management service consuming entity. Correspondingly, the network management service consuming entity receives the communication efficiency data.

[0225] After the network management service providing entity calculates the communication efficiency data, it sends the communication efficiency data to the network management service consuming entity.

[0226] It can be understood that if the existing measurement category list or user-defined measurement list of the above request message carries multiple identifiers, that is, the network management service consumption entity requests to measure multiple communication efficiency data, then multiple identifiers and the communication efficiency data corresponding to each identifier can be sent, and the identifier is also used to identify the communication efficiency data.

[0227] Furthermore, the network management service provider can store the identifier and the first calculation formula locally or on a third-party server. If the network management service consumer requests the communication efficiency data again, it can include the identifier in the request message instead of the first calculation formula. The network management service provider can then search for the first calculation formula corresponding to the identifier locally or on a third-party server based on the identifier in the request message. This reduces request message overhead.

[0228] Furthermore, the network management service provider entity may store the above-mentioned identifier and the first calculation formula locally or on a third-party server. If the network management service consumer entity requests to obtain the communication efficiency data again, and the calculation formula of the communication efficiency data is updated, the second calculation formula carrying the identifier and the update may be selected in the request message. After receiving the request message, the network management service provider entity searches for the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity according to the identifier in the request message, and checks that the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity is partially or completely different from the second calculation formula carried in the request message. The network management service provider entity then uses the second calculation formula carried in the request message to update the first calculation formula corresponding to the identifier stored locally or on a third-party server of the network management service provider entity.

[0229] The network management service providing entity uses the updated second calculation formula carried in the request message to obtain the data indicated by the third calculation factor and the fourth calculation factor included in the second calculation formula, performs calculations, obtains communication efficiency data, and returns the data to the network management service consuming entity. The third calculation factor indicates service metric data associated with the network element set, and the fourth calculation factor indicates cost data associated with the network element set.

[0230] According to a data acquisition method provided by an embodiment of the present application, a network management service consuming entity can send a calculation formula for communication efficiency data to a network management service providing entity. The network management service providing entity can then obtain communication efficiency data based on the calculation formula for communication efficiency data provided by the network management service consuming entity and send the communication efficiency data to the network management service consuming entity. Thus, communication efficiency data can be flexibly acquired based on the needs of the network management service consuming entity, and is not limited to the communication efficiency defined by the standard.

[0231] The business metric data indicated by the first calculation factor can be real-time data collected from the network element set, or it can be predicted data obtained based on the business metric historical data associated with the network element set; the cost data indicated by the second calculation factor can be real-time data collected from the network element set, or it can be predicted data obtained based on the cost historical data associated with the network element set. When the network management service provider entity is unable to obtain the data indicated by the first calculation factor and / or the second calculation factor from the network element set on time (for example, the data processing capability of the network element set is weak or it is performing other tasks), or the digital twin of the network management service provider entity has good prediction capabilities, in order to ensure the timeliness and accuracy of the feedback of the communication efficiency data, or to reduce communication overhead, the prediction function of the network management service provider entity can be utilized, and the predicted data can be obtained based on the business metric historical data associated with the network element set, and / or the predicted data can be obtained based on the cost historical data associated with the network element set. Thereby, the timeliness and accuracy of the feedback of the communication efficiency data can be guaranteed.

[0232] It can be understood that in each of the above embodiments, the methods and / or steps implemented by the network management service providing entity can also be implemented by components (such as chips or circuits) that can be used for the network management service providing entity; the methods and / or steps implemented by the network management service consuming entity can also be implemented by components (such as chips or circuits) that can be used for the network management service consuming entity.

[0233] The above description primarily describes the solutions provided by the embodiments of the present application from the perspective of interactions between various entities. Accordingly, the embodiments of the present application also provide a data acquisition device, which is used to implement the various methods described above. The data acquisition device can be a network management service provider entity in the above method embodiments, or a component that can be used by a network management service provider entity; alternatively, the data acquisition device can be a network management service consumer entity in the above method embodiments, or a component that can be used by a network management service consumer entity. It will be understood that, to implement the aforementioned functions, the data acquisition device includes hardware structures and / or software modules corresponding to each function. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0234] In the embodiment of the present application, the data acquisition device can be divided into functional modules according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0235] Based on the same concept of the above data acquisition method, this application also provides the following data acquisition device:

[0236] As shown in FIG5 , it is a structural diagram of a data acquisition device provided in an embodiment of the present application. The data acquisition device 5000 includes a transceiver unit 501 and a processing unit 502 ; wherein:

[0237] When the data acquisition device is used to implement the functions of the network management service providing entity in the above-mentioned method embodiment, the transceiver unit 501 is used to execute the functions of the network management service providing entity in steps S301 and S302 in the embodiment as shown in Figure 3; or, the transceiver unit 501 is used to execute the functions of the network management service providing entity in steps S402, S404a, S404b, S406a, S407a and S409 in the embodiment as shown in Figure 4, and the processing unit 502 is used to execute steps S403, S405, S407b and S408 in the embodiment as shown in Figure 4.

[0238] When the data acquisition device is used to implement the functions of the network management service consumption entity in the above-mentioned method embodiment, the transceiver unit 501 is used to execute the functions of the network management service consumption entity in steps S301 and S302 in the embodiment as shown in Figure 3; or, the transceiver unit 501 is used to execute the functions of the network management service consumption entity in steps S402, S404a, S404b and S409 in the embodiment as shown in Figure 4, and the processing unit 502 is used to execute step S401 in the embodiment as shown in Figure 4.

[0239] For the specific implementation of the above-mentioned transceiver unit 501 and the processing unit 502, reference may be made to the description in the above-mentioned method embodiment, which will not be repeated here.

[0240] As shown in Figure 6, a schematic diagram of the structure of another data acquisition device provided in an embodiment of the present application is provided. The data acquisition device 6000 includes a processor 601 and may also include an interface circuit 602 and a memory 603 (represented by dotted lines in the figure). The processor 601 and the interface circuit 602 are coupled to each other. It will be understood that the interface circuit 602 can be a transceiver or an input / output interface. The memory 603 is used to store instructions executed by the processor 601, or to store input data required by the processor 601 to execute instructions, or to store data generated after the processor 601 executes instructions.

[0241] In which, when the data acquisition device is used to implement the functions of the network management service providing entity in the above-mentioned method embodiment, the interface circuit 602 is used to execute the functions of the network management service providing entity in steps S301 and S302 in the embodiment as shown in Figure 3; or, the interface circuit 602 is used to execute the functions of the network management service providing entity in steps S402, S404a, S404b, S406a, S407a and S409 in the embodiment as shown in Figure 4, and the processor 601 is used to execute steps S403, S405, S407b and S408 in the embodiment as shown in Figure 4.

[0242] When the data acquisition device is used to implement the functions of the network management service consumption entity in the above-mentioned method embodiment, the interface circuit 602 is used to execute the functions of the network management service consumption entity in steps S301 and S302 in the embodiment as shown in Figure 3; or, the interface circuit 602 is used to execute the functions of the network management service consumption entity in steps S402, S404a, S404b and S409 in the embodiment as shown in Figure 4, and the processor 601 is used to execute step S401 in the embodiment as shown in Figure 4.

[0243] When the data acquisition device is a chip used in a network management service provider, the chip implements the functions of the network management service provider in the above method embodiments. The chip receives information from other modules (such as a radio frequency module or antenna) in the network management service provider, where the information is sent by the network management service consumer to the network management service provider; or the chip sends information to other modules (such as a radio frequency module or antenna) in the network management service provider, where the information is sent by the network management service provider to the network management service consumer.

[0244] When the data acquisition device is a chip used in a network management service consuming entity, the chip implements the functions of the network management service consuming entity in the above method embodiments. The chip receives information from other modules (such as a radio frequency module or antenna) in the network management service consuming entity, where the information is sent by the network management service providing entity to the network management service consuming entity; or the chip sends information to other modules (such as a radio frequency module or antenna) in the network management service consuming entity, where the information is sent by the network management service consuming entity to the network management service providing entity.

[0245] In addition, it should be noted that the aforementioned transceiver unit and / or processing unit may be implemented through virtual modules, for example, the processing unit may be implemented through a software function unit or a virtual device, and the transceiver unit may be implemented through a software function or a virtual device. Alternatively, the processing unit or transceiver unit may also be implemented through a physical device, for example, if the device is implemented using a chip / chip circuit, the transceiver unit may be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing unit is an integrated processor or microprocessor or integrated circuit.

[0246] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single processor, exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in either hardware or software functional modules.

[0247] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0248] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed, the method in the above embodiment is implemented.

[0249] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment.

[0250] An embodiment of the present application further provides a data acquisition system, comprising the above-mentioned data acquisition device.

[0251] The present application also provides a circuit, which is coupled to a memory and is used to execute the method shown in the above embodiment. The circuit may include a chip circuit.

[0252] It should be noted that the above units or one or more of the units can be implemented by software, hardware, or a combination of the two. When any of the above units or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow.

[0253] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.

[0254] The processor can be built into a system on chip (SoC) or ASIC, or it can be a standalone semiconductor chip. In addition to the core that executes software instructions to perform calculations or processing, the processor can also include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement specialized logic operations.

[0255] When the above units or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0256] Optionally, an embodiment of the present application further provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the chip system executes the method in any of the above method embodiments. Optionally, the chip system may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0257] In the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0258] The following "at least one" in this application refers to one or more items. "Multiple" refers to two or more items. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated with each other are in an "or" relationship. In addition, it should be understood that although the terms "first", "second", etc. may be used to describe each object in this application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other. The terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, features defined as "first", "second", etc. may explicitly or implicitly include one or more of these features. In the description of this application, unless otherwise specified, the meaning of "multiple" is two or more.

[0259] The terms "including" and "having" and any variations thereof mentioned in the following description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any method or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0260] The following specific embodiments illustrate the implementation of the present application. Those skilled in the art can understand other advantages and effects of the present application from the contents disclosed in this specification. Although the description of the present application will be introduced in conjunction with the preferred embodiment, this does not mean that the features of this application are limited to this implementation. On the contrary, the purpose of introducing the application in conjunction with the implementation is to cover other options or modifications that may be extended based on the claims of the present application. In order to increase the in-depth understanding of the present application, the following description will contain many specific details. The present application can also be implemented without using these details. In addition, in order to avoid confusion or blurring the focus of the present application, some specific details will be omitted in the description. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other unless there is a conflict.

[0261] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0262] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0263] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0264] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0265] The components in the device of the embodiment of the present application can be merged, divided, or deleted according to actual needs. Those skilled in the art can combine or combine the different embodiments and features of the different embodiments described in this specification.

[0266] The above embodiments are intended only to illustrate the technical solutions of the present application and are not intended to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they may still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein with equivalents; and such modifications or replacements do not deviate from the essence of the corresponding technical solutions within the scope of the technical solutions of the embodiments of the present application.

[0267] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

[0268] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A data acquisition method, characterized in that: The method comprises: Sending a request message, the request message comprising a first calculation formula for calculating communication efficiency data of a network element set, the first calculation formula comprising a first calculation factor and a second calculation factor, the first calculation factor indicating service metric data associated with the network element set, the second calculation factor indicating cost data associated with the network element set, the network element set comprising at least one communication network element; Receive communication efficiency data of the network element set obtained based on the first calculation formula.

2. The method according to claim 1, characterized in that The communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

3. The method according to claim 1 or 2, characterized in that The cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

4. The method according to claim 1 or 2, characterized in that: The cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

5. The method according to claim 4, characterized in that The carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

6. The method according to claim 3 or 5, characterized in that The energy consumption data is real-time data collected from the network element set, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the network element set.

7. The method according to any one of claims 1 to 6, characterized in that: The service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on service measurement historical data associated with the network element set.

8. The method according to any one of claims 1 to 7, characterized in that: The request message also includes an identifier of at least one communication network element in the set of network elements.

9. The method according to any one of claims 1 to 8, characterized in that: The request message also includes an identifier corresponding to the first calculation formula.

10. The method according to claim 9, characterized in that The method further comprises: The identifier and / or the first calculation formula is obtained based on user input.

11. The method according to claim 10, characterized in that The method further comprises: The first calculation factor and / or the second calculation factor are presented for selection by the user.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: Receive the first calculation factor and / or the second calculation factor from an operation, maintenance and management (OAM) server or a third-party server; or, The first calculation factor and / or the second calculation factor is obtained from a configuration file.

13. The method according to any one of claims 9 to 12, characterized in that: The identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

14. A data acquisition method, characterized in that: The method comprises: receiving a request message, the request message comprising a first calculation formula for calculating communication efficiency data of a set of network elements, the first calculation formula comprising a first calculation factor and a second calculation factor, the first calculation factor indicating service metric data associated with the set of network elements, the second calculation factor indicating cost data associated with the set of network elements, the set of network elements comprising at least one communication network element; In response to the request message, the communication efficiency data of the network element set calculated based on the first calculation formula is sent.

15. The method according to claim 14, characterized in that The communication efficiency data is related to a ratio of the first calculation factor to the second calculation factor.

16. The method according to claim 14 or 15, characterized in that The cost data is energy consumption data, and the communication efficiency data is energy efficiency data.

17. The method according to claim 14 or 15, characterized in that The cost data is carbon emission data, and the communication efficiency data is carbon efficiency data.

18. The method according to claim 17, characterized in that The carbon emission data is real-time data collected from the network element set, or the carbon emission data is predicted data obtained based on historical carbon emission data associated with the network element set, or the carbon emission data is obtained based on energy consumption data.

19. The method according to claim 16 or 18, characterized in that The energy consumption data is real-time data collected from the network element set, or the energy consumption data is predicted data obtained based on historical energy consumption data associated with the network element set.

20. The method according to any one of claims 14 to 19, characterized in that: The service measurement data is real-time data collected from the network element set, or the service measurement data is predicted data obtained based on service measurement historical data associated with the network element set.

21. The method according to any one of claims 14 to 20, characterized in that: The request message also includes an identifier of at least one communication network element in the set of network elements.

22. The method according to any one of claims 14 to 21, characterized in that: The method further comprises: Analyze the first calculation formula; Verify the first calculation formula.

23. The method of claim 22, wherein: The first calculation formula further includes an operator, and the operator is used to calculate the first calculation factor and the second calculation factor; The verifying the first calculation formula includes at least one of the following operations: Check whether the first calculation factor and the second calculation factor meet the definition of the standard; or Checks that the operator complies with the definition in the standard.

24. The method according to any one of claims 14 to 23, characterized in that: The request message also includes an identifier corresponding to the first calculation formula.

25. The method of claim 24, wherein: The method further comprises: Check whether the identifier is a duplicate of an identifier defined in the standard.

26. The method according to claim 24 or 25, characterized in that The identifier also corresponds to a second calculation formula used to calculate the communication efficiency data of the network element set, and the request message is used to request to replace the second calculation formula with the first calculation formula.

27. A data acquisition method, characterized in that: The method comprises: The network management service consumption entity sends a request message to the network management service provision entity, the request message including a first calculation formula for calculating communication efficiency data of a network element set, the first calculation formula including a first calculation factor and a second calculation factor, the first calculation factor indicating service metric data associated with the network element set, the second calculation factor indicating cost data associated with the network element set, the network element set including at least one communication network element; The network management service providing entity sends, in response to the request message, the communication efficiency data of the network element set calculated based on the first calculation formula to the network management service consuming entity.

28. A data acquisition device, characterized in that: The apparatus comprises modules for implementing the method according to any one of claims 1-26.

29. A data acquisition device, characterized in that: The device comprises a processor, a memory, and instructions stored in the memory and executed on the processor, wherein when the instructions are executed, the data acquisition device executes the method according to any one of claims 1 to 26.

30. A data acquisition system, characterized in that: It comprises a network management service providing entity and a network management service consuming entity, wherein the network management service providing entity comprises a module for executing the method according to any one of claims 1-13, and the network management service consuming entity comprises a module for implementing the method according to any one of claims 14-26.

31. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises instructions, which, when executed by a processor, enable the method according to any one of claims 1 to 27 to be implemented.

32. A computer program product, characterized in that The computer program product comprises program instructions, and when the program instructions are executed, the method according to any one of claims 1 to 27 is implemented.

Images