Data acquisition method and related apparatus

Abstract

Provided in the present application are a data acquisition method and a related apparatus, which are applied to the technical field of communications. In the present method, a required data type and simulation data of a collection object can be quickly and flexibly provided in response to a data request from a second functional entity, thereby enriching data collection channels in a service-oriented management architecture. Moreover, a request including information, such as an instance identifier, a data type, a collection object or a collection requirement, is sent to a third functional entity that generates simulation data, such that the third functional entity can accurately locate and collect simulation data in a specific instance, thereby meeting customization requirements. In addition, in the present application, a label and data are sent together, such that a receiver precisely distinguishes between simulation data and live network data, thereby enabling the receiver to accurately and efficiently process the data.

Description

Data acquisition method and related apparatus

[0001] The present application claims priority to the Chinese patent application No. 202410718346.9, filed on June 4, 2024, with the State Intellectual Property Office of China, and entitled "Data acquisition method and related apparatus", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication, in particular to a data acquisition method and related apparatus. BACKGROUND

[0003] The 3rd generation partnership project (3GPP) standard proposes a service-based management architecture (SBMA). Among them, the management function (MnF) entity is the basic unit of the SBMA architecture. MnF is a logical entity that provides specific management tasks or functions, and the management capabilities it provides externally are called management services (MnS). MnF can act as a management service producer to provide the MnS it provides to management service consumers. MnS needs to collect a large amount of data in some services, and in the existing technology, these data come from the existing network.

[0004] Exemplarily, MnS includes management data analytics (MDA), which can provide processing and analysis-related reports for network and service operation to achieve normal operation of network and service operation. In network service management, MDA can help perform management tasks in preparation, debugging, operation, and termination stages, for example, MDA can predict network and service demand based on artificial intelligence to achieve timely resource allocation and deployment, thereby achieving rapid network and service deployment.

[0005] However, the model for making predictions requires a large amount of data in the training stage, and these data come from the network elements of the existing network. The amount of data that the network elements of the existing network can provide is relatively fixed, and there may be a situation that the large amount of data required for model training cannot be supported, thereby causing inaccurate prediction of network and service demand by MDA. SUMMARY

[0006] The application provides a data acquisition method and related device, which can establish a new data acquisition channel for a service-oriented management architecture, improve the richness of acquired data, and further improve the accuracy of MDA prediction of network and service demand.

[0007] In a first aspect, a data acquisition method is provided, which is applied to a first function entity and includes:

[0008] receiving first request information from a second function entity, the first request information being used to request collection of simulation data, the first request information including a data type and a collection object; sending second request information to a third function entity according to the first request information, the second request information being used to request simulation data of the data type about the collection object; receiving first simulation data of the data type about the collection object from the third function entity; and sending the first simulation data to the second function entity.

[0009] In the embodiments of the application, the second function entity can be a management function entity MnF, and exemplarily, the second function entity is a cross-domain management system (NMS) in the management function entity, or a module / component in the NMS. The second function entity is a management service consumer, and has a demand for data collection. It should be noted that the second function entity can also be a third-party management service consumer, i.e., the second function entity can be a business support system (BSS). The first function entity is a device / system for data collection, and the third function entity is a device / system for providing simulation data. It should be noted that the first function entity and the third function entity can also be management function entities MnF, for example, the first function entity and the third function entity can be element management systems (EMSs). If the first function entity and the third function entity are both element management systems, the first function entity and the third function entity can be two modules / components of the same system. Optionally, the third function entity can be a network digital twin (NDT) related device.

[0010] The second function entity interacts with the first function entity through the first request information to request the first function entity to collect data satisfying the requirement of the first request information, the data being about the collection object, the data satisfying the data type, and the collection object being exemplarily a specified network element, i.e., the simulation data is simulation data of the specified network element, and the data type being a kind or name of the collected data, such as Utilization, latency, etc. Further, the first function entity interacts with the third function entity through the second request information to request the simulation data satisfying the requirement of the first request information. This mechanism can also enable the data request to be responded and satisfied in time, and improve the response speed and accuracy of the data service.

[0011] In the embodiment, the first function entity establishes a perfect data collection channel between the second function entity and the third function entity, which is different from the current data collection channel of the live network, and helps the management service consumer to obtain the simulation data, improves the diversification of the data collection channel in the SBMA and the richness of the collected data, and further improves the accuracy of the prediction of the network and service demand of the MDA. Since the first function entity is responsible for the acquisition and forwarding of the simulation data, it can collect data according to the request of the second function entity, reduce unnecessary data transmission and processing, and thus improve the efficiency of data collection.

[0012] In another optional implementation of the first aspect, the first request information further includes first indication information, the first indication information being used to indicate that the collected data is simulation data, or used to indicate that the collected data includes simulation data.

[0013] In the embodiment, the first indication information is a new parameter, and is used to indicate whether the data collected by the management service consumer is only simulation data or multiple kinds of data including simulation data. This represents that the data requested by the management service consumer is in multiple cases, but in any case, the first request information can indicate the requirement of the first function entity through the first indication information.

[0014] In another optional implementation of the first aspect, the first request information is further used to request real data.

[0015] In the embodiment, the first request information is used to explicitly indicate that the collected data includes both simulation data and real data, and satisfies the requirement of the service consumer for mixed data types. The embodiment can simultaneously acquire simulation data and real data, and provides more comprehensive and accurate data support for data analysis and service, and improves the diversity and accuracy of the data service.

[0016] In a further alternative implementation of the first aspect, the first request information further comprises second indication information, the second indication information being used to indicate collection of data including the simulation data and the real data.

[0017] The first and second indication information are used to indicate the collection requirements of the simulation data and the real data respectively, so that the service consumer can explicitly express its requirements for different types of data. The implementation also improves the pertinence and accuracy of data collection, reduces unnecessary data transmission and processing, and improves the efficiency of data collection.

[0018] In a further alternative implementation of the first aspect, the method further comprises: sending third request information to the in-network network element, the third request information being used to request collection of real data of the data type of the collection object; receiving first real data of the data type of the collection object from the in-network network element; and sending the first real data to the second functional entity.

[0019] In the implementation, the first real data is in-network data, and the collection object and the data type corresponding to the first real data are the same as those corresponding to the simulation data. The difference between the first real data and the simulation data is that the first real data is actually obtained from the collection object, while the simulation data is generated by simulating the data of the collection object.

[0020] In a further alternative implementation of the first aspect, the first request information further comprises proportion information, the proportion information being used to represent the proportion of the real data and the simulation data, and the sending of the second request information to the third functional entity comprises: determining the number of simulation data to be collected according to the number of the first real data and the proportion information; and sending the second request information to the third functional entity, the second request information comprising the number of simulation data to be collected.

[0021] The implementation determines the number of simulation data to be collected according to the number of real data and the proportion information, so that the collected simulation data and real data maintain a certain proportional relationship in quantity. The proportional relationship includes a minimum proportion requirement or a maximum proportion requirement.

[0022] In a further alternative implementation of the first aspect, the first request information further comprises third indication information, the third indication information being used to indicate that the first label is fed back through the response information of the first request information, the first label being used to represent the simulation data, and the method further comprises: receiving the first label from the third functional entity; and sending the first simulation data to the second functional entity, comprising: sending the response information to the second functional entity, the response information comprising the first simulation data and the first label.

[0023] The embodiment enables the management service consumer to clearly identify whether the received data is simulation data or real data by including the first label representing the simulation data in the response information related to the first request information. The embodiment improves the transparency and accuracy of data services, and helps the management service consumer (the first function entity) to better utilize and analyze data after distinguishing real data from simulation data. Optionally, the first label can be generated by the third function entity before returning the simulation data.

[0024] In yet another optional implementation of the first aspect, the first request information further includes third indication information, the third indication information being used to indicate that the first label is fed back through the response information of the first request information, the first label being used to represent the simulation data, and the method further includes: generating the first label; and sending the first simulation data to the second function entity, including: sending the response information to the second function entity, the response information including the first simulation data and the first label.

[0025] In the embodiment, the first label is generated by the first function entity.

[0026] In yet another optional implementation of the first aspect, sending the second request information to the third function entity according to the first request information includes: determining a first instance identifier according to the collection object, the first instance identifier being used to indicate a first instance of the collection object included in the third function entity; and sending the second request information to the third function entity, the second request information including the first instance identifier.

[0027] The embodiment enables the third function entity to accurately identify and process the request by determining the first instance identifier and including the identifier in the request, thereby improving the accuracy and efficiency of data collection. The embodiment reduces data errors and losses caused by data mismatching or misoperation.

[0028] In yet another optional implementation of the first aspect, the first request information further includes collection requirement information of the simulation data, and the second request information further includes the collection requirement information of the simulation data.

[0029] In the embodiment, if the first request information carries the collection requirement information of the simulation data, the first function entity also carries the collection requirement information of the simulation data in the second request information when sending the second request information to the third function entity, so that the third function entity performs data collection according to the collection requirement information of the simulation data.

[0030] In a further alternative implementation of the first aspect, the collection requirement information of the simulation data comprises one or more of a time window, data distribution information, a collection time length, or a quantity of the simulation data, the time window is used to represent collection of data in a specified time period, the data distribution information is used to represent distribution characteristics of the collected data, and the collection time length is used to represent a time length of collection of the simulation data.

[0031] The detailed collection requirement information of the simulation data in the implementation enables the third function entity to collect and process data in a targeted manner according to the requirements. The implementation improves the targeting and accuracy of data collection, and meets the requirements of the service consumer for specific data. Further, if the collection requirement information of the simulation data comprises a quantity of the simulation data, it means that the quantity of the simulation data to be collected is directly specified, so that the third function entity can accurately collect data according to the requirements. The implementation improves the accuracy and efficiency of data collection, and reduces unnecessary data transmission and processing.

[0032] In a further alternative implementation of the first aspect, the method further comprises: receiving fourth indication information from the third function entity, the fourth indication information being used to indicate that the third function entity supports collection of the simulation data, the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of a data type, a collection object, and a time window; and sending the fourth indication information to the second function entity.

[0033] In the implementation, the fourth indication information occurs before the second function entity sends the first request information, and the fourth indication information is information reported by the third function entity, so that the first function entity can be aware that the third function entity currently supports collection of the simulation data and the target parameters of the simulation data that can be provided. It can be understood that the data type included in the first request information is one or more of the data types in the plurality of target parameters, the collection object included in the first request information is one or more of the collection objects in the plurality of target parameters, and if the time window is included in the first request information, the time window included in the first request information is one or more of the time windows in the plurality of target parameters.

[0034] The first function entity in the implementation receives and forwards the data type and the collection object and other information provided by the third function entity, so that the second function entity can be aware of and select data suitable for its requirements for collection. The implementation enhances the flexibility and scalability of data services, and meets the requirements of the service consumer for diversified data.

[0035] In a further alternative implementation of the first aspect, the first functional entity is an element management system, EMS, a network management system, NMS, a network element in a radio access network, or a network element in a core network; the second functional entity is a business support system, BSS, or a network management system, NMS; and the third functional entity is an element management system, EMS, a network management system, NMS, a network element in a radio access network, or a network element in a core network.

[0036] The present implementation specifies the specific types of the respective functional entities, making the overall data acquisition method more specific and explicit. The present implementation facilitates better deployment and implementation of the method in practical applications, improving the reliability and stability of data services.

[0037] In a second aspect, a data acquisition method is provided, which is applied to a second functional entity and includes: sending first request information to a first functional entity, the first request information being used to request acquisition of simulation data, the first request information including a data type and an acquisition object; and receiving first simulation data from the first functional entity, the first simulation data being simulation data of the data type about the acquisition object.

[0038] The present implementation enables the second functional entity to actively request and acquire simulation data of a specific type and object, without waiting for active pushing of data, improving the initiative and flexibility of data acquisition. At the same time, direct acquisition of simulation data also facilitates rapid data analysis and decision-making by the second functional entity, improving work efficiency.

[0039] In a further alternative implementation of the second aspect, the first request information further includes first indication information, the first indication information being used to indicate acquisition of simulation data, or being used to indicate acquisition of data including simulation data.

[0040] The present implementation explicitly expresses the demand of the second functional entity for simulation data through the first indication information, enabling the first functional entity to accurately understand and meet this demand. This helps to reduce misunderstanding and redundancy of data transmission, improving the accuracy and efficiency of data services.

[0041] In a further alternative implementation of the second aspect, the first request information is further used to request real data.

[0042] In a further alternative implementation of the second aspect, the first request information further includes second indication information, the second indication information being used to indicate acquisition of data including simulation data and real data.

[0043] In a further alternative implementation of the second aspect, the method further includes:

[0044] receiving first real data from the first functional entity.

[0045] In a further possible implementation form of the second aspect, the first request information further comprises third indication information, the third indication information being configured to instruct the first function entity to feed back a first label via response information of the first request information, the first label being configured to represent the simulation data; and receiving the first simulation data from the first function entity comprises: receiving the response information from the first function entity, the response information comprising the first simulation data and the first label.

[0046] In a further possible implementation form of the second aspect, the first request information further comprises collection requirement information of the simulation data.

[0047] In a further possible implementation form of the second aspect, the collection requirement information of the simulation data comprises one or more of a time window, data distribution information or a collection time length, the time window being configured to represent data collected in a specified time period, the data distribution information being configured to represent distribution characteristics of the collected data, and the collection time length being configured to represent a time length for collecting the simulation data; and the first request information further comprises proportion information, wherein the proportion information is configured to represent a proportion of real data and simulation data.

[0048] In this implementation form, the second function entity can directly specify the number of simulation data to be collected via the collection requirement information of the simulation data carried by the first request information, which helps to ensure the accuracy and completeness of data collection.

[0049] In a further possible implementation form of the second aspect, the method further comprises: receiving fourth indication information, the fourth indication information being configured to instruct the third function entity to support simulation data collection, the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of a data type, a collection object and a time window; and determining the target parameters of the simulation data to be collected according to the plurality of target parameters comprised in the fourth indication information.

[0050] This implementation form enables the second function entity to explicitly determine that the third function entity currently supports simulation data collection according to the fourth indication information provided by the first function entity / third function entity, and helps the first function entity to autonomously determine the parameters and range of data collection, thereby improving the autonomy and flexibility of data services. At the same time, this also helps to reduce the redundancy and misunderstanding of data transmission, thereby improving the accuracy and efficiency of data processing. It should be noted that the fourth indication information can be sent from the third function entity to the first function entity, or directly sent from the third function entity to the second function entity.

[0051] In a further alternative implementation form of the second aspect, the first functional entity is an element management system, EMS, a network management system, NMS, an element in a radio access network or an element in a core network; the second functional entity is a business support system, BSS, or a network management system, NMS; and the third functional entity is an element management system, EMS, a network management system, NMS, an element in a radio access network or an element in a core network.

[0052] In a third aspect, a data acquisition method is provided, the method being applied to a third functional entity, the method comprising: receiving second request information from a first functional entity, the second request information being used to request simulation data of a data type of a collection object; and sending first simulation data of the data type of the collection object according to the second request information.

[0053] With the implementation, the third functional entity can provide simulation data of a specific collection object and data type in response to a request from the first functional entity. With the implementation, the flexibility and response speed of the data service are enhanced, so that the first functional entity and the second functional entity can acquire required data resources in time and meet their service requirements.

[0054] In a further alternative implementation form of the third aspect, the second request information comprises a first instance identifier, and the method further comprises:

[0055] The first simulation data is obtained by collecting simulation data of the data type of the collection object in the first instance corresponding to the first instance identifier.

[0056] In the implementation of the present application, the first instance identifier is determined by the first functional entity.

[0057] In a further alternative implementation form of the third aspect, the second request information comprises a data type and a collection object, and the method further comprises: determining a first instance according to the collection object; and obtaining the first simulation data by collecting simulation data of the data type of the collection object in the first instance.

[0058] In the implementation of the present application, the first instance identifier is determined by the third functional entity.

[0059] In a further alternative implementation form of the third aspect, the second request information further comprises collection requirement information of the simulation data, and the first simulation data meets a requirement corresponding to the collection requirement information.

[0060] In a further alternative implementation form of the third aspect, the collection requirement information of the simulation data comprises one or more of a time window, data distribution information, a collection time length and a quantity of the simulation data, the time window being used to represent data collected in a specified time period, the data distribution information being used to represent distribution characteristics of the collected data, and the collection time length being used to represent a time length for collecting the simulation data.

[0061] In a further alternative implementation form of the third aspect, the second request information further comprises a number of simulation data requested to be collected.

[0062] In a further alternative implementation form of the third aspect, transmitting the first simulation data on the data type of the collection object according to the second request information comprises: transmitting the first simulation data on the data type of the collection object and a first label, the first label being used to represent the simulation data.

[0063] In the implementation forms of the present application, the first label is used to enable the second functional entity (managing service consumers) to distinguish between simulation data and live network data.

[0064] In a further alternative implementation form of the third aspect, the method further comprises:

[0065] transmitting fourth indication information to the first functional entity, the fourth indication information being used to indicate that the third functional entity supports simulation data collection, the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of: a data type, a collection object, a time window.

[0066] In a further alternative implementation form of the third aspect, the method further comprises:

[0067] transmitting fourth indication information to the second functional entity, the fourth indication information being used to indicate that the third functional entity supports simulation data collection, the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of: a data type, a collection object, a time window.

[0068] In a further alternative implementation form of the third aspect, the first functional entity is an element management system EMS, a network management system NMS, an element in a radio access network or an element in a core network; the second functional entity is a business support system BSS or a network management system NMS; and the third functional entity is an element management system EMS, a network management system NMS, an element in a radio access network or an element in a core network.

[0069] A fourth aspect provides a communication apparatus, comprising:

[0070] a first communication unit configured to receive first request information from a second functional entity, the first request information being used to request simulation data, the first request information comprising a data type and a collection object;

[0071] the first communication unit is further configured to transmit second request information to a third functional entity according to the first request information, the second request information being used to request simulation data on the data type of the collection object;

[0072] The first communication unit is further configured to receive first simulation data of the data type of the collection object from the third function entity.

[0073] The first communication unit is further configured to send the first simulation data to the second function entity.

[0074] The apparatus is configured to implement the method of the first aspect or any of the embodiments of the first aspect.

[0075] In a fifth aspect, a communication apparatus is provided, comprising:

[0076] The second communication unit is configured to send first request information to a first function entity, the first request information being used to request collection of simulation data, the first request information comprising a data type and a collection object.

[0077] The second communication unit is further configured to receive first simulation data from the first function entity, the first simulation data being simulation data of the data type of the collection object.

[0078] The apparatus is configured to implement the method of the second aspect or any of the embodiments of the second aspect.

[0079] In a sixth aspect, a communication apparatus is provided, comprising:

[0080] The third communication unit is configured to receive second request information from a first function entity, the second request information being used to request collection of simulation data of a data type of a collection object.

[0081] The third communication unit is further configured to send first simulation data of the data type of the collection object according to the second request information.

[0082] The apparatus is configured to implement the method of the third aspect or any of the embodiments of the third aspect.

[0083] In a seventh aspect, the present application provides a communication apparatus, which can be a single device, a cluster composed of multiple devices, or a component in a single device. Exemplarily, the communication apparatus can be a management function entity, such as an NMS or an EMS, or can be another function entity other than the management function entity, such as a BSS. The communication apparatus comprises at least one processor and a communication interface. The communication interface is configured to receive and / or send data, and / or the communication interface is configured to provide input and / or output for the processor. The at least one processor is configured to execute computer instructions to enable the communication apparatus to perform the method described in any of the first aspect, any of the second aspect, or any of the third aspect.

[0084] It should be noted that the processor included in the communication apparatus described in the seventh aspect can be a processor specially used for executing the methods (referred to as a special-purpose processor for the sake of distinction), or can be a processor that executes the methods by invoking a computer program, such as a general-purpose processor. Alternatively, the at least one processor can include both a special-purpose processor and a general-purpose processor.

[0085] Alternatively, the computer program described above can exist in a memory. For example, the memory can be a non-transitory memory, such as a Read Only Memory (ROM), which can be integrated on the same device as the processor, or can be separately arranged on different devices, and the type of the memory and the arrangement manner of the memory and the processor are not limited in the embodiments of the present application.

[0086] In a possible implementation, the at least one memory is located outside the communication apparatus.

[0087] In another possible implementation, the at least one memory is located inside the communication apparatus.

[0088] In yet another possible implementation, part of the at least one memory is located inside the communication apparatus, and the other part of the at least one memory is located outside the communication apparatus.

[0089] In the present application, the processor and the memory can also be integrated into one device, that is, the processor and the memory can also be integrated together.

[0090] In the eighth aspect, the embodiments of the present application provide a computer readable storage medium, and the computer readable storage medium stores instructions. When the instructions are run by a computing device (or a computing device cluster), the computing device (or the computing device cluster) implements the method described in any one of the preceding first aspect, any one of the preceding second aspect, or any one of the preceding third aspect.

[0091] In the ninth aspect, the present application provides a computer program product, and the computer program product includes computer instructions. When the instructions are run by a computing device (or a computing device cluster), the computing device (or the computing device cluster) implements the method described in any one of the preceding first aspect, any one of the preceding second aspect, or any one of the preceding third aspect.

[0092] Alternatively, the computer program product can be a software installation package or an image file, and in the case where the method described above needs to be used, the computer program product can be obtained and executed on the computing device.

[0093] In a tenth aspect, the present application provides a chip, comprising: a processor coupled with a memory, the memory being configured to store programs or instructions, when the programs or instructions are executed by the processor, causing a first function entity to perform the method of any one of the first aspect, and / or causing a second function entity to perform the method of any one of the second aspect, and / or causing a computing device to perform the method of any one of the third aspect.

[0094] In an eleventh aspect, the present application provides a data acquisition system, comprising a first function entity and a third function entity;

[0095] The first function entity is configured to implement the method of any one of the first aspect, and the third function entity is configured to implement the method of any one of the third aspect. Optionally, the data acquisition system further comprises a second function entity, and the second function entity is configured to implement the method of any one of the second aspect.

[0096] The technical solutions provided in the fourth aspect to the eleventh aspect of the present application have the beneficial effects of the technical solutions of the first aspect, the second aspect or the third aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0097] FIG. 1 is a data acquisition system provided by an embodiment of the present application;

[0098] FIG. 2 is an architecture schematic diagram of a possible data acquisition system provided by the present application;

[0099] FIG. 3 is an architecture schematic diagram of another possible data acquisition system provided by an embodiment of the present application;

[0100] FIG. 4 is an architecture schematic diagram of another possible data acquisition system provided by an embodiment of the present application;

[0101] FIG. 5 is an architecture schematic diagram of another possible data acquisition system provided by an embodiment of the present application;

[0102] FIG. 6 is a flowchart of a data acquisition method provided by an embodiment of the present application;

[0103] FIG. 7 is a flowchart of an information reporting method provided by an embodiment of the present application;

[0104] FIG. 8 is a flowchart of a possible data acquisition method provided by an embodiment of the present application;

[0105] FIG. 9 is a flowchart of another possible data acquisition method provided by an embodiment of the present application;

[0106] FIG. 10 is a structure schematic diagram of a communication device provided by an embodiment of the present application;

[0107] Figure 11 is a structural schematic diagram of another communication apparatus provided by an embodiment of the present application;

[0108] Figure 12 is a structural schematic diagram of another communication apparatus provided by an embodiment of the present application;

[0109] Figure 13 is a structural schematic diagram of a communication apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0110] Currently, 3GPP TS 28.104 specifies procedures and requirements for MDA capabilities with corresponding analytics inputs and analytics outputs (reports), as well as management data analytics services (MDAS), historical data handling for MDA, and ML support for MDA. This document also describes the MDA function and service framework, as well as the MDA role in the management loop.

[0111] Generally, MDA is a key enabler for automation and intelligence, and it is considered a fundamental capability for mobile network and service management and orchestration. MDA provides the capability to process and analyze data related to network and service events and status, including, for example, performance measurements, key performance indicators (KPIs), reports, alarms, configuration data, network analytics data, and service experience data from analytics functions (AFs). MDA can provide analytics outputs, such as statistics or predictions, root cause analysis problems, and recommendations, to enable necessary actions for network and service operations. MDA outputs are provided by management data analytics services (MDAS) producers to corresponding consumers that request analytics.

[0112] MDAS is a service exposed by MDA. MDAS can be consumed by various consumers, including, for example, management functions (MnFs) (such as management service producers and management service consumers for network and service management, network functions (NFs) (e.g., network data analytics functions (NWDAFs)), self-organizing network (SON) functions, network and service optimization tools / functions, service level specification (SLS) assurance functions, human operators, application functions (AFs), and the like.

[0113] One important area of research and development in 3GPP standards is Artificial Intelligence, AI / Machine Learning, ML, techniques to support various functions of 3GPP systems, such as MDA and others. For example, 3GPP TS 28.105 specifies AI / ML management capabilities and services for 5GS using AI / ML, including management and coordination (e.g., MDA as defined in 3GPP TS 28.104) and 5G networks (e.g., Network Data Analytics Function (NWDAF) as defined in 3GPP S23.288). 3GPP TS 28.105 also describes a framework of functions and services for AI / ML management. AI / ML inference functions in 5GS use ML models for inference. To enable and facilitate AI / ML operations, management of ML entities (which can be ML models or entities containing one or more ML models) and AI / ML inference functions is needed. 3GPP TS 28.105 specifies AI / ML management related capabilities and services, which include ML training for training (one or more) ML models associated with ML entities. For example, 3GPP TS 28.105 specifies AI / ML functions and a framework of services for ML training. An entity playing the role of ML training MnS producer can consume various data for the purpose of ML training. ML entity training capabilities are provided by the ML training MnS producer to authorized consumers in the context of SBMA. ML entity training refers to the training of (one or more) ML models associated with ML entities. The ML training MnS producer can implement internal business logic related to ML training in order to monitor network and / or services related to ML entities with current and historical data related to MDA and 5G networks, prepare data for model training, trigger and conduct appropriate ML training.

[0114] In the actual implementation of the ML training process, a large amount of data is required to participate in the training, most of which is performance data from specific network elements, such as average end-to-end slice latency. There are two ways to collect data defined in the current standard, one is to collect management data based on the control inversion of ManagementDataCollection IOC. The specific attributes of this management object include, for example, collected management data management Data, and collection target node filter target Node Filter; the other is to collect performance indicators based on the control inversion of Perf Metric Job IOC. The specific attributes of this management object include, for example, performance indicators to be collected performanceMetrics, and collection objects object Instance. Specifically, the management service consumer MnS consumer requests the collection of data from the configuration management service provider Provisioning MnS producer, that is, by creating MOI ManagementDataCollection or PerfMetricJob to present the specific request requirements, and the Provisioning MnS producer collects the relevant data according to the data attribute requirements of the request after receiving the task creation request, and reports to the management service consumer after the collection is completed.

[0115] In summary, in the architecture of the management service related to the current 3GPP standard, there is only a single data collection channel for collecting the live data (such as the performance data described above) of the specific network element (s) through the data collection function, which leads to the problems of insufficient training data, low collection efficiency, and high data acquisition cost in the actual implementation of the ML training.

[0116] Based on the above problems, the present application provides a data acquisition method and an architecture of a data acquisition system, which can establish a new data acquisition channel for the service-based management architecture and improve the richness of the acquired data.

[0117] The system architecture related to the embodiments of the present application is explained below.

[0118] Please refer to FIG. 1, which is a data acquisition system provided by an embodiment of the present application. The data acquisition system includes a first functional entity and a third functional entity.

[0119] Among them, the first functional entity and the third functional entity can be management entities defined by 3GPP. That is, the data acquisition method provided by the embodiments of the present application can be applied to the network management architecture of NR.

[0120] The first function entity is a function / device / module / system for data collection, for example, the first function entity can be an element management system (EMS) or a network management system (NMS) in a service-based management architecture defined by 3GPP, or can be an element in a radio access network or an element in a core network. The access network can be a next generation radio access network (NG-RAN), and the core network can be a 5G core network (5GC). The access network can include base stations (e.g., gNB (next generation NodeB) or ng-eNB (next generation eNodeB)), and the base stations are connected by an interface (e.g., an Xn interface). The base stations and the 5GC can be connected by an interface (e.g., an Ng interface). The core network can include an access and mobility management function (AMF). The core network can also include a user plane function (UPF).

[0121] The third function entity is a function / device / module / system for providing simulation data, for example, the third function entity can be an element management system (EMS) or a network management system (NMS) in a service-based management architecture defined by 3GPP, or can be an element in a radio access network or an element in a core network.

[0122] For example, the first function entity and the third function entity can be an element management system (EMS) in a service-based management architecture defined by 3GPP, which means that the first function entity and the third function entity can be the same element management system (EMS), or can belong to different element management systems (EMSs), or means that the first function entity and the third function entity can be a device in an element management system (EMS), or can belong to different devices in an element management system (EMS), which is not limited in the present application.

[0123] In an optional implementation, the system further includes a second function entity, and the second function entity is a requester of the data. The second function entity can be a network management system (NMS) in a service-based management architecture defined by 3GPP, or can be a device / system of a third party capable of invoking a management service, for example, a business support system (BSS).

[0124] Exemplarily, if the first function entity and the third function entity are network management systems (NMSs) in the service-based management architecture defined by 3GPP, the second function entity is a device / system of a third party capable of invoking a management service. If the first function entity and the third function entity are element management systems (EMSs) in the service-based management architecture defined by 3GPP, the second function entity can be a network management system (NMS) or a device / system of a third party capable of invoking a management service. If the first function entity and the third function entity are network elements in a radio access network or network elements in a core network, the second function entity can be a network management system (NMS) or a device / system of a third party capable of invoking a management service.

[0125] The externally visible behavior and interfaces of a management entity in the service-based management architecture defined by 3GPP are defined as management services. In the service-oriented management architecture, a management function (MnF) plays the role of a management service producer (MnS producer) or a management service consumer (MnS consumer). The service-based management architecture focuses on management service producers and management service consumers, where a management service producer can also be referred to as a management service producer.

[0126] Optionally, in the interaction between the first function entity and the second function entity, for example, in the process in which the second function entity sends first request information for requesting simulation data to the first function entity and the first function entity returns simulation data requested by the first request information to the second function entity, the first function entity is a management service producer and the second function entity is a management service consumer; in the interaction between the second function entity and the third function entity, for example, in the process in which the second function entity sends second request information for requesting simulation data to the third function entity and the third function entity returns simulation data requested by the second request information to the second function entity, the first function entity is a management service consumer and the second function entity is a management service producer.

[0127] FIG. 2 is a schematic diagram of an architecture of a possible data acquisition system provided by the present application. Referring to FIG. 2, the data acquisition system includes a business support system (BSS), a cross domain management function (CD-MnF), and a domain management function (Domain-MnF). It should be understood that the cross domain management function can be a node such as an NMS, a management service consumer MnS Producer, or a management service producer MnS Consumer, and the domain management function can be a node such as an EMS, an MAE, a MnS Producer, or a MnS Consumer.

[0128] The data acquisition system provided by the embodiments of the present application can be a standard service-based management architecture, which includes two main concepts of a management service (MnS) and a management function (MnF). The management service provides management capabilities. A management service consumer accesses these management capabilities through a standardized service interface composed of separately specified management service components. The management function is a management entity, and the externally visible behavior and interface of the management function are standardized as a management service. The user of the management service (for example, an operator) provides functions and content for the consumer of the management service, so that the consumer of the management service can decide how to use the management service according to a scenario. The user of the management service can be referred to as a MnS Producer, and the consumer of the management service can be referred to as a MnS Consumer.

[0129] If the management service is a management service provided by the cross domain management function, the cross domain management function is a management service producer, and the business support system is a management service consumer. If the management service is a management service provided by the domain management function, the domain management function is a management service producer, and the cross domain management function is a management service consumer. If the management service is a management service provided by a network element, the network element is a management service producer, and the domain management function is a management service consumer.

[0130] In the system architecture shown in FIG. 2, the second function entity (business support system BSS) is a management service consumer, which needs to invoke the management service to collect simulation data. The first function entity (cross-domain management function unit, such as network management system (NMS)) accepts information related to the data request from the second function entity (business support system BSS), and requests the third function entity (domain management function unit, such as element management system (EMS)) to collect simulation data based on the information. In an optional implementation, the third function entity is a device that generates simulation data, or the third function entity is provided with a function or a module that generates simulation data.

[0131] The business support system is oriented to communication services, and is used to provide functions and management services such as charging, settlement, accounting, customer service, business, network monitoring, communication service life cycle management, and service intent translation. The business support system can be an operation system of an operator, or a vertical OT system.

[0132] The cross-domain management function unit, also called network management function (NMF), can be a network management entity such as network management system (NMS) or network function management service consumer (NFMS_C). The cross-domain management function unit provides one or more of the following management functions or management services: network life cycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization function, and translation of the intent from a communication service provider (Intent-CSP). Optionally, the first function entity, the second function entity, and the third function entity in the present application can be NMS, or devices / modules deployed in NMS.

[0133] The network referred to in the above management function or management service can include one or more network elements or sub-networks, or can be a network slice. That is, the network management function unit can be a network slice management function unit (NSMF), or a cross-domain management data analysis function unit (MDAF), or a cross-domain self-organization network function (SON Function), or an intent-driven management function unit (Intent Driven MnS).

[0134] Optionally, in some deployment scenarios, the cross-domain management function unit can also provide lifecycle management of a sub-network, deployment of a sub-network, fault management of a sub-network, performance management of a sub-network, configuration management of a sub-network, assurance of a sub-network, optimization function of a sub-network, translation of a network intent from a communication service producer (Intent-CSP) or a network intent from a communication service consumer (Intent-CSC) of a sub-network, etc. The sub-network here is composed of multiple small sub-networks, and can be a network slice sub-network.

[0135] The domain management function unit (Domain-MnF) is also called a network management function unit (NMF) or a network element management function unit. For example, the domain management function unit can be a network element management entity such as a mobile broadband automation engine (MAE), an element management system (EMS), a network function management service provider (NFMS_P), etc. Optionally, the first function entity and the third function entity can be an EMS, or a device / module deployed in the EMS.

[0136] The domain management function unit provides one or more of the following functions or management services: lifecycle management of a subnetwork or a network element, deployment of a subnetwork or a network element, fault management of a subnetwork or a network element, performance management of a subnetwork or a network element, assurance of a subnetwork or a network element, optimization function of a subnetwork or a network element, and translation of an intent from a network operator (Intent-NOP) of a subnetwork or a network element. The subnetwork includes one or more network elements. The subnetwork can also include a subnetwork, i.e., one or more subnetworks form a larger subnetwork.

[0137] Optionally, the subnetwork can also be a network slice subnetwork. The domain management system can be a network slice subnetwork management function unit (NSSMF), a domain management data analysis function unit (Domain MDAF), a domain self-organization network function (SON Function), an intent-driven MnS, etc.

[0138] The domain management function unit can be classified in the following ways, including:

[0139] According to the network type, the domain management function unit can be classified into a radio access network domain management function (RAN-Domain-MnF), a core network domain management function (CN-Domain-MnF), a transport network domain management function (TN-Domain-MnF), etc. It should be noted that the domain management function unit can also be a domain network management system that manages one or more of the access network, the core network, or the transport network.

[0140] According to the administrative region, the domain management function unit can be classified into a domain management function unit of a certain region, such as a Shanghai domain management function unit, a Beijing domain management function unit, etc.

[0141] Optionally, the system further comprises an element, which is an entity providing network service, including a core network element, an access network element, etc. The core network element includes an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a network data analytical function (NWDAF), a network repository function (NRF), a gateway, etc. The access network element includes a base station (such as gNB, eNB), a central unit control plane (CUCP), a central unit (CU), a distribution unit (DU), a central unit user plane (CUUP), etc. Optionally, the first function entity and the third function entity can be an element or a device / module / function deployed on an element.

[0142] The element can provide one or more of the following management functions or services: life cycle management of the element, deployment of the element, fault management of the element, performance management of the element, assurance of the element, optimization function of the element, and translation of the intention of the element, etc. In the embodiments of the present application, the element can also provide its own performance data.

[0143] It should be noted that the first function entity and the third function entity can be arranged in the same system / device, or can be arranged separately in different systems / devices. For example, the first function entity and the third function entity can be two function entities in an element management system (EMS).

[0144] The following exemplary describes the architecture in which the first function entity and the third function entity are arranged in the same system / device. Please refer to FIG. 3, which is a schematic diagram of the architecture of another possible data acquisition system according to an embodiment of the present application. As shown in FIG. 3, the data acquisition system comprises a third-party management service consumer, an NMS (the second function entity), and an EMS (the first function entity and the third function entity).

[0145] The third-party management service consumer is a device / system of a third party that can invoke a management service, for example, a business support system (BSS).

[0146] The third-party management service consumer is in communication connection with the NMS, the NMS is in communication connection with the EMS, the third-party management service consumer cannot directly interact with the first function entity and the third function entity arranged in the EMS, and thus cannot request to collect data, therefore, the NMS is commissioned to request data, in this architecture, the third-party management service consumer is the actual management service consumer, and the second function entity is actually a transfer station for the management service consumer to request data, that is, the third-party management service consumer requests data from the function entity providing the data through the second function entity.

[0147] In FIG. 3, the first function entity and the third function entity are arranged in the EMS, that is, the first function entity and the third function entity can be implemented as two modules in the EMS, in this case, the information flow between the first function entity and the third function entity is changed from "sending" and "receiving" to "inputting" and "outputting", for example, the information flow of "the first function entity sends the first request information to the third function entity" can be changed to "the first function entity inputs the first request information to the third function entity". Optionally, the system further includes a core network network element and an access network network element, and the core network network element and the access network network element can be used to provide live network data.

[0148] Referring to FIG. 4, FIG. 4 is a schematic diagram of another possible data acquisition system architecture provided by the embodiment of the present application. As shown in FIG. 4, the data acquisition system includes a third-party management service consumer (a second function entity) and an NMS (a first function entity and a third function entity).

[0149] In this architecture, the first function entity and the third function entity are arranged in the NMS, and thus the interaction with the third-party management service consumer can be implemented.

[0150] Referring to FIG. 5, FIG. 5 is a schematic diagram of another possible data acquisition system architecture provided by the embodiment of the present application. As shown in FIG. 5, the data acquisition system includes a third-party management service consumer, an NMS (a second function entity), and a network element (a first function entity and a third function entity). The network element can be a network element of an access network or a network element of a core network.

[0151] The third-party management service consumer is in communication connection with the NMS, the NMS is in communication connection with the network element, the third-party management service consumer cannot directly interact with the first function entity and the third function entity arranged in the network element, and thus cannot request to collect data, therefore, the NMS is commissioned to request data, in this architecture, the third-party management service consumer is the actual management service consumer, and the second function entity is actually a transfer station for the management service consumer to request data, that is, the third-party management service consumer requests data from the function entity providing the data through the second function entity.

[0152] Based on the system architecture shown in FIG. 1 to FIG. 5, the following explains a data acquisition method provided by the embodiments of the present application.

[0153] FIG. 6 is a flow chart of a data acquisition method provided by the embodiments of the present application. The method can be implemented based on any of the architectures shown in FIG. 1 to FIG. 5. In the embodiments of the present application, the following explains the method based on the system architecture shown in FIG. 1. As shown in FIG. 6, the method includes the following steps:

[0154] S601: The second function entity sends first request information to the first function entity.

[0155] In the embodiments of the present application, the first request information is used to request to collect simulation data, and the first request information includes a data type and a collection object. The data type is used to represent the data type corresponding to the simulation data, such as data category, data name, for example, Utilization, latency, etc. The collection object is used to represent the network element corresponding to the simulation data.

[0156] Based on the above description of the standard service management architecture, it can be known that the management entity has a demand for performance data from each network element. Therefore, the simulation data can be data simulated according to the actual running state of each network element. The performance data includes average end-to-end slice latency and other data. Therefore, the collection object can be understood as each network element. Of course, in actual running, the management service consumer can only need simulation data of a certain network element. In this case, the collection object is "a certain network element".

[0157] It can be understood that the first request information includes the data type and the collection object, which means that the simulation data requested by the first request information should be simulation data about the data type of the collection object.

[0158] In an optional implementation, the simulation data can also be configuration parameter related data or alarm information related data of each network element, for example, network error related data in each network element.

[0159] In an alternative implementation, the first request message can be a createMDA request instance request message, for example, the first request message is a createMDA request IOCRequest operation. The MDA request instance request information is used to request the first management entity to create an MDA request instance. After the first functional entity receives the MDA request instance request information, the first functional entity creates the MDA request instance according to the MDA request information included in the first request message, and sends a response message of creating the MDA request instance to the second functional entity. For example, the response message can be a createMDA request IOCResponse operation. It should be noted that the MDA request instance request message can be sent through an existing operation or a newly defined operation, which is not limited in the present application.

[0160] In another alternative implementation, the first request message can be a feedback request message or a feedback notification message, for example, the first request message is a notification operation. After the first functional entity receives the feedback request message or the feedback notification message, the first functional entity determines that a response message can be sent to the second functional entity according to the feedback information included in the first request message. It should be noted that the first request message can be sent through an existing operation message or a newly defined operation message, which is not limited in the present application.

[0161] It should be noted that the feedback notification message can be sent through an existing notification message or a newly defined notification message, for example, a newly defined Notification, which is not limited in the present application. The feedback notification message can be a feedback request message, which can be sent through an existing request operation or a newly defined request operation, which is not limited in the present application.

[0162] In an alternative implementation, the first functional entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0163] In an alternative implementation, the second functional entity is a business support system BSS or a network management system NMS.

[0164] In the embodiments of the present application, the second functional entity sends the first request information to the first functional entity to request simulation data, which represents that in the interaction process between the first functional entity and the second functional entity, the first functional entity is a management service provider and the second functional entity is a management service consumer.

[0165] In an alternative embodiment, the first request information further comprises first indication information, which is used to indicate that the collected data is simulation data, or used to indicate that the collected data comprises simulation data. In this embodiment, the second function entity can prompt the first function entity through the first indication information that the simulation data is needed. This includes two cases, case one, the first indication information indicates that the second function entity only needs simulation data; case two, the second function entity needs to collect data comprising simulation data, for example, the second function entity requests to collect simulation data and real data, and it should be noted that in case two, the data types and collection objects of the simulation data and the real data are the same. The first indication information in this embodiment is a new parameter, which is used to indicate whether the data collected by the management service consumer is only simulation data or a plurality of data comprising simulation data, which represents that the data requested by the management service consumer is in multiple cases, but in any case, the first request information can indicate the demand of the first function entity through the first indication information.

[0166] In another alternative embodiment, in addition to collecting data comprising simulation data according to the first indication information, the second function entity can directly request real data through the first request information, which represents that the first request information is used to request simulation data and real data, and the first request information is also used to request real data.

[0167] Considering that the second function entity needs comprehensive and accurate data support in some embodiments, in another alternative embodiment, the first request information further comprises second indication information, which is used to indicate that the collected data comprises simulation data and real data. This improves the diversity and accuracy of data services.

[0168] Since in some cases where the second function entity needs data comprising simulation data, the second function entity has requirements for the proportion of the requested data, in an alternative embodiment, the first request information further comprises proportion information, which is used to represent the proportion of real data and simulation data. The proportion relationship includes a minimum proportion requirement or a maximum proportion requirement.

[0169] It can be understood that the first function entity can determine the quantity of another data according to the proportion information and the data that is preferentially collected. Generally, the first function entity preferentially collects data other than simulation data.

[0170] In the scenario that the second function entity requests the simulation data and the live network data through the first request information, the second function entity can not distinguish the requested simulation data and live network data. To solve the problem, in an optional implementation, the first request information further includes third indication information, the third indication information is used to indicate that the first label is fed back through the response information of the first request information, and the first label is used to represent the simulation data.

[0171] It can be understood that the first label corresponds to the simulation data and is used to represent that the current data is the simulation data. Optionally, there is also a second label, and the second label is used to represent the live network data.

[0172] In an optional implementation, the first request information further includes collection requirement information of the simulation data, and the collection requirement information of the simulation data is used to represent the requirement of collecting the simulation data, for example, the collection quantity of the simulation data, the format requirement of the simulation data, and the like. After the first function entity receives the collection requirement information of the simulation data, the simulation data is collected according to the collection requirement information of the simulation data.

[0173] Optionally, the collection requirement information of the simulation data includes one or more of a time window, data distribution information, a collection time length, or a quantity of the simulation data.

[0174] The time window is used to represent the data collected in a specified time period.

[0175] The data distribution information is used to represent the distribution characteristics of the collected data. For example, the data distribution information is a distribution requirement that the collected data needs to meet, for example, a normal distribution with a mean of A and a variance of B. The data distribution information can be for the simulation data, that is, the collected simulation data needs to meet the distribution requirement represented by the data distribution information, or can be for all data, that is, the data including the simulation data.

[0176] The collection time length is used to represent the time length of collecting the simulation data.

[0177] In an optional implementation, the management service consumer of the third party is a substantial management service consumer, and the second function entity is a relay station for the management service consumer to request data, that is, the management service consumer of the third party requests the data from the function entity providing the data through the second function entity. In this case, the second function entity sends the first request information to the first function entity after receiving the information of the management service consumer of the third party requesting the data.

[0178] In an optional implementation, before the second function entity sends the first request information to the first function entity, the third function entity reports information related to the simulation data. For example, the information related to the simulation data includes whether the third function entity currently supports simulation data collection. If the third function entity supports simulation data collection, the information related to the simulation data further includes target parameters of the supported simulation data, which include one or more of the following: data type, collection object, and time window. Optionally, the target parameters further include the number of simulation data. Alternatively, the third function entity is an entity that provides simulation data. For example, the third function entity is a network digital twin (NDT), or a system or device that includes the NDT. For example, the third function entity can be an element management system (EMS), a network management system (NMS), a network element in a radio access network, or a network element in a core network.

[0179] The process of the third function entity reporting information related to the simulation data is exemplarily described below with reference to FIG. 7. FIG. 7 is a flowchart of an information reporting method according to an embodiment of the present application, which includes the following steps.

[0180] In S701, the third function entity sends fourth indication information to the first function entity.

[0181] The fourth indication information is used to indicate that the third function entity supports simulation data collection. The fourth indication information includes target parameters, which include one or more of the following: data type, collection object, and time window.

[0182] In S702, the first function entity receives the fourth indication information from the third function entity.

[0183] In S703, the first function entity sends the fourth indication information to the second function entity.

[0184] In S704, the second function entity receives the fourth indication information from the first function entity.

[0185] In S705, the second function entity determines target parameters of the simulation data to be collected according to the target parameters included in the fourth indication information.

[0186] Specifically, the second function entity receives the fourth indication information, and determines the target parameter of the requested simulation data according to the target parameter in the fourth indication information. It should be noted that the determined target parameter is consistent with the information related to the target parameter included in the first request information. For example, the multiple target parameters include the data type, and the data type includes the network performance index, the time delay, and the throughput. The second function entity determines that the data type of the requested simulation data is the time delay according to the target parameter included in the fourth indication information. Therefore, the data type included in the first request information is also the time delay. It can be understood that if the second function entity determines that the third function entity does not include the simulation data required by the second function entity through the fourth indication information, the second function entity will not perform the subsequent processes such as sending the first request information.

[0187] The fourth indication information shown in FIG. 7 is sent by the third function entity to the second function entity through the first function entity. In an optional embodiment, the fourth indication information can be sent by the third function entity to the second function entity directly without forwarding through the first function entity. In this embodiment, the third function entity establishes a communication connection with the second function entity. If the third function entity collects the simulation data through the instance, the third function entity can also send the instance identifier included in the third function entity through the communication connection between the third function entity and the second function entity. Optionally, the instance identifier can be sent through the fourth indication information, or can be sent through other information.

[0188] S602: The first function entity receives the first request information from the second function entity.

[0189] S603: The first function entity sends the second request information to the third function entity according to the first request information.

[0190] The second request information is used to request the simulation data of the data type of the collection object.

[0191] In an optional embodiment, the first function entity requests the simulation data of the data type of the collection object from the third function entity by forwarding the first request information. This means that the second request information is the same as the first request information. Of course, in other embodiments, the first function entity can also regenerate the second request information according to the first request information, and then send the second request information to the third function entity.

[0192] In order to ensure consistency of the data, in an optional embodiment, the first request information further comprises collection requirement information of the simulation data, and the second request information also comprises the collection requirement information of the simulation data. It can be understood that the collection requirement information of the simulation data comprised in the first request information is consistent with the collection requirement information of the simulation data comprised in the second request information. For example, the collection requirement information of the simulation data comprised in the first request information comprises the following contents: time window, data distribution information, collection duration, and number of simulation data, and the collection requirement information of the simulation data comprised in the second request information also comprises the same contents.

[0193] In an optional embodiment, the first functional entity determines, according to the first request information, that the second functional entity also requests to collect the real network data, and therefore, before sending the second request information, the first functional entity sends third request information to a real network element (collection object), wherein the third request information is used to request to collect real data of the data type about the collection object; the real network element receives the third request information and sends, according to the third request information, real data to the first functional entity; the first functional entity receives first real data of the data type about the collection object from the real network element; and the first functional entity sends the first real data to the second functional entity. It can be understood that the above process further comprises that the second functional entity receives the first real data.

[0194] In the embodiment, the first request information further comprises proportion information, and the first functional entity can determine the number of simulation data to be collected according to the number of the first real data and the proportion information. It can be understood that the second request information sent by the third functional entity comprises the number of simulation data to be collected.

[0195] In an optional embodiment, the third functional entity collects simulation data through instances, and the third functional entity comprises a plurality of instances, each instance being used to represent one or more collection objects. The second request information comprises a first instance identifier, and the first instance identifier is used to represent a first instance comprising the collection object. It can be understood that the third functional entity can quickly locate the first instance related to the collection object according to the first instance identifier.

[0196] Optionally, the first instance identifier can be one of a plurality of instance identifiers comprised in the fourth indication information, and the second functional entity sends the first instance identifier to the first functional entity through the first request information after selecting the plurality of instance identifiers, so as to make the first functional entity send the first instance identifier to the third functional entity.

[0197] Optionally, the first instance identifier can be determined by the first function entity, and a plurality of instance identifiers are preset in the first function entity. The first function entity can determine the identifier of the first instance according to the data type and the collection object in the first request information, i.e., the first instance identifier.

[0198] S604: The third function entity receives the second request information from the first function entity.

[0199] Specifically, the third function entity can determine the simulation data requested by the first function entity / the second function entity according to the second request information.

[0200] In an optional embodiment, the second request information includes the first instance identifier. In this embodiment, the third function entity obtains the first simulation data by collecting simulation data of the data type of the collection object in the instance corresponding to the first instance identifier.

[0201] In an optional embodiment, the second request information includes the data type and the collection object. The third function entity can determine the first instance according to the collection object, and then obtain the first simulation data by collecting simulation data of the data type of the collection object in the first instance. In this embodiment, without the instance identifier, the third function entity can still determine the instance corresponding to the collection object according to the specific information, thereby reducing the communication overhead.

[0202] In an optional embodiment, the second request information includes the collection requirement information of the simulation data, and the collection requirement information of the simulation data includes one or more of the following: a time window, data distribution information, a collection time length, and a number of simulation data. The third function entity can determine the collection requirement of the simulation data according to the collection requirement information of the simulation data included in the second request information, and then collect the simulation data meeting the collection requirement. It should be noted that in different embodiments, the collection requirement of the first simulation data can be different, and accordingly, the content of the collected first simulation data can also be different.

[0203] S605: The third function entity sends the first simulation data of the data type of the collection object according to the second request information.

[0204] S606: The first function entity receives the first simulation data of the data type of the collection object from the third function entity.

[0205] In the scenario that the second function entity requests the simulation data and the live network data through the first request information, there can be a problem that the second function entity cannot distinguish the requested simulation data and live network data. To solve the problem, in an embodiment in which the first request information further comprises third indication information, the third indication information is used to indicate that the first function entity feeds back a first label in the response information of the first request information, and the first label is used to represent the simulation data. Optionally, the first label can be generated by the first function entity after receiving the simulation data returned by the third function entity, or can be generated by the third function entity. In the embodiment, the response information of the first request information comprises the first simulation data and the first label.

[0206] The first label can have multiple implementations. For example, the first label can be specific identification information added before the simulation data. The first label is described below by way of example. If the first simulation data is saved in the form of a one-dimensional array, in order not to affect the continuity of the first simulation data, the process of generating the first label can be to expand the one-dimensional array list into a two-dimensional array, and add specific labels, for example, 0 and 1, to each data in the one-dimensional array, where 0 represents live network data and 1 represents simulation data. In this way, the second function entity can distinguish the simulation data and the live network data through the specific labels 0 and 1. It can be understood that the 1 described above is the first label. Optionally, there is also a second label, which is used to represent live network data, and the second label can be 0 described above.

[0207] S607: The first function entity sends the first simulation data to the second function entity.

[0208] S608: The second function entity receives the first simulation data from the first function entity.

[0209] The first simulation data is simulation data of the data type of the collection object.

[0210] In the embodiment in which the first request information further comprises third indication information, the third indication information is used to indicate that the first function entity feeds back a first label in the response information of the first request information, and the first label is used to represent the simulation data. The second function entity receiving the first simulation data from the first function entity can be the response information. The response information comprises the first simulation data and the first label.

[0211] The embodiment of the application improves the richness of the data obtained by the management service consumer in the service management architecture by establishing a new simulation data collection channel, thereby improving the performance of the management service consumer. Further, by introducing instance identification, data type, and collection object information, the third function entity can accurately locate and collect simulation data in a specific instance, thereby improving the accuracy and pertinence of data collection. By supporting collection requirement information (such as time window, data distribution information, and collection duration), the third function entity can collect simulation data according to the specific requirements of the first function entity, thereby realizing customized data services. Allowing the first function entity to specify the requested data quantity helps the third function entity to reasonably allocate resources and avoid resource waste. In addition, by using the first label, the second function entity can clearly perceive whether the received data is simulation data or live network data, thereby facilitating the second function entity to accurately process the collected data.

[0212] To further illustrate the specific implementation of the method, refer to FIG. 8, which is a flowchart of a possible data acquisition method provided by the embodiment of the application, and the specific implementation is as follows:

[0213] S801: The second function entity sends first request information to the first function entity.

[0214] In this embodiment, the first request information includes first indication information, third indication information, data type, collection object, proportion information, and simulation data collection requirement information.

[0215] The first indication information is used to indicate that the collected data includes simulation data.

[0216] The third indication information is used to indicate that the first label is fed back through the response information of the first request information.

[0217] The simulation data collection requirement information is used to represent the requirement for collecting simulation data, such as the collection quantity of simulation data, the format requirement of simulation data, and the like. In this embodiment, the simulation data collection requirement information includes a time window and data distribution information. The data distribution information is used to represent the distribution requirement of the data (including simulation data and live network data) to be collected.

[0218] S802: The first function entity receives the first request information from the second function entity.

[0219] S803: The first function entity determines to collect simulation data from the third function entity according to the first indication information included in the first request information.

[0220] S804: The first function entity determines the first instance identification according to the collection object included in the first request information.

[0221] S805: The first function entity sends third request information to the existing network element.

[0222] S806: The existing network element receives the third request information from the first function entity.

[0223] S807: The existing network element sends first real data to the first function entity according to the third request information.

[0224] S808: The first function entity receives the first real data from the existing network element.

[0225] S809: The first function entity determines the number of simulation data to be collected according to the number and proportion information of the first real data.

[0226] S810: The first function entity determines the data distribution requirement of the simulation data according to the data value distribution of the first real data and the data distribution information.

[0227] S811: The first function entity sends second request information to the third function entity.

[0228] The second request information includes first instance identification, data type, collection object, and collection requirement information of simulation data. The collection requirement information of simulation data includes time window and data distribution information, and the data distribution information is the data distribution requirement of the simulation data determined by the first function entity according to the data value distribution of the first real data and the data distribution information.

[0229] S812: The third function entity receives the second request information from the first function entity.

[0230] S813: The third function entity sends first simulation data about the data type of the collection object according to the second request information.

[0231] Specifically, the third function entity determines the first instance according to the first instance identification; and obtains the first simulation data by collecting simulation data that meets the collection object, data type, and collection requirement information of simulation data in the instance corresponding to the first instance identification.

[0232] The first simulation data is simulation data about the data type of the collection object, and meets the time window and each condition of the data distribution requirement of the simulation data in the collection requirement information of the simulation data.

[0233] S814: The first function entity receives the first simulation data about the data type of the collection object from the third function entity.

[0234] S815: The first function entity generates a first label.

[0235] S816: The first function entity sends response information to the second function entity.

[0236] The response information comprises the first simulation data, a first label, and first real data.

[0237] Optionally, the response information further comprises a second label.

[0238] S817: The second function entity receives the response information from the first function entity.

[0239] Embodiments of the present application improve the collection accuracy of simulation data for various parameters (simulation data indication, scale, distribution, etc.), thereby obtaining a large amount of simulation data. If these simulation data are involved in model training, the model prediction accuracy in the service-oriented management architecture can be improved. Meanwhile, the simulation data and the live network data are distinguished by the first label.

[0240] To further illustrate the specific implementation of the method, please refer to FIG. 9, which is a flowchart of another possible data acquisition method provided by an embodiment of the present application, and the specific implementation is as follows:

[0241] S901: The second function entity sends first request information to the first function entity.

[0242] In the embodiment, the first request information comprises first indication information, third indication information, data type, collection object, and collection requirement information of simulation data.

[0243] The first indication information is used to indicate collection of simulation data.

[0244] The third indication information is used to indicate that the first label is fed back through the response information of the first request information.

[0245] In the embodiment, the collection requirement information of simulation data comprises simulation data quantity and / or collection duration. The collection duration is used to represent the duration of collection of simulation data.

[0246] S902: The first function entity receives the first request information from the second function entity.

[0247] S903: The first function entity determines, according to the first indication information comprised in the first request information, collection of simulation data from the third function entity.

[0248] S904: The first function entity determines, according to the collection object comprised in the first request information, a first instance identifier.

[0249] S905: The first function entity sends second request information to the third function entity.

[0250] The second request information includes a first instance identifier, a data type, a collection object, and collection requirement information of simulation data. The collection requirement information of simulation data includes a simulation data quantity and / or a collection duration.

[0251] S906: The third function entity receives second request information from the first function entity.

[0252] S907: The third function entity sends first simulation data of the data type of the collection object according to the second request information.

[0253] Specifically, the third function entity determines a first instance according to the first instance identifier, and then collects simulation data according to the collection object, the data type, the collection requirement information of simulation data, and the first instance, so as to obtain the first simulation data.

[0254] The first simulation data is simulation data of the data type of the collection object, and meets each condition of the simulation data quantity and / or the collection duration in the collection requirement information of simulation data.

[0255] S908: The first function entity receives the first simulation data of the data type of the collection object from the third function entity.

[0256] S909: The first function entity generates a first label.

[0257] S910: The first function entity sends response information to the second function entity.

[0258] The response information includes the first simulation data and the first label.

[0259] S911: The second function entity receives the response information from the first function entity.

[0260] Embodiments of the present application replace the time window with the simulation data quantity and / or the collection duration, so that the simulation data quantity does not need to be calculated, resource consumption is reduced, and the collection accuracy of simulation data is improved.

[0261] The above describes the method of embodiments of the present application in detail. Based on the same technical concept, embodiments of the present application further provide a communication device for executing the method performed by the first function entity in the above embodiments.

[0262] Please refer to FIG. 10, which is a structural schematic diagram of a communication device provided by embodiments of the present application.

[0263] As shown in FIG. 10, the communication apparatus 100 can include a first communication unit 1001. The first communication unit 1001 can be software, hardware, or a combination of software and hardware.

[0264] The first communication unit 1001 can implement a sending function and / or a receiving function. The first communication unit 1001 can also be a unit that integrates an obtaining unit and a sending unit, where the obtaining unit is configured to implement the receiving function, and the sending unit is configured to implement the sending function. Alternatively, the first communication unit 1001 can be configured to receive information sent by another apparatus, and can also be configured to send information to another apparatus.

[0265] In a possible design, the communication apparatus 100 can correspond to the first function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, and can be the first function entity or a chip in the first function entity. The communication apparatus 100 can include units configured to perform operations performed by the first function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, and each unit in the communication apparatus 100 is configured to implement the operations performed by the first function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9. Details of each unit are as follows:

[0266] The first communication unit 1001 is configured to receive first request information from a second function entity, where the first request information is used to request to collect simulation data, and the first request information includes a data type and a collection object.

[0267] The first communication unit 1001 is further configured to send, to a third function entity, second request information according to the first request information, where the second request information is used to request simulation data of the data type about the collection object.

[0268] The first communication unit 1001 is further configured to receive, from the third function entity, first simulation data of the data type about the collection object.

[0269] The first communication unit 1001 is further configured to send, to the second function entity, the first simulation data.

[0270] In a possible implementation, the first request information further includes first indication information, where the first indication information is used to indicate that the collected data is simulation data, or is used to indicate that the collected data includes simulation data.

[0271] In a possible implementation, the first request information is further used to request real data.

[0272] In a possible implementation, the first request information further includes second indication information, the second indication information being used to indicate that the data including the simulation data and the real data is collected.

[0273] In a possible implementation, the first communication unit 1001 is further configured to send third request information to a network element in a live network, the third request information being used to request collection of real data of the data type of the collection object.

[0274] The first communication unit 1001 is further configured to receive first real data of the data type of the collection object from the network element in the live network.

[0275] The first communication unit 1001 is further configured to send the first real data to the second function entity.

[0276] In a possible implementation, the first request information further includes proportion information, the proportion information being used to represent a proportion of real data and simulation data, and the first communication unit 1001 is further configured to determine a quantity of simulation data requested to be collected according to a quantity of the first real data and the proportion information.

[0277] The first communication unit 1001 is further configured to send the second request information to the third function entity, the second request information including the quantity of simulation data requested to be collected.

[0278] In a possible implementation, the first request information further includes third indication information, the third indication information being used to indicate that a first label is fed back through response information of the first request information, the first label being used to represent simulation data, and the first communication unit 1001 is further configured to receive the first label from the third function entity.

[0279] In the aspect of sending the first simulation data to the second function entity, the first communication unit 1001 is specifically configured to:

[0280] send the response information to the second function entity, the response information including the first simulation data and the first label.

[0281] In a possible implementation, the first request information further includes third indication information, the third indication information being used to indicate that a first label is fed back through response information of the first request information, the first label being used to represent simulation data, and the communication apparatus 100 further includes a first processing unit, the first processing unit being configured to generate the first label.

[0282] In the aspect of sending the first simulation data to the second function entity, the first communication unit 1001 is specifically configured to:

[0283] sending the response information to the second function entity, the response information comprising the first simulation data and the first label.

[0284] In a possible implementation, according to the sending of the second request information to the third function entity according to the first request information, the first communication unit 1001 is specifically configured to:

[0285] determining a first instance label according to the collection object, the first instance label being used to indicate a first instance including the collection object in the third function entity;

[0286] sending the second request information to the third function entity, the second request information comprising the first instance label.

[0287] In a possible implementation, the first request information further comprises collection requirement information of the simulation data, and the second request information further comprises the collection requirement information of the simulation data.

[0288] In a possible implementation, the collection requirement information of the simulation data comprises one or more of a time window, data distribution information, a collection time length, or a quantity of simulation data, the time window being used to represent data collected in a specified time period, the data distribution information being used to represent distribution characteristics of the collected data, and the collection time length being used to represent a time length for collecting the simulation data.

[0289] In a possible implementation, the first communication unit 1001 is further configured to receive fourth indication information from the third function entity, the fourth indication information being used to indicate that the third function entity supports simulation data collection, and the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of a data type, a collection object, and a time window.

[0290] The first communication unit 1001 is further configured to send the fourth indication information to the second function entity.

[0291] In a possible implementation, the first function entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0292] The second function entity is a business support system BSS or a network management system NMS.

[0293] The third function entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0294] The embodiment of the present application further provides a communication device for executing the method executed by the second function entity in the above embodiment.

[0295] Please refer to FIG. 11, which is a structural schematic diagram of another communication device provided by the embodiment of the present application.

[0296] As shown in FIG. 11, the communication device 110 can include a second communication unit 1101. The second communication unit 1101 can be software, hardware, or a combination of software and hardware.

[0297] The second communication unit 1101 can realize the sending function and / or the receiving function. The second communication unit 1101 can also be a unit integrating the acquisition unit and the sending unit, wherein the acquisition unit is used to realize the receiving function, and the sending unit is used to realize the sending function. Alternatively, the second communication unit 1101 can be used to receive information sent by other devices, and also can be used to send information to other devices.

[0298] In a possible design, the communication device 110 can correspond to the second function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, for example, the communication device 110 can be the second function entity, or can be a chip in the second function entity. The communication device 110 can include units used to execute the operations performed by the second function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, and each unit in the communication device 110 is configured to implement the operations performed by the second function entity in the method embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9. Details of each unit are as follows:

[0299] The second communication unit 1101 is configured to send first request information to the first function entity, wherein the first request information is used to request to collect simulation data, and the first request information includes a data type and a collection object.

[0300] The second communication unit 1101 is further configured to receive first simulation data from the first function entity, wherein the first simulation data is simulation data of the data type about the collection object.

[0301] In a possible implementation, the first request information further includes first indication information, and the first indication information is used to indicate to collect simulation data, or is used to indicate to collect data including simulation data.

[0302] In a possible implementation, the first request information is further used to request real data.

[0303] In a possible implementation, the first request information further includes second indication information, where the second indication information is used to indicate collection of data including simulation data and real data.

[0304] In a possible implementation, the second communication unit 1101 is further configured to receive first real data from the first function entity.

[0305] In a possible implementation, the first request information further includes third indication information, where the third indication information is used to indicate that the first function entity feeds back a first label through response information of the first request information, and the first label is used to represent simulation data; and in the aspect of receiving the first simulation data from the first function entity, the second communication unit 1101 is specifically configured to:

[0306] receive response information from the first function entity, where the response information includes the first simulation data and the first label.

[0307] In a possible implementation, the first request information further includes collection requirement information of the simulation data.

[0308] In a possible implementation, the collection requirement information of the simulation data includes one or more of a time window, data distribution information, or collection duration, where the time window is used to represent collection of data in a specified time period, the data distribution information is used to represent distribution characteristics of the collected data, and the collection duration is used to represent a duration of collection of the simulation data; and the first request information further includes proportion information, where the proportion information is used to represent a proportion of real data and simulation data.

[0309] In a possible implementation, the communication apparatus 110 further includes a second processing unit, and the second communication unit 1101 is further configured to receive fourth indication information, where the fourth indication information is used to indicate that the third function entity supports simulation data collection, and the fourth indication information includes a plurality of target parameters, and the target parameters include one or more of a data type, a collection object, and a time window.

[0310] The second processing unit is configured to determine target parameters of simulation data to be collected according to the plurality of target parameters included in the fourth indication information.

[0311] In a possible implementation, the first function entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0312] The second function entity is a business support system BSS or a network management system NMS.

[0313] The third function entity is an element management system (EMS), a network management system (NMS), an element in a radio access network, or an element in a core network.

[0314] The embodiment of the present application further provides a communication device for executing the method performed by the third function entity in the above embodiment.

[0315] Please refer to Fig. 12, which is a structural schematic diagram of another communication device provided by the embodiment of the present application.

[0316] As shown in Fig. 12, the communication device 120 at least includes a third communication unit 1201. The third communication unit 1201 can be software, hardware, or a combination of software and hardware.

[0317] The third communication unit 1201 can realize the sending function and / or the receiving function. The third communication unit 1201 can also be a unit integrating an acquisition unit and a sending unit, wherein the acquisition unit is used to realize the receiving function, and the sending unit is used to realize the sending function. Alternatively, the third communication unit 1201 can be used to receive information sent by other devices, and also can be used to send information to other devices.

[0318] In a possible design, the communication device 120 can correspond to the third function entity in the method embodiments shown in Figs. 6, 7, 8 and 9, for example, the communication device 120 can be the third function entity, or a chip in the third function entity. The communication device 120 can include units used to execute the operations performed by the third function entity in the method embodiments shown in Figs. 6, 7, 8 and 9, and each unit in the communication device 120 is configured to implement the operations performed by the third function entity in the method embodiments shown in Figs. 6, 7, 8 and 9. Details of each unit are as follows:

[0319] The third communication unit 1201 is configured to receive second request information from a first function entity, where the second request information is used to request to collect simulation data of a data type about a collection object.

[0320] The third communication unit 1201 is further configured to send first simulation data of the data type about the collection object according to the second request information.

[0321] In a possible implementation, the second request information includes a first instance identifier, and the communication device 120 further includes:

[0322] The third processing unit is configured to obtain the first simulation data by collecting simulation data of the data type about the collection object in an instance corresponding to the first instance identifier.

[0323] In a possible implementation, the second request information includes the data type and the collection object, and the third processing unit is further configured to determine a first instance according to the collection object; and the third processing unit is further configured to obtain the first simulation data by collecting simulation data of the data type related to the collection object in the first instance.

[0324] In a possible implementation, the second request information further includes collection requirement information of simulation data, and the first simulation data meets a requirement corresponding to the collection requirement information.

[0325] In a possible implementation, the collection requirement information of simulation data includes one or more of a time window, data distribution information, a collection duration, and a quantity of simulation data, the time window is used to represent collection of data in a specified time period, the data distribution information is used to represent distribution characteristics of collected data, and the collection duration is used to represent a duration for collecting simulation data.

[0326] In a possible implementation, the second request information further includes a quantity of requested simulation data.

[0327] In a possible implementation, the third communication unit 1201 is specifically configured to:

[0328] send the first simulation data of the data type related to the collection object and a first label, the first label being used to represent simulation data.

[0329] In a possible implementation, the third communication unit 1201 is further configured to send fourth indication information to the first function entity, the fourth indication information being used to indicate that the third function entity supports simulation data collection, and the fourth indication information includes a plurality of target parameters, the target parameters including one or more of a data type, a collection object, and a time window.

[0330] In a possible implementation, the first function entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0331] The second function entity is a business support system BSS or a network management system NMS.

[0332] The third function entity is an element management system EMS, a network management system NMS, a network element in a radio access network, or a network element in a core network.

[0333] Please refer to FIG. 13, which is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application.

[0334] The communication apparatus 130 is a device or a third-party management service consumer in a service-oriented management architecture. For example, the communication apparatus 130 can be a functional entity such as an element management system (EMS), a network management system (NMS), a network element in a radio access network, a network element in a core network, or a business support system (BSS), or one of the devices in the functional entity.

[0335] Optionally, the communication apparatus 130 is any one of the first functional entity, the second functional entity, and the third functional entity shown in FIG. 1.

[0336] The communication apparatus 130 can include at least one processor 1301 and at least one memory 1303. Optionally, the communication apparatus 130 further includes a communication interface 1302, and further optionally, can include a connection line 1304, wherein the processor 1301, the communication interface 1302, and / or the memory 1303 are connected through the connection line 1304, and communicate with each other, transmit control and / or data signals through the connection line 1304. Wherein:

[0337] (1) The processor 1301 is a module for performing arithmetic operations and / or logical operations, and can specifically include one or more of the following modules: a central processing unit (CPU), an application processor (AP), a microcontroller unit (MCU), an electronic control unit (ECU), a microprocessor unit (MPU), an application specific integrated circuit (ASIC), an image signal processor (ISP), a digital signal processor (DSP), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), or a co-processor, etc.

[0338] (2) The communication interface 1302 can be configured to provide information input or output for the at least one processor 1301. In some possible scenarios, the communication interface 1302 can include interface circuitry. And / or, the communication interface 1302 can be configured to receive data transmitted from outside and / or transmit data to outside. For example, the communication interface 1302 can include a wired link interface such as an Ethernet cable, and / or a wireless link interface (Wi-Fi, Bluetooth, universal wireless transmission, vehicle-mounted short-range communication technology, or other short-range wireless communication technology, etc.). Optionally, the communication interface 1302 can further include a transmitter (such as a radio frequency transmitter, or an antenna, etc.) coupled with the interface, or a receiver, etc.

[0339] Optionally, if the communication apparatus 130 is a standalone device, the communication interface 1302 can include a receiver and a transmitter. The receiver and the transmitter can be the same component, or different components. When the receiver and the transmitter are the same component, the component can be referred to as a transceiver.

[0340] Optionally, if the communication apparatus 130 is a chip or circuit, the communication interface 1302 can include an input interface and an output interface. The input interface and the output interface can be the same interface, or can be different interfaces.

[0341] Optionally, the functions of the communication interface 1302 can be implemented by a transceiver circuit or a dedicated chip of the transceiver. The processor 1301 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

[0342] (3) The memory 1303 is configured to provide a storage space, in which data such as an operating system and a computer program can be stored. The memory 1303 can be one or a combination of a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a compact disc read-only memory (CD-ROM).

[0343] It is to be understood that the functions and actions of the modules or units in the above-mentioned communication apparatus 130 are merely exemplary.

[0344] Optionally, the processor 1301 can be a processor specially configured to execute the foregoing method (for ease of distinction, referred to as a special-purpose processor), or a processor configured to execute the foregoing method by calling a computer program (for ease of distinction, referred to as a special-purpose processor). Optionally, the at least one processor can include both a special-purpose processor and a general-purpose processor.

[0345] Optionally, in the case where the computing device comprises at least one memory 1303, if the processor 1301 implements the aforementioned method by invoking a computer program, the computer program can be stored in the memory 1303.

[0346] The functional units in the communication apparatus 130 can be configured to implement the steps performed by any one of the first functional entity, the second functional entity and the third functional entity in the aforementioned data obtaining method, such as the method described by any one of the first functional entity, the second functional entity and the third functional entity in the embodiments shown in FIG. 6, FIG. 7, FIG. 8 and FIG. 9.

[0347] The present application provides a chip, comprising: a processor coupled with a memory, the memory being configured to store a program or instructions, when the program or instructions are executed by the processor, causing the first functional entity to perform the method of the first functional entity side in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, and / or causing the second functional entity to perform the method of the first functional entity side in FIG. 6, FIG. 7, FIG. 8 and FIG. 9, and / or causing the computing device to perform the method of the first functional entity side in FIG. 3.

[0348] It should be apparent that the embodiments of the present application can be provided as methods, systems or computer program products. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROMs, optical storage devices, etc.) containing computer usable program code.

[0349] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction devices, which implement the functions specified in one or more flows of the flow chart and / or one or more blocks of the block diagram.

[0350] These computer program instructions can also be loaded into a computer or other programmable data processing apparatus, so that a series of operation steps are performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing apparatus provide steps for implementing the functions specified in one or more flows of the flow chart and / or one or more blocks of the block diagram.

[0351] In the embodiments of this application, the words "exemplary" or "for example" are used to mean "an example of" or "an example, only. Any embodiment or design solution described as "exemplary" or "for example" in this application should not be construed as preferred or advantageous over other embodiments or design solutions. In fact, the use of the words "exemplary" or "for example" is intended to present related concepts in a particular manner.

[0352] In the embodiments of this application, "information", "signal", "message", "channel", and "signaling" can be used interchangeably, and it should be pointed out that their meanings are consistent when their differences are not emphasized. "Of", "corresponding", and "corresponding" can be used interchangeably, and it should be pointed out that their meanings are consistent when their differences are not emphasized.

[0353] In this application, "at least one" refers to one or more, and "multiple" refers to two or more. "At least one of the following" or the like refers to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, and c can be single or multiple. "And / or" describes the association relationship between the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which can represent: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects.

[0354] In addition, unless otherwise stated, the ordinal numbers "first", "second", etc. used in the embodiments of this application are used to distinguish a plurality of objects, and are not used to limit the order, time sequence, priority or importance of the plurality of objects. For example, the first device and the second device are only for ease of description, and do not mean that the structures, importance, etc. of the first device and the second device are different. In some embodiments, the first device and the second device can also be the same device.

[0355] In the above embodiments, the term "when" can be interpreted as meaning "if" or "after" or "in response to determining" or "in response to detecting" according to the context. The above is only an optional embodiment of the present application and is not used to limit the present application. Any modification, equivalent replacement, improvement, etc. within the concept and principle of the present application shall be included in the protection scope of the present application.

[0356] A person of ordinary skill in the art can understand that all or part of the steps of the above embodiments can be completed by hardware or by a program instructing relevant hardware, and the program can be stored in a computer readable storage medium. The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

Claims

1. A data acquisition method, characterized by, The method is applied to a first function entity, and comprises: receiving first request information from a second function entity, the first request information being used for requesting to collect simulation data, the first request information comprising a data type and a collection object; sending second request information to a third function entity according to the first request information, the second request information being used for requesting simulation data of the data type about the collection object; receiving first simulation data of the data type about the collection object from the third function entity; sending the first simulation data to the second function entity.

2. The method of claim 1, wherein, The first request information further comprises first indication information, the first indication information being used for indicating that the collected data is simulation data, or being used for indicating that the collected data comprises simulation data.

3. The method of claim 1, wherein, The first request information is further used for requesting real data.

4. The method of claim 3, wherein, The first request information further comprises second indication information, the second indication information being used for indicating that the collected data comprises simulation data and real data.

5. The method according to claim 3 or 4, characterized in that, The method further comprises: sending third request information to a live network element, the third request information being used for requesting to collect real data of the data type about the collection object; receiving first real data of the data type about the collection object from the live network element; sending the first real data to the second function entity.

6. The method of claim 5, wherein, The first request information further comprises proportion information, the proportion information being used for representing a proportion of real data to simulation data, and the sending of the second request information to the third function entity according to the first request information comprises: determining a quantity of simulation data to be collected according to a quantity of the first real data and the proportion information; sending the second request information to the third function entity, the second request information comprising the quantity of simulation data to be collected.

7. The method according to any one of claims 1 to 6, characterized in that, The first request information further comprises third indication information, the third indication information being used for indicating that a first label is fed back through response information of the first request information, the first label being used for representing simulation data, and the method further comprises: receiving the first label from the third function entity; the sending of the first simulation data to the second function entity comprises: sending the response information to the second function entity, the response information comprising the first simulation data and the first label.

8. The method according to any one of claims 1 to 6, characterized in that, The first request information further comprises third indication information, the third indication information being used for indicating that a first label is fed back through response information of the first request information, the first label being used for representing simulation data, and the method further comprises: generating the first label; the sending of the first simulation data to the second function entity comprises: sending the response information to the second function entity, the response information comprising the first simulation data and the first label.

9. The method according to any one of claims 1 to 8, characterized in that, The sending of the second request information to the third function entity according to the first request information comprises: determining a first instance identifier according to the collection object, the first instance identifier being used for indicating a first instance comprising the collection object in the third function entity; sending the second request information to the third function entity, the second request information comprising the first instance identifier.

10. The method according to any one of claims 1 to 9, characterized in that, The first request information further comprises collection requirement information of the simulation data, and the second request information further comprises the collection requirement information of the simulation data.

11. The method of claim 10, wherein, The collection requirement information of the simulation data comprises one or more of a time window, data distribution information, collection duration or quantity of simulation data, the time window being used to represent collection of data in a specified time period, the data distribution information being used to represent distribution characteristics of the collected data, and the collection duration being used to represent duration of collection of simulation data.

12. The method according to any one of claims 1 to 11, characterized in that, The method further comprises: receiving fourth indication information from the third function entity, the fourth indication information being used to indicate that the third function entity supports collection of simulation data, the fourth indication information comprising a plurality of target parameters, the target parameters comprising one or more of a data type, a collection object, a time window; sending the fourth indication information to the second function entity.

13. The method according to any one of claims 1 to 12, characterized in that, The first function entity is an element management system (EMS), a network management system (NMS), a network element in a radio access network or a network element in a core network. The second function entity is a business support system (BSS) or a network management system (NMS). The third function entity is an element management system (EMS), a network management system (NMS), a network element in a radio access network or a network element in a core network.

14. A data acquisition method characterized by, The method is applied to a second function entity, comprising: sending first request information to a first function entity, the first request information being used to request collection of simulation data, the first request information comprising a data type and a collection object; receiving first simulation data from the first function entity, the first simulation data being simulation data of the data type about the collection object.

15. The method of claim 14, wherein, The first request information further comprises first indication information, the first indication information being used to indicate collection of simulation data or being used to indicate collection of data comprising simulation data.

16. The method of claim 14, wherein, The first request information is further used to request real data.

17. The method of claim 16, wherein, The first request information further comprises second indication information, the second indication information being used to indicate collection of data comprising simulation data and real data.

18. The method of claim 17, wherein, The method further comprises: receiving first real data from the first function entity.

19. The method according to any one of claims 14-18, characterized by, The first request information further comprises third indication information, the third indication information being used to indicate that the first function entity feeds back a first label through response information of the first request information, the first label being used to represent simulation data. The receiving of the first simulation data from the first function entity comprises: receiving response information from the first function entity, the response information comprising the first simulation data and the first label.

20. The method according to any one of claims 14-19, characterized by, The first request information further comprises collection requirement information of simulation data.

21. The method of claim 20, wherein, The collection requirement information of the simulation data comprises one or more of a time window, data distribution information or collection duration, the time window being used to represent collection of data in a specified time period, the data distribution information being used to represent distribution characteristics of the collected data, and the collection duration being used to represent duration of collection of simulation data. The first request information further comprises proportion information, wherein the proportion information is used to represent the proportion of real data and simulation data.

22. The method according to any one of claims 14-21, characterized by, The method further comprises: receiving fourth indication information, wherein the fourth indication information is used to indicate that the third function entity supports simulation data collection, and the fourth indication information comprises a plurality of target parameters, and the target parameters comprise one or more of the following: data type, collection object, time window; determining the target parameters of the simulation data to be collected according to the plurality of target parameters comprised in the fourth indication information.

23. The method according to any one of claims 14-22, characterized by, The first function entity is an element management system (EMS), a network management system (NMS), a network element in a radio access network, or a network element in a core network. The second function entity is a business support system (BSS) or a network management system (NMS). The third function entity is an element management system (EMS), a network management system (NMS), a network element in a radio access network, or a network element in a core network.

24. A data acquisition method, characterized by, The method is applied to a third function entity, and the method comprises: receiving second request information from a first function entity, wherein the second request information is used to request simulation data of the data type about the collection object; sending first simulation data of the data type about the collection object according to the second request information.

25. The method of claim 24, wherein, The second request information comprises a first instance identifier, and the method further comprises: obtaining the first simulation data by collecting simulation data of the data type about the collection object in the instance corresponding to the first instance identifier.

26. The method of claim 24, wherein, The second request information comprises the data type and the collection object, and the method further comprises: determining a first instance according to the collection object; obtaining the first simulation data by collecting simulation data of the data type about the collection object in the first instance.

27. The method of claim 25 or 26, wherein, The second request information further comprises simulation data collection requirement information, and the first simulation data meets the requirement corresponding to the collection requirement information.

28. The method of claim 27, wherein, The simulation data collection requirement information comprises one or more of the following: time window, data distribution information, collection time length, and number of simulation data, wherein the time window is used to represent data collected in a specified time period, the data distribution information is used to represent the distribution characteristics of the collected data, and the collection time length is used to represent the time length of collecting simulation data.

29. The method of claim 24, wherein, The second request information further comprises the number of simulation data to be collected.

30. The method of any one of claims 24-29, wherein, The sending of the first simulation data of the data type about the collection object according to the second request information comprises: sending the first simulation data of the data type about the collection object and a first label, wherein the first label is used to represent simulation data.

31. The method according to any one of claims 24-30, wherein, The method further comprises: sending fourth indication information to the first function entity, wherein the fourth indication information is used to indicate that the third function entity supports simulation data collection, and the fourth indication information comprises a plurality of target parameters, and the target parameters comprise one or more of the following: data type, collection object, time window.

32. The method of any one of claims 24-31, wherein, The first function entity is an element management system (EMS), a network management system (NMS), a network element in a radio access network, or a network element in a core network. The second function entity is a business support system (BSS) or a network management system (NMS); The third function entity is an element management system (EMS), a network management system (NMS), an element in a radio access network, or an element in a core network.

33. A communications device, characterized by Comprising: A first communication unit configured to receive first request information from a second function entity, the first request information being used to request collection of simulation data, the first request information comprising a data type and a collection object; The first communication unit is further configured to send second request information to a third function entity according to the first request information, the second request information being used to request simulation data of the data type about the collection object; The first communication unit is further configured to receive first simulation data of the data type about the collection object from the third function entity; The first communication unit is further configured to send the first simulation data to the second function entity.

34. A communications device, characterized by Comprising: A second communication unit configured to send first request information to a first function entity, the first request information being used to request collection of simulation data, the first request information comprising a data type and a collection object; The second communication unit is further configured to receive first simulation data from the first function entity, the first simulation data being simulation data of the data type about the collection object.

35. A communications device, characterized by Comprising: A third communication unit configured to receive second request information from a first function entity, the second request information being used to request collection of simulation data of a data type about a collection object; The third communication unit is further configured to send first simulation data of the data type about the collection object according to the second request information.

36. A communications device, characterized by Comprising at least one processor and a memory; The memory is configured to store computer instructions; The at least one processor is configured to execute the computer instructions to implement the method of any one of claims 1-13, or implement the method of any one of claims 14-23, or implement the method of any one of claims 24-32.

37. A data acquisition system characterized by, The system comprises a first function entity and a third function entity; The first function entity is configured to implement the method of any one of claims 1-13; The third function entity is configured to implement the method of any one of claims 24-32.

38. The system of claim 37, wherein, The system further comprises a second function entity; The second function entity is configured to implement the method of any one of claims 14-23.

39. A computer-readable storage medium, characterized in that, Comprising: The computer readable storage medium is configured to store instructions or computer programs; when the instructions or the computer programs are executed, the method of any one of claims 1-32 is implemented.

40. A computer program product, characterised in that, Comprising: Instructions or computer programs; When the instructions or the computer programs are executed, the method of any one of claims 1-32 is implemented.

Images