Data Processing Method And Apparatus
US-2022231929-A1 · Jul 21, 2022 · US
US11894995B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11894995-B2 |
| Application number | US-202217715762-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 7, 2022 |
| Priority date | Oct 12, 2019 |
| Publication date | Feb 6, 2024 |
| Grant date | Feb 6, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Example data processing methods and apparatus are described. One example data processing method includes receiving data description information and reported data, where the data description information includes at least one of a vendor name, network element version information, a data type supported by a network management system, or a coding mode supported by the network management system. The reported data is converted based on the data description information, where reported data obtained through conversion meets a virtual network function event streaming (VES) specification. A VES event is sent, where the VES event includes the reported data obtained through conversion.
Opening claim text (preview).
What is claimed is: 1. A data processing method, comprising: receiving a first message sent by a collector, wherein the first message comprises identification information of the collector, a data type supported by the collector, a coding mode supported by the collector, and an address of the collector; creating a context of the collector based on the first message, wherein the context comprises the identification information of the collector, the data type supported by the collector, the coding mode supported by the collector, and the address of the collector; receiving a second message, wherein the second message is used to indicate a data collection requirement; determining, based on a locally stored context of each collector and the second message, a collector that supports a data type and coding mode in the second message, wherein a context of the collector comprises attribute capability information of the collector; receiving data description information and reported data from the determined collector that supports the data type and coding mode in the second message, wherein the data description information comprises at least one of a vendor name, network element version information, a data type supported by a network management system, or a coding mode supported by the network management system; converting the reported data based on the data description information, wherein reported data obtained through conversion meets a virtual network function event streaming (VES) specification; and sending a VES event, wherein the VES event comprises the reported data obtained through conversion. 2. The data processing method according to claim 1 , wherein the converting the reported data based on the data description information comprises: determining a data conversion template based on the data description information; and converting the reported data based on the data conversion template. 3. The data processing method according to claim 1 , wherein the data processing method further comprises: sending a third message to a software defined network controller (SDNC), wherein the third message is used to indicate information about the collector that meets the data collection requirement. 4. The data processing method according to claim 3 , wherein: when the collector that meets the data collection requirement is a file collector or a virtual network function (VNF) event stream collector, the third message comprises the identification information of the collector; or when the collector that meets the data collection requirement is a stream collector or a simple network management protocol (SNMP) trap collector, the third message comprises at least one of the identification information of the collector or the address of the collector. 5. A data processing method, comprising: sending, by a collector, a first message to a data mapping processing function module, wherein the first message comprises identification information of the collector, a data type supported by the collector, a coding mode supported by the collector, and an address of the collector; receiving, by the collector, data description information; and sending, by the collector, the data description information and reported data to the data mapping processing function module, wherein the data description information comprises at least one of a vendor name, network element version information, a data type supported by a network management system, or a coding mode supported by the network management system; wherein the collector is determined, based on a locally stored context of each collector and a second message, to support a data type and a coding mode in the second message received by the data mapping processing function module, wherein the second message indicates a data collection requirement, and wherein a third message is sent by the data mapping processing function module to a software defined network controller (SDNC) to indicate information about the collector that meets a data collection requirement. 6. The data processing method according to claim 5 , wherein: the collector is a file collector, the reported data is file data, and the receiving, by a collector, data description information comprises: receiving, by the file collector, a fourth message sent by a software defined network controller (SDNC), wherein the fourth message comprises file information and the data description information, and the file information is used to indicate a location of the file data; and downloading, by the file collector, the file data from the location of the file data based on the file information; or the collector is a stream collector, the reported data is stream data, and the receiving, by a collector, data description information comprises: creating, by the stream collector, a transmission control protocol (TCP) connection to a network element or an element management system; and receiving, by the stream collector, the stream data and the data description information through the TCP connection; or the collector is a simple network management protocol (SNMP) trap collector, the reported data is character data, and the receiving, by a collector, data description information comprises: receiving, by the SNMP trap collector, a fifth message sent by an SDNC, wherein the fifth message comprises the data description information and management information base (MIB) data; receiving, by the SNMP trap collector, fault data sent by a network element or an element management system; and decoding, by the SNMP trap collector, the fault data into the character data based on the MIB data; or the collector is a virtual network function event streaming (VES) collector, the reported data is a VES event, and the receiving, by a collector, data description information comprises: receiving, by the VES collector, the VES event and the data description information that are sent by a network element or an element management system, wherein the data description information comprises the data type supported by the network management system. 7. An apparatus, comprising: at least one processor coupled to one or more memories; and the one or more memories coupled to the at least one processor and storing program instructions for execution by the at least one processor to: receive a first message sent by a collector, wherein the first message comprises identification information of the collector, a data type supported by the collector, a coding mode supported by the collector, and an address of the collector; create a context of the collector based on the first message, wherein the context comprises the identification information of the collector, the data type supported by the collector, the coding mode supported by the collector, and the address of the collector; receive a second message, wherein the second message is used to indicate a data collection requirement; determine, based on a locally stored context of each collector and the second message, a collector that supports a data type and coding mode in the second message, wherein a context of the collector comprises attribute capability information of the collector; receive data description information and reported data from the determined collector that supports the data type and coding mode in the second message, wherein the data description information comprises at least one of a vendor name, network element version information, a data type supported by a network management system, or a coding mode supported by the network management system; convert the reported data based on the data description information, wherein reported data obtained through conversion meets a virtual network function event streaming (VES) specification; and send a VES event,
Processing captured monitoring data, e.g. for logfile generation · CPC title
Data format conversion from or to a database · CPC title
using logs of notifications; Post-processing of notifications · CPC title
Management of faults, events, alarms or notifications · CPC title
Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.