WO2021068959A1 - 数据处理方法和装置 - Google Patents

数据处理方法和装置 Download PDF

Info

Publication number
WO2021068959A1
WO2021068959A1 PCT/CN2020/120318 CN2020120318W WO2021068959A1 WO 2021068959 A1 WO2021068959 A1 WO 2021068959A1 CN 2020120318 W CN2020120318 W CN 2020120318W WO 2021068959 A1 WO2021068959 A1 WO 2021068959A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
collector
management system
network element
message
Prior art date
Application number
PCT/CN2020/120318
Other languages
English (en)
French (fr)
Inventor
李明东
王耀光
王恩博
曹龙雨
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020227015965A priority Critical patent/KR20220079970A/ko
Priority to JP2022521699A priority patent/JP7402321B2/ja
Priority to EP20873754.4A priority patent/EP4044508A4/en
Publication of WO2021068959A1 publication Critical patent/WO2021068959A1/zh
Priority to US17/715,762 priority patent/US11894995B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/022—Multivendor or multi-standard integration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0226—Mapping or translating multiple network management protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • This application relates to communication technology, and in particular to a data processing method and device.
  • the Open Network Automation Platform (ONAP) platform provides a real-time, strategy-driven orchestration automation integrated platform for physical/virtual network functions.
  • Software, network, IT, cloud service providers and developers can use ONAP Deploy new services quickly and automatically, and support full life cycle management.
  • ONAP supports the operation and maintenance management of cross-vendor physical/virtual network functions, and is deployed between the Network Management System (NMS) and the Element Management System (EMS)/Network Element (NE) Space is an optional deployment method.
  • the Software Defined Network Controller (SDNC) in ONAP collects alarms or performance data through the EMS/NE northbound management interface (createMeasurementJob, getAlarmList), and transmits the collected alarms or performance data to ONAP data consumers ( Consumer), the ONAP Consumer can be an NMS or ONAP big data analysis engine or other data consumers.
  • NMS Network Management System
  • EMS Element Management System
  • NE Network Element
  • SDNC Software Defined Network Controller
  • the alarm or performance data transmitted to ONAP Consumer is the data reported by different manufacturers, different types of network elements, and different network element versions.
  • the data protocol and data format of the data reported by different manufacturers, different types of network elements, and different network element versions are all. There are large differences, resulting in low efficiency of ONAP Consumer's analysis or use of alarms or performance data.
  • This application provides a data processing method and device to improve the analysis or use efficiency of the reported data.
  • this application provides a data processing method.
  • the method includes: receiving data description information and reported data.
  • the data description information includes manufacturer name, network element version information, and data types or encoding methods supported by the network management system. At least one item.
  • the reported data is converted according to the data description information, and the converted reported data meets the VES specification of the virtual network function event stream. Send a VES event, the VES event includes the reported data after conversion.
  • the reported data is converted into a VES event that meets the VES specification, which can realize automatic data conversion, so that the data consumer (for example, ONAP Consumer) module can directly use the converted The reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • the data consumer for example, ONAP Consumer
  • the data description information and the reported data come from at least one of a collector or a software-defined network controller SDNC.
  • the collector includes a file collector, a stream collector, and a simple network management protocol (Simple Network Management Protocol). At least one of Network Management Protocol, SNMP) trap collector or VES collector.
  • SNMP Network Management Protocol
  • the method may further include: receiving a first message sent by the collector, the first message including the identification information of the collector and the support of the collector.
  • the context of the collector is created according to the first message, and the context includes the identification information of the collector, the data type supported by the collector, the encoding mode supported by the collector, and the address of the collector.
  • the first message can be sent after the collector is online, and the data mapping processing function module can create the context of the collector based on the first message, so that the online collector can be managed uniformly for subsequent business with SDNC Capacity negotiation.
  • the method may further include: sending a sixth message to the collector, where the sixth message includes the identification information of the collector and the registration result.
  • converting the reported data according to the data description information includes: determining the corresponding data according to the data description information Data conversion template.
  • the data mapping module is used to convert the reported data into VES events conforming to VES specifications. Convert the reported data according to the data conversion template.
  • the method may further include: receiving a seventh message sent by the SDNC, where the seventh message is used to create, update, or delete the data conversion template.
  • the seventh message includes at least one of manufacturer name, network element version information, data type or encoding method, and data template information.
  • the method may further include: receiving a second message sent by the SDNC, where the second message is used to indicate a data collection requirement. According to the second message and the context, it is determined whether there is a collector that meets the data collection requirement. Send a third message to the SDNC, where the third message is used to indicate the information of the collector that meets the data collection requirements.
  • the second message includes at least one of a reporting mode, a data type supported by the network management system, or an encoding mode supported by the network management system.
  • the third message when the collector meeting the data collection requirement is a file collector or a VNF event stream collector, the third message includes the identification information of the collector.
  • the third message when the collector meeting the data collection requirement is a stream collector or an SNMP trap collector, the third message includes at least one of the identification information of the collector or the address of the collector.
  • the data description information includes the data type, and performing data conversion on the reported data according to the data description information may include: The elements included in the data are added or deleted.
  • the reported data includes at least one of file data, stream data, alarm data, VES events, or character data.
  • an embodiment of the present application provides a data processing method.
  • the method may include: a collector receiving data description information.
  • the collector sends the data description information and the reported data to the data mapping processing function module.
  • the data description information includes at least one of the manufacturer's name, network element version information, and data types or encoding methods supported by the network management system.
  • the method may further include: the collector sends a first message to the data mapping processing function module, and the first message includes the identification information of the collector, the collection The data type supported by the collector, the encoding method supported by the collector, and the address of the collector.
  • the collector is a file collector
  • the reported data is file data
  • the collector receives data description information, including: the file collector receives the fourth message sent by the software-defined network controller SDNC, the The fourth message includes file information and the data description information, and the file information is used to indicate the location of the file data.
  • the file collector downloads the file data from the corresponding location according to the file information.
  • the collector is a stream collector
  • the reported data is stream data
  • the collector receives data description information, including: the stream collector establishes a transmission control protocol with the network element or the network element management system (Transmission Control Protocol). Control Protocol, TCP) connection.
  • TCP Transmission Control Protocol
  • the stream collector receives stream data and data description information through a TCP connection.
  • the collector is an SNMP trap collector
  • the reported data is character data
  • the collector receives data description information, including: the SNMP trap collector receives the fifth message sent by SDNC, and the fifth message Including data description information and Management Information Base (MIB) data; the SNMP trap collector receives alarm data sent by the network element or the network element management system; the SNMP trap collector decodes the alarm data into character data according to the MIB data.
  • MIB Management Information Base
  • the collector is a VES collector
  • the reported data is a VES event
  • the collector receives data description information, including: the VES collector receives the VES event and data description sent by the network element or the network element management system Information, the data description information includes data types supported by the network management system.
  • an embodiment of the present application provides a data processing method.
  • the method may include: receiving a data collection request message sent by a software-defined network controller SDNC.
  • the data collection request message includes a reporting method, a collection period, and network management system support. At least one of the data type or the encoding method supported by the network management system; collect the reported data according to the data collection request message. For example, at least one of file data, stream data, alarm data, VES event, or character data.
  • the method may further include: establishing a TCP connection with the flow collector; sending flow data and data description information to the flow collector through the TCP connection, the data description information including the manufacturer name and network element version information , At least one of the data type or encoding method supported by the network management system.
  • the method may further include: sending MIB data to the SDNC, where the MIB data is used to decode the alarm data.
  • the method may further include: sending VES events and data types supported by the network management system to the VES collector.
  • an embodiment of the present application provides a data processing method.
  • the method may include: receiving a service request message sent by a network management system, where the service request message includes a reporting method, a data type supported by the network management system, or the network management system At least one of the supported encoding methods; sending a first capability negotiation message to the network element or the network element management system, and the first capability negotiation message is used to trigger the network element or the network element management system to feedback whether the reporting method and the data type are supported Or at least one of the encoding methods; according to the feedback of the network element or the network element management system, send a data collection request message to the network element or the network element management system.
  • the service request message further includes an object list, the object list is used to indicate at least one network element, and the network element management system is used to manage one or more of the at least one network element.
  • the service request message further includes an object list
  • the object list is used to indicate at least one network element
  • the network element management system is used to manage one or more of the at least one network element
  • the The method further includes: parsing the object list to obtain identification information; sending a first capability negotiation message to a network element or a network element management system, including: sending a first capability negotiation message to a network element or a network element management system corresponding to the identification information.
  • an embodiment of the present application provides a data processing method.
  • the method may include: receiving a first capability negotiation message sent by a software-defined network controller SDNC, where the first capability negotiation message is used to trigger network element or network element management
  • the system feedbacks whether it supports at least one of the reporting method of the network management system, the data type or the encoding method supported by the network management system; the feedback result is sent to SDNC, and the feedback result is used to indicate whether the reporting method of the network management system and the network management system are supported At least one of the supported data types or encoding methods.
  • the first capability negotiation message includes a reporting mode, data type, encoding mode, and an object list
  • the object list is used to indicate at least one network element
  • the network element management system is used to manage the at least one network element
  • the method may further include: parsing the object list to obtain identification information; obtaining, according to the identification information, whether the network element or the network element management system supports the reporting method, the data type and code of the network management system the way.
  • an embodiment of the present application provides a data processing device, which has the function of implementing the method in the first aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions, for example, a transceiver unit or module, and a processing unit or module.
  • an embodiment of the present application provides a collector, which has the function of implementing the method of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions, for example, a transceiver unit or module, and a processing unit or module.
  • an embodiment of the present application provides a data processing device that has the function of implementing the method of the third aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions, for example, a transceiver unit or module, and a processing unit or module.
  • an embodiment of the present application provides a software-defined network controller, which has the function of implementing the method of the fourth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions, for example, a transceiver unit or module, and a processing unit or module.
  • an embodiment of the present application provides a data processing device that has the function of implementing the method of the fifth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions, for example, a transceiver unit or module, and a processing unit or module.
  • the present application provides a data processing device, including: one or more processors; a memory for storing one or more programs; when the one or more programs are processed by the one or more The processor executes, so that the one or more processors implement the method described in any one of the foregoing first aspect, or the one or more processors implement the method described in any one of the foregoing second aspect
  • the method, or the one or more processors are caused to implement the method according to any one of the above-mentioned third aspect, or the one or more processors are caused to implement the method according to any one of the above-mentioned fourth aspects
  • the method described above, or the one or more processors are caused to implement the method described in any one of the above fifth aspects.
  • the present application provides a computer-readable storage medium, including a computer program, which when executed on a computer, causes the computer to execute the method described in any one of the above-mentioned first aspects, or , Causing the computer to execute the method according to any one of the above second aspects, or causing the computer to execute the method according to any one of the above third aspects, or causing the computer to execute the above fourth aspect
  • the method according to any one of the above, or the computer is caused to execute the method according to any one of the above fifth aspects.
  • the present application provides a computer program product, which includes instructions, when the instructions are executed by a computer, they are used to execute the method described in any one of the first aspects above, or to Performing the method according to any one of the above-mentioned second aspects, or for performing the method according to any one of the above-mentioned third aspects, or, for performing the method according to any one of the above-mentioned fourth aspects, Or, used to execute the method described in any one of the above fifth aspects.
  • the present application provides a chip including a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the first
  • the method of any one of the above aspects, or the method of any one of the above-mentioned second aspects, or the method of any one of the above-mentioned third aspects, or the execution of the above-mentioned fourth aspect The method of any one of the above, or the method of any one of the fifth aspects above is executed.
  • embodiments of the present application provide a data processing system, which may include a data mapping processing function module, at least one collector, SDNC, and a network element or a network element management system.
  • the data mapping processing function module can execute the method described in any one of the above-mentioned first aspect
  • any collector can execute the method described in any one of the above-mentioned second aspect
  • the network element or the network element management system can execute the above-mentioned method.
  • the SDNC may execute the method described in any one of the fourth aspect above.
  • the data processing method and device of the present application send data description information and reported data to the data mapping processing function module through the collector.
  • the data description information may include the name of the manufacturer, the version information of the network element, the data type or the network supported by the network management system At least one of the encoding methods supported by the management system, the data mapping processing function module converts the reported data according to the data description information, the converted reported data meets the VES specification, and the data mapping processing function module sends VES events to the data consumer module
  • the VES event includes the converted reported data, which can convert the reported data from different sources (for example, different vendors, different types of network elements, and different network element versions) into data that meets the VES specifications, so that data consumers ( For example, the ONAP (Consumer) module can directly use the converted reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the application
  • FIG. 2 is a flowchart of a data processing method according to an embodiment of the application
  • FIG. 3 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 4 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 5 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 6 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 7 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 8 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 9 is a flowchart of a data processing method according to an embodiment of the application.
  • FIG. 10 is a schematic block diagram of a data processing device 900 according to an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of a data processing device 1000 according to an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of a collector 1100 according to an embodiment of the application.
  • FIG. 13 is a schematic structural diagram of a collector 1200 provided by an embodiment of the application.
  • FIG. 14 is a schematic structural diagram of a data processing device 1300 provided by an embodiment of the application.
  • FIG. 15 is a schematic structural diagram of a data processing device 1400 according to an embodiment of the application.
  • FIG. 16 is a schematic structural diagram of a software-defined network controller 1500 provided by an embodiment of the application.
  • FIG. 17 is a schematic structural diagram of a software-defined network controller 1600 provided by an embodiment of this application.
  • At least one (item) refers to one or more, and “multiple” refers to two or more.
  • “And/or” is used to describe the association relationship of associated objects, indicating that there can be three types of relationships, for example, “A and/or B” can mean: only A, only B, and both A and B , Where A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a) or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a, b, or c can mean: 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.
  • Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the application.
  • the system architecture may include NMS, ONAP, EMS/NE, and consumers.
  • the user may be an NMS, an analysis application (Analytic Applications), or an electronic computing platform (Electronic Computing Platform, TCA).
  • ONAP can include SDNC and data collection, analysis, and events (Data Collection, Analytics, and Events, DCAE) modules.
  • the DCAE module can include data mapping processing function module (Data Mapper), mapping template database function module (Mapper catalog) and various types of collectors, for example, VES collector (VES Collector), file collector (File Collector), stream Collector (Stream Collector), or SNMP Trap Collector (SNMP Trap Collector), etc.
  • VES collector VES Collector
  • File Collector file collector
  • Stream Collector stream Collector
  • SNMP Trap Collector SNMP Trap Collector
  • SDNC collects performance data or alarm data through the northbound management interface of the EMS/NE, such as an interface used to create a measurement task (createMeasurementJob) and an interface used to obtain an alarm list (getAlarmList).
  • Network Function Virtualization Network Function Virtualization
  • NFV Network Function Virtualization
  • the NE can be used as a core network element, such as an MME, or as an access network element, such as a base station (gNB) in 5G.
  • MME mobile phone
  • gNB base station
  • Each NE can flexibly deploy computing hardware, storage hardware and/or network hardware in the sub-hardware resource layer through one or more virtual network functions (VNF).
  • VNF virtual network functions
  • EMS can manage multiple NEs, and each EMS can correspond to a vendor (Vendor).
  • ONAP is connected to EMS/NEs of different vendors.
  • HTTP server corresponds to vendor X
  • VES client corresponds to Vendor A
  • File Transfer Service FTP Server
  • SNMP Trap Agent corresponds to Vendor B
  • GRPC corresponds to Vendor C.
  • the data protocol and data format of data reported by different vendors, different types of network elements, and different network element versions are quite different.
  • the following data processing methods in the embodiments of this application can improve ONAP Consumer’s response to alarms or performance data. For analysis or use efficiency, the specific implementation can be found in the explanation of the following embodiments.
  • the data mapping processing function module, collector, SDNC, etc. in the system shown in FIG. 1 are only a name, and the name does not constitute a limitation on the function module itself.
  • the entities corresponding to the data mapping processing function module, the collector, and the SDNC may have other names, which are not specifically limited in the embodiment of the present application.
  • Fig. 2 is a flowchart of a data processing method according to an embodiment of the application. As shown in Fig. 2, this embodiment relates to a data mapping processing function module, a collector, and a data consumer module.
  • the data consumer module may be, for example, an NMS , Or analysis application, or TCA, or ONAP big data analysis engine, etc., the method of this embodiment may include:
  • Step 101 The collector sends data description information and reported data to the data mapping processing function module.
  • the data mapping processing function module receives the data description information and the reported data sent by the collector.
  • the data description information may include at least one of a vendor name (Vendor name), network element version information (NE version), a data type (Domain type) supported by the network management system, or an encoding method (Supported datatype) supported by the network management system.
  • the vendor name (Vendor name) is used to uniquely identify a vendor.
  • the vendor A mentioned above can understand that the vendor name may also be an identity document (ID).
  • ID For example, the ID of vendor A is 0000001.
  • the network element version information (NE version) is used to indicate the software version of the NE corresponding to the reported data, and the NE corresponding to the reported data may be the NE that generated the reported data.
  • the data type (Domain type) supported by the network management system represents the data type supported by the NMS.
  • the data type supported by the NMS can be the data type initiated by the NMS to create the task, for example, fault, measurement, 3GPP alarm (fault3gpp), 3GPP performance data (perf3gpp), etc.
  • the encoding method (Supported datatype) supported by the network management system indicates the file format/encoding method supported by the NMS, for example, Extensible Markup Language (XML), JavaScript Object Notation (JSON), or the same Three kinds of markup languages (Yet Another Markup Language, YAML), Google Mixed Language Data Standard (Google Protocol Buffers, GPB), Abstract Syntax Notation One (ASN.1), etc.
  • XML Extensible Markup Language
  • JSON JavaScript Object Notation
  • YAML Three kinds of markup languages
  • Google Mixed Language Data Standard Google Protocol Buffers, GPB
  • ASN.1 Abstract Syntax Notation One
  • the collector sends the data description information and the reported data to the data mapping processing function module through the data transmission interface with the data mapping processing function module.
  • the data description information and the reported data come from NE/EMS, For example, from the above FTP Server.
  • NE/EMS can generate the reported data based on the data collection service triggered by the NMS.
  • the service request message can carry the data description information and report it to the collector.
  • the collector sends the data description information and the reported data to the data mapping process. functional module.
  • Step 102 The data mapping processing function module converts the reported data according to the data description information, and the converted reported data meets the VNF Event Streaming (VES) specification.
  • VFS VNF Event Streaming
  • the reported data comes from EMS/NEs of different manufacturers, different types of network elements, different network element versions, or different data management fields (such as performance, alarms, logs), etc., and their data protocols or data formats are quite different.
  • the reported data can be converted through the data mapping processing function module of the embodiment of the application, so that the converted reported data meets the VES specification, for example, the Multi-Vendor VES specification, which is 3GPP data The standard specification of the reporting format.
  • Step 103 The data mapping processing function module sends a VES event to the data consumer module, where the VES event includes the converted and reported data.
  • the data protocol or data format of the reported data sent to the data consumer module can be made into a unified specification.
  • the data consumer module After the data consumer module receives the converted reported data, it does not need to perform Preprocessing can be used directly, for example, for data analysis and aggregation.
  • the data description information and the reported data are sent to the data mapping processing function module through the collector.
  • the data description information may include the name of the manufacturer, the version information of the network element, the data type supported by the network management system, or the code supported by the network management system.
  • the data mapping processing function module converts the reported data according to the data description information, and the converted reported data meets the VES specification, and the data mapping processing function module sends a VES event to the data consumer module.
  • the VES event includes
  • the converted reported data can convert the reported data from different sources (for example, different vendors, different types of network elements, and different network element versions) into data that meets the VES specification, thereby enabling data consumers (for example, ONAP Consumer)
  • the module can directly use the converted reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • step 102 in the embodiment of the present application is that the data mapping processing function module determines the corresponding data conversion template according to the data description information, and the data mapping processing function module converts the reported data according to the data conversion template.
  • the later reported data meets the virtual network function event stream (VNF Event Streaming, VES) specification.
  • the data conversion template may be a parameter conversion rule, for example, a mapping relationship.
  • the parameter A corresponds to the parameter A', that is, the parameter A in the reported data is converted to the parameter A'according to the data conversion template.
  • the data mapping processing function module can be stored in the mapping template database function module (Mapper catalog) in Figure 1 above, and the mapping template database function module (Mapper catalog) can be co-located with the data mapping processing function module (Data Mapper). It can be set separately from the data mapping processing function module (Data Mapper), and the embodiment of the present application takes the separate set as an example for illustration, which is not limited by this.
  • the data mapping processing function module may send data description information to the mapping template database function module, the mapping template database function module obtains the corresponding data conversion template according to the data description information, and sends the data conversion template to the data mapping processing function module,
  • the data mapping processing function module converts the reported data according to the data conversion template, so that the converted and reported data conforms to the VES specification.
  • map template database function module Mapper catalog
  • Mapper catalog For the data conversion template in the map template database function module (Mapper catalog), it can be online/updated/deleted by the method of the embodiment shown in FIG. 3 below.
  • FIG. 3 For specific explanation, please refer to the following embodiment.
  • Fig. 3 is a flowchart of a data processing method according to an embodiment of the application. As shown in Fig. 3, this embodiment relates to NMS, SDNC, and Mapper catalog. The method of this embodiment may include:
  • Step 201 The NMS sends a first service request message to the SDNC, where the first service request message is used to create, update or delete a data conversion template.
  • the NMS receives the first service request message sent by the SDNC.
  • the first service request message may carry a parameter list (Parameterlist), for example, vendor name (Vendor name), network element version information (NE version), data type (Domain type), or encoding method (Supported datatype). At least one item, and corresponding data template information (templateinfo), where the data template information (templateinfo) is used to indicate the aforementioned data conversion template.
  • the first service request message may also carry type indication information.
  • the type indication information may be two bits. For example, 00 is used to indicate the creation of a data conversion template, 01 is used to indicate to update the data conversion template, and 10 is used to indicate deletion of data conversion. template.
  • Step 202 The SDNC sends a seventh message to the mapping template database function module (Mapper catalog), where the seventh message is used to create, update, or delete a data conversion template.
  • Mapper catalog mapping template database function module
  • the corresponding mapping template database function module receives the seventh message sent by the SDNC.
  • the seventh message may carry various information carried in the above-mentioned first service request message, for example, vendor name (Vendor name), network element version information (NE version), data type (Domain type), or encoding method At least one item in (Supported datatype) and the corresponding data template information (templateinfo).
  • Step 203 The mapping template database function module (Mapper catalog) creates, updates or deletes the data conversion template according to the seventh message.
  • the mapping template database function module can establish a vendor name (Vendor name), network element version information (NE version), and data according to the seventh message. Correspondence between at least one of the type (Domain type) or the encoding method (Supported datatype) and the data conversion template.
  • the mapping template database function module can establish the vendor name (Vendor name), network element version information (NE version), and data type (Domain type) according to the seventh message.
  • mapping template database function module can establish the vendor name (Vendor name), network element version information (NE version), and data type (Domain type) according to the seventh message.
  • the mapping template database function module can establish the vendor name (Vendor name), network element version information (NE version), and data type (Domain type) according to the seventh message.
  • the encoding method (Supported datatype), match and find the corresponding data conversion template, and delete the corresponding data conversion template.
  • the data type can be alarm (fault), measurement (measurement), 3GPP alarm (fault3gpp), 3GPP performance data (perf3gpp), and so on.
  • the encoding method can be Extensible Markup Language (XML), JavaScript Object Notation (JSON), Still Another Markup Language (YAML), Google Hybrid Language data standards (Google Protocol Buffers, GPB), Abstract Syntax Notation One (ASN.1), etc.
  • Step 204 The mapping template database function module (Mapper catalog) sends a notification message to the SDNC, where the notification message is used to indicate the result of the creation, update, or deletion of the data conversion template.
  • Mapper catalog The mapping template database function module
  • the SDNC receives the notification message sent by the mapping template database function module (Mapper catalog).
  • the notification message can be used to indicate that the creation, update, or deletion of the data conversion template is successful, or it can be used to indicate that the creation, update, or deletion of the data conversion template fails.
  • the NMS sends a first service request message to the SDNC.
  • the first service request message is used to create, update, or delete a data conversion template.
  • the SDNC sends a seventh message to the Mapper catalog. Messages are used to create, update or delete data conversion templates, the mapping template database function module (Mapper catalog) creates, updates or deletes data conversion templates according to the seventh message, and the mapping template database function module (Mapper catalog) sends notification messages to SDNC,
  • the notification message is used to indicate the result of the creation, update, or deletion of the data conversion template, and realize the creation, update, or deletion of the data conversion template.
  • collectors there are many types of collectors in the embodiment of the present application, for example, VES collectors (VES Collector), file collectors (File Collector), stream collectors (Stream Collector), or SNMP Trap collectors SNMP Trap Collector, etc., and different collectors support different network protocols and/or encoding methods. Therefore, when each collector is successfully deployed (deploy), the collector needs to send its attribute capability information to the data mapping processing function module, and the data mapping processing function module uniformly manages all collectors.
  • VES Collector VES collectors
  • File Collector file collectors
  • Stream Collector stream collectors
  • SNMP Trap collectors SNMP Trap Collector
  • the attribute capability information can be The identification information of the collector (for example, the name of the collector (Collector name)), the data type supported by the collector (Domain type), the encoding method supported by the collector (Supported-datatype), and the address of the collector (Target address), etc. .
  • the data mapping processing function module can feed back results to the SDNC based on the attribute capability information of the collector.
  • the attribute capability information of the collector in the data mapping processing function module can also be deleted through the related process.
  • Fig. 4 is a flowchart of a data processing method according to an embodiment of the application. As shown in Fig. 4, this embodiment relates to a collector and a data mapping processing function module.
  • the collector may be a VES collector, a file Collector (File Collector), Stream Collector (Stream Collector), or SNMP Trap Collector (SNMP Trap Collector), etc.
  • the method of this embodiment may include:
  • Step 301 The collector completes online deployment based on ONAP's current functional module deployment mechanism OOM.
  • Step 302 The collector sends a first message to the data mapping processing function module.
  • the data mapping processing function module receives the first message sent by the collector.
  • the first message is used to notify the collector of the successful online.
  • the first message may include the attribute capability information of the collector, and the attribute capability information may include the identification information of the collector, the data type supported by the collector, the encoding mode supported by the collector, and the address of the collector.
  • the data mapping processing function module may be a data mapping processing function module configured in the collector to manage the collector. For example, when the collector is deployed, the collector will be configured to manage the information of the data mapping processing function module of the collector.
  • the information of the data mapping processing function module may be the IP address of the data mapping processing function module (Data Mapper IP address), etc. After the collector goes online, it can send the first message to the data mapping processing function module indicated by the IP address.
  • the first message may also adopt other message names, for example, collector register request message (Collector register request), etc.
  • the message name is not limited by this.
  • Step 303 The data mapping processing function module creates the context of the collector according to the first message.
  • the context may include the identification information of the collector, the data type supported by the collector, the encoding method supported by the collector, and the address of the collector and other attribute capability information as described above.
  • Step 304 The data mapping processing function module sends a sixth message to the collector.
  • the collector receives the sixth message sent by the data mapping processing function module.
  • the sixth message may include the identification information and the registration result of the collector, or may include the registration result of the collector.
  • the registration result may be acceptance of registration. (Registration-accept), Registration-reject, Error, etc.
  • the secretary mapping module After the secretary mapping module successfully creates a context for the collector through step 303, it can send a sixth message indicating acceptance of registration to the collector.
  • the sixth message may also adopt other message names, for example, collector registration response message (Collect register response), registration response message, etc.
  • collector registration response message Cold register response
  • registration response message etc.
  • the message name is not limited by this.
  • the implementation principle is similar to the registration process of the collector online. For example, when it needs to go offline, send the collector de-registration request message to the data mapping processing function module, and the collector de-registers the request The message is used to instruct the data mapping processing function module to delete the context of the collector.
  • the data mapping processing function module deletes the context of the collector according to the collector de-registration request message, and sends a de-registration response message to the collector, for example, de-register The response message is used to indicate acceptance to register.
  • the collector when the collector is online or offline, a corresponding message is sent to the data mapping processing function module, and the data mapping processing function module creates or deletes context according to the message, so that in the dynamic and flexible deployment process of the collector,
  • the data mapping processing function module can obtain the online collectors and their attribute capability information in time.
  • the data mapping processing function module manages each collector in a unified manner. In the subsequent business capability negotiation process with SDNC, it can be based on the attribute capability information of each collector Decide on data collection and conversion capabilities to provide data collection services that meet the needs.
  • the collector as a file collector as an example, the data processing method in the embodiment of the present application will be described as an example.
  • FIG. 5 is a flowchart of a data processing method according to an embodiment of the application. As shown in FIG. 5, this embodiment involves NMS, SDNC, EN/EMS, File Collector, data mapping processing function module, mapping Template database function module (Mapper catalog) and data consumer module, the method of this embodiment may include:
  • Step 401 The NMS sends a second service request message to the SDNC.
  • the SDNC receives the second service request message sent by the NMS.
  • the second service request message is used to create a data collection service, so that the collector completes the data collection reported by different transmission protocols and/or data formats, and the data mapping processing function module completes the reported data from different data sources to those that meet the VES specifications. Conversion.
  • the second service request message includes at least one of a reporting method (reporting method) supported by the NMS, a data type supported by the NMS, or an encoding method supported by the NMS.
  • a reporting method reporting method
  • the data type supported by the NMS and the encoding method supported by the NMS may be the same as the data type supported by the NMS and the encoding method supported by the NMS in step 101 of the embodiment shown in FIG. No longer.
  • the reporting method supported by the NMS is used to indicate file reporting or stream reporting.
  • the second service request message may further include an object list, the object list is used to indicate at least one network element, and the network management system is used to manage one or more of the at least one network element, for example, the object
  • the list includes an object class list (IOC class list) and an object class instance list (IOC instance list).
  • the object class list may be an information object class (iOC) object list (InstanceList).
  • the iOC object instance list is used to indicate one or more managed object instances (managed object instances), one or more managed object instances correspond to one NE, and the EMS can manage one or more NEs.
  • the reporting mode supported by the NMS, the data type supported by the NMS, or the coding mode supported by the NMS may be the reporting mode, data type, or coding mode supported by the data consumer module.
  • the data conversion template can also be saved in the mapping template database function module during the onboarding of the NE, for example, as shown in step 0 of FIG. 5, the dotted line of step 0
  • the box indicates that the order of execution is not limited by the sequence number and the upper and lower figures of the figure, and the implementation manner may include each step of the embodiment shown in FIG. 3, and its specific explanation and description will not be repeated here.
  • Step 4021a SDNC sends a first capability negotiation message to NE/EMS.
  • the NE/EMS receives the first capability negotiation message sent by the SDNC.
  • the first capability negotiation message is used to trigger the NE/EMS to feed back whether it supports at least one of the reporting mode, data type, or encoding mode carried in the second service request message. That is, the SDNC initiates capability negotiation to the NE/EMS based on the reporting mode, data type, and/or coding mode in step 401.
  • the first capability negotiation message may include one or more of a data type supported by the NMS, an encoding method supported by the NMS, or a reporting method (reporting method) supported by the NMS.
  • the first capability negotiation message may also include an object class list (IOC class list) and an object class instance list (IOC instance list).
  • Step 4022a The NE/EMS parses the object class list (IOC class list) and the object class instance list (IOC instance list) to obtain identification information.
  • the identification information is an ID list of NE
  • the ID list of the NE may include the IDs of one or more network elements.
  • Step 4023a NE/EMS sends a first response message to SDNC.
  • the SDNC receives the first response message sent by one or more NE/EMS.
  • the first response message is used to indicate whether each NE corresponding to the ID list of the NE supports the data type, encoding mode, and/or reporting mode.
  • the first response message carries the NE ID and confirmation information, and the confirmation information is used to indicate ACK, which means that the NE corresponding to the NE ID supports the data type and encoding method.
  • the first response message may carry the NE ID and non-acknowledgement information, and the non-acknowledgement information is used to indicate NACK.
  • step 4023a When there is an NE that does not support the data type or encoding method, after step 4023a is executed, step 407 can be executed. When there is an NE that supports the data type or encoding method, after step 4023a is executed, step 408 may be executed.
  • Step 4021b The SDNC parses the object class list (IOC class list) and the object class instance list (IOC instance list) to obtain identification information.
  • step 4022a For the specific explanation of the identification information, please refer to the explanation of step 4022a, which will not be repeated here.
  • Step 4022b SDNC sends a first capability negotiation message to NE/EMS.
  • the first capability negotiation message in step 4022b does not include the object class list (IOC class list) and the object class instance list (IOC instance list), but includes the NE ID list.
  • the ID list of the NE may include the IDs of one or more network elements, and the NE/EMS queries whether the corresponding NE supports the data type, encoding method, and/or reporting method according to the NE ID list.
  • Step 4023b NE/EMS sends a first response message to SDNC.
  • step 4023b please refer to the explanation of step 4023a, which will not be repeated here.
  • step 4021a to 4023a can confirm whether the NE/EMS supports the data type and encoding method in step 401.
  • step 4021a to step 4023a may be executed, or step 4021b to step 4023b may be executed.
  • the dashed frame from step 4021a to step 4023a in FIG. 5, and the dashed frame from step 4021b to step 4023b indicate optional.
  • Step 403 The SDNC sends a second message to the data mapping processing function module.
  • the data mapping processing function module receives the second message sent by the SDNC.
  • the second message is used to indicate data collection requirements.
  • the second message may include at least one of the data type, encoding method, or reporting method in step 401.
  • the SDNC queries whether the collector supports the corresponding data type, encoding method or reporting method.
  • the reporting method may be a reporting method (reportingMethod) supported by the NMS, for example, stream reporting or file reporting.
  • Step 404 The data mapping processing function module determines whether there is a collector that meets the data collection requirement according to the second message and the context.
  • the data mapping processing function module is based on the context of each collector stored locally, for example, through the context created in the embodiment shown in FIG. 4, it queries whether there is a corresponding collector and whether the collector supports data types and encoding methods.
  • Step 405 The data mapping processing function module sends a third message to the SDNC.
  • the SDNC receives the third message sent by the data mapping processing function module.
  • the third message is used to indicate the information of the collector that meets the data collection requirement.
  • the third message may include the target address and result of the collector, or the identification information and result of the collector, or the target address, identification information and result of the collector, and the result may be used to indicate an ack or non-acknowledgement ( nack).
  • nack ack or non-acknowledgement
  • step 406 is executed.
  • step 407 may be executed.
  • Step 406 SDNC feeds back failure information to NMS.
  • Step 407 SDNC sends a data collection request message to NE/EMS.
  • NE/EMS receives the data collection request message sent by SDNC.
  • the data collection request message may include at least one of a reporting mode, a collection period (granularityPeriod), a data type supported by the network management system, or an encoding mode supported by the network management system.
  • SDNC creates performance measurement tasks, carrying at least one of the reporting method, the acquisition period (granularityPeriod), the data type supported by the network management system, or the encoding method supported by the network management system. NE/EMS will return confirmation after receiving the task. .
  • SDNC initiates a configuration request to NE/EMS, carrying at least one of the reporting method, acquisition period (granularityPeriod), data type supported by the network management system, or encoding method supported by the network management system, and configure the reporting method of alarm data reporting , NE/EMS returns a confirmation message after receiving the configuration request.
  • the data collection request message can be sent to the NE/ which has passed the above steps 4021a to 4023a, or the above steps 4021b to 4023b, and feeds back the reporting method, data type and/or encoding method in step 401.
  • EMS EMS.
  • Step 408 The NE/EMS periodically sends a file preparation notification message to the SDNC according to the data collection request message.
  • the file preparation notification message can carry parameters such as file information list (FileinfoList), vendor name (Vendorname), network element version information (NEversion), among which, the file information list (FileinfoList) may include file location (fileLocation), file size (fileSize), etc. ), file preparation time (fileReadyTime), file expiration time (fileExpirationTime), file compression (fileCompression), file format (fileFormat) and other information.
  • FileinfoList file information list
  • vendor name Vendorname
  • NEversion network element version information
  • the file information list (FileinfoList) may include file location (fileLocation), file size (fileSize), etc. ), file preparation time (fileReadyTime), file expiration time (fileExpirationTime), file compression (fileCompression), file format (fileFormat) and other information.
  • Step 409 SDNC sends a fourth message to the file collector.
  • the file collector receives the fourth message sent by SDNC.
  • the fourth message may include file information and data description information.
  • the file information is used to indicate various parameters in step 408.
  • the data description information may include various information described in step 101 of the embodiment shown in FIG. 2. Its specific explanation will not be repeated here.
  • Step 410 The file collector downloads the reported data from the corresponding location according to the file information.
  • the reported data comes from NE/EMS.
  • the reported data can be file data.
  • Step 411 The file collector sends the data description information and file data to the data mapping processing function module.
  • Step 412 The data mapping processing function module sends a request template message to the mapping template database function module.
  • the request template message may carry the data description information.
  • Step 413 The mapping template database function module matches a suitable data conversion template according to the data description information, and feeds back a matching result to the data conversion template.
  • the matching result may include a data conversion template, or information used to indicate that there is no suitable data conversion template.
  • the data conversion template please refer to the explanation of the embodiment shown in FIG. 3, which will not be repeated here.
  • Step 414 The data mapping processing function module converts the file data according to the data conversion module, and the converted file data meets the VES specification.
  • the data mapping processing function module When the data mapping processing function module receives the data conversion template fed back by the mapping template database function module, the data mapping processing function module converts the above-mentioned file data through step 414, and then executes the following step 416.
  • the data mapping processing function module receives the feedback from the mapping template database function module that there is no suitable data conversion template, the following step 415 is executed to convert the above-mentioned file data.
  • Step 415 The data mapping processing function module sends a data conversion failure message to the SDNC.
  • the data conversion failure message is used to indicate that an error occurred in the data conversion.
  • Step 416 The data mapping processing function module sends a VES event to the data consumer module, where the VES event includes the converted file data.
  • data reported from different sources can be converted into data that meets the VES specification, so that the data consumer (for example, ONAP Consumer) module can directly Use the converted reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • the data consumer for example, ONAP Consumer
  • Fig. 6 is a flowchart of a data processing method according to an embodiment of the application. As shown in Fig. 6, this embodiment relates to NMS, SDNC, EN/EMS, Stream Collector, data mapping processing function module, and mapping Template database function module (Mapper catalog) and data consumer module, the method of this embodiment may include:
  • Step 501 The NMS sends a second service request message to the SDNC.
  • step 501 For the specific implementation of step 501, refer to step 401 of the embodiment shown in FIG. 5, which will not be repeated here.
  • Step 502 Confirm whether the NE/EMS supports the data type and encoding method in step 501.
  • step 502 may adopt steps 4021a to 4023a of the embodiment shown in FIG. 5, or steps 4021b to 4023b, which will not be repeated here.
  • Step 503 The SDNC sends a second message to the data mapping processing function module.
  • Step 504 The data mapping processing function module determines whether there is a collector that meets the data collection requirement according to the second message and the context.
  • steps 503 to 504 For the explanations of steps 503 to 504, reference may be made to steps 403 to 404 of the embodiment shown in FIG. 5, which will not be repeated here.
  • Step 505 The data mapping processing function module sends a third message to the SDNC.
  • the SDNC receives the third message sent by the data mapping processing function module.
  • the third message in this embodiment may include the target address and result of the stream collector.
  • the result can be used to indicate confirmation (ack) or non-confirmation (nack).
  • step 506 is executed.
  • step 507 may be executed.
  • the target address of the flow collector can facilitate the establishment of a TCP connection between the NE/EMS and the flow collector in the following steps.
  • the target address can be the IP and port information of the flow collector.
  • Step 506 SDNC feeds back failure information to NMS.
  • Step 507 SDNC sends a data collection request message to NE/EMS.
  • step 507 refers to step 407 of the embodiment shown in FIG. 5, which will not be repeated here.
  • the data collection request message also includes the target address of the above-mentioned flow collection.
  • Step 508 The NE/EMS establishes a TCP connection with the stream collector according to the data collection request message, sends various parameters in the data collection request message to the stream collector, and sends the reported data regularly according to the granularity period (granularityPeriod).
  • the reported data may be streaming data.
  • Step 509 The stream collector retrieves the stream data and decodes the stream data.
  • Step 510 The stream collector sends the decoded stream data and data description information to the data mapping processing function module.
  • Step 512 The data mapping processing function module sends request template information to the mapping module.
  • Step 513 The mapping template database function module matches a suitable data conversion template according to the data description information, and feeds back the matching result to the data conversion template.
  • the matching result may include a data conversion template, or information used to indicate that there is no suitable data conversion template.
  • the data conversion template please refer to the explanation of the embodiment shown in FIG. 3, which will not be repeated here.
  • Step 514 The data mapping processing function module converts the stream data according to the data conversion module, and the converted stream data meets the VES specification.
  • the data mapping processing function module When the data mapping processing function module receives the data conversion template fed back by the mapping template database function module, the data mapping processing function module converts the above-mentioned stream data through step 514, and then executes the following step 516.
  • the data mapping processing function module receives the feedback from the mapping template database function module that there is no suitable data conversion template, the following step 515 is executed to convert the above-mentioned stream data.
  • Step 515 The data mapping processing function module sends a data conversion failure message to the SDNC.
  • the data conversion failure message is used to indicate that there is an error in the data conversion.
  • Step 516 The data mapping processing function module sends a VES event to the data consumer module, where the VES event includes the converted stream data.
  • data reported from different sources can be converted into data that meets the VES specification, so that the data consumer (for example, ONAP Consumer) module can directly Use the converted reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • the data consumer for example, ONAP Consumer
  • SNMP Trap Collector SNMP Trap Collector
  • the data processing method of the embodiment of the present application will be described as an example.
  • FIG. 7 is a flowchart of a data processing method according to an embodiment of the application. As shown in Figure 7, this embodiment involves NMS, SDNC, EN/EMS, SNMP Trap Collector (SNMP Trap Collector), and data mapping processing function modules , A mapping template database function module (Mapper catalog), and a data consumer module.
  • the method of this embodiment may include:
  • Step 601 The NMS sends a second service request message to the SDNC.
  • step 601 For the specific implementation of step 601, reference may be made to step 401 of the embodiment shown in FIG. 5, which will not be repeated here.
  • Step 602 Confirm whether the NE/EMS supports the data type and encoding method in step 601.
  • step 602 may adopt steps 4021a to 4023a of the embodiment shown in FIG. 5, or steps 4021b to 4023b, which will not be repeated here.
  • Step 603 The SDNC sends a second message to the data mapping processing function module.
  • Step 604 The data mapping processing function module determines whether there is a collector that meets the data collection requirement according to the second message and the context.
  • Step 605 The data mapping processing function module sends a third message to the SDNC.
  • Step 606 SDNC feeds back failure information to NMS.
  • Step 607 SDNC sends a data collection request message to NE/EMS.
  • steps 603 to 607 For explanations of steps 603 to 607, reference may be made to steps 403 to 407 in the embodiment shown in FIG. 5, which will not be repeated here.
  • Step 608 The NE/EMS returns a confirmation message to the SDNC.
  • the confirmation message may include data description information such as vendor name (Vendorname), network element version information (NEversion), and MIB data, where MIB data is used to parse SNMP protocol content.
  • Step 609 The SDNC sends the fifth message to the SNMP Trap collector.
  • the SNMP Trap collector receives the fifth message sent by SDNC, and the fifth message can be data description information and MIB data.
  • Step 610 When a new alarm is generated in the NE/EMS, an alarm Trap is triggered, and the alarm data is sent to the SNMP Trap collector.
  • the NE/EMS can send the alarm data to the SNMP Trap collector according to the target address in the data collection request message.
  • Step 611 The SNMP Trap collector receives the alarm data, decodes the SNMP protocol alarm data according to the MIB data, and converts the OID data into character data.
  • Step 612 The SNMP Trap collector sends character data and data description information to the data mapping processing function module.
  • Step 613 The data mapping processing function module sends request template information to the mapping module.
  • Step 614 The mapping template database function module matches a suitable data conversion template according to the data description information, and feeds back the matching result to the data conversion template.
  • the matching result may include a data conversion template, or information used to indicate that there is no suitable data conversion template.
  • the data conversion template please refer to the explanation of the embodiment shown in FIG. 3, which will not be repeated here.
  • Step 615 The data mapping processing function module converts the character data according to the data conversion module, and the converted character data meets the VES specification.
  • the data mapping processing function module When the data mapping processing function module receives the data conversion template fed back by the mapping template database function module, the data mapping processing function module converts the above-mentioned stream data through step 615, and then executes the following step 617.
  • the data mapping processing function module receives the feedback from the mapping template database function module that there is no suitable data conversion template, the following step 616 is executed to convert the above-mentioned stream data.
  • Step 616 The data mapping processing function module sends a data conversion failure message to the SDNC.
  • the data conversion failure message is used to indicate that an error occurred in the data conversion.
  • Step 617 The data mapping processing function module sends a VES event to the data consumer module, where the VES event includes the converted character data.
  • data reported from different sources can be converted into data that meets the VES specification, so that the data consumer (for example, ONAP Consumer) module can directly Use the converted reported data to improve the analysis or use efficiency of the reported data by the data consumer module.
  • the data consumer for example, ONAP Consumer
  • VES Collector VES Collector
  • FIG. 8 is a flowchart of a data processing method according to an embodiment of the application. As shown in FIG. 8, this embodiment relates to NMS, SDNC, EN/EMS, VES Collector, data mapping processing function module, mapping Template database function module (Mapper catalog) and data consumer module, the method of this embodiment may include:
  • Step 701 The NMS sends a second service request message to the SDNC.
  • step 701 For the specific implementation of step 701, reference may be made to step 401 of the embodiment shown in FIG. 5, which will not be repeated here.
  • Step 702 Confirm whether the NE/EMS supports the data type and encoding method in step 701.
  • step 702 may adopt steps 4021a to 4023a of the embodiment shown in FIG. 5, or steps 4021b to 4023b, which will not be repeated here.
  • Step 703 The SDNC sends a second message to the data mapping processing function module.
  • Step 704 The data mapping processing function module determines whether there is a collector that meets the data collection requirement according to the second message and the context.
  • Step 705 The data mapping processing function module sends a third message to the SDNC.
  • Step 706 The SDNC feeds back failure information to the NMS.
  • Step 707 SDNC sends a data collection request message to NE/EMS.
  • steps 703 to 707 please refer to steps 403 to 407 in the embodiment shown in FIG.
  • Step 708 NE/EMS returns a confirmation message to SDNC.
  • Step 709 The NE/EMS sends an event notification to the VES collector.
  • the event notification includes the VES event and data description information.
  • the data description information includes information such as data type.
  • Step 710 The VES collector queries the collected VES events. If the VES specification version of the VES event is consistent with the version used by ONAP, step 711 is executed. If the VES specification version of the VES event is inconsistent with the version used by ONAP, then execute Step 712.
  • Step 711 The VES collector sends the VES event to the data consumer module.
  • Step 712 The VES collector sends the VES event and data description information to the data mapping processing function module.
  • Step 713 The data mapping processing function module converts the VES event into the used VES specification version according to the data description information, and sends the converted VES event to the data consumer module.
  • the data mapping processing function module can convert the data of a different VES specification version used by ONAP into the used VES specification version based on the data type (for example, by adding or subtracting data content).
  • This embodiment can enhance the function of processing data that supports different versions of VES specifications, and realizes the function of automatically converting VES data into MVVES specifications used by ONAP when NE supports different versions of MV VES specification data.
  • the following describes the data processing method of the embodiment of the present application by taking a process in which the NMS obtains the alarm information of the network element through the RESTAPI interface in the SDNC and transmits the alarm information to the DCAE as an example.
  • This embodiment is aimed at alarm management.
  • FIG. 9 is a flowchart of a data processing method according to an embodiment of the application. As shown in FIG. 9, this embodiment involves NMS, SDNC, EN/EMS, data mapping processing function modules, and mapping template database function modules (Mapper catalog) , And the data consumer module, the method of this embodiment may include:
  • Step 801 The NMS sends a second service request message to the SDNC.
  • the SDNC receives the second service request message sent by the NMS.
  • the second service request message is used to create a data collection service.
  • the data collection service may be collecting alarm information.
  • step 802a the SDNC sends an alarm request message to the NE/EMS through the getAlarmList API.
  • the alarm request message is used to obtain a list of alarm information.
  • the alarm request message can carry the alarm acknowledgement state (alarmAckState) and filter conditions (filter).
  • the value range of the alarm acknowledgement state (alarmAckState) is all alarms (allAlarms) and all alarms. Active alarms (allActiveAlarms), all active and acknowledged alarms (allActiveAndAcknowledgedAlarms), all active but unacknowledged alarms (allActiveAndUnacknowledgedAlarms), all clear and unacknowledged alarms (allClearedAndUnacknowledgedAlarms), all unacknowledged alarms (allUnacknowledgedAlarms).
  • Step 803a NE/EMS returns alarm information (alarmInformation) and additional information (addtionalInfo).
  • additional information may include NE information, such as manufacturer name, network element version information, and so on.
  • Step 804a The SDNC sends data description information and alarm information to the data mapping processing function module.
  • the data description information may include the above-mentioned additional information, as well as the name and data type of the collector.
  • the name of the collector is an Alarm Representation State Transfer (REST) protocol adapter (Adaptor), and the FMREST Adaptor It is a functional module in SDNC.
  • the FMREST Adaptor indicates that the alarm information is obtained through RestAPI.
  • the data type is alarm (fault)
  • Step 805a The data mapping processing function module sends a request template message to the mapping template database function module.
  • the request template message may include the manufacturer name, network element version information, and data type.
  • Step 802b SDNC initiates an alarm notification subscription request to NE/EMS.
  • the alarm notification subscription request includes subscription information.
  • the subscription information may include an alarm notification type.
  • the alarm notification type may be a new alarm notification (notifyNewAlarm), an acknowledged state change notification (notifyAckStateChanged), notifyClearedAlarm (clear alarm notification), and a reconstruction alarm notification.
  • notifyAlarmListRebuiltAlarm alarm information change notification (notifyChangedAlarm), comment notification (notifyComments), potential alarm list notification (notifyPotentialFaultyAlarmList), associated notification change notification (notifyCorrelatedNotificationChanged), alarm general information change (notifyChangedAlarmGeneral), etc.
  • Step 803b Based on the subscription information, the NE/EMS sends an alarm notification to the SDNC when an alarm is generated.
  • the value range of the notification type of the alarm notification is the alarm notification type in step 802b.
  • the NE/EMS sends a new alarm generation notification, carrying the notification type (notificationType), additional information (addtionalInfo) and alarm information .
  • additional information may include NE information, such as manufacturer name, network element version information, and so on.
  • Step 804b The SDNC sends the data description information and the alarm information to the data mapping processing function module.
  • the data description information may include the above-mentioned additional information, as well as the name and data type of the collector.
  • the name of the collector is an Alarm Representation State Transfer (REST) protocol adapter (Adaptor)
  • the FMREST Adaptor is The function module in SDNC, through the FMREST Adaptor, indicates that the alarm information is obtained through RestAPI.
  • the data type is fault.
  • Step 805b The data mapping processing function module sends a request template message to the mapping template database function module.
  • the request template message may include the manufacturer name, network element version information, and data type.
  • Step 806 The mapping template database function module sends the data conversion template to the data mapping processing function module.
  • the data conversion template may be a data conversion template matched by the mapping template database function module based on the request template message sent in step 805a or step 805b.
  • Step 807 The data mapping processing function module converts the alarm information according to the data conversion template, and the converted alarm information meets the VES specification.
  • Step 808 The data mapping processing function module sends a VES event to the data consumer module, where the VES event includes the converted alarm information.
  • alarm information from different sources can be converted into data that meets the VES specification, so that the data consumer (for example, ONAP Consumer) module can be used directly
  • the converted reported data can improve the analysis or use efficiency of the reported data by the data consumer module.
  • FIG. 10 is a schematic block diagram of a data processing device 900 according to an embodiment of the application.
  • the data processing device 900 of this embodiment can be used as the data mapping processing function module involved in the foregoing method embodiment.
  • the data processing device 900 includes a transceiver unit 901 and a processing unit 902.
  • the units of the data processing device 900 are respectively used to perform the following operations and/or processing.
  • the transceiver unit 901 is configured to receive data description information and reported data, where the data description information includes at least one of manufacturer name, network element version information, and data type or encoding mode supported by the network management system.
  • the processing unit 902 is configured to convert the reported data according to the data description information, and the converted reported data meets the VES specification of the virtual network function event stream.
  • the transceiver unit 901 is further configured to send a VES event, and the VES event includes the converted reported data.
  • the data description information and the reported data come from at least one of a collector or a software-defined network controller SDNC.
  • the collector includes a file collector, a stream collector, an SNMP trap collector, or At least one of the VES collectors.
  • the transceiver unit 901 is further configured to: receive a first message sent by the collector, the first message including the identification information of the collector, the data type supported by the collector, the encoding method supported by the collector, and The address of the collector.
  • the processing unit 902 is further configured to create a context of the collector according to the first message, the context including the identification information of the collector, the data type supported by the collector, the encoding mode supported by the collector, and the address of the collector.
  • the transceiver unit 901 is further configured to send a sixth message to the collector, where the sixth message includes the identification information of the collector and the registration result.
  • the processing unit 902 is configured to: determine the corresponding data conversion template according to the data description information, and the data mapping module uses To convert the reported data into a VES event that conforms to the VES specification, and convert the reported data according to the data conversion template.
  • the transceiver unit 901 is further configured to: receive a seventh message sent by the SDNC, where the seventh message is used to create, update, or delete a data conversion template.
  • the seventh message includes at least one of manufacturer name, network element version information, data type or encoding method, and data template information.
  • the transceiver unit 901 is further configured to receive a second message sent by SDNC, the second message is used to indicate data collection requirements, and the processing unit 902 is further configured to determine whether there is a satisfactory For collectors with data collection requirements, the transceiver unit 901 is further configured to send a third message to the SDNC, where the third message is used to indicate information about the collectors that meet the data collection requirements.
  • the second message includes at least one of a reporting manner, a data type supported by the network management system, or an encoding manner supported by the network management system.
  • the third message when the collector meeting the data collection requirement is a file collector or a VNF event stream collector, the third message includes the identification information of the collector.
  • the third message when the collector meeting the data collection requirement is a stream collector or an SNMP trap collector, the third message includes at least one of the identification information of the collector or the address of the collector.
  • the data description information includes a data type
  • the processing unit 902 is configured to add or delete elements included in the reported data according to the data type.
  • the reported data includes at least one of file data, stream data, alarm data, VES events, or character data.
  • the data processing apparatus 900 may also have other functions of the data mapping processing function module in the method embodiment at the same time.
  • the processing unit 902 may be a processor
  • the transceiving unit 901 may be a transceiver.
  • the transceiver includes a receiver and a transmitter, and has both sending and receiving functions.
  • the processing unit 902 may be a processing device, and the functions of the processing device may be partially or fully implemented by software.
  • the functions of the processing device may be partially or fully implemented by software.
  • the processing device may include a memory and a processor.
  • the memory is used to store a computer program
  • the processor reads and executes the computer program stored in the memory to execute the steps implemented inside the data mapping processing function module in each method embodiment.
  • the processing device includes a processor.
  • the memory for storing the computer program is located outside the processing device, and the processor is connected to the memory through a circuit/wire to read and execute the computer program stored in the memory.
  • the data processing device 900 may be a chip.
  • the transceiving unit 901 may specifically be a communication interface or a transceiving circuit.
  • This application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium.
  • the computer program executes the data mapping processing function module in any of the above-mentioned method embodiments. The steps and/or processing performed.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes the data mapping processing function module in any of the above-mentioned method embodiments. Steps and/or treatments.
  • the application also provides a chip including a processor.
  • the memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the steps and/or processing performed by the data mapping processing function module in any method embodiment.
  • the chip may also include a memory and a communication interface.
  • the communication interface may be an input/output interface, a pin, an input/output circuit, or the like.
  • FIG. 11 is a schematic structural diagram of a data processing device 1000 provided by an embodiment of the application.
  • the data processing apparatus 1000 may be the data mapping processing function module involved in the foregoing embodiment.
  • the data processing device 1000 includes a processor 1001 and a transceiver 1002.
  • the data processing apparatus 1000 further includes a memory 1003.
  • the processor 1001, the transceiver 1002, and the memory 1003 can communicate with each other through an internal connection path to transfer control signals and/or data signals.
  • the memory 1003 is used to store computer programs.
  • the processor 1001 is configured to execute a computer program stored in the memory 1003, so as to implement various functions in the foregoing device embodiments.
  • the memory 1003 may also be integrated in the processor 1001 or independent of the processor 1001.
  • FIG. 12 is a schematic structural diagram of a collector 1100 provided by an embodiment of the application.
  • the collector 1100 may correspond to the collector in each method embodiment.
  • the collector 1100 includes a transceiver unit 1101 and a processing unit 1102.
  • the units of the collector 1100 are respectively used to perform the following operations and/or processing.
  • the transceiver unit 1101 is used to receive data description information.
  • the processing unit 1102 is configured to send the data description information and the reported data to the data mapping processing function module through the transceiver unit 1101.
  • the data description information includes the name of the manufacturer, the version information of the network element, the data type or the encoding method supported by the network management system At least one item.
  • the transceiver unit 1101 is further configured to send a first message to the data mapping processing function module, the first message including the identification information of the collector, the data type supported by the collector, and the encoding method supported by the collector And the address of the collector.
  • the collector 1100 is a file collector
  • the reported data is file data
  • the transceiver unit 1101 is configured to receive a fourth message sent by the software-defined network controller SDNC, and the fourth message includes the file Information and the data description information, the file information is used to indicate the location of the file data; the processing unit 1102 is also used to download the file data from the corresponding location through the transceiver unit 1101 according to the file information.
  • the collector 1100 is a stream collector
  • the reported data is stream data
  • the transceiver unit 1101 is used to establish a TCP connection with the network element or the network element management system
  • the processing unit 1102 is also used to pass The TCP connection receives stream data and data description information.
  • the collector 1100 is an SNMP trap collector
  • the reported data is character data
  • the transceiver unit 1101 is configured to receive a fifth message sent by SDNC.
  • the fifth message includes data description information and MIB Data
  • the transceiver unit 1101 is also used to receive alarm data sent by a network element or a network element management system; the processing unit 1102 is also used to decode the alarm data into character data according to the MIB data.
  • the collector 1100 is a VES collector
  • the reported data is a VES event
  • the transceiver unit 1101 is configured to receive the VES event and data description information sent by the network element or the network element management system.
  • the data The description information includes the data types supported by the network management system.
  • the processing unit 1102 may be a processor
  • the transceiving unit 1101 may be a transceiver.
  • the transceiver includes a receiver and a transmitter, and has both sending and receiving functions.
  • the processing unit 1102 may be a processing device, and the functions of the processing device may be partially or fully implemented by software.
  • the functions of the processing device may be partially or fully implemented by software.
  • the processing device may include a memory and a processor.
  • the memory is used to store a computer program
  • the processor reads and executes the computer program stored in the memory to execute the steps implemented inside the collector in each method embodiment.
  • the processing device includes a processor.
  • the memory for storing the computer program is located outside the processing device, and the processor is connected to the memory through a circuit/wire to read and execute the computer program stored in the memory.
  • the data processing device 1100 may be a chip.
  • the transceiving unit 1101 may specifically be a communication interface or a transceiving circuit.
  • This application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium.
  • the computer program When the computer program is executed by a computer, the computer executes the steps performed by the collector in any of the above-mentioned method embodiments. And/or processing.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes the steps executed by the collector in any of the foregoing method embodiments and/ Or deal with.
  • the application also provides a chip including a processor.
  • the memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the steps and/or processing performed by the collector in any method embodiment.
  • the chip may also include a memory and a communication interface.
  • the communication interface may be an input/output interface, a pin, an input/output circuit, or the like.
  • FIG. 13 is a schematic structural diagram of a collector 1200 provided by an embodiment of the application. As shown in FIG. 13, the collector 1200 may be the collector involved in the foregoing embodiment.
  • the collector 1200 includes a processor 1201 and a transceiver 1202.
  • the collector 1200 further includes a memory 1203.
  • the processor 1201, the transceiver 1202, and the memory 1203 can communicate with each other through an internal connection path to transfer control signals and/or data signals.
  • the memory 1203 is used to store computer programs.
  • the processor 1201 is configured to execute a computer program stored in the memory 1203, so as to implement various functions in the foregoing device embodiments.
  • the memory 1203 may also be integrated in the processor 1201 or independent of the processor 1201.
  • the foregoing device embodiment may be used to implement the technical solution of the collector in the method embodiment, and its implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 14 is a schematic structural diagram of a data processing device 1300 provided by an embodiment of the application.
  • the data processing apparatus 1300 may correspond to the network element or the network element management system in each method embodiment.
  • the data processing device 1300 includes a transceiving unit 1301 and a processing unit 1302.
  • the units of the data processing device 1300 are respectively used to perform the following operations and/or processing.
  • the transceiver unit 1301 is configured to receive a data collection request message sent by the software-defined network controller SDNC.
  • the data collection request message includes at least one of a reporting method, a collection period, a data type supported by the network management system, or an encoding method supported by the network management system item.
  • the processing unit 1302 is configured to collect at least one of file data, stream data, alarm data, VES events, or character data according to the data collection request message.
  • the processing unit 1302 is further configured to establish a TCP connection with the stream collector through the transceiver unit 1301; send stream data and data description information to the stream collector through the TCP connection, and the data description information includes the name of the manufacturer , At least one of network element version information, data type or encoding method supported by the network management system.
  • the transceiver unit 1301 is further configured to send MIB data to the SDNC, where the MIB data is used to decode the alarm data.
  • the transceiver unit 1301 is further configured to send VES events and data types supported by the network management system to the VES collector.
  • the processing unit 1302 may be a processor
  • the transceiving unit 1301 may be a transceiver.
  • the transceiver includes a receiver and a transmitter, and has both sending and receiving functions.
  • the processing unit 1302 may be a processing device, and the functions of the processing device may be partially or fully implemented by software.
  • the functions of the processing device may be partially or fully implemented by software.
  • the processing device may include a memory and a processor.
  • the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to execute the steps implemented by the network element or the network element management system in each method embodiment.
  • the processing device includes a processor.
  • the memory for storing the computer program is located outside the processing device, and the processor is connected to the memory through a circuit/wire to read and execute the computer program stored in the memory.
  • the data processing device 1300 may be a chip.
  • the transceiving unit 1301 may specifically be a communication interface or a transceiving circuit.
  • the present application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium.
  • the computer program When the computer program is executed by a computer, the computer executes any of the above-mentioned method embodiments by a network element or a network element. The steps and/or processing performed by the management system.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes any of the above-mentioned method embodiments.
  • the network element or the network element management system The steps and/or processing performed.
  • the application also provides a chip including a processor.
  • the memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the steps and/or processing executed by the network element or the network element management system in any method embodiment.
  • the chip may also include a memory and a communication interface.
  • the communication interface may be an input/output interface, a pin, an input/output circuit, or the like.
  • FIG. 15 is a schematic structural diagram of a data processing device 1400 according to an embodiment of the application.
  • the data processing device 1400 may correspond to a network element or a network element management system in each method embodiment.
  • the data processing device 1400 includes a processor 1401 and a transceiver 1402.
  • the data processing device 1400 further includes a memory 1403.
  • the processor 1401, the transceiver 1402, and the memory 1403 can communicate with each other through an internal connection path to transfer control signals and/or data signals.
  • the memory 1403 is used to store computer programs.
  • the processor 1401 is configured to execute a computer program stored in the memory 1403, so as to implement various functions in the foregoing device embodiments.
  • the memory 1403 may also be integrated in the processor 1401 or independent of the processor 1401.
  • the embodiment of the application also provides a network element or network element management system.
  • the network element or network element management system adopts the same structure as that in FIG. 14, wherein the transceiver unit is used to receive the first data sent by the software-defined network controller SDNC.
  • a capability negotiation message where the first capability negotiation message is used to trigger the network element or network element management system to feed back whether it supports at least one of the reporting mode, data type, or encoding mode of the network management system; the processing unit is used to pass all
  • the transceiver unit sends a feedback result to the SDNC, where the feedback result is used to indicate whether to support at least one of a reporting mode, a data type, or an encoding mode of the network management system.
  • the first capability negotiation message includes the reporting method, the data type, the encoding method, and the object list.
  • the object list is used to indicate at least one network element, and the network element management system is used to manage the One or more network elements in at least one network element; the processing unit is further configured to parse the object list, obtain identification information, and obtain whether the network element or the network element management system supports the reporting of the network management system according to the identification information Method, data type and encoding method.
  • FIG. 16 is a schematic structural diagram of a software-defined network controller 1500 provided by an embodiment of the application.
  • the software-defined network controller 1500 may correspond to the SDNC in each method embodiment.
  • the software-defined network controller 1500 includes a transceiver unit 1501 and a processing unit 1502.
  • the units of the software-defined network controller 1500 are respectively used to perform the following operations and/or processing.
  • the transceiver unit 1501 is configured to receive a service request message sent by a network management system, where the service request message includes a data type supported by the network management system and an encoding method supported by the network management system;
  • the transceiver unit 1501 is further configured to send a first capability negotiation message to the network element or the network element management system, where the first capability negotiation message is used to trigger the network element or the network element management system to feedback whether the data type and the encoding method are supported;
  • the processing unit 1502 is configured to send a data collection request message to the network element or the network element management system through the transceiver unit 1501 according to the feedback of the network element or the network element management system.
  • the service request message further includes an object list
  • the first capability negotiation message includes a data type, an encoding method, and an object list.
  • the object list is used to indicate at least one network element, and the network element management system Used to manage one or more network elements in at least one network element.
  • the service request message further includes an object list, the object list is used to indicate at least one network element, and the network element management system is used to manage one or more of the at least one network element
  • the processing unit 1502 is further configured to parse the object list and obtain identification information; the processing unit 1502 is also configured to send the first capability negotiation message to the network element corresponding to the identification information or the network element management system through the transceiver unit 1501.
  • the processing unit 1502 may be a processor
  • the transceiving unit 1501 may be a transceiver.
  • the transceiver includes a receiver and a transmitter, and has both sending and receiving functions.
  • the processing unit 1502 may be a processing device, and the functions of the processing device may be partially or fully implemented by software.
  • the functions of the processing device may be partially or fully implemented by software.
  • the processing device may include a memory and a processor.
  • the memory is used to store a computer program
  • the processor reads and executes the computer program stored in the memory to execute the steps implemented inside the SDNC in each method embodiment.
  • the processing device includes a processor.
  • the memory for storing the computer program is located outside the processing device, and the processor is connected to the memory through a circuit/wire to read and execute the computer program stored in the memory.
  • the software-defined network controller 1500 may be a chip.
  • the transceiving unit 1501 may specifically be a communication interface or a transceiving circuit.
  • This application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium.
  • the computer program When the computer program is executed by a computer, the computer executes the steps and steps executed by SDNC in any of the above-mentioned method embodiments. /Or processing.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes the steps and/or steps executed by SDNC in any of the foregoing method embodiments. deal with.
  • the application also provides a chip including a processor.
  • the memory for storing the computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to execute the steps and/or processing executed by the SDNC in any method embodiment.
  • the chip may also include a memory and a communication interface.
  • the communication interface may be an input/output interface, a pin, an input/output circuit, or the like.
  • FIG. 17 is a schematic structural diagram of a software-defined network controller 1600 provided by an embodiment of this application.
  • the software-defined network controller 1600 can correspond to the SDNC in each method embodiment.
  • the software-defined network controller 1600 includes a processor 1601 and a transceiver 1602.
  • the software-defined network controller 1600 further includes a memory 1603.
  • the processor 1601, the transceiver 1602, and the memory 1603 can communicate with each other through an internal connection path to transfer control signals and/or data signals.
  • the memory 1603 is used to store computer programs.
  • the processor 1601 is configured to execute a computer program stored in the memory 1603, so as to implement various functions in the foregoing device embodiments.
  • the memory 1603 may also be integrated in the processor 1601 or independent of the processor 1601.
  • the foregoing device embodiment may be used to implement the SDNC technical solution in the method embodiment, and its implementation principles and technical effects are similar, and will not be repeated here.
  • the processor mentioned in the above embodiments may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the processor can be a general-purpose processor, digital signal processor (digital signal processor, DSP), application-specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware encoding processor, or executed and completed by a combination of hardware and software modules in the encoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory mentioned in the above embodiments may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (personal computer, server, or network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供一种数据处理方法和装置。本申请的数据处理方法，包括：接收数据描述信息和上报的数据，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项；根据所述数据描述信息对所述上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流VES规范；发送VES事件，所述VES事件包括所述转换后的上报的数据。本申请可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。

Description

数据处理方法和装置
本申请要求于2019年10月12日提交中国专利局、申请号为201910969633.6、申请名称为“数据处理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种数据处理方法和装置。
背景技术
开放网络自动化平台(Open Network Automation Platform，ONAP)平台为物理/虚拟的网络功能提供了一个实时的、策略驱动的编排自动化综合平台，软件、网络、IT、云业务提供商和开发人员可以通过ONAP快速且自动化的部署新的业务，并支持全生命周期管理。
ONAP支持跨厂商的物理/虚拟的网络功能的运维管理，部署在网络管理系统(Network Management System，NMS)和网元管理系统(Element Management System，EMS)/网元(Network Element，NE)之间是一种可选地部署方式。ONAP中的软件定义网络控制器(Software Defined Network controller，SDNC)通过EMS/NE北向管理接口(createMeasurementJob、getAlarmList)进行告警或性能数据的收集，将收集的告警或性能数据传输到ONAP数据消费者(Consumer)，该ONAP Consumer可以是NMS或ONAP大数据分析引擎或其他数据消费者。
传输给ONAP Consumer的告警或性能数据为不同厂商、不同类型网元、不同网元版本的上报的数据，不同厂商、不同类型网元、不同网元版本的上报的数据的数据协议和数据格式均存在较大差异，导致ONAP Consumer对告警或性能数据的分析或使用效率低。
发明内容
本申请提供一种数据处理方法和装置，以提升上报的数据的分析或使用效率。
第一方面，本申请提供一种数据处理方法，该方法包括：接收数据描述信息和上报的数据，该数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。根据该数据描述信息对上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流VES规范。发送VES事件，该VES事件包括转换后的上报的数据。
本实现方式，根据接收到的数据描述信息，将上报的数据转换为满足VES规范的VES事件，可以实现数据的自动转换，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
在一种可能的设计中，该数据描述信息和上报的数据来自于采集器或软件定义网络控制器SDNC中至少一项，该采集器包括文件采集器、流采集器、简单网络管理协议(Simple Network Management Protocol，SNMP)trap采集器或VES采集器中至少一项。
在一种可能的设计中，在接收所述数据描述信息和上报的数据之前，该方法还可以包括：接收采集器发送的第一消息，该第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。根据该第一消息创建采集器的上下文，该上下文包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
本实现方式，采集器上线后可以发送该第一消息，数据映射处理功能模块可以根据该第一消息创建该采集器的上下文，从而可以统一管理上线的采集器，以便后续与SDNC之间的业务能力协商。
在一种可能的设计中，该方法还可以包括：向采集器发送第六消息，该第六消息包括采集器的标识信息和注册结果。
在一种可能的设计中，当采集器为文件采集器、流采集器或SNMP trap采集器时，根据所述数据描述信息对所述上报的数据进行转换，包括：根据数据描述信息确定对应的数据转换模板，该数据映射模块用于将上报的数据转换为符合VES规范的VES事件。根据数据转换模板对上报的数据进行转换。
在一种可能的设计中，该方法还可以包括：接收SDNC发送的第七消息，该第七消息用于创建、更新或删除所述数据转换模板。
在一种可能的设计中，该第七消息包括厂商名称、网元版本信息、数据类型或编码方式中至少一项，以及数据模板信息。
在一种可能的设计中，该方法还可以包括：接收SDNC发送的第二消息，该第二消息用于指示数据收集需求。根据该第二消息和该上下文确定是否存在满足数据收集需求的采集器。向SDNC发送第三消息，该第三消息用于指示满足数据收集需求的采集器的信息。
在一种可能的设计中，该第二消息包括上报方式、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项。
在一种可能的设计中，当满足数据收集需求的采集器为文件采集器或VNF事件流采集器时，该第三消息包括所述采集器的标识信息。
在一种可能的设计中，当满足数据收集需求的采集器为流采集器或SNMP trap采集器时，该第三消息包括采集器的标识信息或采集器的地址中至少一项。
在一种可能的设计中，当采集器为VES采集器时，该数据描述信息包括数据类型，根据所述数据描述信息对所述上报的数据进行数据转换，可以包括：根据数据类型对上报的数据所包括的元素进行增加或删除。
在一种可能的设计中，该上报的数据包括文件数据、流数据、告警数据、VES事件或字符数据中至少一项。
第二方面，本申请实施例提供一种数据处理方法，该方法可以包括：采集器接收数据描述信息。采集器向数据映射处理功能模块发送所述数据描述信息和上报的数据，该数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
在一种可能的设计中，在接收数据描述信息和上报的数据之前，该方法还可以包括：采集器向数据映射处理功能模块发送第一消息，该第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
在一种可能的设计中，该采集器为文件采集器，该上报的数据为文件数据，采集器接收数据描述信息，包括：文件采集器接收软件定义网络控制器SDNC发送的第四消息，该第四消息包括文件信息和该数据描述信息，该文件信息用于指示所述文件数据的位置。文件采集器根据该文件信息从对应的位置下载所述文件数据。
在一种可能的设计中，该采集器为流采集器，该上报的数据为流数据，采集器接收数据描述信息，包括：流采集器与网元或网元管理系统建立传输控制协议(Transmission Control Protocol，TCP)连接。流采集器通过TCP连接接收流数据和数据描述信息。
在一种可能的设计中，该采集器为SNMP trap采集器，该上报的数据为字符数据，采集器接收数据描述信息，包括：SNMP trap采集器接收SDNC发送的第五消息，该第五消息包括数据描述信息和管理信息库(Management Information Base，MIB)数据；SNMP trap采集器接收网元或网元管理系统发送的告警数据；SNMP trap采集器根据MIB数据将告警数据解码为字符数据。
在一种可能的设计中，该采集器为VES采集器，上报的数据为VES事件，采集器接收数据描述信息，包括：VES采集器接收网元或网元管理系统发送的VES事件和数据描述信息，该数据描述信息包括网络管理系统支持的数据类型。
第三方面，本申请实施例提供一种数据处理方法，该方法可以包括：接收软件定义网络控制器SDNC发送的数据收集请求消息，该数据收集请求消息包括上报方式、采集周期、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项；根据该数据收集请求消息收集上报的数据。例如，文件数据、流数据、告警数据、VES事件或字符数据中至少一项。
在一种可能的设计中，该方法还可以包括：与流采集器建立TCP连接；通过TCP连接接向流采集器发送流数据和数据描述信息，该数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
在一种可能的设计中，该方法还可以包括：向SDNC发送MIB数据，该MIB数据用于解码所述告警数据。
在一种可能的设计中，该方法还可以包括：向VES采集器发送VES事件和网络管理系统支持的数据类型。
第四方面，本申请实施例提供一种数据处理方法，该方法可以包括：接收网络管理系统发送的服务请求消息，该服务请求消息包括上报方式、网络管理系统支持的数据类型或该网络管理系统支持的编码方式中至少一项；向网元或网元管理系统发送第一能力协商消息，该第一能力协商消息用于触发网元或网元管理系统反馈是否支持该上报方式、该数据类型或该编码方式中至少一项；根据网元或网元管理系统的反馈，向网元或网元管理系统发送数据收集请求消息。
在一种可能的设计中，该服务请求消息还包括对象列表，该对象列表用于指示至少一个网元，该网元管理系统用于管理至少一个网元中的一个或多个网元。
在一种可能的设计中，该服务请求消息还包括对象列表，该对象列表用于指示至少一 个网元，该网元管理系统用于管理至少一个网元中的一个或多个网元，该方法还包括：解析该对象列表，获取标识信息；向网元或网元管理系统发送第一能力协商消息，包括：向该标识信息对应的网元或网元管理系统发送第一能力协商消息。
第五方面，本申请实施例提供一种数据处理方法，该方法可以包括：接收软件定义网络控制器SDNC发送的第一能力协商消息，该第一能力协商消息用于触发网元或网元管理系统反馈是否支持网络管理系统的上报方式、网络管理系统支持的数据类型或编码方式中至少一项；向SDNC发送反馈结果，该反馈结果用于指示是否支持网络管理系统的上报方式、网络管理系统支持的数据类型或编码方式中至少一项。
在一种可能的设计中，该第一能力协商消息包括上报方式、数据类型、编码方式和对象列表，对象列表用于指示至少一个网元，网元管理系统用于管理所述至少一个网元中的一个或多个网元；该方法还可以包括：解析该对象列表，获取标识信息；根据该标识信息获取网元或网元管理系统是否支持该上报方式、网络管理系统的数据类型和编码方式。
第六方面，本申请实施例提供一种数据处理装置，该装置具有实现上述第一方面的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块，例如，收发单元或模块，处理单元或模块。
第七方面，本申请实施例提供一种采集器，该采集器具有实现上述第二方面的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块，例如，收发单元或模块，处理单元或模块。
第八方面，本申请实施例提供一种数据处理装置，该数据处理装置具有实现上述第三方面的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块，例如，收发单元或模块，处理单元或模块。
第九方面，本申请实施例提供一种软件定义网络控制器，该软件定义网络控制器具有实现上述第四方面的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块，例如，收发单元或模块，处理单元或模块。
第十方面，本申请实施例提供一种数据处理装置，该数据处理装置具有实现上述第五方面的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块，例如，收发单元或模块，处理单元或模块。
第十一方面，本申请提供一种数据处理装置，包括：一个或多个处理器；存储器，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如上述第一方面中任一项所述的方法，或者，使得所述一个或多个处理器实现如上述第二方面中任一项所述的方法，或者，使得所述一个或多个处理器实现如上述第三方面中任一项所述的方法，或者，使得所述一个或多个处理器实现如上述第四方面中任一项所述的方法，或者，使得所述一个或多个处理器实现如上述第五方面中任一项所述的方法。
第十二方面，本申请提供一种计算机可读存储介质，包括计算机程序，所述计算机程 序在计算机上被执行时，使得所述计算机执行上述第一方面中任一项所述的方法，或者，使得所述计算机执行上述第二方面中任一项所述的方法，或者，使得所述计算机执行上述第三方面中任一项所述的方法，或者，使得所述计算机执行上述第四方面中任一项所述的方法，或者，使得所述计算机执行上述第五方面中任一项所述的方法。
第十三方面，本申请提供一种计算机程序产品，该计算机程序产品包括指令，当所述指令被计算机执行时，用于执行上述第一方面中任一项所述的方法，或者，用于执行上述第二方面中任一项所述的方法，或者，用于执行上述第三方面中任一项所述的方法，或者，用于执行上述第四方面中任一项所述的方法，或者，用于执行上述第五方面中任一项所述的方法。
第十四方面，本申请提供一种芯片，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如上述第一方面中任一项所述的方法，或者，执行上述第二方面中任一项所述的方法，或者，执行上述第三方面中任一项所述的方法，或者，执行上述第四方面中任一项所述的方法，或者，执行上述第五方面中任一项所述的方法。
第十五方面，本申请实施例提供一种数据处理系统，该系统可以包括数据映射处理功能模块、至少一个采集器、SDNC以及网元或网元管理系统。该数据映射处理功能模块可以执行上述第一方面中任一项所述的方法，任意一个采集器可以执行上述第二方面中任一项所述的方法，网元或网元管理系统可以执行上述第三方面或第五方面中任一项所述的方法，SDNC可以执行上述第四方面中任一项所述的方法。
本申请的数据处理方法和装置，通过采集器向数据映射处理功能模块发送数据描述信息和上报的数据，该数据描述信息可以包括厂商名称、网元版本信息、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项，数据映射处理功能模块根据数据描述信息对上报的数据进行转换，转换后的上报的数据满足VES规范，数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的上报的数据，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
附图说明
图1为本申请实施例的一种系统架构的示意图；
图2为本申请实施例的一种数据处理方法的流程图；
图3为本申请实施例的一种数据处理方法的流程图；
图4为本申请实施例的一种数据处理方法的流程图；
图5为本申请实施例的一种数据处理方法的流程图；
图6为本申请实施例的一种数据处理方法的流程图；
图7为本申请实施例的一种数据处理方法的流程图；
图8为本申请实施例的一种数据处理方法的流程图；
图9为本申请实施例的一种数据处理方法的流程图；
图10为本申请实施例提供的数据处理装置900的示意性框图；
图11为本申请实施例提供的一种数据处理装置1000的结构示意图；
图12为本申请实施例提供的采集器1100的示意性结构图；
图13为本申请实施例提供的一种采集器1200的结构示意图；
图14为本申请实施例提供的数据处理装置1300的示意性结构图；
图15为本申请实施例提供的一种数据处理装置1400的示意性结构图；
图16为本申请实施例提供的软件定义网络控制器1500的示意性结构图；
图17为本申请实施例提供的一种软件定义网络控制器1600的示意性结构图。
具体实施方式
本申请所涉及的术语“第一”、“第二”等仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元。方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
应当理解，在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，用于描述关联对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”，其中a，b，c可以是单个，也可以是多个。
图1为本申请实施例的一种系统架构的示意图，如图1所述，该系统架构可以包括NMS、ONAP、EMS/NE以及用户(Consumer)。其中，该用户(Consumer)可以是NMS、分析应用(Analytic Applications)或电子计算平台(Electronic Computing Platform，TCA)。ONAP可以包括SDNC和数据采集、分析和事件(Data Collection,Analytics,and Events，DCAE)模块。DCAE模块可以包括数据映射处理功能模块(Data Mapper)、映射模板数据库功能模块(Mapper catalog)和各种类型的采集器，例如，VES采集器(VES Collector)、文件采集器(File Collector)、流采集器(Stream Collector)、或SNMP Trap采集器(SNMP Trap Collector)等。该数据映射处理功能模块与上述各种类型的采集器之间有通信接口。该数据映射处理功能模块与SDNC之间有通信接口。SDNC通过EMS/NE的北向管理接口，如用于创建测量任务(createMeasurementJob)的接口、用于获取告警列表(getAlarmList)的接口，进行性能数据或告警数据的收集。
本申请实施例的上述系统架构可以应用于通过网络功能虚拟化(Network Function Virtualization，NFV)技术实现的各种网络中，例如，一个数据中心网络、运营商网络或局域网中来实现具有特定功能的网络服务，在实现具有特定功能的网络服务过程中具体可以通过多个NE实现。NE可以作为核心网网元，例如MME，也可以作为接入网网元，例如，5G中的基站(gNB)。每一个NE可以通过一个或多个虚拟网络功能(Virtual Network Function，VNF)灵活部署子硬件资源层中的计算硬件、存储硬件和/或网络硬件。EMS可以管理多个NE，每个EMS可以对应一个厂商(Vendor)，如图1所述，ONAP对接的不同 厂商的EMS/NE，例如，HTTP服务(HTTP Server)对应厂商X，VES客户端(VES Client)对应厂商A，文件传输服务(FTP Server)和SNMP Trap代理对应厂商B，GRPC对应厂商C。不同厂商、不同类型网元、不同网元版本的上报的数据的数据协议和数据格式均存在较大差异，通过本申请实施例的下述数据处理方法，可以提升ONAP Consumer对告警或性能数据的分析或使用效率，其具体实现方式可以参见下述实施例的解释说明。
需要说明的是，上述图1所示的系统中的数据映射处理功能模块、采集器、SDNC等仅是一个名字，名字对功能模块本身不构成限定。在5G网络以及未来其它的网络中，数据映射处理功能模块、采集器、SDNC所对应的实体可以是其他的名字，本申请实施例对此不作具体限定。
图2为本申请实施例的一种数据处理方法的流程图，如图2所示，本实施例涉及数据映射处理功能模块、采集器和数据消费者模块，该数据消费者模块例如可以是NMS、或分析应用、或TCA、或ONAP大数据分析引擎等，本实施例的方法可以包括：
步骤101、采集器向数据映射处理功能模块发送数据描述信息和上报的数据。
相应的，数据映射处理功能模块接收采集器发送的数据描述信息和上报的数据。该数据描述信息可以包括厂商名称(Vendor name)、网元版本信息(NE version)、网络管理系统支持的数据类型(Domain type)或网络管理系统支持的编码方式(Supported datatype)中至少一项。
该厂商名称(Vendor name)用于唯一标识一个厂商，例如，上述厂商A，可以理解的，该厂商名称也可以是身份标识号(Identity document，ID)，例如，厂商A的ID为0000001。网元版本信息(NE version)用于表示该上报的数据对应的NE的软件版本，该上报的数据对应的NE可以是产生该上报的数据的NE。网络管理系统支持的数据类型(Domain type)表示NMS所支持的数据类型，该NMS所支持的数据类型可以是NMS发起创建任务的数据类型，例如，告警(fault)、测量(measurement)、3GPP告警(fault3gpp)、3GPP性能数据(perf3gpp)等。网络管理系统支持的编码方式(Supported datatype)表示NMS支持的文件格式/编码方式，例如，可扩展标记语言(Extensible Markup Language，XML)、JavaScript对象表示法(JavaScript Object Notation，JSON)、仍是一种标记语言(Yet Another Markup Language，YAML)、谷歌混合语言数据标准(Google Protocol Buffers，GPB)、抽象语法编码1(Abstract Syntax Notation One，ASN.1)等。
示例性的，采集器通过与数据映射处理功能模块之间的数据传输接口将该数据描述信息和上报的数据发送给数据映射处理功能模块，该数据描述信息和上报的数据来源于NE/EMS，例如，来源于上述FTP Server。NE/EMS可以基于NMS所触发的数据收集服务产生该上报的数据，该服务请求消息可以携带该数据描述信息，并上报至采集器，采集器将数据描述信息和上报的数据发送给数据映射处理功能模块。
步骤102、数据映射处理功能模块根据数据描述信息对上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流(VNF Event Streaming，VES)规范。
例如，该上报的数据来源于不同厂商的EMS/NE、不同类型网元、不同网元版本、或不同数据管理领域(如性能、告警、日志)等，其数据协议或数据格式存在较大差异，通过本申请实施例的数据映射处理功能模块可以对该上报的数据进行转换，以使得转换后的 上报的数据满足VES规范，例如，多厂商(Multi-Vendor)VES规范，该规范是3GPP数据上报格式的标准规范。
步骤103、数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的上报的数据。
通过数据映射处理功能模块的转换操作，可以使得发送给数据消费者模块的上报的数据的数据协议或数据格式为统一的规范，数据消费者模块接收到该转换后的上报的数据后，无需进行预处理，可以直接使用，例如，进行数据分析、汇总等。
本实施例，通过采集器向数据映射处理功能模块发送数据描述信息和上报的数据，该数据描述信息可以包括厂商名称、网元版本信息、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项，数据映射处理功能模块根据数据描述信息对上报的数据进行转换，转换后的上报的数据满足VES规范，数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的上报的数据，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
本申请实施例的步骤102的一种可实现方式为，数据映射处理功能模块根据数据描述信息确定对应的数据转换模板，数据映射处理功能模块根据该数据转换模板对该上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流(VNF Event Streaming，VES)规范。该数据转换模板可以是参数的转换规则，例如，一种映射关系，举例而言，参数A对应参数A’，即根据该数据转换模板，将上报的数据中的参数A转换为参数A’。
该数据映射处理功能模块可以存储在上述图1中的映射模板数据库功能模块(Mapper catalog)中，该映射模板数据库功能模块(Mapper catalog)可以与数据映射处理功能模块(Data Mapper)合设，也可以与数据映射处理功能模块(Data Mapper)分设，本申请实施例以分设为例进行举例说明，其不以此作为限制。例如，数据映射处理功能模块可以向映射模板数据库功能模块发送数据描述信息，映射模板数据库功能模块根据该数据描述信息获取对应的数据转换模板，并将该数据转换模板发送给数据映射处理功能模块，数据映射处理功能模块根据该数据转换模板对上报的数据进行转换，以使得转换后的上报的数据符合VES规范。
对于映射模板数据库功能模块(Mapper catalog)中的数据转换模板，其可以通过下述图3所示实施例的方法进行上线/更新/删除，其具体解释说明可以参见下述实施例。
图3为本申请实施例的一种数据处理方法的流程图，如图3所示，本实施例涉及NMS、SDNC和映射模板数据库功能模块(Mapper catalog)，本实施例的方法可以包括：
步骤201、NMS向SDNC发送第一服务请求消息，该第一服务请求消息用于创建、更新或删除数据转换模板。
相应的，NMS接收SDNC发送的第一服务请求消息。示例性的，该第一服务请求消息可以携带参数列表(Parameterlist)，例如，厂商名称(Vendor name)、网元版本信息(NE version)、数据类型(Domain type)或编码方式(Supported datatype)中至少一项，以及对应的数据模板信息(templateinfo)，该数据模板信息(templateinfo)用于指示上述数据 转换模板。该第一服务请求消息还可以携带类型指示信息，该类型指示信息可以是两比特位，例如，00用于指示创建数据转换模板，01用于指示更新数据转换模板，10用于指示删除数据转换模板。
步骤202、SDNC向映射模板数据库功能模块(Mapper catalog)发送第七消息，该第七消息用于创建、更新或删除数据转换模板。
相应的映射模板数据库功能模块(Mapper catalog)接收SDNC发送的第七消息。示例性的，该第七消息可以携带上述第一服务请求消息所携带的各项信息，例如，厂商名称(Vendor name)、网元版本信息(NE version)、数据类型(Domain type)或编码方式(Supported datatype)中至少一项，以及对应的数据模板信息(templateinfo)。
步骤203、映射模板数据库功能模块(Mapper catalog)根据该第七消息创建、更新或删除数据转换模板。
示例性的，当该第七消息用于创建数据转换模板时，映射模板数据库功能模块(Mapper catalog)可以根据该第七消息建立厂商名称(Vendor name)、网元版本信息(NE version)、数据类型(Domain type)或编码方式(Supported datatype)中至少一项，与数据转换模板的对应关系。当该第七消息用于更新数据转换模板时，映射模板数据库功能模块(Mapper catalog)可以根据该第七消息建立厂商名称(Vendor name)、网元版本信息(NE version)、数据类型(Domain type)或编码方式(Supported datatype)中至少一项，匹配查找对应的数据转换模板，使用第七消息所指示的数据转换模板更新匹配到的数据转换模板。当该第七消息用于删除数据转换模板时，映射模板数据库功能模块(Mapper catalog)可以根据该第七消息建立厂商名称(Vendor name)、网元版本信息(NE version)、数据类型(Domain type)或编码方式(Supported datatype)中至少一项，匹配查找对应的数据转换模板，并删除对应的数据转换模板。
该数据类型可以是告警(fault)、测量(measurement)、3GPP告警(fault3gpp)、3GPP性能数据(perf3gpp)等。该编码方式(Supported datatype)可以是可扩展标记语言(Extensible Markup Language，XML)、JavaScript对象表示法(JavaScript Object Notation，JSON)、仍是一种标记语言(Yet Another Markup Language，YAML)、谷歌混合语言数据标准(Google Protocol Buffers，GPB)、抽象语法编码1(Abstract Syntax Notation One，ASN.1)等。
步骤204、映射模板数据库功能模块(Mapper catalog)向SDNC发送通知消息，该通知消息用于指示数据转换模板的创建、更新或删除的结果。
相应的，SDNC接收映射模板数据库功能模块(Mapper catalog)发送的通知消息。该通知消息可以用于指示数据转换模板的创建、更新或删除成功，也可以用指示数据转换模板的创建、更新或删除失败。
本实施例，NMS向SDNC发送第一服务请求消息，该第一服务请求消息用于创建、更新或删除数据转换模板，SDNC向映射模板数据库功能模块(Mapper catalog)发送第七消息，该第七消息用于创建、更新或删除数据转换模板，映射模板数据库功能模块(Mapper catalog)根据该第七消息创建、更新或删除数据转换模板，映射模板数据库功能模块(Mapper catalog)向SDNC发送通知消息，该通知消息用于指示数据转换模板的创建、更新或删除的结果，实现对数据转换模板的创建、更新或删除，基于不同的数据转换模板可 以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
由上述图1所示，本申请实施例的采集器的类型有多种，例如，VES采集器(VES Collector)、文件采集器(File Collector)、流采集器(Stream Collector)、或SNMP Trap采集器(SNMP Trap Collector)等，且不同的采集器支持不同的网络协议和/或编码方式。因此，当每个采集器部署(deploy)成功后，采集器需要将其属性能力信息发送给数据映射处理功能模块，由数据映射处理功能模块统一管理所有采集器，例如，该属性能力信息可以是采集器的标识信息(例如，采集器的名称(Collector name))、采集器支持的数据类型(Domain type)、采集器支持的编码方式(Supported-datatype)和采集器的地址(Target address)等。当SDNC与数据映射处理功能模块进行采集器能力协商时，数据映射处理功能模块可以基于采集器的属性能力信息向SDNC反馈结果。当采集器下线时，也可以通过相关流程删除数据映射处理功能模块中采集器的属性能力信息。
以数据映射处理功能模块对上线的采集器进行管理为例进行举例说明，其具体实施方式可以参见下述实施例的解释说明。
图4为本申请实施例的一种数据处理方法的流程图，如图4所示，本实施例涉及采集器和数据映射处理功能模块，该采集器可以是VES采集器(VES Collector)、文件采集器(File Collector)、流采集器(Stream Collector)、或SNMP Trap采集器(SNMP Trap Collector)等，本实施例的方法可以包括：
步骤301、采集器基于ONAP当前的功能模块部署机制OOM完成上线部署。
步骤302、采集器向数据映射处理功能模块发送第一消息。
相应的，数据映射处理功能模块接收采集器发送的第一消息。该第一消息用于通知采集器上线成功。示例性的，该第一消息可以包括采集器的属性能力信息，该属性能力信息可以包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
该数据映射处理功能模块可以是采集器中配置的管理该采集器的数据映射处理功能模块。例如，采集器部署时，采集器中会配置管理该采集器的数据映射处理功能模块的信息，该数据映射处理功能模块的信息可以是数据映射处理功能模块的IP地址(Data Mapper IP address)等，采集器上线后，可向该IP地址所标示的数据映射处理功能模块发送该第一消息。
需要说明的是，该第一消息也可以采用其他消息名称，例如，采集器注册请求消息(Collector register request)等，其消息名称不以此作为限制。
步骤303、数据映射处理功能模块根据该第一消息创建该采集器的上下文。
该上下文可以包括如上所述的采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址等属性能力信息。
步骤304、数据映射处理功能模块向采集器发送第六消息。
相应的，采集器接收数据映射处理功能模块发送的第六消息，该第六消息可以包括采集器的标识信息和注册结果，或者，可以包括采集器的注册结果，例如，注册结果可以是 接受注册(Registration-accept)、拒绝注册(Registration-reject)、错误(Error)等。例如，当书记映射模块通过步骤303成功为采集器创建上下文后，可以向采集器发送指示接受注册的第六消息。
需要说明的是，第六消息也可以采用其他消息名称，例如，采集器注册回复消息(Collect register response)、注册响应消息等，其消息名称不以此作为限制。
对于采集器下线的去注册流程，其实现原理与采集器上线的注册流程类似，例如，在需要下线时，向数据映射处理功能模块发送采集器去注册请求消息，该采集器去注册请求消息用于指示数据映射处理功能模块删除该采集器的上下文，数据映射处理功能模块根据该采集器去注册请求消息删除该采集器的上下文，向采集器发送去注册响应消息，例如，该去注册响应消息用于指示接受去注册。
本申请实施例，通过采集器在上线或下线时，向数据映射处理功能模块发送相应消息，数据映射处理功能模块根据该消息创建上下文或删除上下文，从而在采集器的动态灵活部署过程中，数据映射处理功能模块可以及时获得上线的采集器及其属性能力信息，由数据映射处理功能模块统一管理各个采集器，在后续与SDNC进行业务能力协商过程中，可以基于各个采集器的属性能力信息决定数据采集与转换能力，以提供满足需求的数据收集服务。
以采集器为文件采集器(File Collector)为例，对本申请实施例的数据处理方法进行举例说明。
图5为本申请实施例的一种数据处理方法的流程图，如图5所示，本实施例涉及NMS、SDNC、EN/EMS、文件采集器(File Collector)、数据映射处理功能模块、映射模板数据库功能模块(Mapper catalog)、以及数据消费者模块，本实施例的方法可以包括：
步骤401、NMS向SDNC发送第二服务请求消息。
相应的，SDNC接收NMS发送的第二服务请求消息。该第二服务请求消息用于创建数据收集服务，以使得采集器完成不同传输协议和/或数据格式的上报的数据收集，数据映射处理功能模块完成不同数据来源的上报的数据到满足VES规范的转换。
在一些实施例中，该第二服务请求消息包括NMS支持的上报方式(reportingMethod)、NMS支持的数据类型或NMS支持的编码方式中至少一项。该NMS支持的数据类型和NMS支持的编码方式可以与图2所示实施例的步骤101中的NMS支持的数据类型和NMS支持的编码方式相同，其具体解释说明可以参见上述实施例，此处不再赘述。该NMS支持的上报方式用于指示文件上报或流上报。
示例性的，该第二服务请求消息还可以包括对象列表，该对象列表用于指示至少一个网元，网络管理系统用于管理至少一个网元中的一个或多个网元，例如，该对象列表包括对象类别列表(IOC class list)和对象类实例列表(IOC instance list)，该对象类别列表可以是信息对象类(information object class，iOC)对象列表(InstanceList)。该iOC对象实例列表用于指示一个或多个管理对象实例(managed object instance)，一个或多个管理对象实例对应一个NE，EMS可以管理一个或多个NE。
示例性的，该NMS支持的上报方式、NMS支持的数据类型或NMS支持的编码方式可以是数据消费者模块所支持的上报方式、数据类型或编码方式。
在一些实施例中，在执行步骤401之前还可以在NE上线(onboarding)过程中将数据转换模板保存到映射模板数据库功能模块中，例如，如图5所示的步骤0，该步骤0的虚线框表示其执行顺序不以序号及图示上下作为限制，其实现方式可以包括图3所示实施例的各个步骤，其具体解释说明，此处不再赘述。
步骤4021a、SDNC向NE/EMS发送第一能力协商消息。
相应的，NE/EMS接收SDNC发送的第一能力协商消息。该第一能力协商消息用于触发NE/EMS反馈是否支持上述第二服务请求消息所携带的上报方式、数据类型或编码方式中至少一项。即SDNC基于步骤401中的上报方式、数据类型和/或编码方式向NE/EMS发起能力协商。该第一能力协商消息可以包括NMS支持的数据类型、NMS支持的编码方式或NMS支持的上报方式(reportingMethod)中的一项或多项。在一些实施例中，该第一能力协商消息还可以包括对象类别列表(IOC class list)和对象类实例列表(IOC instance list)。
步骤4022a、NE/EMS解析该对象类别列表(IOC class list)和对象类实例列表(IOC instance list)，获取标识信息。
例如，该标识信息是NE的ID列表，该NE的ID列表可以包括一个或多个网元的ID，NE/EMS根据该NE的ID列表查询相应的NE是否支持该数据上报方式、该数据类型或编码方式中的一项或多项。
步骤4023a、NE/EMS向SDNC发送第一响应消息。
相应的，SDNC接收一个或多个NE/EMS发送的第一响应消息。该第一响应消息用于指示该NE的ID列表对应的各个NE是否支持该数据类型、编码方式和/或上报方式时。例如，该第一响应消息携带NE ID和确认信息，该确认信息用于指示ACK，即表示该NE ID对应的NE支持该数据类型和编码方式。当存在NE不支持该数据类型、或编码方式时，该第一响应消息可以携带NE ID和不确认信息，该不确认信息用于指示NACK。存在不支持该数据类型或编码方式的NE时，执行步骤4023a后，可以执行步骤407。存在支持该数据类型或编码方式的NE时，执行步骤4023a后，可以执行步骤408。
步骤4021b、SDNC解析对象类别列表(IOC class list)和对象类实例列表(IOC instance list)，获取标识信息。
该标识信息的具体解释说明可以参见步骤4022a的解释说明，此处不再赘述。
步骤4022b、SDNC向NE/EMS发送第一能力协商消息。
该第一能力协商请求消息的解释说明可以参见步骤4021a，此处不再赘述。其不同之处在于，步骤4022b中的第一能力协商消息不包括对象类别列表(IOC class list)和对象类实例列表(IOC instance list)，而包括的是NE的ID列表。该NE的ID列表可以包括一个或多个网元的ID，NE/EMS根据该NE的ID列表查询相应的NE是否支持该数据类型、编码方式和/或上报方式。
步骤4023b、NE/EMS向SDNC发送第一响应消息。
其中，步骤4023b的解释说明可以参见步骤4023a的解释说明，此处不再赘述。
上述步骤4021a至步骤4023a，或者，上述步骤4021b至步骤4023b，可以确认NE/EMS是否支持步骤401中的数据类型和编码方式。在执行步骤401之后，可以执行步骤4021a至步骤4023a，或者，执行步骤4021b至步骤4023b。其中图5中的步骤4021a至步骤4023a的虚线框，步骤4021b至步骤4023b的虚线框表示可选的。
步骤403、SDNC向数据映射处理功能模块发送第二消息。
相应的，数据映射处理功能模块接收SDNC发送的第二消息。该第二消息用于指示数据收集需求。
在一些实施例中，该第二消息可以包括步骤401中的数据类型、编码方式、或上报方式中至少一项。SDNC通过该第二消息，查询采集器是否支持相应的数据类型、编码方式或上报方式。该上报方式可以是NMS支持的上报方式(reportingMethod)，例如，流上报或文件上报。
步骤404、数据映射处理功能模块根据该第二消息和上下文确定是否存在满足数据收集需求的采集器。
数据映射处理功能模块基于本地存储的各个采集器的上下文，例如，通过上述图4所示实施例所创建的上下文，查询是否存在相应的采集器，该采集器是否支持数据类型和编码方式。
步骤405、数据映射处理功能模块向SDNC发送第三消息。
相应的，SDNC接收数据映射处理功能模块发送的第三消息。该第三消息用于指示满足数据收集需求的采集器的信息。例如，第三消息可以包括采集器的目标地址和结果，或者采集器的标识信息和结果，或者采集器的目的地址、标识信息和结果，该结果可以用于指示确认(ack)或不确认(nack)。当该结果指示不确认(nack)时，执行步骤406。当该结果指示确认(ack)时，可以执行步骤407。
步骤406、SDNC向NMS反馈失败信息。
步骤407、SDNC向NE/EMS发送数据收集请求消息。
相应的，NE/EMS接收SDNC发送的该数据收集请求消息。该数据收集请求消息可以包括上报方式、采集周期(granularityPeriod)、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项。
针对性能管理，SDNC创建性能测量任务，携带上报方式、采集周期(granularityPeriod)、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项，NE/EMS收到任务后返回确认信息。针对告警管理，SDNC向NE/EMS发起配置请求，携带上报方式、采集周期(granularityPeriod)、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项，配置告警数据上报的上报方式，NE/EMS收到配置请求后返回确认信息。
需要说明的是，该数据收集请求消息可以是发送给通过上述步骤4021a至步骤4023a，或者，上述步骤4021b至步骤4023b，反馈支持步骤401中的上报方式、数据类型和/或编码方式的NE/EMS。
步骤408、NE/EMS根据该数据收集请求消息定时向SDNC发送文件准备通知消息。
NE/EMS根据该采集周期(granularityPeriod)定时向SDNC发送文件准备(FileReady)通知消息。该文件准备通知消息可以携带文件信息列表(FileinfoList)、厂商名称(Vendorname)、网元版本信息(NEversion)等参数，其中，文件信息列表(FileinfoList)可以包括文件位置(fileLocation)、文件大小(fileSize)、文件准备时间(fileReadyTime)、文件过期时间(fileExpirationTime)、文件压缩(fileCompression)、文件格式(fileFormat)等信息。
步骤409、SDNC向文件采集器发送第四消息。
相应的，文件采集器接收SDNC发送的第四消息。该第四消息可以包括文件信息和数据描述信息，该文件信息用于指示上述步骤408中的各个参数，该数据描述信息可以包括如图2所示实施例的步骤101所描述的各项信息，其具体解释说明，此处不再赘述。
步骤410、文件采集器根据文件信息从对应的位置下载上报的数据。
该上报的数据来源于NE/EMS。该上报的数据可以为文件数据。
步骤411、文件采集器向数据映射处理功能模块发送数据描述信息和文件数据。
步骤412、数据映射处理功能模块向映射模板数据库功能模块发送请求模板消息。
该请求模板消息可以携带该数据描述信息。
步骤413、映射模板数据库功能模块根据该数据描述信息匹配合适的数据转换模板，并向该数据转换模板反馈匹配结果。
其中，该匹配结果可以包括数据转换模板，或者，用于指示没有合适的数据转换模板的信息。该数据转换模板的解释说明具体可以参见图3所示实施例的解释说明，此处不再赘述。
步骤414、数据映射处理功能模块根据该数据转换模块对文件数据进行转换，转换后的文件数据满足VES规范。
当数据映射处理功能模块接收到映射模板数据库功能模块反馈的数据转换模板时，数据映射处理功能模块通过步骤414对上述的文件数据进行转换，之后执行下述步骤416。当数据映射处理功能模块接收到映射模板数据库功能模块反馈的没有合适的数据转换模板时，执行下述步骤415对上述的文件数据进行转换。
其中，该VES规范的解释说明可以参见图2所示实施例的步骤102，此处不再赘述。
步骤415、数据映射处理功能模块向SDNC发送数据转换失败消息。该数据转换失败消息用于指示数据转换出现错误。
步骤416、数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的文件数据。
本实施例，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
以采集器为流采集器(Stream Collector)为例，对本申请实施例的数据处理方法进行举例说明。
图6为本申请实施例的一种数据处理方法的流程图，如图6所示，本实施例涉及NMS、SDNC、EN/EMS、流采集器(Stream Collector)、数据映射处理功能模块、映射模板数据库功能模块(Mapper catalog)、以及数据消费者模块，本实施例的方法可以包括：
步骤501、NMS向SDNC发送第二服务请求消息。
其中，步骤501的具体实现方式可以参见图5所示实施例的步骤401，此处不再赘述。
步骤502、确认NE/EMS是否支持步骤501中的数据类型和编码方式。
其中，步骤502的具体实现方式可以采用图5所示实施例的步骤4021a至步骤4023a，或者，步骤4021b至步骤4023b，此处不再赘述。
步骤503、SDNC向数据映射处理功能模块发送第二消息。
步骤504、数据映射处理功能模块根据该第二消息和上下文确定是否存在满足数据收集需求的采集器。
其中，步骤503至步骤504的解释说明可以参见图5所示实施例的步骤403至步骤404，此处不再赘述。
步骤505、数据映射处理功能模块向SDNC发送第三消息。
相应的，SDNC接收数据映射处理功能模块发送的第三消息。本实施例的第三消息可以包括流采集器的目标地址和结果。该结果可以用于指示确认(ack)或不确认(nack)。当该结果指示不确认(nack)时，执行步骤506。当该结果指示确认(ack)时，可以执行步骤507。该流采集器的目标地址可以方便下述步骤中，NE/EMS与流采集器建立TCP连接。该目标地址可以是流采集器的IP和端口信息。
步骤506、SDNC向NMS反馈失败信息。
步骤507、SDNC向NE/EMS发送数据收集请求消息。
其中，步骤507的解释说明可以参见图5所示实施例的步骤407，此处不再赘述。其中，该数据收集请求消息中还包括上述流采集的目标地址。
步骤508、NE/EMS根据该数据收集请求消息与流采集器建立TCP连接，并将数据收集请求消息中的各项参数发送给流采集器，并根据采集周期(granularityPeriod)定时发送上报的数据。
该上报的数据可以是流数据。
步骤509、流采集器检索到流数据并将流数据解码。
步骤510、流采集器向数据映射处理功能模块发送解码后的流数据和数据描述信息。
步骤512、数据映射处理功能模块向映射模块发送请求模板信息。
步骤513、映射模板数据库功能模块根据该数据描述信息匹配合适的数据转换模板，并向该数据转换模板反馈匹配结果。
其中，该匹配结果可以包括数据转换模板，或者，用于指示没有合适的数据转换模板的信息。该数据转换模板的解释说明具体可以参见图3所示实施例的解释说明，此处不再赘述。
步骤514、数据映射处理功能模块根据该数据转换模块对流数据进行转换，转换后的流数据满足VES规范。
当数据映射处理功能模块接收到映射模板数据库功能模块反馈的数据转换模板时，数据映射处理功能模块通过步骤514对上述的流数据进行转换，之后执行下述步骤516。当数据映射处理功能模块接收到映射模板数据库功能模块反馈的没有合适的数据转换模板时，执行下述步骤515对上述的流数据进行转换。
其中，该VES规范的解释说明可以参见图2所示实施例的步骤102，此处不再赘述。
步骤515、数据映射处理功能模块向SDNC发送数据转换失败消息。该数据转换失败消息用于指示数据转换出现错误。
步骤516、数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的流数据。
本实施例，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上 报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
以采集器为SNMP Trap采集器(SNMP Trap Collector)为例，对本申请实施例的数据处理方法进行举例说明。
图7为本申请实施例的一种数据处理方法的流程图，如图7所示，本实施例涉及NMS、SDNC、EN/EMS、SNMP Trap采集器(SNMP Trap Collector)、数据映射处理功能模块、映射模板数据库功能模块(Mapper catalog)、以及数据消费者模块，本实施例的方法可以包括：
步骤601、NMS向SDNC发送第二服务请求消息。
其中，步骤601的具体实现方式可以参见图5所示实施例的步骤401，此处不再赘述。
步骤602、确认NE/EMS是否支持步骤601中的数据类型和编码方式。
其中，步骤602的具体实现方式可以采用图5所示实施例的步骤4021a至步骤4023a，或者，步骤4021b至步骤4023b，此处不再赘述。
步骤603、SDNC向数据映射处理功能模块发送第二消息。
步骤604、数据映射处理功能模块根据该第二消息和上下文确定是否存在满足数据收集需求的采集器。
步骤605、数据映射处理功能模块向SDNC发送第三消息。
步骤606、SDNC向NMS反馈失败信息。
步骤607、SDNC向NE/EMS发送数据收集请求消息。
其中，步骤603至步骤607的解释说明可以参见图5所示实施例的步骤403至步骤407，此处不再赘述。
步骤608、NE/EMS向SDNC返回确认消息，该确认消息可以包括厂商名称(Vendorname)、网元版本信息(NEversion)等数据描述信息以及MIB数据，其中MIB数据用于解析SNMP协议内容。
步骤609、SDNC向SNMP Trap采集器发送第五消息。
SNMP Trap采集器接收SDNC发送的第五消息，该第五消息可以数据描述信息和MIB数据。
步骤610、当NE/EMS有新告警产生时，触发告警Trap，向SNMP Trap采集器发送告警数据。
具体的，NE/EMS可以根据数据收集请求消息中的目标地址，将告警数据发送到SNMP Trap采集器。
步骤611、SNMP Trap采集器收到告警数据，根据MIB数据解码SNMP协议告警数据，将OID数据转换为字符数据。
步骤612、SNMP Trap采集器向数据映射处理功能模块发送字符数据和数据描述信息。
步骤613、数据映射处理功能模块向映射模块发送请求模板信息。
步骤614、映射模板数据库功能模块根据该数据描述信息匹配合适的数据转换模板，并向该数据转换模板反馈匹配结果。
其中，该匹配结果可以包括数据转换模板，或者，用于指示没有合适的数据转换模板的信息。该数据转换模板的解释说明具体可以参见图3所示实施例的解释说明，此处不再赘述。
步骤615、数据映射处理功能模块根据该数据转换模块对字符数据进行转换，转换后的字符数据满足VES规范。
当数据映射处理功能模块接收到映射模板数据库功能模块反馈的数据转换模板时，数据映射处理功能模块通过步骤615对上述的流数据进行转换，之后执行下述步骤617。当数据映射处理功能模块接收到映射模板数据库功能模块反馈的没有合适的数据转换模板时，执行下述步骤616对上述的流数据进行转换。
其中，该VES规范的解释说明可以参见图2所示实施例的步骤102，此处不再赘述。
步骤616、数据映射处理功能模块向SDNC发送数据转换失败消息。该数据转换失败消息用于指示数据转换出现错误。
步骤617、数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的字符数据。
本实施例，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的上报的数据转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
以采集器为VES采集器(VES Collector)为例，对本申请实施例的数据处理方法进行举例说明。
图8为本申请实施例的一种数据处理方法的流程图，如图8所示，本实施例涉及NMS、SDNC、EN/EMS、VES采集器(VES Collector)、数据映射处理功能模块、映射模板数据库功能模块(Mapper catalog)、以及数据消费者模块，本实施例的方法可以包括：
步骤701、NMS向SDNC发送第二服务请求消息。
其中，步骤701的具体实现方式可以参见图5所示实施例的步骤401，此处不再赘述。
步骤702、确认NE/EMS是否支持步骤701中的数据类型和编码方式。
其中，步骤702的具体实现方式可以采用图5所示实施例的步骤4021a至步骤4023a，或者，步骤4021b至步骤4023b，此处不再赘述。
步骤703、SDNC向数据映射处理功能模块发送第二消息。
步骤704、数据映射处理功能模块根据该第二消息和上下文确定是否存在满足数据收集需求的采集器。
步骤705、数据映射处理功能模块向SDNC发送第三消息。
步骤706、SDNC向NMS反馈失败信息。
步骤707、SDNC向NE/EMS发送数据收集请求消息。
其中，步骤703至步骤707的解释说明可以参见图5所示实施例的步骤403至步骤407，此处不再赘述。
步骤708、NE/EMS向SDNC返回确认消息。
步骤709、NE/EMS向VES采集器发送事件通知，该事件通知包括VES事件和数据描 述信息。
例如，该数据描述信息包括数据类型等信息。
步骤710、VES采集器查询收集到的VES事件，如果该VES事件的VES规范版本与ONAP使用的版本一致，则执行步骤711，如果该VES事件的VES规范版本与ONAP使用的版本不一致，则执行步骤712。
步骤711、VES采集器将VES事件发送到数据消费者模块。
步骤712、VES采集器将VES事件和数据描述信息发送至数据映射处理功能模块。
步骤713、数据映射处理功能模块根据数据描述信息，将VES事件转换为使用的VES规范版本，并将转换后的VES事件发送给数据消费者模块。
数据映射处理功能模块可以基于数据类型，将与ONAP使用的不同VES规范版本的数据转换为使用的VES规范版本(例如，采用增加或减少数据内容的方式)。
本实施例，可以增强对支持不同版本VES规范的数据的处理功能，实现了NE支持不同版本MV VES规范数据的情况下，VES数据自动转换为ONAP使用的MV VES规范的功能。
下面以NMS通过SDNC中的RESTAPI接口获得网元的告警信息，并将告警信息传输到DCAE中的过程，对本申请实施例的数据处理方法进行举例说明，本实施例针对告警管理。
图9为本申请实施例的一种数据处理方法的流程图，如图9所示，本实施例涉及NMS、SDNC、EN/EMS、数据映射处理功能模块、映射模板数据库功能模块(Mapper catalog)、以及数据消费者模块，本实施例的方法可以包括：
步骤801、NMS向SDNC发送第二服务请求消息。
相应的，SDNC接收NMS发送的第二服务请求消息。该第二服务请求消息用于创建数据收集服务，例如，该数据收集服务可以是收集告警信息。
步骤802a、SDNC通过获取告警列表接口(getAlarmList API)向NE/EMS发送告警请求消息。
该告警请求消息用于获取告警信息列表，该告警请求消息可以携带告警确认状态(alarmAckState)和过滤条件(filter)，其中，告警确认状态(alarmAckState)的取值范围为所有告警(allAlarms)、所有激活的告警(allActiveAlarms)，所有激活且已确认的告警(allActiveAndAcknowledgedAlarms),所有激活但未确认的告警(allActiveAndUnacknowledgedAlarms),所有清楚的且未确认的告警(allClearedAndUnacknowledgedAlarms),所有未确认的告警(allUnacknowledgedAlarms)。
步骤803a、NE/EMS返回告警信息(alarmInformation)和附加信息(addtionalInfo)。
其中，附加信息(addtionalInfo)可以包括NE的信息，如厂商名称、网元版本信息等。
步骤804a、SDNC向数据映射处理功能模块发送数据描述信息和告警信息。
其中，数据描述信息可以包括上述附加信息、以及采集器的名称和数据类型，本实施例中该采集器的名称为告警表征状态转移(Representational State Transfer，REST)协议适配器(Adaptor)，该FMREST Adaptor为SDNC中的功能模块，通过该FMREST Adaptor表明是通过RestAPI获得的告警信息。该数据类型为告警(fault)
步骤805a、数据映射处理功能模块向映射模板数据库功能模块发送请求模板消息。
该请求模板消息可以包括厂商名称、网元版本信息和数据类型。
步骤802b、SDNC向NE/EMS发起告警通知订阅请求。
该告警通知订阅请求包括订阅信息，该订阅信息可以包括告警通知类型，该告警通知类型可以是新告警通知(notifyNewAlarm)、确认状态改变通知(notifyAckStateChanged)、notifyClearedAlarm(清楚告警通知)、重构告警通知(notifyAlarmListRebuiltAlarm)、告警信息变化通知(notifyChangedAlarm)、注释通知(notifyComments)、潜在告警列表通知(notifyPotentialFaultyAlarmList)、关联通知变化通知(notifyCorrelatedNotificationChanged)、告警通用信息改变(notifyChangedAlarmGeneral)等。
步骤803b、NE/EMS基于订阅信息，当告警产生时，向SDNC发送告警通知。
该告警通知的通知类型的取值范围为步骤802b中的告警通知类型，以新告警产生为例，NE/EMS发送新告警产生通知，携带通知类型(notificationType)、附加信息(addtionalInfo)和告警信息。其中，附加信息(addtionalInfo)可以包括NE的信息，如厂商名称、网元版本信息等。
步骤804b、SDNC将数据描述信息和告警信息发送到数据映射处理功能模块。
该数据描述信息可以包括上述附加信息、以及采集器的名称和数据类型，本实施例中该采集器的名称为告警表征状态转移(Representational State Transfer，REST)协议适配器(Adaptor)，该FMREST Adaptor为SDNC中的功能模块，通过该FMREST Adaptor表明是通过RestAPI获得的告警信息。该数据类型为告警(fault)。
步骤805b、数据映射处理功能模块向映射模板数据库功能模块发送请求模板消息。
该请求模板消息可以包括厂商名称、网元版本信息和数据类型。
步骤806、映射模板数据库功能模块向数据映射处理功能模块发送数据转换模板。
该数据转换模板可以是映射模板数据库功能模块基于步骤805a或步骤805b发送的请求模板消息，所匹配到的数据转换模板。
步骤807、数据映射处理功能模块根据数据转换模板对告警信息进行转换，转换后的告警信息满足VES规范。
步骤808、数据映射处理功能模块向数据消费者模块发送VES事件，该VES事件包括转换后的告警信息。
本实施例，可以将不同来源(例如，不同厂商、不同类型网元、不同网元版本)的告警信息转换为满足VES规范的数据，从而使得数据消费者(例如，ONAP Consumer)模块可以直接使用该转换后的上报的数据，以提升数据消费者模块对上报的数据的分析或使用效率。
图10为本申请实施例提供的数据处理装置900的示意性框图。本实施例的数据处理装置900可以作为上述方法实施例所涉及的数据映射处理功能模块，该数据处理装置900包括收发单元901和处理单元902。
在一个实施例中，数据处理装置900的各单元分别用于执行如下操作和/或处理。
收发单元901，用于接收数据描述信息和上报的数据，该数据描述信息包括厂商名称、 网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
处理单元902，用于根据该数据描述信息对所述上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流VES规范。
收发单元901，还用于发送VES事件，所述VES事件包括该转换后的上报的数据。
在一种可能的实现方式中，该数据描述信息和上报的数据来自于采集器或软件定义网络控制器SDNC中至少一项，该采集器包括文件采集器、流采集器、SNMP trap采集器或VES采集器中至少一项。
在一种可能的实现方式中，收发单元901还用于：接收采集器发送的第一消息，该第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。处理单元902还用于根据该第一消息创建采集器的上下文，该上下文包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
在一种可能的实现方式中，收发单元901还用于：向采集器发送第六消息，该第六消息包括采集器的标识信息和注册结果。
在一种可能的实现方式中，当采集器为文件采集器、流采集器或SNMP trap采集器时，处理单元902用于：根据该数据描述信息确定对应的数据转换模板，该数据映射模块用于将上报的数据转换为符合VES规范的VES事件，根据该数据转换模板对上报的数据进行转换。
在一种可能的实现方式中，收发单元901还用于：接收SDNC发送的第七消息，该第七消息用于创建、更新或删除数据转换模板。
在一种可能的实现方式中，该第七消息包括厂商名称、网元版本信息、数据类型或编码方式中至少一项，以及数据模板信息。
在一种可能的实现方式中，收发单元901还用于接收SDNC发送的第二消息，该第二消息用于指示数据收集需求，处理单元902还用于根据第二消息和上下文确定是否存在满足数据收集需求的采集器，收发单元901还用于向SDNC发送第三消息，该第三消息用于指示满足数据收集需求的采集器的信息。
在一种可能的实现方式中，该第二消息包括上报方式、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项。
在一种可能的实现方式中，当满足数据收集需求的采集器为文件采集器或VNF事件流采集器时，该第三消息包括采集器的标识信息。
在一种可能的实现方式中，当满足数据收集需求的采集器为流采集器或SNMP trap采集器时，该第三消息包括采集器的标识信息或采集器的地址中至少一项。
在一种可能的实现方式中，当采集器为VES采集器时，该数据描述信息包括数据类型，处理单元902用于根据数据类型对上报的数据所包括的元素进行增加或删除。
在一种可能的实现方式中，该上报的数据包括文件数据、流数据、告警数据、VES事件或字符数据中至少一项。
可选地，数据处理装置900也可以同时具有方法实施例中数据映射处理功能模块的其它功能。类似说明可以参考前述方法实施例的描述。为避免重复，这里不再赘述。
可选地，处理单元902可以是处理器，收发单元901可以是收发器。收发器包括接收器和发射器，同时具有发送和接收的功能。
可选地，处理单元902可以是一个处理装置，处理装置的功能可以部分或全部通过软件实现。
在一种可能的实现方式中，处理装置的功能可以部分或全部通过软件实现。此时，处理装置可以包括存储器和处理器。其中，存储器用于存储计算机程序，处理器读取并执行存储器中存储的计算机程序，以执行各方法实施例中由数据映射处理功能模块内部实现的步骤。
可选地，在一种可能的实现方式中，处理装置包括处理器。用于存储计算机程序的存储器位于处理装置之外，处理器通过电路/电线与存储器连接，以读取并执行存储器中存储的计算机程序。
在另一个实施例中，数据处理装置900可以为芯片。此时，收发单元901具体可以为通信接口或者收发电路。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行上述任一方法实施例中由数据映射处理功能模块执行的步骤和/或处理。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述任一方法实施例中由数据映射处理功能模块执行的步骤和/或处理。
本申请还提供一种芯片，所述芯片包括处理器。用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，以执行任一方法实施例中由数据映射处理功能模块执行的步骤和/或处理。
进一步地，所述芯片还可以包括存储器和通信接口。所述通信接口可以是输入/输出接口、管脚或输入/输出电路等。
图11为本申请实施例提供的一种数据处理装置1000的结构示意图。如图11所示，数据处理装置1000可以是上述实施例中涉及到的数据映射处理功能模块。数据处理装置1000包括处理器1001和收发器1002。
可选地，数据处理装置1000还包括存储器1003。其中，处理器1001、收发器1002和存储器1003之间可以通过内部连接通路互相通信，传递控制信号和/或数据信号。
其中，存储器1003用于存储计算机程序。处理器1001用于执行存储器1003中存储的计算机程序，从而实现上述装置实施例中的各功能。
可选地，存储器1003也可以集成在处理器1001中，或者独立于处理器1001。
上述装置实施例可以用于执行方法实施例中数据映射处理功能模块的技术方案，其实现原理和技术效果类似，此处不再赘述。
图12为本申请实施例提供的采集器1100的示意性结构图。采集器1100可以对应各方法实施例中的采集器。如图12所示，采集器1100包括收发单元1101和处理单元1102。
在一个实施例中，采集器1100的各单元分别用于执行如下操作和/或处理。
收发单元1101，用于接收数据描述信息。
处理单元1102，用于通过收发单元1101向数据映射处理功能模块发送该数据描述信息和上报的数据，该数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数 据类型或编码方式中至少一项。
在一种可能的实现方式中，收发单元1101还用于向数据映射处理功能模块发送第一消息，该第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
在一种可能的实现方式中，该采集器1100为文件采集器，该上报的数据为文件数据，收发单元1101用于接收软件定义网络控制器SDNC发送的第四消息，该第四消息包括文件信息和该数据描述信息，该文件信息用于指示文件数据的位置；处理单元1102还用于通过收发单元1101，根据文件信息从对应的位置下载文件数据。
在一种可能的实现方式中，该采集器1100为流采集器，该上报的数据为流数据，收发单元1101用于与网元或网元管理系统建立TCP连接；处理单元1102还用于通过TCP连接接收流数据和数据描述信息。
在一种可能的实现方式中，该采集器1100为SNMP trap采集器，该上报的数据为字符数据，收发单元1101用于接收SDNC发送的第五消息，该第五消息包括数据描述信息和MIB数据；收发单元1101还用于接收网元或网元管理系统发送的告警数据；处理单元1102还用于根据MIB数据将告警数据解码为字符数据。
在一种可能的实现方式中，该采集器1100为VES采集器，该上报的数据为VES事件，收发单元1101用于接收网元或网元管理系统发送的VES事件和数据描述信息，该数据描述信息包括网络管理系统支持的数据类型。
可选地，处理单元1102可以是处理器，收发单元1101可以是收发器。收发器包括接收器和发射器，同时具有发送和接收的功能。
可选地，处理单元1102可以是一个处理装置，处理装置的功能可以部分或全部通过软件实现。
在一种可能的实现方式中，处理装置的功能可以部分或全部通过软件实现。此时，处理装置可以包括存储器和处理器。其中，存储器用于存储计算机程序，处理器读取并执行存储器中存储的计算机程序，以执行各方法实施例中由采集器内部实现的步骤。
可选地，在一种可能的实现方式中，处理装置包括处理器。用于存储计算机程序的存储器位于处理装置之外，处理器通过电路/电线与存储器连接，以读取并执行存储器中存储的计算机程序。
在另一个实施例中，数据处理装置1100可以为芯片。此时，收发单元1101具体可以为通信接口或者收发电路。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行上述任一方法实施例中由采集器执行的步骤和/或处理。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述任一方法实施例中由采集器执行的步骤和/或处理。
本申请还提供一种芯片，所述芯片包括处理器。用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，以执行任一方法实施例中由采集器执行的步骤和/或处理。
进一步地，所述芯片还可以包括存储器和通信接口。所述通信接口可以是输入/输出接口、管脚或输入/输出电路等。
图13为本申请实施例提供的一种采集器1200的结构示意图。如图13所示，采集器1200可以是上述实施例中涉及到采集器。采集器1200包括处理器1201和收发器1202。
可选地，采集器1200还包括存储器1203。其中，处理器1201、收发器1202和存储器1203之间可以通过内部连接通路互相通信，传递控制信号和/或数据信号。
其中，存储器1203用于存储计算机程序。处理器1201用于执行存储器1203中存储的计算机程序，从而实现上述装置实施例中的各功能。
可选地，存储器1203也可以集成在处理器1201中，或者独立于处理器1201。
上述装置实施例可以用于执行方法实施例中采集器的技术方案，其实现原理和技术效果类似，此处不再赘述。
图14为本申请实施例提供的数据处理装置1300的示意性结构图。数据处理装置1300可以对应各方法实施例中的网元或网元管理系统。如图14所示，数据处理装置1300包括收发单元1301和处理单元1302。
在一个实施例中，数据处理装置1300的各单元分别用于执行如下操作和/或处理。
收发单元1301，用于接收软件定义网络控制器SDNC发送的数据收集请求消息，该数据收集请求消息包括上报方式、采集周期、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项。
处理单元1302，用于根据所述数据收集请求消息收集文件数据、流数据、告警数据、VES事件或字符数据中至少一项。
在一种可能的实现方式中，处理单元1302还用于通过收发单元1301与流采集器建立TCP连接；通过TCP连接接向流采集器发送流数据和数据描述信息，该数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
在一种可能的实现方式中，收发单元1301还用于：向SDNC发送MIB数据，该MIB数据用于解码告警数据。
在一种可能的实现方式中，收发单元1301还用于：向VES采集器发送VES事件和网络管理系统支持的数据类型。
可选地，处理单元1302可以是处理器，收发单元1301可以是收发器。收发器包括接收器和发射器，同时具有发送和接收的功能。
可选地，处理单元1302可以是一个处理装置，处理装置的功能可以部分或全部通过软件实现。
在一种可能的实现方式中，处理装置的功能可以部分或全部通过软件实现。此时，处理装置可以包括存储器和处理器。其中，存储器用于存储计算机程序，处理器读取并执行存储器中存储的计算机程序，以执行各方法实施例中由网元或网元管理系统内部实现的步骤。
可选地，在一种可能的实现方式中，处理装置包括处理器。用于存储计算机程序的存储器位于处理装置之外，处理器通过电路/电线与存储器连接，以读取并执行存储器中存储的计算机程序。
在另一个实施例中，数据处理装置1300可以为芯片。此时，收发单元1301具体可以为通信接口或者收发电路。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行上述任一方法实施例中由网元或网元管理系统执行的步骤和/或处理。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述任一方法实施例中由网元或网元管理系统执行的步骤和/或处理。
本申请还提供一种芯片，所述芯片包括处理器。用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，以执行任一方法实施例中由网元或网元管理系统执行的步骤和/或处理。
进一步地，所述芯片还可以包括存储器和通信接口。所述通信接口可以是输入/输出接口、管脚或输入/输出电路等。
图15为本申请实施例提供的一种数据处理装置1400的示意性结构图。数据处理装置1400可以对应各方法实施例中的网元或网元管理系统。数据处理装置1400包括处理器1401和收发器1402。
可选地，数据处理装置1400还包括存储器1403。其中，处理器1401、收发器1402和存储器1403之间可以通过内部连接通路互相通信，传递控制信号和/或数据信号。
其中，存储器1403用于存储计算机程序。处理器1401用于执行存储器1403中存储的计算机程序，从而实现上述装置实施例中的各功能。
可选地，存储器1403也可以集成在处理器1401中，或者独立于处理器1401。
上述装置实施例可以用于执行方法实施例中网元或网元管理系统的技术方案，其实现原理和技术效果类似，此处不再赘述。
本申请实施例还提供一种网元或网元管理系统，该网元或网元管理系统采用与图14相同的结构，其中，收发单元，用于接收软件定义网络控制器SDNC发送的第一能力协商消息，所述第一能力协商消息用于触发所述网元或网元管理系统反馈是否支持网络管理系统的上报方式、数据类型或编码方式中至少一项；处理单元，用于通过所述收发单元向所述SDNC发送反馈结果，所述反馈结果用于指示是否支持网络管理系统的上报方式、数据类型或编码方式中至少一项。
在一些实施例中，该第一能力协商消息包括该上报方式、该数据类型、该编码方式和该对象列表，该对象列表用于指示至少一个网元，该网元管理系统用于管理所述至少一个网元中的一个或多个网元；处理单元还用于解析所述对象列表，获取标识信息，根据所述标识信息获取所述网元或网元管理系统是否支持网络管理系统的上报方式、数据类型和编码方式。
图16为本申请实施例提供的软件定义网络控制器1500的示意性结构图。软件定义网络控制器1500可以对应各方法实施例中的SDNC。如图16所示，软件定义网络控制器1500包括收发单元1501和处理单元1502。
在一个实施例中，软件定义网络控制器1500的各单元分别用于执行如下操作和/或处理。
收发单元1501，用于接收网络管理系统发送的服务请求消息，该服务请求消息包括网络管理系统支持的数据类型和网络管理系统支持的编码方式；
收发单元1501，还用于向网元或网元管理系统发送第一能力协商消息，该第一能力协商消息用于触发网元或网元管理系统反馈是否支持该数据类型和该编码方式；
处理单元1502，用于根据网元或网元管理系统的反馈，通过收发单元1501向网元或网元管理系统发送数据收集请求消息。
在一种可能的实现方式中，该服务请求消息还包括对象列表，该第一能力协商消息包括数据类型、编码方式和对象列表，该对象列表用于指示至少一个网元，该网元管理系统用于管理至少一个网元中的一个或多个网元。
在一种可能的实现方式中，该服务请求消息还包括对象列表，该对象列表用于指示至少一个网元，该网元管理系统用于管理该至少一个网元中的一个或多个网元，处理单元1502还用于解析对象列表，获取标识信息；处理单元1502还用于通过收发单元1501向标识信息对应的网元或网元管理系统发送第一能力协商消息。
可选地，处理单元1502可以是处理器，收发单元1501可以是收发器。收发器包括接收器和发射器，同时具有发送和接收的功能。
可选地，处理单元1502可以是一个处理装置，处理装置的功能可以部分或全部通过软件实现。
在一种可能的实现方式中，处理装置的功能可以部分或全部通过软件实现。此时，处理装置可以包括存储器和处理器。其中，存储器用于存储计算机程序，处理器读取并执行存储器中存储的计算机程序，以执行各方法实施例中由SDNC内部实现的步骤。
可选地，在一种可能的实现方式中，处理装置包括处理器。用于存储计算机程序的存储器位于处理装置之外，处理器通过电路/电线与存储器连接，以读取并执行存储器中存储的计算机程序。
在另一个实施例中，软件定义网络控制器1500可以为芯片。此时，收发单元1501具体可以为通信接口或者收发电路。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被计算机执行时，使得计算机执行上述任一方法实施例中由SDNC执行的步骤和/或处理。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述任一方法实施例中由SDNC执行的步骤和/或处理。
本申请还提供一种芯片，所述芯片包括处理器。用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，以执行任一方法实施例中由SDNC执行的步骤和/或处理。
进一步地，所述芯片还可以包括存储器和通信接口。所述通信接口可以是输入/输出接口、管脚或输入/输出电路等。
图17为本申请实施例提供的一种软件定义网络控制器1600的示意性结构图。软件定 义网络控制器1600可以对应各方法实施例中的SDNC。软件定义网络控制器1600包括处理器1601和收发器1602。
可选地，软件定义网络控制器1600还包括存储器1603。其中，处理器1601、收发器1602和存储器1603之间可以通过内部连接通路互相通信，传递控制信号和/或数据信号。
其中，存储器1603用于存储计算机程序。处理器1601用于执行存储器1603中存储的计算机程序，从而实现上述装置实施例中的各功能。
可选地，存储器1603也可以集成在处理器1601中，或者独立于处理器1601。
上述装置实施例可以用于执行方法实施例中SDNC的技术方案，其实现原理和技术效果类似，此处不再赘述。
以上各实施例中提及的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。处理器可以是通用处理器、数字信号处理器(digital signal processor,DSP)、特定应用集成电路(application-specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。本申请实施例公开的方法的步骤可以直接体现为硬件编码处理器执行完成，或者用编码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
上述各实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (30)

  1. 一种数据处理方法，其特征在于，包括：
    接收数据描述信息和上报的数据，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项；
    根据所述数据描述信息对所述上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流VES规范；
    发送VES事件，所述VES事件包括所述转换后的上报的数据。
  2. 根据权利要求1所述的方法，其特征在于，在接收所述数据描述信息和上报的数据之前，所述方法还包括：
    接收采集器发送的第一消息，所述第一消息包括所述采集器的标识信息、所述采集器支持的数据类型、采集器支持的编码方式和采集器的地址；
    根据所述第一消息创建所述采集器的上下文，所述上下文包括所述采集器的标识信息、所述采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
  3. 根据权利要求1或2所述的方法，其特征在于，所述根据所述数据描述信息对所述上报的数据进行转换，包括：
    根据所述数据描述信息确定对应的数据转换模板，所述数据映射模块用于将所述上报的数据转换为符合VES规范的VES事件；
    根据所述数据转换模板对所述上报的数据进行转换。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    接收软件定义网络控制器SDNC发送的第二消息，所述第二消息用于指示数据收集需求；
    根据所述第二消息和所述上下文确定是否存在满足数据收集需求的采集器；
    向所述SDNC发送第三消息，所述第三消息用于指示满足数据收集需求的采集器的信息。
  5. 根据权利要求4所述的方法，其特征在于，当满足数据收集需求的采集器为文件采集器或虚拟网络功能VNF事件流采集器时，所述第三消息包括所述采集器的标识信息；
    当满足数据收集需求的采集器为流采集器或SNMP trap采集器时，所述第三消息包括所述采集器的标识信息或所述采集器的地址中至少一项。
  6. 一种数据处理方法，其特征在于，包括：
    采集器接收数据描述信息；
    所述采集器向数据映射处理功能模块发送所述数据描述信息和上报的数据，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
  7. 根据权利要求6所述的方法，其特征在于，在接收所述数据描述信息和上报的数据之前，所述方法还包括：
    所述采集器向所述数据映射处理功能模块发送第一消息，所述第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
  8. 根据权利要求6或7所述的方法，其特征在于，所述采集器为文件采集器，所述上 报的数据为文件数据，所述采集器接收数据描述信息，包括：所述文件采集器接收软件定义网络控制器SDNC发送的第四消息，所述第四消息包括文件信息和所述数据描述信息，所述文件信息用于指示所述文件数据的位置；所述文件采集器根据所述文件信息从对应的位置下载所述文件数据；或者，
    所述采集器为流采集器，所述上报的数据为流数据，所述采集器接收数据描述信息，包括：所述流采集器与网元或网元管理系统建立传输控制协议TCP连接；所述流采集器通过所述TCP连接接收所述流数据和所述数据描述信息；或者，
    所述采集器为SNMP trap采集器，所述上报的数据为字符数据，所述采集器接收数据描述信息，包括：所述SNMP trap采集器接收SDNC发送的第五消息，所述第五消息包括所述数据描述信息和管理信息库MIB数据；所述SNMP trap采集器接收网元或网元管理系统发送的告警数据；所述SNMP trap采集器根据所述MIB数据将所述告警数据解码为所述字符数据；或者，
    所述采集器为虚拟网络功能事件流VES采集器，所述上报的数据为VES事件，所述采集器接收数据描述信息，包括：所述VES采集器接收网元或网元管理系统发送的VES事件和所述数据描述信息，所述数据描述信息包括网络管理系统支持的数据类型。
  9. 一种数据处理方法，其特征在于，包括：
    接收软件定义网络控制器SDNC发送的数据收集请求消息，所述数据收集请求消息包括上报方式、采集周期、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项；
    根据所述数据收集请求消息收集上报的数据。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    与流采集器建立传输控制协议TCP连接；
    通过所述TCP连接接向所述流采集器发送所述上报的数据和数据描述信息，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    向所述SDNC发送管理信息库MIB数据，所述MIB数据用于解码所述上报的数据；
    或，
    向虚拟网络功能数据流VES采集器发送所述上报的数据和网络管理系统支持的数据类型。
  12. 根据权利要求9至11任一项所述的方法，其特征在于，所述方法还包括：
    接收所述SDNC发送的第一能力协商消息，所述第一能力协商消息用于触发网元或网元管理系统反馈是否支持网络管理系统的上报方式、网络管理系统支持的数据类型或编码方式中至少一项；
    向所述SDNC发送反馈结果，所述反馈结果用于指示是否支持网络管理系统的上报方式、网络管理系统支持的数据类型或编码方式中至少一项。
  13. 一种数据处理方法，其特征在于，包括：
    接收网络管理系统发送的服务请求消息，所述服务请求消息包括上报方式、网络管理系统支持的数据类型或所述网络管理系统支持的编码方式中至少一项；
    向网元或网元管理系统发送第一能力协商消息，所述第一能力协商消息用于触发所述网元或网元管理系统反馈是否支持所述上报方式、所述数据类型或所述编码方式中至少一项；
    根据所述网元或网元管理系统的反馈，向网元或网元管理系统发送数据收集请求消息。
  14. 根据权利要求13所述的方法，其特征在于，所述服务请求消息还包括对象列表，所述方法还包括：
    解析所述对象列表，获取标识信息；
    所述向网元或网元管理系统发送第一能力协商消息，包括：
    向所述标识信息对应的网元或网元管理系统发送第一能力协商消息。
  15. 一种数据处理装置，其特征在于，所述数据处理装置作为数据映射处理功能模块，所述数据处理装置包括：
    收发单元，用于接收数据描述信息和上报的数据，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项；
    处理单元，用于根据所述数据描述信息对所述上报的数据进行转换，转换后的上报的数据满足虚拟网络功能事件流VES规范；
    所述收发单元，还用于发送VES事件，所述VES事件包括所述转换后的上报的数据。
  16. 根据权利要求15所述的装置，其特征在于，所述收发单元还用于：接收采集器发送的第一消息，所述第一消息包括所述采集器的标识信息、所述采集器支持的数据类型、采集器支持的编码方式和采集器的地址；
    所述处理单元，还用于根据所述第一消息创建所述采集器的上下文，所述上下文包括所述采集器的标识信息、所述采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
  17. 根据权利要求15或16所述的装置，其特征在于，所述处理单元用于：根据所述数据描述信息确定对应的数据转换模板，所述数据映射模块用于将所述上报的数据转换为符合VES规范的VES事件；根据所述数据转换模板对所述上报的数据进行转换。
  18. 根据权利要求15至17任一项所述的装置，其特征在于，所述收发单元还用于接收软件定义网络控制器SDNC发送的第二消息，所述第二消息用于指示数据收集需求；
    所述处理单元还用于根据所述第二消息和所述上下文确定是否存在满足数据收集需求的采集器；
    所述收发单元还用于向所述SDNC发送第三消息，所述第三消息用于指示满足数据收集需求的采集器的信息。
  19. 根据权利要求18所述的装置，其特征在于，当满足数据收集需求的采集器为文件采集器或虚拟网络功能VNF事件流采集器时，所述第三消息包括所述采集器的标识信息；
    当满足数据收集需求的采集器为流采集器或SNMP trap采集器时，所述第三消息包括所述采集器的标识信息或所述采集器的地址中至少一项。
  20. 一种采集器，其特征在于，包括：
    收发单元，用于接收数据描述信息；
    处理单元，用于通过所述收发单元向数据映射处理功能模块发送所述数据描述信息和上报的数据，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
  21. 根据权利要求20所述的采集器，其特征在于，所述收发单元还用于向所述数据映射处理功能模块发送第一消息，所述第一消息包括采集器的标识信息、采集器支持的数据类型、采集器支持的编码方式和采集器的地址。
  22. 根据权利要求20或21所述的采集器，其特征在于，所述采集器为文件采集器，所述上报的数据为文件数据，所述收发单元用于接收软件定义网络控制器SDNC发送的第四消息，所述第四消息包括文件信息和所述数据描述信息，所述文件信息用于指示所述文件数据的位置；所述处理单元还用于通过所述收发单元，根据所述文件信息从对应的位置下载所述文件数据；或者，
    所述采集器为流采集器，所述上报的数据为流数据，所述收发单元用于与网元或网元管理系统建立传输控制协议TCP连接；所述处理单元还用于通过所述TCP连接接收所述流数据和所述数据描述信息；或者，
    所述采集器为SNMP trap采集器，所述上报的数据为字符数据，所述收发单元用于接收SDNC发送的第五消息，所述第五消息包括所述数据描述信息和管理信息库MIB数据；所述收发单元还用于接收网元或网元管理系统发送的告警数据；所述处理单元还用于根据所述MIB数据将所述告警数据解码为所述字符数据；或者，
    所述采集器为虚拟网络功能事件流VES采集器，所述上报的数据为VES事件，所述收发单元用于接收网元或网元管理系统发送的VES事件和所述数据描述信息，所述数据描述信息包括网络管理系统支持的数据类型。
  23. 一种数据处理装置，其特征在于，所述数据处理装置作为网元或网元管理系统，所述数据处理装置包括：
    收发单元，用于接收软件定义网络控制器SDNC发送的数据收集请求消息，所述数据收集请求消息包括上报方式、采集周期、网络管理系统支持的数据类型或网络管理系统支持的编码方式中至少一项；
    处理单元，用于根据所述数据收集上报的数据。
  24. 根据权利要求23所述的装置，其特征在于，所述处理单元还用于通过所述收发单元与流采集器建立传输控制协议TCP连接；通过所述TCP连接接向所述流采集器发送所述上报的数据和数据描述信息，所述数据描述信息包括厂商名称、网元版本信息、网络管理系统支持的数据类型或编码方式中至少一项。
  25. 根据权利要求23所述的装置，其特征在于，所述收发单元还用于：
    向所述SDNC发送管理信息库MIB数据，所述MIB数据用于解码所述上报的数据，
    或，
    向虚拟网络功能事件流VES采集器发送所述上报的数据和网络管理系统支持的数据类型。
  26. 根据权利要求23至25任一项所述的装置，其特征在于，所述收发单元还用于接收所述SDNC发送的第一能力协商消息，所述第一能力协商消息用于触发所述网元或网元管理系统反馈是否支持网络管理系统的数据类型和编码方式；
    处理单元，用于通过所述收发单元向所述SDNC发送反馈结果，所述反馈结果用于指示是否支持网络管理系统的数据类型和编码方式。
  27. 一种软件定义网络控制器，其特征在于，包括：
    收发单元，用于接收网络管理系统发送的服务请求消息，所述服务请求消息包括上报方式、网络管理系统支持的数据类型或所述网络管理系统支持的编码方式中至少一项；
    所述收发单元，还用于向网元或网元管理系统发送第一能力协商消息，所述第一能力协商消息用于触发所述网元或网元管理系统反馈是否支持所述上报方式、所述数据类型或所述编码方式中至少一项；
    处理单元，用于根据所述网元或网元管理系统的反馈，通过所述收发单元向网元或网元管理系统发送数据收集请求消息。
  28. 根据权利要求27所述的软件定义网络控制器，其特征在于，所述服务请求消息还包括对象列表，所述对象列表用于指示至少一个网元，所述网元管理系统用于管理所述至少一个网元中的一个或多个网元。
  29. 根据权利要求28所述的软件定义网络控制器，其特征在于，所述处理单元还用于解析所述对象列表，获取标识信息；
    所述处理单元还用于通过所述收发单元向所述标识信息对应的网元或网元管理系统发送第一能力协商消息。
  30. 一种计算机程序产品，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得所述计算机执行权利要求1至5中任一项所述的方法，或者，使得所述计算机执行权利要求6至8中任一项所述的方法，或者，使得所述计算机执行权利要求13或14所述的方法。
PCT/CN2020/120318 2019-10-12 2020-10-12 数据处理方法和装置 WO2021068959A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020227015965A KR20220079970A (ko) 2019-10-12 2020-10-12 데이터 처리 방법 및 장치
JP2022521699A JP7402321B2 (ja) 2019-10-12 2020-10-12 データ処理方法及び装置
EP20873754.4A EP4044508A4 (en) 2019-10-12 2020-10-12 DATA PROCESSING METHOD AND DEVICE
US17/715,762 US11894995B2 (en) 2019-10-12 2022-04-07 Data processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910969633.6 2019-10-12
CN201910969633.6A CN112653566B (zh) 2019-10-12 2019-10-12 数据处理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/715,762 Continuation US11894995B2 (en) 2019-10-12 2022-04-07 Data processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2021068959A1 true WO2021068959A1 (zh) 2021-04-15

Family

ID=75343008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/120318 WO2021068959A1 (zh) 2019-10-12 2020-10-12 数据处理方法和装置

Country Status (6)

Country Link
US (1) US11894995B2 (zh)
EP (1) EP4044508A4 (zh)
JP (1) JP7402321B2 (zh)
KR (1) KR20220079970A (zh)
CN (1) CN112653566B (zh)
WO (1) WO2021068959A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112653566B (zh) * 2019-10-12 2023-02-10 华为技术有限公司 数据处理方法和装置
US20240073156A1 (en) * 2022-08-26 2024-02-29 Ciena Corporation Detecting shortfalls in an agreement between a publisher and a subscriber

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1649343A (zh) * 2004-01-26 2005-08-03 株式会社理光 经由网络生成并提供装置管理数据
CN101989928A (zh) * 2010-11-05 2011-03-23 中兴通讯股份有限公司 网络设备信息采集方法、系统、管理系统和网络设备
CN103684822A (zh) * 2012-09-12 2014-03-26 中国移动通信集团公司 一种网络设备管理方法及设备
CN108762768A (zh) * 2018-05-17 2018-11-06 烽火通信科技股份有限公司 网络服务智能化部署方法及系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6934749B1 (en) * 2000-05-20 2005-08-23 Ciena Corporation Tracking distributed data retrieval in a network device
US7392310B2 (en) * 2002-12-26 2008-06-24 Ricoh Company, Ltd. Method and system for using data structures to store database information for multiple vendors and model support for remotely monitored devices
US7328260B1 (en) * 2002-06-04 2008-02-05 Symantec Operating Corporation Mapping discovered devices to SAN-manageable objects using configurable rules
US8019849B1 (en) * 2002-09-13 2011-09-13 Symantec Operating Corporation Server-side storage area network management interface
US7631055B1 (en) * 2003-04-23 2009-12-08 Cisco Technology, Inc. Method and apparatus providing automatic connection announcement from a modular network device to a network management point
US7296079B2 (en) * 2004-01-27 2007-11-13 Ricoh Company, Ltd. Method and system for initializing protocol information used to extract status information from networked devices
KR100748701B1 (ko) * 2006-09-05 2007-08-13 삼성전자주식회사 Ｓｎｍｐ를 사용하는 네트워크 장비 관리 시스템 및 그방법
US8874725B1 (en) * 2006-11-15 2014-10-28 Conviva Inc. Monitoring the performance of a content player
KR100959663B1 (ko) 2008-02-26 2010-05-26 성균관대학교산학협력단 고성능망 지원 웹기반의 단대단 망 성능측정 및 진단시스템 및 방법
JP2011205327A (ja) 2010-03-25 2011-10-13 Nikon Corp 画像出力装置
US9059939B2 (en) * 2012-02-23 2015-06-16 Infosys Limited End-to-end network service assurance solution
AU2014101209A4 (en) * 2014-09-18 2014-11-13 Tech Mahindra Ltd. System and method for orchestrating dynamic recovery actions for business services across traditional and sdn supporting openflow protocol
US11418496B2 (en) * 2015-06-25 2022-08-16 Panasonic Intellectual Property Management Co., Ltd. Image capture system and application control method
US10225169B2 (en) 2015-11-23 2019-03-05 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for autonomously relaying statistics to a network controller in a software-defined networking network
CN106452839A (zh) * 2016-09-05 2017-02-22 杭州华为数字技术有限公司 一种消息上报方法及装置
CN107800554B (zh) 2016-09-05 2021-04-09 华为数字技术（苏州）有限公司 数据采集方法、装置和系统
KR102275659B1 (ko) 2016-11-17 2021-07-12 한국전자통신연구원 복수의 이기종 수동형 광네트워크를 소프트웨어 정의 네트워크에 연동하는 장치 및 방법
CN109274513A (zh) * 2017-07-17 2019-01-25 中国移动通信有限公司研究院 一种数据处理方法、装置及计算机可读存储介质
CN108200190B (zh) * 2018-01-26 2019-11-22 青岛国信发展（集团）有限责任公司 基于云计算的物联网数据服务系统和方法
US11552962B2 (en) * 2018-08-31 2023-01-10 Sophos Limited Computer assisted identification of intermediate level threats
CN112653566B (zh) * 2019-10-12 2023-02-10 华为技术有限公司 数据处理方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1649343A (zh) * 2004-01-26 2005-08-03 株式会社理光 经由网络生成并提供装置管理数据
CN101989928A (zh) * 2010-11-05 2011-03-23 中兴通讯股份有限公司 网络设备信息采集方法、系统、管理系统和网络设备
CN103684822A (zh) * 2012-09-12 2014-03-26 中国移动通信集团公司 一种网络设备管理方法及设备
CN108762768A (zh) * 2018-05-17 2018-11-06 烽火通信科技股份有限公司 网络服务智能化部署方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Study on integration of Open Network Automation Platform (ONAP) and 3GPP management for 5G networks (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.890, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V2.0.0, 14 March 2019 (2019-03-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 45, XP051722782 *
See also references of EP4044508A4

Also Published As

Publication number Publication date
CN112653566A (zh) 2021-04-13
EP4044508A1 (en) 2022-08-17
EP4044508A4 (en) 2022-11-30
JP2022551182A (ja) 2022-12-07
US11894995B2 (en) 2024-02-06
CN112653566B (zh) 2023-02-10
KR20220079970A (ko) 2022-06-14
US20220231929A1 (en) 2022-07-21
JP7402321B2 (ja) 2023-12-20

Similar Documents

Publication Publication Date Title
EP3893436B1 (en) Coap-based opc ua message transmission method, and server
US10009707B2 (en) Interworking light weight machine-to-machine protocol with device management protocol
US9331953B2 (en) Device management method, middleware, and machine-to-machine communications platform, device, and system
CN111416736B (zh) 网络设备的配置管理方法、装置、计算设备及存储介质
US11894995B2 (en) Data processing method and apparatus
JPWO2004071014A1 (ja) Ｓｎｍｐプロキシエージェント、及び管理情報中継方法
CN113572651B (zh) 基于多协议设备管理架构的云平台资源管理方法和系统
CN105052076A (zh) 一种接口管理服务实体、功能服务实体及网元管理方法
US20220255818A1 (en) Device management method, apparatus, system, and device, and storage medium
EP4030725A1 (en) Data subscription method, apparatus and system
KR20160103110A (ko) 네트워크 요소 데이터 액세스 방법, 액세스 장치, 및 네트워크 관리 시스템
WO2021057878A1 (zh) 数据处理方法、装置及存储介质
WO2022095785A1 (zh) 获取采集数据格式文件的方法、装置和系统、设备、介质
US20230412466A1 (en) Managing cloud-native virtual network functions
US20220261383A1 (en) Mechanism for registration, discovery and retrieval of data in a communication network
WO2023244311A1 (en) Managing cloud-native virtual network functions
Basig et al. Reliable Event Routing in the Cloud and on the Edge
WO2024112317A1 (en) Open interface predictive and responsive adaptor system and method
CN117176679A (zh) 一种多租户消息事件处理系统、方法及相关装置
CN115866048A (zh) 数据处理方法及装置、存储介质、电子装置
WO2022119554A1 (en) Mechanism for integrating non-standard related data sources into communication network
TW202309745A (zh) 虛擬機器運行監控方法、監控系統及監控設備
CN117749852A (zh) 仪表参数的发送方法及装置、存储介质及电子装置
CN114244698A (zh) 一种基于mqtt的cpe管理配置方法
CN116828407A (zh) 一种抓包方法、系统和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20873754

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022521699

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227015965

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2020873754

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2020873754

Country of ref document: EP

Effective date: 20220512