WO2022222577A1

WO2022222577A1 - Data format conversion method and apparatus, device, and computer-readable storage medium

Info

Publication number: WO2022222577A1
Application number: PCT/CN2022/075563
Authority: WO
Inventors: 张丽雅
Original assignee: 华为技术有限公司
Priority date: 2021-04-20
Filing date: 2022-02-08
Publication date: 2022-10-27
Also published as: CN115221113A

Abstract

The present application discloses a data format conversion method and apparatus, a device, and a computer-readable storage medium. The method comprises: a device obtains source data and mapping information obtained on the basis of a service requirement; and the device obtains target data on the basis of the mapping information and the source data, the mapping information comprising a mapping relationship, and the mapping relationship comprising a correspondence between first position information and second position information of at least one data object in the source data, wherein the first position information is a position of the at least one data object in a data structure of the source data, the second position information is a position of the at least one data object in a data structure of the target data, and the data object in the position corresponding to the second position information comprises the data object in the position corresponding to the first position information. The conversion efficiency of the data format according to the method is high. Because the conversion of the data format is performed according to the mapping information, the structure of the target data after conversion is controllable.

Description

Data format conversion method, apparatus, device, and computer-readable storage medium

This application claims the priority of the Chinese patent application with the application number 202110423829.2 and the invention titled "A method and device for data acquisition" filed on April 20, 2021, the entire contents of which are incorporated into this application by reference; The application also claims the priority of the Chinese patent application with application number 202110518463.7 filed on May 12, 2021 and the invention title is "Data Format Conversion Method, Apparatus, Equipment and Computer-readable Storage Medium", the entire contents of which are by reference Incorporated in this application.

technical field

The present application relates to the technical field of data processing, and in particular, to a data format conversion method, apparatus, device, and computer-readable storage medium.

Background technique

With the diversification of data formats, there are often conversion requirements between different data formats. For example, for conversion between two-dimensional data formats and object-oriented data formats.

In the related art, a hard-coded conversion method is used to develop a product release version according to the requirements put forward by the customer. Since this data format conversion method needs to be released with the product version, it not only has a long development cycle, but also a long release cycle and high customization costs.

SUMMARY OF THE INVENTION

The present application proposes a data format conversion method, device, device and computer-readable storage medium, which are used to improve the conversion efficiency of the data format, realize the controllable structure of the converted target data, and are suitable for a wide range of source data structures. .

A first aspect provides a data format conversion method, including: a device obtains source data and mapping information, where the mapping information is obtained based on business requirements; the device obtains target data based on the mapping information and the source data, The mapping information includes a mapping relationship, and the mapping relationship includes a corresponding relationship between the first position information and the second position information of at least one data object in the source data; wherein, the first position information is the at least one piece of data the position of the object in the data structure of the source data, the second position information is the position of the at least one data object in the data structure of the target data, the data in the position corresponding to the second position information The object includes a data object in a location corresponding to the first location information.

The method obtains the mapping information according to the business requirements, and converts the data structure of the source data based on the mapping information to obtain the target data, so that the conversion efficiency of the data format is higher. Secondly, since the data conversion is performed according to the mapping information, the mapping information includes the correspondence between the first position information and the second position information of at least one data object in the source data, so that the structure of the converted target data is controllable . For different source data structures, the target data converted according to the same mapping information has the same format, and this method is applicable to a wide range of source data structures.

In a possible implementation manner, the mapping information further includes an information identifier and conversion mode information; the information identifier is used to identify the mapping information; the conversion mode information is used to indicate the conversion mode, the source data The format and the format of the target data, the conversion mode is used to indicate the conversion from the format of the source data to the format of the target data. The mapping information can be quickly acquired through the information identification.

In a possible implementation manner, the format of the source data is an object-oriented data format, the format of the target data is a two-dimensional data format, and the mapping information is used to convert the source data in the object-oriented data format. into the target data in the two-dimensional data format.

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the attribute path, and the second position information includes the title column ; The device obtains target data based on the mapping information and the source data, including: the device generates target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.

In a possible implementation manner, the device generates the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data, including: the device generates the target data from the mapping relationship Obtain a first title column, and generate a first title array according to the first title column, where the first title array includes the attribute path, the array count value, and the quantity value of the attribute path under the first title array ; Determine that the attribute path is not the last attribute path under the first title array based on the array count value and the quantity value, and change the attribute path corresponding to the first title array from the Obtain a data object from the source data and output it as a row of target data in the two-dimensional data format.

In a possible implementation manner, the format of the source data is a two-dimensional data format, the format of the target data is an object-oriented data format, and the mapping information is used to convert the source data of the two-dimensional data format. into the target data in the object-oriented data format.

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the title column, and the second position information includes the attribute path ; The device obtains target data based on the mapping information and the source data, including: the device generates target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.

In a possible implementation manner, the device generates the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data, including: the device generates the target data from the mapping relationship Obtain a second title column, and generate a second title array according to the second title column, where the second title array includes a property path and an array count value; in response to the current row of the source data being less than the total number of rows, the source data The data object indicated by the current row in the data is filled into the data structure of the target data according to the position specified by the attribute path and the array count value.

In a possible implementation manner, the business requirement includes associated information for acquiring the mapping information; the obtaining the mapping information, the mapping information is obtained based on the business requirement, includes: based on the business requirement to obtain the mapping information from the associated information. The mapping information is obtained through the associated information, and the method for obtaining the mapping information in this method is more flexible.

In a possible implementation manner, the association information includes an information identifier of the mapping information.

In a possible implementation manner, the obtaining of the mapping information, where the mapping information is obtained based on business requirements, includes: obtaining user-specified mapping information or default mapping information based on the business requirements. The acquired mapping information may also be specified mapping information or default mapping information acquired based on business requirements. This method acquires the mapping information in a more flexible way.

In a possible implementation manner, the format of the source data is JSON format, the format of the target data is CSV format, or the format of the source data is CSV format, and the format of the target data is JSON format.

In a possible implementation manner, the type of the device includes at least one of a network management system, a software-defined network SDN controller network element device, a terminal, and a server.

In addition, since the title column in the mapping information is associated with the attribute path, the method realizes the conversion between the object-oriented data format and the two-dimensional data format, and the conversion between the two-dimensional data format and the object-oriented data format. The transformation process of the data structure is reversible. In the conversion process of object-oriented data format-two-dimensional data format-object-oriented data format, the object-oriented data format before and after the conversion is the same.

In a second aspect, a data format conversion device is provided, including:

an acquisition module for acquiring source data and mapping information, where the mapping information is acquired based on business requirements;

A conversion module, configured to obtain target data based on the mapping information and the source data, where the mapping information includes a mapping relationship, and the mapping relationship includes first position information and second position information of at least one data object in the source data Corresponding relationship of location information; wherein, the first location information is the location of the at least one data object in the data structure of the source data, and the second location information is the at least one data object in the target The position in the data structure of the data, the data object in the position corresponding to the second position information includes the data object in the position corresponding to the first position information.

In a possible implementation manner, the mapping information further includes an information identifier and conversion mode information; the information identifier is used to identify the mapping information; the conversion mode information is used to indicate the conversion mode, the source data The format and the format of the target data, the conversion mode is used to indicate the conversion from the format of the source data to the format of the target data.

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the attribute path, and the second position information includes the title column ; The conversion module is configured to generate target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.

In a possible implementation manner, the conversion module is configured to obtain a first title column from the mapping relationship, and generate a first title array according to the first title column, where the first title array includes the property path, array count value, and quantity value of the property path under the first title array; determining that the property path is not the last one under the first title array based on the array count value and the quantity value an attribute path, obtaining a data object from the source data according to the attribute path corresponding to the first title array according to the array count value and outputting it as a row of the target data in the two-dimensional data format.

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the title column, and the second position information includes the attribute path ; The conversion module is configured to generate target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.

In a possible implementation manner, the conversion module is configured to obtain a second title column from the mapping relationship, and generate a second title array according to the second title column, where the second title array includes an attribute path and an array count value; in response to the current row of the source data being less than the total number of rows, the data object indicated by the current row in the source data is filled into the target data according to the location specified by the attribute path and the array count value in the data structure.

In a possible implementation manner, the business requirement includes association information for obtaining the mapping information; the obtaining module is configured to obtain the mapping information based on the association information in the business requirement.

In a possible implementation manner, the obtaining module is configured to obtain user-specified mapping information or default mapping information based on the business requirement.

In a possible implementation manner, the type of the device includes at least one of a network management system, an SDN controller network element device, a terminal, and a server.

In a third aspect, a data format conversion device is provided, including a processor and a computer program. When the processor executes the computer program, the data format conversion device implements the data format conversion method according to any one of the first aspect above.

In a fourth aspect, a computer-readable storage medium is provided on which a computer program is stored, and when the computer program is executed by a computer, the data format conversion method according to any one of the first aspect above is implemented.

In a fifth aspect, a computer program product is provided, including a computer program. When the computer program is executed by a computer, the data format conversion method according to any one of the above first aspect is implemented.

In a sixth aspect, a communication apparatus is provided, the apparatus comprising: a transceiver, a memory and a processor. The transceiver, the memory and the processor communicate with each other through an internal connection path, the memory is used for storing instructions, and the processor is used for executing the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , and when the processor executes the instructions stored in the memory, the processor is caused to execute the method in the first aspect or any possible implementation manner of the first aspect.

Optionally, there are one or more processors and one or more memories.

Alternatively, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

In the specific implementation process, the memory can be a memory, for example, a read only memory (ROM), which can be integrated with the processor on the same chip, or can be respectively set on different chips. There are no restrictions on the type of memory and how the processor is set up.

In a seventh aspect, a chip is provided, including a processor for invoking and executing instructions stored in the memory from a memory, so that a communication device on which the chip is installed executes the first aspect or any of the first aspects possible. method in an embodiment.

In an eighth aspect, another chip is provided, comprising: an input interface, an output interface, a processor, and a memory, the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute codes in the memory , when the code is executed, the processor is configured to execute the method in the first aspect or any possible implementation manner of the first aspect.

Description of drawings

1 is a schematic diagram of an implementation environment of a data format conversion method provided by an embodiment of the present application;

2 is a flowchart of a method for converting a data format provided by an embodiment of the present application;

3 is a schematic diagram of service planning information provided by an embodiment of the present application;

4 is a schematic diagram of a conversion interaction process of a data format provided by an embodiment of the present application;

5 is a schematic diagram of an object-oriented data provided by an embodiment of the present application;

6 is a schematic diagram of a two-dimensional data provided by an embodiment of the present application;

7 is a schematic diagram of a mapping information provided by an embodiment of the present application;

8 is a schematic diagram of another mapping information provided by an embodiment of the present application;

9 is a schematic structural diagram of a target data provided by an embodiment of the present application;

10 is a schematic structural diagram of another target data provided by an embodiment of the present application;

11 is a schematic structural diagram of a data format conversion device provided by an embodiment of the present application;

12 is a schematic structural diagram of a data format conversion device provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of another data format conversion device provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

An embodiment of the present application provides a method for converting a data format, taking the method applied to the conversion between an object-oriented data format and a two-dimensional data format as an example, wherein the object-oriented data format includes but is not limited to javascript object notation (javascript object notation, JSON), extensible markup language (extensible markup language, xml), two-dimensional data formats including but not limited to comma separated values (comma separated values, CSV), EXCEL. Taking the data format conversion between JSON and CSV as an example, the implementation environment of this method can be shown in the JSON and CSV conversion interface architecture diagram in FIG. 1 .

In Figure 1, an operation support system (OSS) is an operator's operation and maintenance support system, including a business planning system and a resource system. The business planning system is used to plan business requirements, such as outputting data files such as business requirements in a two-dimensional data format, and the resource system is used to collect resource information on the network, such as receiving data files such as business requirements in a two-dimensional data format. The business application (application, APP) interacts with the OSS, receives the two-dimensional data format file of business requirements input by the OSS, and outputs the two-dimensional data format file to the OSS.

In the application process of the business APP, it includes the business creation process and the business export process. Among them, the business creation process is used to import files in two-dimensional data format. For example, a user inputs order requirements to the business planning system, and the business planning system inputs files in two-dimensional data format of business requirements to the business APP, so that the business APP imports the two-dimensional data. format file. Alternatively, the user directly operates the business APP, and imports a file in a two-dimensional data format into the business APP. The business creation process is also used to invoke a conversion model that converts the two-dimensional data format and the object-oriented data format, also called a converter. The converter reads the corresponding mapping information and parses the two-dimensional data format into object-oriented data. Format, for example, calling the converter of the two-dimensional data format and the object-oriented data format through the business interface to parse the two-dimensional data format file, and converting the two-dimensional data format file into JSON through the mapping information of the two-dimensional data format to the object-oriented data format format file.

The business export process is used to output data in object-oriented format, such as JSON data, call the converter, convert the data in object-oriented format into two-dimensional data format, and pass it to the resource system. The converter of the two-dimensional data format and the object-oriented data format is used to receive the object-oriented data format file, and realize the controllable mutual conversion between the object-oriented data format file and the two-dimensional data format file according to the mapping information. In FIG. 1, mapping information is used to control the content of conversion, wherein the mapping information is used to convert source data in object-oriented data format into target data in two-dimensional data format or for converting source data in two-dimensional data format target data in an object-oriented data format.

Next, the method flow shown in FIG. 2 is taken as an example to explain the conversion process of the data format provided by the embodiment of the present application. Exemplarily, the methods provided in the embodiments of the present application may be applied to the implementation environment shown in FIG. 1 , including but not limited to step 201 and step 202 . Wherein, the method is performed by a data format conversion device, hereinafter referred to as a device, and the types of the device include but are not limited to network management systems, software defined networks (software defined network, SDN) controller network element devices, terminals and servers. at least one.

In step 201, the device obtains source data and mapping information, and the mapping information is obtained based on business requirements.

The source data is the data that needs to be converted into a data format. Exemplarily, the source data and the service requirements may be input by the user, and the embodiment of the present application does not limit the acquisition method of the source data and the service requirements.

In a possible implementation manner, before executing the method provided by the embodiment of the present application, multiple mapping information may be pre-configured, and the multiple mapping information corresponds to different service requirements. Illustratively, business requirements may include business planning information. For example, the service planning information is shown in Figure 3. The service planning information includes service name, service type, source site, source network element, source port, sink site, sink network element, sink port, actual bandwidth, customer name and service remarks . The service requirements include but are not limited to: service name, service type, source network element, source port, sink network element, and service remarks. Then, according to the business requirement, mapping information corresponding to the business requirement can be configured. Exemplarily, multiple pieces of mapping information may be pre-configured by a user, and then the device can perform the method provided in this embodiment of the present application based on the multiple pieces of mapping information. For example, in the data format conversion interaction process shown in Figure 4, the user configures multiple mapping information, specifies source data and business requirements, and inputs the multiple mapping information, source data and business requirements into the data format conversion system, the The data format conversion system includes the device; the device executes the method provided by the embodiment of the present application based on the mapping information, source data and business requirements. Optionally, a conversion model is stored in the device, and the conversion model is used to obtain the target data based on the mapping information and the source data. Wherein, the input of the conversion model includes source data and mapping information, and the output of the conversion model includes target data after data format conversion.

Exemplarily, when the user inputs the plurality of mapping information, source data and business requirements into the conversion system of the data format, he can directly input them into the device, or he can input the data that can communicate with the device in the conversion system of the data format. other devices. Therefore, the device can receive mapping information, source data, and service requirements sent by other devices, and then execute the methods provided by the embodiments of the present application based on the mapping information, source data, and service requirements.

In a possible implementation manner, the business requirements include, but are not limited to, association information for acquiring mapping information. Exemplarily, the mapping information is obtained based on the associated information in the business requirement. That is to say, to obtain the mapping information, the mapping information is obtained based on the business requirement, including: obtaining the mapping information based on the associated information in the business requirement. Optionally, the associated information includes an information identifier of the mapping information. According to different types of information identifiers, the acquisition of mapping information based on the associated information in business requirements includes but is not limited to the following two ways.

Manner 1: Obtain the mapping information based on the name of the mapping information in the business requirement.

Wherein, when the type of the information identifier is a name, the first method is used to obtain the mapping information. For example, if the name of the mapping information included in the associated information is ABC, based on the ABC, the mapping information with the name ABC is acquired from a plurality of pre-configured mapping information.

Manner 2: Obtain the mapping information based on the number of the mapping information in the business requirement.

Wherein, when the type of the information identifier is a serial number, the second method is used to obtain the mapping information. In a possible implementation manner, corresponding to the multiple preconfigured mapping information, the user is preconfigured with a mapping information list, where the mapping information list includes the multiple preconfigured mapping information and a number corresponding to each mapping information. For example, if the number of the mapping information included in the associated information is 1, the first mapping information in the mapping information list is acquired based on the number.

In a possible implementation manner, the mapping information is user-specified mapping information or default mapping information obtained based on business requirements. That is to say, the mapping information is obtained, and the mapping information is obtained based on business requirements, including: obtaining user-specified mapping information or default mapping information based on business requirements. For example, for any business requirement converted from data format 1 to data format 2, obtain mapping information 1; for any business requirement converted from data format 2 to data format 1, obtain mapping information 2.

Exemplarily, as mentioned above, the mapping information includes an information identifier, and the information identifier is used to identify the mapping information. Secondly, the mapping information also includes conversion mode information, where the conversion mode information is used to indicate the conversion mode (transMode), the format of the source data (objectType), and the format of the target data (fileType), and the conversion mode is used to indicate the conversion mode of the source data. format to convert to the format of the target data.

Step 202, the device obtains target data based on the mapping information and the source data.

In a possible implementation manner, the device performs data format conversion on the source data based on the mapping information to obtain the target data. Exemplarily, the mapping information includes a mapping relationship, and the mapping relationship includes a corresponding relationship between the first location information and the second location information of at least one data object in the source data. The first location information is the location of at least one data object in the data structure of the source data, the second location information is the location of the at least one data object in the data structure of the target data, and the data in the location corresponding to the second location information The object includes a data object in a location corresponding to the first location information. Through the mapping relationship, the position mapping of the same data object in different data structures of the source data and the target data can be realized, thereby realizing the conversion of the same data object between the data format of the source data and the data format of the target data.

Exemplarily, the format of the source data is JSON format and the format of target data is CSV format, or the format of source data is CSV format and the format of target data is JSON format. It should be noted that, the data format of the source data and the data format of the target data may also be other data formats that need to be converted, which are not limited in this embodiment of the present application. Exemplarily, the representation of the first location information corresponds to the data format of the source data, and the representation of the second location information corresponds to the data format of the target data. The embodiments of the present application are described by taking the representation of the location information corresponding to the object-oriented data as an attribute path, and the representation of the location information corresponding to the two-dimensional data as a title column as an example. For example, the source data is the object-oriented data shown in FIG. 5 , and the target data is the two-dimensional data shown in FIG. 6 . For the data object "branch1", the first position information of the data object is Root[index=0]Branch, and the second position information of the data object is the root node of the title column. For another example, the source data is the two-dimensional data shown in FIG. 6 , and the target data is the object-oriented data shown in FIG. 5 . For the data object "branch1", the first position information of the data object is the root node of the title column, and the second position information of the data object is Root[index=0]Branch. For data formats other than object-oriented data or two-dimensional data, the representation form of the location information corresponding to the data format can be determined, and the format conversion is performed by using the method provided in the embodiment of the present application, which is not repeated here. .

Optionally, according to different formats of the source data, the target data is obtained based on the mapping information and the source data, including but not limited to the following two cases.

In case 1, the format of the source data is the object-oriented data format, the format of the target data is the two-dimensional data format, the conversion mode is used to indicate the conversion from the object-oriented data format to the two-dimensional data format, and the mapping information is used to convert the object-oriented data format into the two-dimensional data format. The source data is converted into target data in a two-dimensional data format.

For case 1, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes an attribute path, and the second position information includes a title column; the device obtains the target data based on the mapping information and the source data, including: the device obtains the target data based on the mapping information and the source data. The title column in the relationship, the attribute path corresponding to the title column, and the source data generate the target data.

Exemplarily, the device generates the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data, including: the device obtains the first title column from the mapping relationship, and generates the first title array according to the first title column, The first title array includes the attribute path, the array count value (index), and the number value (max) of the attribute path under the first title array; it is determined based on the array count value and the number value that the attribute path is not the last attribute under the first title array path, obtains the data object from the source data according to the attribute path corresponding to the first title array according to the array count value, and outputs it as a row of the target data in the two-dimensional data format. Exemplarily, if the number of attribute paths in the first title array is 1, the array count value (index) of the attribute path is 0, and the number value (max) of the attribute path under the first title array is 1. If the number of attribute paths in the first title array is 2, the array count value (index) of one attribute path is 0, and the array count value (index) of the other attribute path is 1. The number value (max) under a title array is 2.

For example, in the mapping information shown in FIG. 7 , the information of the mapping information is identified as mapping information 1, and the mapping information is used to convert the source data in the object-oriented data format into the target data in the two-dimensional data format. The conversion mode information included in the mapping information indicates that the conversion mode is from an object-oriented data format to a two-dimensional data format (JSON-to-CSV), the format of the source data is JSON, and the format of the target data is CSV. The title column (title) includes the root node, network branch, network sub-branch and other branch information; the attribute path (mappingScript) corresponding to the root node includes $Root[*].Branch, and the attribute path corresponding to the network branch includes $Root[*] .NstBranch[*].Branch, the attribute path corresponding to the network sub-branch includes $Root[*].NstBranch[*].Twig, and the attribute path corresponding to other branch information includes $Root[*].OthNstBranch[*].

Then, the first title column obtained from the mapping relationship by calling the transformation model includes: root node, network branch, network sub-branch and other branch information. The first title array generated according to the first title column includes: [$Root[index, max].Branch, $Root[index, max].NstBranch[index, max].Branch, $Root[index, max]. NstBranch[index, max].Twig, $Root[index, max].OthNstBranch[index, max]]. Where, $Root[index, max].Branch, $Root[index, max].NstBranch[index, max].Branch, $Root[index, max].NstBranch[index, max].Twig and $Root[index , max].OthNstBranch[index, max] is the array node in the first title array. Exemplarily, if one attribute path is included under the first title array, and the number of the attribute path in the first title array is 1, the first title array may not include the quantity value. That is, if the number of property paths in the first header array is 1, the first header array includes property paths and an array count value.

For example, the source data is the object-oriented data shown in FIG. 5 , and the value of the property path $Root[*].Branch under the first title array is 2, that is, max is equal to 2. Exemplarily, the array count value is initially 0, that is, index=0. Therefore, the array node $Root[index, max].Branch is $Root[index=0, max=2].Branch. Therefore, the first header array includes: [$Root[index=0, max=2].Branch, $Root[index=0, max=2].NstBranch[index=0, max=2].Branch, $Root [index=0, max=2].NstBranch[index=0, max=2].Twig, $Root[index=0, max=2].OthNstBranch[index=0, max=0]]. When the array count value is initially 0, in response to the array count value being less than max-1, the property path is not the last property path under the first title array. Obtain the data object from the source data according to the array count value corresponding to the attribute path of the first title array and output it as a row of target data in two-dimensional data format, that is, the first row of the output target data includes: branch1, nbranch1. 1. twig1.1. Among them, branch1 is the data object obtained by the corresponding array node $Root[index=0, max=2].Branch, that is, branch1 is the attribute path $Root[*].Branch obtained from the source data according to index=0 Data object; nbranch1.1 is the data object obtained by the corresponding array node $Root[index=0, max=2].NstBranch[index=0, max=2].Branch, twig1.1 is the corresponding array node $Root[index] =0,max=2].NstBranch[index=0,max=2].Twig fetched data object. Since the source data does not include the data objects corresponding to the array nodes $Root[index=0, max=2].OthNstBranch[index=0, max=0], the first row of the target data does not include other branch information corresponding to data object. Exemplarily, the output target data in a two-dimensional data format is shown in FIG. 6 .

In a possible implementation manner, after the attribute path corresponding to the first title array is obtained from the source data according to the array count value, the data object is outputted as a row of target data in two-dimensional data format, and the last attribute path in the array node that satisfies the If the array count value is less than max-1, add 1 to the array count value, reset the other array count value and the quantity value corresponding to the array count value. For example, after outputting the first line of target data, the first title array includes: [$Root[index=0, max=2].Branch, $Root[index=0, max=2].NstBranch[index=1, max=2].Branch, $Root[index=0, max=2].NstBranch[index=1, max=2].Twig, $Root[index=0, max=2].OthNstBranch[index=0, max=0]]. Then the second line of the output target data includes: nbranch1.2, twig1.2. Among them, nbranch1.2 is the data object obtained by the corresponding array node $Root[index=0, max=2].NstBranch[index=1, max=2].Branch, and twig1.2 is the corresponding array node $Root[index= 0, max=2].NstBranch[index=1,max=2].Data object acquired by Twig. Since the branch1 corresponding to the array node $Root[index=0, max=2].Branch has been output in the first line, the branch1 is no longer output. Since the source data does not include the data objects corresponding to the array nodes $Root[index=0, max=2].OthNstBranch[index=0, max=0], the second row of the target data does not include other branch information corresponding to data object.

For another example, after outputting the second line of target data, the first title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2].NstBranch[index=0 , max=2].Branch, $Root[index=1, max=2].NstBranch[index=0, max=2].Twig, $Root[index=1, max=2].OthNstBranch[index=0 , max=3]]. Then the third line of the output target data includes: branch2, nbranch2.1, twig2.1, 1. Among them, branch2 is the data object obtained by the corresponding array node $Root[index=1, max=2].Branch, and nbranch2.1 is the corresponding array node $Root[index=1, max=2].NstBranch[index=0, The data object obtained by max=2].Branch, twig2.1 is the data object obtained by the corresponding array node $Root[index=1, max=2].NstBranch[index=0, max=2].Twig, 1 is the corresponding The data object obtained by the array node $Root[index=1, max=2].OthNstBranch[index=0, max=3].

For another example, after outputting the third line of target data, the first title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2].NstBranch[index=1 , max=2].Branch, $Root[index=1, max=2].NstBranch[index=1, max=2].Twig, $Root[index=1, max=2].OthNstBranch[index=1 , max=3]]. Then the fourth line of the output target data includes: nbranch2.2, twig2.2, 2. Among them, nbranch2.2 is the data object obtained by the corresponding array node $Root[index=1, max=2].NstBranch[index=1, max=2].Branch, and twig2.2 is the corresponding array node $Root[index= 1, max=2].NstBranch[index=1, max=2]. The data object obtained by Twig, 2 is the corresponding array node $Root[index=1, max=2].OthNstBranch[index=1, max=3 ] to get the data object.

For another example, after outputting the fourth line of target data, the first title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2].NstBranch[index=1 , max=2].Branch, $Root[index=1, max=2].NstBranch[index=1, max=2].Twig, $Root[index=1, max=2].OthNstBranch[index=2 , max=3]]. Then the fifth row of the output target data includes: 3. Among them, 3 is the data object obtained by the corresponding array node $Root[index=1, max=2].OthNstBranch[index=2, max=3].

Exemplarily, in response to the array count value being not less than max-1, the property path is the last property path under the first title array. Exemplarily, when it is determined based on the array count value and the quantity value that the attribute path is the last attribute path under the first title array, the attribute path corresponding to the first title array is obtained from the source data according to the array count value and outputs the data object. A row of target data in two-dimensional data format. The conversion process of the data format ends, and the output of the target data in the two-dimensional data format is stopped.

In case 2, the format of the source data is a two-dimensional data format, the format of the target data is an object-oriented data format, the conversion mode is used to indicate the conversion from a two-dimensional data format to an object-oriented data format, and the mapping information is used to convert the two-dimensional data format The source data is converted into target data in an object-oriented data format.

For the second case, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first location information includes a title column, and the second location information includes an attribute path; the device obtains the target data based on the mapping information and the source data, including: the device obtains the target data based on the mapping information and the source data. The title column in the relationship, the attribute path corresponding to the title column, and the source data generate the target data.

Exemplarily, generating the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data includes: the device obtains a second title column from the mapping relationship, generates a second title array according to the second title column, The second title array includes the attribute path and the array count value; in response to the current row of the source data being less than the total number of rows, the data object indicated by the current row in the source data is filled into the data structure of the target data according to the position specified by the attribute path and the array count value . Illustratively, the initial value of the current row is 0.

For example, in the mapping information shown in FIG. 8 , the information of the mapping information is identified as mapping information 2, and the mapping information is used to convert the source data in the two-dimensional data format into the target data in the object-oriented data format. The conversion mode information included in the mapping information indicates that the conversion mode is to convert from a two-dimensional data format to an object-oriented data format (CSV-to-JSON), the format of the source data is CSV, and the format of the target data is JSON. It should be noted that, since the attribute paths corresponding to the title column are related to each other, the data structure of the target data can be determined according to the attribute paths corresponding to the title column.

In the mapping information shown in Figure 8, the title column includes root node, network branch, network sub-branch and other branch information; the attribute path corresponding to the root node includes $Root[*].Branch, and the attribute path corresponding to the network branch includes $ Root[*].NstBranch[*].Branch, the attribute path corresponding to the network sub-branch includes $Root[*].NstBranch[*].Twig, and the attribute path corresponding to other branch information includes $Root[*].OthNstBranch[* ]. Then, the second title column obtained from the mapping relationship by calling the transformation model includes: root node, network branch, network sub-branch and other branch information. The second title array generated according to the second title column includes: [$Root[index].Branch, $Root[index].NstBranch[index].Branch, $Root[index].NstBranch[index].Twig, $ Root[index].OthNstBranch[index]].

Among them, $Root[index].Branch, $Root[index].NstBranch[index].Branch, $Root[index].NstBranch[index].Twig and $Root[index].OthNstBranch[index] are the second Array nodes in the header array. Exemplarily, the data structure of the target data determined according to the attribute path corresponding to the title column is shown in FIG. 9 .

Still taking the two-dimensional data shown in FIG. 6 as an example for description, the two-dimensional data includes five rows of data objects, and the total number of rows of the two-dimensional data is five. That is, for the first row data object of the two-dimensional data, the current row is 0; the array count value is initially 0. Therefore, the second header array includes:

[$Root[index=0].Branch,

$Root[index=0].NstBranch[index=0].Branch,

$Root[index=0].NstBranch[index=0].Twig,

$Root[index=0].OthNstBranch[index=0]].

The current row is 0. In response to the current row being less than the total number of rows, the data object indicated by the current row in the source data is filled into the data structure of the target data according to the position specified by the attribute path and the array count value. That is, as shown in FIG. 9, the data objects branch1, nbranch1.1 and twig1.1 indicated by the current behavior 0 are filled into the data structure of the target data. Among them, branch1 is filled in according to the array node $Root[index=0].Branch, that is, branch1 is filled in according to the location specified by the attribute path $Root[*].Branch and the array count value index=0; nbranch1.1 is filled in according to the array The node $Root[index=0].NstBranch[index=0].Branch is filled in, and twig1.1 is filled in according to the array node $Root[index=0].NstBranch[index=0].Twig. Since the current behavior is 0, the indicated data objects do not include data objects with other branch information objects, and the data objects filled in the data structure of the target data according to the array node $Root[index=0].OthNstBranch[index=0] are: Empty (null). Exemplarily, in response to the data object filled in the data structure of the target data being empty, the part corresponding to the array node in the data structure of the target data is deleted. For example, the data structure of the target data shown in FIG. 10 does not include the part corresponding to the array node $Root[index=0].OthNstBranch[index=0].

In a possible implementation manner, after the data object indicated by the current row in the source data is filled into the data structure of the target data according to the position specified by the attribute path and the array count value, the current row is incremented by 1. In addition, the second title array also includes the number value (max) of the attribute path under the second title array. In response to the data object indicated by the current row in the source data is not empty, the last one in the array node satisfies the array count value less than The array count value of the condition of max-1 is incremented by 1, other array count values after resetting the array count value and the quantity value corresponding to the array count value; in response to the data object indicated by the current row in the source data being empty, the array The count value remains unchanged. For example, the second header array includes: [$Root[index,max].Branch,$Root[index,max].NstBranch[index,max].Branch,$Root[index,max].NstBranch[index,max] .Twig, $Root[index, max].OthNstBranch[index, max]]. In the two-dimensional data shown in FIG. 6 , the number value of the attribute path $Root[*].Branch under the second title array is 2, that is, max=2.

For example, after filling in the data object indicated by the current row 0, the current row is 1, and the second title array includes: [$Root[index=1, max=2].Branch, $Root[index=0, max=2]. NstBranch[index=1, max=2].Branch, $Root[index=0, max=2].NstBranch[index=1, max=2].Twig, $Root[index=1, max=2]. OthNstBranch[index=0, max=3]]. Therefore, the data objects nbranch1.2 and twig1.2 indicated by the current behavior 1 are filled into the data structure of the target data. Among them, nbranch1.2 is filled in according to the array node $Root[index=0, max=2].NstBranch[index=1, max=2].Branch, and twig1.2 is filled in according to the array node $Root[index=0, max= 2].NstBranch[index=1, max=2].Twig is filled in.

For another example, after filling in the data object indicated by the current row 1, the current row 2, the second title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2] .NstBranch[index=0, max=2].Branch, $Root[index=1, max=2].NstBranch[index=0, max=2].Twig, $Root[index=1, max=2] .OthNstBranch[index=0, max=3]]. Therefore, the data objects branch2, nbranch2.1, twig2.1 and 1 indicated by the current behavior 2 are filled into the data structure of the target data. Among them, branch2 is filled in according to the array node $Root[index=1, max=2].Branch, and nbranch2.1 is filled in according to the array node $Root[index=1, max=2].NstBranch[index=0, max=2] .Branch is filled in, twig2.1 is filled in according to the array node $Root[index=1, max=2].NstBranch[index=0, max=2].Twig is filled in, 1 is according to the array node $Root[index=1, max =2].OthNstBranch[index=0, max=3] is filled in.

For another example, after filling in the data object indicated by the current behavior 2, the current behavior 3, the second title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2] .NstBranch[index=1, max=2].Branch, $Root[index=1, max=2].NstBranch[index=1, max=2].Twig, $Root[index=1, max=2] .OthNstBranch[index=1, max=3]]. Therefore, the data objects nbranch2.2, twig2.2 and 2 indicated by the current behavior 3 are filled into the data structure of the target data. Among them, nbranch2.2 is filled in according to the array node $Root[index=1, max=2].NstBranch[index=1, max=2].Branch, and twig2.2 is filled in according to the array node $Root[index=1, max= 2].NstBranch[index=1, max=2].Twig is filled in, and 2 is filled in according to the array node $Root[index=1, max=2].OthNstBranch[index=1, max=3].

For another example, after filling in the data object indicated by the current behavior 3, the current behavior 4, the second title array includes: [$Root[index=1, max=2].Branch, $Root[index=1, max=2] .NstBranch[index=1, max=2].Branch, $Root[index=1, max=2].NstBranch[index=1, max=2].Twig, $Root[index=1, max=2] .OthNstBranch[index=2,max=3]]. Therefore, the data object 3 indicated by the current behavior 4 is filled into the data structure of the target data. Among them, 3 is filled in according to the array node $Root[index=1, max=2].OthNstBranch[index=2, max=3].

Exemplarily, when the current row of the source data is greater than or equal to the total number of rows, the conversion process of the data format ends, and stops filling the data object indicated by the current row in the source data with the data of the target data according to the position specified by the attribute path and the array count value. in the structure.

In the embodiment of the present application, the source data is converted into the data structure based on the mapping information obtained according to the business requirements to obtain the target data, and the conversion efficiency of the data format of this method is higher.

Secondly, since the data conversion is performed according to the mapping information, the structure of the converted target data is controllable. For different source data structures, the target data converted according to the same mapping information has the same format, and this method is applicable to a wide range of source data structures.

The embodiment of the present application also provides a data format conversion device. FIG. 11 is a schematic structural diagram of a data format conversion apparatus provided by an embodiment of the present application. Based on the following multiple modules shown in FIG. 11 , the data format conversion apparatus shown in FIG. 11 can perform all or part of the operations performed by the data format conversion device. It should be understood that the apparatus may include more additional modules than the shown modules or omit a part of the modules shown therein, which is not limited in this embodiment of the present application. As shown in FIG. 11 , the apparatus includes: an acquisition module 1101 and a conversion module 1102 .

In a possible implementation manner, the obtaining module 1101 is used to obtain source data and mapping information, and the mapping information is obtained based on business requirements; the conversion module 1102 is used to obtain target data based on the mapping information and the source data, and the mapping information includes A mapping relationship, the mapping relationship includes a correspondence between the first position information and the second position information of at least one data object in the source data; wherein, the first position information is the position of the at least one data object in the data structure of the source data, and the first position information is the position of the at least one data object in the data structure of the source data. The second position information is the position of the at least one data object in the data structure of the target data, and the data object in the position corresponding to the second position information includes the data object in the position corresponding to the first position information.

In a possible implementation manner, the mapping information further includes an information identifier and conversion mode information; the information identifier is used to identify the mapping information; the conversion mode information is used to indicate the conversion mode, the format of the source data and the format of the target data, and the conversion mode uses Used to indicate the conversion from the format of the source data to the format of the target data.

In a possible implementation manner, the format of the source data is an object-oriented data format, the format of the target data is a two-dimensional data format, and the mapping information is used to convert the source data of the object-oriented data format into the target data of the two-dimensional data format .

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes an attribute path, and the second position information includes a title column; the conversion module 1102 is configured to, based on the mapping relationship, include the attribute path and the second position information. The title column, the attribute path corresponding to the title column, and the source data generate the target data.

In a possible implementation manner, the conversion module 1102 is configured to obtain the first title column from the mapping relationship, and generate a first title array according to the first title column, where the first title array includes an attribute path, an array count value, and an attribute path The quantity value under the first title array; based on the array count value and the quantity value, it is determined that the attribute path is not the last attribute path under the first title array, and the attribute path corresponding to the first title array is obtained from the source data according to the array count value Data object and output as a row of target data in two-dimensional data format.

In a possible implementation manner, the format of the source data is a two-dimensional data format, the format of the target data is an object-oriented data format, and the mapping information is used to convert the source data of the two-dimensional data format into the target data of the object-oriented data format .

In a possible implementation manner, the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes a title column, and the second position information includes an attribute path; the conversion module 1102 is configured to, based on the mapping relationship, The title column, the attribute path corresponding to the title column, and the source data generate the target data.

In a possible implementation manner, the conversion module 1102 is configured to obtain the second title column from the mapping relationship, and generate a second title array according to the second title column, where the second title array includes an attribute path and an array count value; in response to If the current row of the source data is less than the total number of rows, the data object indicated by the current row in the source data is filled into the data structure of the target data according to the position specified by the attribute path and the array count value.

In a possible implementation manner, the business requirement includes association information for obtaining the mapping information; the obtaining module 1101 is configured to obtain the mapping information based on the association information in the business requirement.

In a possible implementation manner, the obtaining module 1101 is configured to obtain user-specified mapping information or default mapping information based on business requirements.

In a possible implementation manner, the format of the source data is JSON format, and the format of target data is CSV format, or the format of source data is CSV format, and the format of target data is JSON format.

It should be understood that when the device provided in the above-mentioned FIG. 11 realizes its functions, it is only illustrated by the division of the above-mentioned functional modules. The internal structure is divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments, which will not be repeated here.

Referring to FIG. 12, FIG. 12 shows a schematic structural diagram of a data format conversion device 2000 provided by an exemplary embodiment of the present application. The data format conversion apparatus 2000 shown in FIG. 12 is used to perform the operations involved in the above-described data format conversion method shown in FIG. 2 . The data format conversion device 2000 is, for example, a switch, a router, etc. The data format conversion device 2000 can be implemented by a general bus architecture.

As shown in FIG. 12 , the data format conversion device 2000 includes at least one processor 2001 , memory 2003 and at least one communication interface 2004 .

The processor 2001 is, for example, a general-purpose central processing unit (central processing unit, CPU), a digital signal processor (digital signal processor, DSP), a network processor (network processor, NP), a graphics processing unit (graphics processing unit, GPU), A neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor or one or more integrated circuits for implementing the solution of the present application. For example, the processor 2001 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. It may implement or execute the various logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the present invention. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

Optionally, the data format conversion device 2000 further includes a bus. The bus is used to transfer information between the various components of the data format conversion apparatus 2000 . The bus may be a peripheral component interconnect (PCI for short) bus or an extended industry standard architecture (EISA for short) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is shown in FIG. 12, but it does not mean that there is only one bus or one type of bus.

The memory 2003 is, for example, a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, or a random access memory (random access memory, RAM) or a memory device that can store information and instructions. Other types of dynamic storage devices, such as electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disks storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of Any other medium accessed by a computer without limitation. The memory 2003 exists independently, for example, and is connected to the processor 2001 through a bus. The memory 2003 may also be integrated with the processor 2001 .

The communication interface 2004 uses any device such as a transceiver for communicating with other devices or a communication network, which may be Ethernet, a radio access network (RAN), or a wireless local area network (WLAN), or the like. Communication interface 2004 may include a wired communication interface and may also include a wireless communication interface. Specifically, the communication interface 2004 may be an ethernet (ethernet) interface, a fast ethernet (FE) interface, a gigabit ethernet (GE) interface, an asynchronous transfer mode (ATM) interface, a wireless local area network ( wireless local area networks, WLAN) interfaces, cellular network communication interfaces, or a combination thereof. The Ethernet interface can be an optical interface, an electrical interface or a combination thereof. In this embodiment of the present application, the communication interface 2004 may be used for the data format conversion device 2000 to communicate with other devices.

In a specific implementation, as an embodiment, the processor 2001 may include one or more CPUs, such as CPU0 and CPU1 as shown in FIG. 12 . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In a specific implementation, as an embodiment, the data format conversion device 2000 may include multiple processors, such as the processor 2001 and the processor 2005 shown in FIG. 12 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In a specific implementation, as an embodiment, the data format conversion device 2000 may further include an output device and an input device. The output device communicates with the processor 2001 and can display information in a variety of ways. For example, the output device may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like. The input device communicates with the processor 2001 and can receive user input in various ways. For example, the input device may be a mouse, a keyboard, a touch screen device, or a sensor device, or the like.

In some embodiments, the memory 2003 is used to store the program code 2010 for executing the solutions of the present application, and the processor 2001 can execute the program code 2010 stored in the memory 2003 . That is, the data format conversion device 2000 can implement the data format conversion method provided by the method embodiment through the processor 2001 and the program code 2010 in the memory 2003 . One or more software modules may be included in the program code 2010 . Optionally, the processor 2001 itself may also store program codes or instructions for executing the solutions of the present application.

In a specific embodiment, the data format conversion device 2000 in this embodiment of the present application may correspond to the data format conversion device in the above-mentioned respective data format conversion method embodiments, and the processor 2001 in the data format conversion device 2000 reads The instructions in the memory 2003 enable the data format conversion apparatus 2000 shown in FIG. 12 to perform all or part of the operations performed by the data format conversion apparatus.

The data format conversion device 2000 may also correspond to the data format conversion device shown in FIG. 11 , and each functional module in the data format conversion device is implemented by software of the data format conversion device 2000 . In other words, the functional modules included in the data format conversion apparatus are generated after the processor 2001 of the data format conversion device 2000 reads the program code 2010 stored in the memory 2003 .

Wherein, each step of the data format conversion method shown in FIG. 2 is completed by the hardware integrated logic circuit in the processor of the data format conversion device 2000 or the instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. 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, which will not be described in detail here to avoid repetition.

Referring to FIG. 13, FIG. 13 shows a schematic structural diagram of a data format conversion device 2100 provided by another exemplary embodiment of the present application. The data format conversion device 2100 shown in FIG. 13 is configured to perform all or part of the operations involved in the above-mentioned data format conversion method shown in FIG. 2 . The data format conversion device 2100 is, for example, a switch, a router, etc. The data format conversion device 2100 can be implemented by a general bus architecture.

As shown in FIG. 13 , the data format conversion device 2100 includes: a main control board 2110 and an interface board 2130 .

The main control board is also called the main processing unit (MPU) or the route processor card (route processor card). The main control board 2110 is used for the control and management of each component in the data format conversion device 2100, including route calculation. , Equipment management, equipment maintenance, protocol processing functions. The main control board 2110 includes: a central processing unit 2111 and a memory 2112 .

The interface board 2130 is also referred to as a line processing unit (LPU), a line card (line card) or a service board. The interface board 2130 is used to provide various service interfaces and realize data packet forwarding. The service interface includes, but is not limited to, an Ethernet interface, a POS (packet over SONET/SDH) interface, etc. The Ethernet interface is, for example, a flexible Ethernet service interface (flexible ethernet clients, FlexE Clients). The interface board 2130 includes: a central processing unit 2131, a network processor 2132, a forwarding table entry memory 2134, and a physical interface card (PIC) 2133.

The central processing unit 2131 on the interface board 2130 is used to control and manage the interface board 2130 and communicate with the central processing unit 2111 on the main control board 2110 .

The network processor 2132 is used to implement packet forwarding processing. The form of the network processor 2132 may be a forwarding chip. The forwarding chip may be a network processor (NP). In some embodiments, the forwarding chip may be implemented by an application-specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Specifically, the network processor 2132 is configured to forward the received message based on the forwarding table stored in the forwarding table entry memory 2134. If the destination address of the message is the address of the data format conversion device 2100, the message is sent to the to the CPU (such as the central processing unit 2131) for processing; if the destination address of the message is not the address of the conversion device 2100 of the data format, then find the next hop and the outgoing interface corresponding to the destination address from the forwarding table according to the destination address, Forward the packet to the outbound interface corresponding to the destination address. Wherein, the processing of the uplink message may include: processing of the incoming interface of the message, and forwarding table lookup; the processing of the downlink message may include: forwarding table lookup, and so on. In some embodiments, the central processing unit can also perform the function of a forwarding chip, such as implementing software forwarding based on a general-purpose CPU, so that a forwarding chip is not required in the interface board.

The physical interface card 2133 is used to realize the interconnection function of the physical layer, the original traffic enters the interface board 2130 through this, and the processed packets are sent from the physical interface card 2133 . The physical interface card 2133 is also called a daughter card, which can be installed on the interface board 2130, and is responsible for converting the photoelectric signal into a message, and after checking the validity of the message, it is forwarded to the network processor 2132 for processing. In some embodiments, the central processing unit 2131 can also perform the functions of the network processor 2132 , such as implementing software forwarding based on a general-purpose CPU, so that the network processor 2132 is not required in the physical interface card 2133 .

Optionally, the data format conversion device 2100 includes a plurality of interface boards. For example, the data format conversion device 2100 further includes an interface board 2140. The interface board 2140 includes: a central processing unit 2141, a network processor 2142, a forwarding entry storage 2144 and Physical interface card 2143. The functions and implementation manners of the components in the interface board 2140 are the same as or similar to those of the interface board 2130, and will not be repeated here.

Optionally, the data format conversion device 2100 further includes a switch fabric board 2120 . The switch fabric unit 2120 may also be referred to as a switch fabric unit (switch fabric unit, SFU). When the data format conversion device has multiple interface boards, the switching network board 2120 is used to complete data exchange between the interface boards. For example, the interface board 2130 and the interface board 2140 can communicate through the switch fabric board 2120 .

The main control board 2110 is coupled with the interface board. E.g. The main control board 2110, the interface board 2130, the interface board 2140, and the switching network board 2120 are connected to the system backplane through a system bus to achieve intercommunication. In a possible implementation manner, an inter-process communication (IPC) channel is established between the main control board 2110 and the interface board 2130 and the interface board 2140, and the main control board 2110 and the interface board 2130 and the interface board 2140 The communication is carried out through the IPC channel.

Logically, the data format conversion device 2100 includes a control plane and a forwarding plane, the control plane includes a main control board 2110 and a central processing unit 2111, and the forwarding plane includes various components that perform forwarding, such as forwarding entry storage 2134, physical interface card 2133 and network processor 2132. The control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol packets, and configuring and maintaining the status of network devices. The control plane issues the generated forwarding tables to the forwarding plane. On the forwarding plane, the network processor 2132 controls the The following forwarding table forwards the packets received by the physical interface card 2133 by looking up the table. The forwarding table issued by the control plane may be stored in the forwarding table entry storage 2134 . In some embodiments, the control plane and forwarding plane may be completely separated and not on the same network device.

It is worth noting that there may be one or more main control boards, and when there are multiple main control boards, they may include the main main control board and the backup main control board. There may be one or more interface boards. The stronger the data processing capability of the data format conversion device, the more interface boards provided. There can also be one or more physical interface cards on the interface board. There may be no switch fabric boards, or there may be one or more boards. When there are multiple boards, load sharing and redundancy backup can be implemented together. Under the centralized forwarding architecture, the data format conversion device does not need to switch the network board, and the interface board is responsible for the processing function of the service data of the entire system. Under the distributed forwarding architecture, the data format conversion device can have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capability of the data format conversion device of the distributed architecture is greater than that of the data format conversion device of the centralized architecture. Optionally, the data format conversion device can also be in the form of only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board. At this time, the central processing unit on the interface board. and the central processing unit on the main control board can be combined into a central processing unit on this board to perform the superimposed functions of the two. The data exchange and processing capacity of the conversion device of this morphological data format is low (for example, network devices such as low-end switches or routers). The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

In a specific embodiment, the data format conversion device 2100 corresponds to the data format conversion apparatus shown in FIG. 11 above. In some embodiments, the acquisition module 1101 in the data format conversion apparatus shown in FIG. 11 is equivalent to the physical interface card 2133 in the data format conversion device 2100 ; the conversion module 1102 is equivalent to the center in the data format conversion device 2100 Processor 2111 or Network Processor 2132.

Based on the data format conversion device shown in FIG. 12 and FIG. 13 , an embodiment of the present application further provides a data format conversion system, the system includes: a control device and a display interface. Optionally, the control device is the data format conversion device 2000 shown in FIG. 12 or the data format conversion device 2100 shown in FIG. 13 , and the display interface is the data format conversion device 2000 shown in FIG. 12 or the data format shown in FIG. 13 . The data format conversion device 2100.

For the data format conversion method performed by the data format conversion device, reference may be made to the relevant description of the embodiment shown in FIG. 2 above, which will not be repeated here.

An embodiment of the present application also provides a communication apparatus, the apparatus includes: a transceiver, a memory, and a processor. The transceiver, the memory and the processor communicate with each other through an internal connection path, the memory is used for storing instructions, and the processor is used for executing the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , and when the processor executes the instructions stored in the memory, the processor is made to execute the data format conversion method required to be executed by the control device.

An embodiment of the present application also provides a communication apparatus, the apparatus includes: a transceiver, a memory, and a processor. The transceiver, the memory and the processor communicate with each other through an internal connection path, the memory is used for storing instructions, and the processor is used for executing the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , and when the processor executes the instructions stored in the memory, the processor is made to execute the data format conversion method required to be executed by the display interface.

It should be understood that the above-mentioned processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (digital signal processing, DSP), application specific integrated circuits (application specific integrated circuits, ASIC), field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or any conventional processor or the like. It should be noted that the processor may be a processor supporting an advanced RISC machine (ARM) architecture.

Further, in an optional embodiment, the above-mentioned memory may include read-only memory and random access memory, and provide instructions and data to the processor. The memory may also include non-volatile random access memory. For example, the memory may also store device type information.

The memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access Memory (double data date SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

Embodiments of the present application further provide a computer-readable storage medium, where at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to implement any one of the above-described data format conversion methods.

The embodiments of the present application also provide a computer program (product), when the computer program is executed by a computer, the processor or the computer can be made to execute each step and/or process of the corresponding data format conversion method in the above method embodiments.

An embodiment of the present application further provides a chip, including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip performs the data format conversion in the above aspects method.

An embodiment of the present application further provides another chip, including: an input interface, an output interface, a processor, and a memory, wherein the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the The processor is configured to execute the code in the memory, and when the code is executed, the processor is configured to execute the data format conversion method in the above aspects.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer program instructions, when loaded and executed on a computer, result in whole or in part of the processes or functions described herein. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks), and the like.

Those of ordinary skill in the art can realize that, in combination with the method steps and modules described in the embodiments disclosed herein, they can be implemented in software, hardware, firmware or any combination thereof, in order to clearly illustrate the interoperability of hardware and software Alternatively, the steps and components of each embodiment have been generally described in terms of their functions in the foregoing description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Persons of ordinary skill in the art may use different methods of implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

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

When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer program instructions. As an example, the methods of the embodiments of the present application may be described in the context of machine-executable instructions, such as included in program modules executed in a device on a target's real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data structures. In various embodiments, the functionality of the program modules may be combined or divided among the described program modules. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote storage media.

Computer program code for implementing the methods of the embodiments of the present application may be written in one or more programming languages. Such computer program code may be provided to a processor of a general purpose computer, special purpose computer or other programmable data processing apparatus such that the program code, when executed by the computer or other programmable data processing apparatus, causes the flowchart and/or block diagrams The functions/operations specified in are implemented. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.

In the context of embodiments of the present application, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and the like.

Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.

A machine-readable medium may be any tangible medium that contains or stores a program for or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination thereof. More detailed examples of machine-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only Memory (EPROM or flash memory), optical storage devices, magnetic storage devices, or any suitable combination thereof.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, for the specific working process of the above-described systems, devices and modules, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or Integration into another system, or some features can be ignored, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or modules, and may also be electrical, mechanical or other forms of connection.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically alone, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

In this application, the terms "first", "second" and other words are used to distinguish the same or similar items with basically the same function and function, and it should be understood that between "first", "second" and "nth" There are no logical or timing dependencies, and no restrictions on the number and execution order. It will also be understood that, although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another.

It should also be understood that, in each embodiment of the present application, the size of the sequence number of each process does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not be used in the embodiment of the present application. Implementation constitutes any limitation.

In this application, the meaning of the term "at least one" refers to one or more, and the meaning of the term "plurality" in this application refers to two or more. For example, a plurality of second messages refers to two or more more than one second message. The terms "system" and "network" are often used interchangeably herein.

It is to be understood that the terminology used in describing the various described examples herein is for the purpose of describing particular examples and is not intended to be limiting. As used in the description of the various described examples and the appended claims, the singular forms "a", "an")" and "the" are intended to include the plural forms as well, unless the context dictates otherwise. clearly instructed.

It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The term "and/or" is an association relationship that describes an associated object, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist simultaneously, and B exists alone. a situation. In addition, the character "/" in this application generally indicates that the related objects are an "or" relationship.

It will also be understood that the term "includes" (also referred to as "includes", "including", "comprises" and/or "comprising") when used in this specification designates the presence of stated features, integers, steps, operations, elements , and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groupings thereof.

It should also be understood that the terms "if" and "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, depending on the context, the phrases "if it is determined..." or "if the [stated condition or event] is detected" can be interpreted to mean "when determining..." or "in response to determining... ” or “on detection of [recited condition or event]” or “in response to detection of [recited condition or event]”.

It should be understood that determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.

It should also be understood that references throughout the specification to "one embodiment," "an embodiment," and "one possible implementation" mean that a particular feature, structure, or characteristic associated with the embodiment or implementation is included herein. in at least one embodiment of the application. Thus, appearances of "in one embodiment" or "in an embodiment" or "one possible implementation" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

The above descriptions are only optional embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. within.

Claims

A method for converting data formats, comprising:

The device obtains source data and mapping information, and the mapping information is obtained based on business requirements;

The device obtains target data based on the mapping information and the source data, where the mapping information includes a mapping relationship, and the mapping relationship includes first position information and second position information of at least one data object in the source data The corresponding relationship; wherein, the first position information is the position of the at least one data object in the data structure of the source data, and the second position information is the at least one data object in the target data. The position in the data structure, the data object in the position corresponding to the second position information includes the data object in the position corresponding to the first position information.
The method according to claim 1, wherein the mapping information further comprises information identification and conversion mode information;

The information identifier is used to identify the mapping information;

The conversion mode information is used to indicate a conversion mode, the format of the source data, and the format of the target data, and the conversion mode is used to indicate the conversion from the format of the source data to the format of the target data.
The method according to claim 1 or 2, wherein the format of the source data is an object-oriented data format, the format of the target data is a two-dimensional data format, and the mapping information is used to convert the object-oriented data The source data in the data format is converted into the target data in the two-dimensional data format.
The method according to claim 3, wherein the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the attribute path, and the second position information includes the title column;

The device obtains target data based on the mapping information and the source data, including:

The device generates target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data.
The method according to claim 4, wherein the device generates the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data, comprising:

The device obtains the first title column from the mapping relationship, and generates a first title array according to the first title column, where the first title array includes the attribute path, the array count value, and where the attribute path is located. Describe the quantity value under the first title array;

Based on the array count value and the quantity value, it is determined that the attribute path is not the last attribute path under the first title array, and the attribute path corresponding to the first title array is converted from the A data object is obtained from the source data and output as a row of the target data in the two-dimensional data format.
The method according to claim 1 or 2, wherein the format of the source data is a two-dimensional data format, the format of the target data is an object-oriented data format, and the mapping information is used to convert the two-dimensional data The source data in the data format is converted into the target data in the object-oriented data format.
The method according to claim 6, wherein the mapping relationship includes a title column and an attribute path corresponding to the title column, the first location information includes the title column, and the second location information includes the property path;

The device obtains target data based on the mapping information and the source data, including:

The device generates target data based on the title column in the mapping relationship, the attribute path corresponding to the title column, and the source data.
The method according to claim 7, wherein the device generates the target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data, comprising:

The device obtains a second title column from the mapping relationship, and generates a second title array according to the second title column, where the second title array includes an attribute path and an array count value;

In response to the current row of the source data being less than the total number of rows, the data object indicated by the current row in the source data is filled into the data structure of the target data according to the location specified by the attribute path and the array count value.
The method according to any one of claims 1-8, wherein the business requirement includes association information for acquiring the mapping information;

The obtaining of the mapping information, where the mapping information is obtained based on business requirements, includes: acquiring the mapping information based on the association information in the business requirements.
The method according to claim 9, wherein the associated information includes an information identifier of the mapping information.
The method according to any one of claims 1-8, wherein the obtaining mapping information is obtained based on business requirements, comprising: obtaining user-specified mapping information or default mapping information based on the business requirements mapping information.
The method according to any one of claims 1-11, wherein the source data is in a Javascript Object Notation JSON format, and the target data is in a comma-separated value CSV format, or

The format of the source data is CSV format, and the format of the target data is JSON format.
The method according to any one of claims 1-12, wherein the type of the device includes at least one of a network management system, a software-defined network SDN controller network element device, a terminal, and a server.
A conversion device of a data format, comprising:

an acquisition module for acquiring source data and mapping information, where the mapping information is acquired based on business requirements;

A conversion module, configured to obtain target data based on the mapping information and the source data, where the mapping information includes a mapping relationship, and the mapping relationship includes first position information and second position information of at least one data object in the source data Corresponding relationship of location information; wherein, the first location information is the location of the at least one data object in the data structure of the source data, and the second location information is the at least one data object in the target The position in the data structure of the data, the data object in the position corresponding to the second position information includes the data object in the position corresponding to the first position information.
The apparatus according to claim 14, wherein the mapping information further comprises information identification and conversion mode information;

The information identifier is used to identify the mapping information;

The conversion mode information is used to indicate a conversion mode, the format of the source data, and the format of the target data, and the conversion mode is used to indicate the conversion from the format of the source data to the format of the target data.
The apparatus according to claim 14 or 15, wherein the source data is in an object-oriented data format, the target data is in a two-dimensional data format, and the mapping information is used to convert the object-oriented data The source data in the data format is converted into the target data in the two-dimensional data format.
The apparatus according to claim 16, wherein the mapping relationship includes a title column and an attribute path corresponding to the title column, the first position information includes the attribute path, and the second position information includes the title column;

The conversion module is configured to generate target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.
The apparatus according to claim 17, wherein the conversion module is configured to obtain a first title column from the mapping relationship, and generate a first title array according to the first title column, and the first title The array includes the attribute path, an array count value, and a quantity value of the attribute path under the first title array; determining that the attribute path is not the first title array based on the array count value and the quantity value In the last attribute path below, the attribute path corresponding to the first title array is to obtain a data object from the source data according to the array count value and output it as a row of the target data in the two-dimensional data format.
The device according to claim 14 or 15, wherein the format of the source data is a two-dimensional data format, the format of the target data is an object-oriented data format, and the mapping information is used to convert the two-dimensional data format. The source data in the data format is converted into the target data in the object-oriented data format.
The apparatus according to claim 19, wherein the mapping relationship includes a title column and an attribute path corresponding to the title column, the first location information includes the title column, and the second location information includes the property path;

The conversion module is configured to generate target data based on the title column in the mapping relationship, the attribute path corresponding to the title column and the source data.
The device according to claim 20, wherein the conversion module is configured to obtain a second title column from the mapping relationship, and generate a second title array according to the second title column, the second title The array includes a property path and an array count value; in response to the current row of the source data being less than the total number of rows, the data object indicated by the current row in the source data is filled in according to the location specified by the property path and the array count value in the data structure of the target data.
The apparatus according to any one of claims 14-21, wherein the service requirement includes association information for acquiring the mapping information;

The obtaining module is configured to obtain the mapping information based on the association information in the business requirement.
The apparatus according to claim 22, wherein the association information includes an information identifier of the mapping information.
The apparatus according to any one of claims 14-21, wherein the acquiring module is configured to acquire mapping information specified by a user or default mapping information based on the business requirement.
The device according to any one of claims 14-24, wherein the format of the source data is Javascript Object Notation JSON format, and the format of the target data is a comma-separated value CSV format, or the format of the source data is The format is CSV format, and the format of the target data is JSON format.
The apparatus according to any one of claims 14-25, wherein the type of the device includes at least one of a network management system, a software-defined network SDN controller network element device, a terminal, and a server.
A data format conversion device, characterized in that it includes a processor and a computer program, and when the processor executes the computer program, the data format conversion device realizes any one of claims 1-13. The conversion method of the data format.
A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a computer, the data format conversion method according to any one of claims 1-13 is implemented.
A computer program product is characterized in that it includes a computer program, and when the computer program is executed by a computer, the data format conversion method according to any one of claims 1-13 is implemented.