Data processing method and apparatus, device cluster, and storage medium

Abstract

A data processing method and apparatus, a device cluster, and a storage medium, relating to the technical field of computers. The method comprises: acquiring a first template and first metadata, wherein the first metadata is used for describing an application model developed on the basis of a first platform, the first metadata comprises first declaration data of a model field in the application model, the first declaration data is used for declaring features of the model field on the first platform, and the first template indicates a mapping relationship between the position of the first declaration data and the position of second declaration data; and on the basis of the first template, determining the second declaration data corresponding to the first declaration data, wherein the second declaration data is used for declaring features of the model field on a second platform. For a plurality of application models developed on the basis of the first platform, the second declaration data corresponding to the first declaration data in the first metadata of the application model can be determined by using the first template.

Description

Data processing methods, devices, equipment clusters, and storage media

[0001] This application claims priority to Chinese Patent Application No. 202510127674.6, filed on January 27, 2025, entitled “Data Processing Method, Apparatus, Equipment Cluster and Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and in particular to data processing methods, apparatus, equipment clusters and storage media. Background Technology

[0003] With the development of computer technology, an increasing number of platforms can be used to develop application models. These platforms include no-code (NC) platforms, low-code platforms, and high-code platforms. When developing an application model using a platform, metadata describing that application model is generated. If the application model includes multiple fields, the metadata will also include declarative data to declare the characteristics of those fields. The metadata generated by different platforms differs, and the declarative data within the metadata also varies.

[0004] In scenarios involving multi-platform integration, the declared data across different platforms needs to be converted. Taking a scenario where the platforms are a low-code platform and a zero-code platform, with the conversion direction being the conversion of declared data from the zero-code platform to the low-code platform, the declared data on the zero-code platform is an automatically generated random string, while the declared data on the low-code platform is a declaration of field meaning or type. Since users will encode based on the declared data from both platforms in the integration scenario, the random string on the zero-code platform needs to be converted into a declaration of meaning or type on the low-code platform so that users can understand it and use it in subsequent coding processes. Summary of the Invention

[0005] This application provides a data processing method, apparatus, equipment cluster, and storage medium for converting declared data on different platforms. The technical solution is as follows.

[0006] In a first aspect, a data processing method is provided, executed by a processing device providing cloud services. The method includes: acquiring a first template and first metadata, wherein the first metadata describes an application model developed based on a first platform, the first metadata includes first declared data of model fields in the application model, the model fields are used to determine at least one of the types or formats of data processed by the application model, the data processing by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation, the first declared data is used to declare the characteristics of the model fields on the first platform, the first template indicates the mapping relationship between the positions of the first declared data and the positions of the second declared data, the position of the first declared data is the position of the first declared data in the first metadata, the position of the second declared data is the position of the second declared data in the second metadata, the second metadata is processed by a second platform, and the second platform and the first platform are different platforms; determining second declared data corresponding to the first declared data based on the first template, the second declared data being used to declare the characteristics of the model fields on the second platform, the characteristics of the model fields on the second platform being different from the characteristics of the model fields on the first platform.

[0007] The syntax structure of the first metadata on the first platform is fixed, and the syntax structure of the first metadata for each application model developed based on the first platform is the same. The position of the first declaration data in the first metadata of each application model is fixed. Furthermore, since the syntax structure of the second metadata on the second platform is fixed, the position of the second declaration data corresponding to the first declaration data in the second metadata is also fixed. Therefore, when the first template indicates the positional mapping relationship between the first and second declaration data, for multiple application models developed on the first platform, the first template can be used to determine the second declaration data corresponding to the first declaration data in the first metadata of the application model. This approach is applicable to multiple application models on the first platform and has broad versatility.

[0008] In one possible implementation, the syntax structures of the first metadata and the second metadata are different. Determining the second declared data corresponding to the first declared data based on the first template includes: converting the first metadata into third metadata based on the first template. The syntax structure of the third metadata is the same as that of the second metadata. The amount of declared data in the third metadata is less than that in the first metadata. The third metadata includes the first declared data. The location of the first declared data in the third metadata is found in the first template based on the location of the first declared data in the first metadata. The second declared data is determined based on the location of the first declared data in the third metadata. Since the syntax structures of the third metadata and the second metadata are identical, the location of the first declared data in the third metadata and the location of the second declared data in the second metadata are also identical. By converting the first metadata into third metadata, the location of the second declared data can be concretely represented from abstract metadata to its actual location within the metadata, even when the location of the second declared data is identified by metadata identifiers.

[0009] In one possible implementation, the third metadata is the metadata fragment containing the first declared data. Converting the first metadata into third metadata based on a first template includes: determining the first declared data within the first metadata based on the first template; determining the position of the second declared data from the first template based on the position of the first declared data in the first metadata; and generating a metadata fragment based on the position of the second declared data and the first declared data, where the position of the first declared data within the metadata fragment is the position of the second declared data. Since the position of the first declared data indicates its location within the metadata fragment, the process of determining the second declared data corresponding to the first declared data only references the metadata fragment containing the first declared data, and does not involve using metadata fragments in the first metadata where the first declared data is not located. Determining the third metadata based on the metadata fragment containing the first declared data filters out unused metadata fragments, thereby controlling the amount of third metadata without affecting the determination of the second declared data.

[0010] In one possible implementation, determining the second declaration data based on the position of the first declaration data within the third metadata includes: performing text conversion on the third metadata to obtain text data, which describes the first declaration data included in the third metadata and its position within the third metadata; inputting the text data into a mapping model, and using the mapping model to generate the second declaration data based on the position of the first declaration data within the third metadata, where the grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata. Since the grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata, the mapping model has learned the grammatical structure of the training data during training. Therefore, the mapping model can determine the declaration data that should be located at the position of the first declaration data described in the text data within the third metadata, based on the learned grammatical structure, thus obtaining the second declaration data.

[0011] In one possible implementation, the first declared data is located in the third metadata at a first position. Based on this position, the second declared data is determined, including: acquiring historical metadata processed by the second platform; and determining the second declared data corresponding to the first position from the historical metadata. The declared data located in the first position of the historical metadata is used as the second declared data. The second declared data can be determined by searching for its position in the historical metadata, and the process of determining the second declared data is simple.

[0012] This application does not limit the process of determining the second declaration data based on the location of the first declaration data in the third metadata. It can be determined using a mapping model or based on historical metadata, offering high flexibility.

[0013] In one possible implementation, determining the second declared data corresponding to the first declared data based on the first template includes: determining the first declared data from the first metadata based on the first template; based on the position of the first declared data in the first metadata, searching for the position of the second declared data that has a mapping relationship with the position of the first declared data in the first template; and determining the second declared data located at the found position from historical metadata, where the historical metadata is metadata processed by the second platform. After determining the position of the second declared data, a position search can be performed in the historical metadata to determine the second declared data located at the found position. The process of determining the second declared data is simple and has low operational complexity.

[0014] This application does not limit the method of determining the second declaration data based on the first template. The first template can be used to convert the first metadata into the third metadata, and then the second declaration data can be determined according to the position of the first declaration data in the third metadata. Alternatively, the position of the second declaration data can be determined using the first template, and then the second declaration data can be determined according to the historical metadata. This method offers high flexibility.

[0015] In one possible implementation, the syntax structures of the first metadata and the second metadata are different. After determining the second declared data corresponding to the first declared data based on the first template, the process further includes: converting the first metadata into fourth metadata based on the location of the second declared data. The fourth metadata includes the second declared data, and its syntax structure is the same as that of the second metadata. This fourth metadata is used to adjust the application model on the second platform. Since the purpose of the processing device in converting the first declared data is to assist users in adjusting the application model using the second platform, the processing device, in addition to determining the second or third declared data corresponding to the first declared data, also converts the syntax structure of the first metadata to adjust it into fourth metadata that can be processed by the second platform.

[0016] In one possible implementation, after determining the second declaration data corresponding to the first declaration data based on the first template, the method further includes: providing a mapping display page, which includes the first and second declaration data; and modifying the second declaration data to the third declaration data indicated by the modification instruction when a modification instruction is received based on the mapping display page. By providing the mapping display page, the second declaration data mapped from the first declaration data to the second declaration data on the second platform can be synchronized with the user in a timely manner. Furthermore, if the user has a need to modify the second declaration data, it can be updated promptly based on the modification instruction, resulting in a high level of interactive experience.

[0017] In one possible implementation, the first platform includes a zero-code platform, and the second platform includes at least one of a low-code platform or a high-code platform. The first declaration data includes a random string generated by the zero-code platform, and the second declaration data is used to declare the definition or type of model fields. The low-code platform and the high-code platform are platforms that support code editing. Since the definition or type of model fields can be understood based on the second declaration data, mapping meaningless random strings into understandable second declaration data facilitates subsequent coding and use by the user on the second platform.

[0018] In one possible implementation, the first platform includes at least one of a low-code platform or a high-code platform, the second platform includes a zero-code platform, the first declaration data is used to declare the definition or type of the model field, and the second declaration data includes a random string generated by the zero-code platform.

[0019] This application does not limit the conversion direction between the zero-code platform and the code-editing platform. It can be to convert the first declaration data on the zero-code platform into the second declaration data on the code-editing platform, or it can be to convert the first declaration data on the code-editing platform into the second declaration data on the zero-code platform.

[0020] In one possible implementation, the definition includes at least one of field name, field label, model label, or field type, where the type includes at least one of numeric, character, input, or single-line input. This application does not limit the definition or type of the declared data; it may include one or more of the above, offering high flexibility.

[0021] In one possible implementation, the first and second platforms are deployed in cloud devices within a cloud computing network. This application is also applicable to cloud computing scenarios and has high versatility.

[0022] Secondly, a data processing apparatus is provided, applied to a processing device providing cloud services. The apparatus includes: an acquisition module for acquiring a first template and first metadata, wherein the first metadata describes an application model developed based on a first platform, the first metadata includes first declaration data of model fields in the application model, the model fields are used to determine at least one of the types or formats of data processed by the application model, the data processing by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation, the first declaration data is used to declare the characteristics of the model fields on the first platform, the first template indicates the mapping relationship between the positions of the first declaration data and the positions of the second declaration data, the position of the first declaration data is the position of the first declaration data in the first metadata, the position of the second declaration data is the position of the second declaration data in the second metadata, the second metadata is processed by a second platform, and the second platform and the first platform are different platforms; and a determination module for determining the second declaration data corresponding to the first declaration data based on the first template, the second declaration data being used to declare the characteristics of the model fields on the second platform, the characteristics of the model fields on the second platform being different from the characteristics of the model fields on the first platform.

[0023] In one possible implementation, the syntax structure of the first metadata is different from that of the second metadata. A determining module is used to convert the first metadata into third metadata based on a first template. The syntax structure of the third metadata is the same as that of the second metadata. The amount of declared data in the third metadata is less than that of the declared data in the first metadata. The third metadata includes first declared data. The position of the first declared data in the third metadata is obtained from the first template based on the position of the first declared data in the first metadata. Based on the position of the first declared data in the third metadata, the second declared data is determined.

[0024] In one possible implementation, the third metadata is the metadata fragment containing the first declared data. The determining module is used to determine the first declared data in the first metadata based on the first template; determine the position of the second declared data from the first template based on the position of the first declared data in the first metadata; and generate a metadata fragment based on the position of the second declared data and the first declared data, wherein the position of the first declared data in the metadata fragment is the position of the second declared data.

[0025] In one possible implementation, a determination module is used to perform text conversion on the third metadata to obtain text data, which describes the first declaration data included in the third metadata and the position of the first declaration data in the third metadata; the text data is input into a mapping model, and the mapping model generates second declaration data based on the position of the first declaration data in the third metadata, wherein the grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata.

[0026] In one possible implementation, the first declaration data is located at the position of the third metadata as the first position. The determining module is used to obtain the historical metadata processed by the second platform and determine the second declaration data corresponding to the first position from the historical metadata.

[0027] In one possible implementation, a determining module is used to determine first declared data from first metadata based on a first template; based on the position of the first declared data in the first metadata, to find the position of second declared data that has a mapping relationship with the position of the first declared data in the first template; and to determine the second declared data located at the found position from historical metadata, wherein the historical metadata is metadata processed by a second platform.

[0028] In one possible implementation, the syntax structure of the first metadata is different from that of the second metadata. The apparatus further includes a conversion module for converting the first metadata into fourth metadata based on the location of the second declared data. The fourth metadata includes the second declared data. The syntax structure of the fourth metadata is the same as that of the second metadata. The fourth metadata is used to adjust the application model on the second platform.

[0029] In one possible implementation, the apparatus further includes: a modification module for providing a mapping display page, the mapping display page including first declaration data and second declaration data; and modifying the second declaration data to third declaration data indicated by the modification instruction upon receiving a modification instruction based on the mapping display page.

[0030] In one possible implementation, the first platform includes a zero-code platform, the second platform includes at least one of a low-code platform or a high-code platform, the first declaration data includes a random string generated by the zero-code platform, and the second declaration data is used to declare the definition or type of the model field.

[0031] In one possible implementation, the first platform includes at least one of a low-code platform or a high-code platform, the second platform includes a zero-code platform, the first declaration data is used to declare the definition or type of the model field, and the second declaration data includes a random string generated by the zero-code platform.

[0032] In one possible implementation, the definition includes at least one of field name, field label, model label, or field type, where the type includes at least one of numeric, character, input, or single-line input.

[0033] In one possible implementation, the first and second platforms are deployed in cloud devices within a cloud computing network.

[0034] Thirdly, a computing device cluster is provided, the computing device cluster including at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs any of the data processing methods of the first aspect described above.

[0035] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium including computer program instructions, which, when executed by a cluster of computing devices, perform any of the data processing methods described in the first aspect above.

[0036] Fifthly, a computer program (product) containing instructions is provided, which, when run by a cluster of computing devices, causes the cluster of computing devices to perform any of the data processing methods described in the first aspect.

[0037] A sixth aspect provides a communication device comprising: a transceiver, a memory, and a processor. The transceiver, the memory, and the processor communicate with each other via an internal connection path. The memory stores instructions, and the processor executes the instructions stored in the memory to control the transceiver to receive and transmit signals. When the processor executes the instructions stored in the memory, it causes the processor to perform the method of the first aspect or any possible implementation thereof.

[0038] Optionally, there may be one or more processors and one or more memories.

[0039] Alternatively, the memory can be integrated with the processor, or the memory can be set up separately from the processor.

[0040] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. This application does not limit the type of memory or the way the memory and processor are set.

[0041] In a seventh aspect, a chip is provided, including a processor for retrieving and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the methods in the foregoing aspects.

[0042] Eighthly, another chip is provided, comprising: 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 via an internal connection path, and the processor is used to execute code in the memory. When the code is executed, the processor is used to execute the methods in the above aspects.

[0043] It should be understood that the apparatus mentioned in the second or sixth aspect above can be the chip mentioned in the seventh or eighth aspect, or it can be the device cluster of the third aspect. The beneficial effects achieved by the technical solutions and corresponding possible implementations of the second to eighth aspects of this application can be found in the above description of the technical effects of the first aspect and its corresponding possible implementations, and will not be repeated here. Attached Figure Description

[0044] Figure 1 is a schematic diagram of metadata provided in an embodiment of this application;

[0045] Figure 2 is a schematic diagram of the implementation environment provided in the embodiments of this application;

[0046] Figure 3 is a flowchart of the data processing method provided in an embodiment of this application;

[0047] Figure 4 is a schematic diagram of a software development platform provided in an embodiment of this application;

[0048] Figure 5 is a schematic diagram of another type of metadata provided in an embodiment of this application;

[0049] Figure 6 is a schematic diagram of a process for configuring a first template according to an embodiment of this application;

[0050] Figure 7 is a schematic diagram of a process for processing declaration data provided in an embodiment of this application;

[0051] Figure 8 is a schematic diagram of another process for processing declaration data provided in an embodiment of this application;

[0052] Figure 9 is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0053] Figure 10 is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0054] Figure 11 is a schematic diagram of a device cluster provided in an embodiment of this application;

[0055] Figure 12 is a schematic diagram of the connection of a computing device provided in an embodiment of this application. Detailed Implementation

[0056] The terminology used in the embodiments section of this application is only for explaining specific embodiments of this application and is not intended to limit this application. To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0057] In the field of computer technology, a software development platform refers to a collection of tools and environments used in the software development process. A software development platform integrates commonly used modeling tools, development kits, and other tools involved in developing application models. Based on the tools provided by the software development platform, the speed at which business personnel develop application models can be accelerated. According to the amount of code involved in developing application models, software development platforms can be divided into zero-code platforms, low-code platforms, and high-code platforms. In a zero-code platform, business personnel can design and build application models using pre-defined modules and components without writing code. In a low-code platform, business personnel can write code to implement more complex functions when necessary, using a combination of visual development tools and code to develop complex applications. In a high-code platform, business personnel need to write a large amount of code to develop the application model.

[0058] In some cases, software development platforms generate metadata for application models during the development process. This metadata describes the application model itself and its related attributes. For example, if an application model is used to collect user information data, the metadata can describe the structure, attributes, and relationships of the user information form. In other cases, metadata includes meta-meta-meta-data and declarative data. Meta-meta-meta-data describes the attributes, rules, and structure of the metadata, while declarative data declares the characteristics of fields in the application model.

[0059] Figure 1 is a schematic diagram of metadata provided in an embodiment of this application. The left column of the metadata in Figure 1 is metadata, and the right column is declaration data. The metadata defines which features are declared in the declaration data of the metadata. The features defined by the metadata in Figure 1 include name, label, data type, identity document (id), data length, precision, and data column. In Figure 1, the declaration data declares the field name as fax, label as Fax, data type as Phone, etc. Phone is an integer (int) type.

[0060] Because different software development platforms generate different metadata, and the declared data within that metadata also differs, if business users develop application models using multiple software development platforms, they will need to convert the declared data generated by each platform. Therefore, a data processing method is urgently needed to convert the declared data from different software development platforms.

[0061] Figure 2 is a schematic diagram of an implementation environment provided by an embodiment of this application. The implementation environment includes a processing device 01, and a communication connection is established between the processing device 01 and a first platform and a second platform. The processing device 01 can obtain first metadata on the first platform based on the communication connection, and use the data processing method provided by the embodiment of this application to transform the first declaration data in the first metadata based on the first template to obtain second declaration data. The second declaration data declares the characteristics of the model field on the second platform.

[0062] For example, processing device 01 can be a server, such as a central server, an edge server, or a local server in a local data center. The server can be a physical server or a cloud server providing cloud computing services. In some embodiments, processing device 01 can also be a terminal device such as a desktop computer, laptop computer, or smartphone involved in cloud services. Furthermore, the above method can be executed by one processing device 01 as shown in FIG2, or by multiple processing devices 01; multiple processing devices 01 may be referred to as a computing device cluster in some cases. Moreover, processing device 01 can be a standalone device or a component on a device, such as a transceiver, processor, or chip. The first platform and second platform connected to processing device 01 can be a first platform and second platform configured on processing device 01, or a cloud platform; this embodiment does not limit this.

[0063] This application provides a data processing method that can be applied to the implementation environment shown in Figure 2 above. The method can be executed by a processing device, and the flowchart of the method is shown in Figure 3, including S301-S302.

[0064] S301, Obtain a first template and first metadata. The first metadata is used to describe an application model developed based on a first platform. The first metadata includes first declaration data of model fields in the application model. The model fields are used to determine at least one of the types or formats of data processed by the application model. The data processing by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation. The first declaration data is used to declare the characteristics of the model fields on the first platform. The first template indicates the mapping relationship between the position of the first declaration data and the position of the second declaration data. The position of the first declaration data is the position of the first declaration data in the first metadata. The position of the second declaration data is the position of the second declaration data in the second metadata. The second metadata is processed by a second platform. The second platform and the first platform are different platforms.

[0065] In one possible implementation, the first metadata describes the application model developed by the first platform. This application model can be any model used for data processing, such as performing at least one of the following processes: data analysis, data collection, data filtering, or data aggregation. Furthermore, the data processed by the application model can be of various types, such as text data, image data, or video data. Taking video data as an example, the application model can statistically analyze the viewing time of a particular video by people of different ages, and then analyze the audience of the video based on the statistically analyzed viewing time. In some cases, the application model may be referred to as an application program or a program model, etc.

[0066] Optionally, the application model may require adjustments. Taking the application model currently being created as an example, during the creation process, the user may adjust the application model, such as adding, deleting, or modifying its functionality. The application model can also be a previously created historical model; for example, if a historical model has issues during use and needs to be readjusted.

[0067] Regardless of the application model, the processing device can access the first platform and obtain the first metadata on the first platform based on the adjustment requirements of the application model. For example, when a user selects an application model to be adjusted on the first platform, the first platform sends an adjustment command to the processing device based on the user's operation. The processing device then locates the application model to be adjusted in the models created on the first platform based on the adjustment command and obtains the first metadata of that application model.

[0068] In some cases, users may utilize a second platform to adjust the application model. The first and second platforms can be any different software development platforms, or they can be different platforms of the same type. For example, the first and second platforms can be different zero-code platforms. Optionally, the first and second platforms can also be platforms of different types. For example, the first platform can be a zero-code platform, and the second platform can be a software development platform that supports code editing, including at least one of low-code or high-code platforms. In this case, the first declared data to be converted in the first metadata can be any data different from the declared data on the second platform.

[0069] Optionally, the first declared data can also be data used during the process of adjusting the application model using the second platform. For example, the model fields declared in the first declared data are used to determine at least one of the types or formats of data processed by the application model. Taking a user information form as an example, the data processed by the application model can be variables written in the user information form, and the model fields can be, for example, the field name, field label, or field type of the variable.

[0070] Taking a platform that is a zero-code platform and a platform that is a low-code platform as an example, where the first declared data is the declared data of field names, the process of adjusting the application model using the second platform can be achieved by writing code to adjust the application model using the low-code platform. This is because the first declared data on the zero-code platform might be a random string generated by the zero-code platform, such as nwrFYGG. Before using the data in the code on the second platform, the meaning of the model fields needs to be clarified. Therefore, the first declared data needs to be converted into second declared data that can declare meaning, such as "name," for subsequent coding.

[0071] For the first declaration data in the first metadata that needs to be converted into second declaration data, the processing device can obtain a first template to convert the first declaration data. Optionally, the processing device can construct the first template based on a first platform and a second platform. Since the metadata syntax structure of different application models developed on the first platform is consistent, and the metadata syntax structure of different application models developed on the second platform is also consistent, the processing device can determine the first template according to the location of the first declaration data and the location of the second declaration data, so as to achieve the effect that the constructed first template is applicable to the mapping of any application model on the first platform and the second platform.

[0072] Taking the zero-code platform shown in Figure 4 as an example, business users develop application models using the zero-code platform by dragging and dropping components. For instance, dragging the single-line text component from the left side of Figure 4 onto the right side of the interface adds the function of counting single-line text to the application model. Therefore, the difference between different application models developed based on the same zero-code platform lies in the different components dragged; these can be different components provided on the zero-code platform or different numbers of the same components. Furthermore, since the metadata corresponding to each component on the zero-code platform is fixed, the syntax structure of the metadata for different application models developed based on the zero-code platform is consistent. Continuing with the metadata shown in Figure 1 as an example, the metadata in Figure 1 includes two metadata fragments, each corresponding to one component. In Figure 1, the declared data in different metadata fragments are different, but the distribution of metadata is consistent, and the syntax structure of different metadata fragments is the same.

[0073] Optionally, the processing device can obtain metadata fragments corresponding to each first component on the first platform, determine the position of the first declaration data in the metadata fragment based on the metadata fragments corresponding to each first component, and obtain a second template of the first platform. The second template is used to declare the position of the first declaration data of any model field in the metadata fragment. In one possible case, the position of the first declaration data is based on the metadata indication in the metadata fragment. Figure 5 is a schematic diagram of metadata provided by an embodiment of this application. Figure 5(1) shows the metadata on the low-code platform, and Figure 5(2) shows the metadata on the zero-code platform. Referring to Figure 5(1), when the model field declared by the first declaration data is a field name, the position of the first declaration data is the name metadata under the fields metadata, which can be represented as fields[]name.

[0074] Taking the first platform as the flow low-code platform as an example, and the first component as name, the second template of the flow low-code platform can be represented as:

[0075] When the model field is a field label, the location of the first declared data corresponding to that model field in the first metadata is $.content.fields[*].field_label.

[0076] Similar to the operation of the first platform, the processing device can also obtain metadata fragments corresponding to each second component on the second platform, determine the location of the second declaration data in the metadata fragments based on the metadata fragments corresponding to each second component, and obtain the third template of the second platform. Taking the JianDao Cloud platform as an example, when the component on the second platform is 'name', the third template of the JianDao Cloud platform is as follows:

[0077] When the model field is field_label, the location of the second declaration data corresponding to this model field in the second metadata is $.content.items[*].label.

[0078] After determining the second and third templates, the processing device can directly use them as the first template to obtain a first template that includes the second and third templates. The first template indicates the indirect mapping relationship between the positions of the first and second declared data. The indirect mapping process is as follows: since the second template indicates the position of the first declared data corresponding to each model field on the first platform within the first metadata, and the third template indicates the position of the second declared data corresponding to each model field on the second platform within the second metadata, a mapping relationship exists between the positions of the two declared data if they correspond to the same model field.

[0079] Continuing with the example of the first platform being the flow low-code platform in the above embodiment, and the location of the first declared data being $.content.fields[*].field_label, the model field declared by this first declared data is field_label. In the case of the second platform being the Jiandao Cloud platform in the above embodiment, the location of the second declared data corresponding to field_label is determined from the third template to be $.content.items[*].label.

[0080] In one possible scenario, the processing device can also merge the second template and the third template to obtain a first template, which is used to determine the direct mapping relationship between the positions of the first and second declared data. Optionally, the processing device can merge the positions of declared data corresponding to the same model field into positions of declared data with a mapping relationship, based on the model fields in the second template and the model fields in the third template. Continuing with the second and third templates in the above embodiment as an example, when the model field is field_label, the processing device can merge “field_label_path:$.content.fields[*].field_label” and “field_label_path:$.content.items[*].label”, omitting the duplicate field_label_path, and the resulting direct mapping relationship is $.content.fields[*].field_label: $.content.items[*].label.

[0081] In some cases, due to the different components provided on different software development platforms, there may be situations where the first declaration data provided on the first platform does not have corresponding declaration data on the second platform. Corresponding declaration data refers to the declaration data describing the same feature of the same model field as the first declaration data. Taking the zero-code platform shown in Figure 4 as an example, the components provided by this platform include single-line text, while the low-code platform (the second platform) does not provide this component. Therefore, for the first declaration data in the metadata fragment generated by dragging and dropping single-line text, the low-code platform will not have corresponding declaration data. In this case, the processing device can perform type mapping on the first declaration data, and the second declaration data indicates the type of the first declaration data.

[0082] For example, the first template also includes a mapping relationship between the location of the first declared data and the type of the first declared data. Since the location of the first declared data in the first metadata is determined based on the component, and the reason why the first declared data does not exist on the second platform is because the component corresponding to the first declared data does not exist on the second platform, it can be understood that each piece of first declared data in the metadata fragment corresponding to the component will not have corresponding declared data on the second platform. Therefore, the location of the first declared data can be indicated by the component.

[0083] Taking the first platform as the Zero platform, the second template in the first template is, for example:

[0084] In addition to metadata mapping, the second template also includes data type mapping to determine the type of the first declared data on the second platform. When the component corresponding to the first declared data is single-line text, the type of the first declared data on the second platform is Text, and the corresponding second declared data is Text. When the component corresponding to the first declared data is an input box, the type of the first declared data on the second platform is Input, and the corresponding second declared data is Input. Based on these examples, it can be seen that the second declared data can not only be used to declare the meaning of model fields on the second platform as shown in the above embodiments, but also to declare the type of model fields on the second platform. Furthermore, the type of the first declared data in the first template can be indicated directly as shown in the above embodiments, or it can be indicated based on the position of the second declared data.

[0085] Optionally, the first template can also be set by the user based on experience. Figure 6 is a schematic diagram of the construction of a first template provided by an embodiment of this application. The user in Figure 6 can be a person who develops the first platform and the second platform, or a person who develops an application model based on the first platform and the second platform. The first platform in Figure 6 is a zero-code platform, the second platform is a low-code platform, and the configured first template is a zero-code platform template. The user can configure the mapping relationship between the zero-code platform model fields and the low-code domain specified language (DSL) to obtain the model scheme shown in Figure 6, and configure the mapping relationship between the zero-code platform supported types and the low-code platform types to obtain the type scheme shown in Figure 6. The processing device generates the first template based on the mapping relationship configured by the user. Among them, the model scheme corresponds to the metadata_mapping in the above embodiment, and the type scheme corresponds to the datatype_mapping in the above embodiment.

[0086] The embodiments of this application do not limit the timing of constructing the first template. It can be done before developing the application model using the first platform. For example, if the user is the developer of both the first and second platforms, the user will create the first template for both platforms after development. In this case, the processing device can obtain the constructed first template if there is first declaration data to be mapped. Alternatively, the first template can be constructed after developing the application model using the first platform. In this case, during the construction of the first template, it is not necessary to consider the metadata fragments corresponding to all components on the zero-code platform; instead, only the metadata fragments corresponding to the components used in the process of creating the application model need to be referenced.

[0087] Continuing with Figure 6 as an example, users will also configure the zero-code platform environment. By configuring the zero-code platform environment, application models can be created on the zero-code platform, resulting in the environment scheme shown in Figure 6. Configuring the zero-code platform environment includes: querying metadata to define a uniform resource locator (URL); performing operations on the defined URL; and configuring environment authentication access key (AK) / secret access key (SK) information.

[0088] Optionally, the metadata URL is used to retrieve a list of all metadata. Users can determine the metadata definition URL through the application programming interface (API) documentation or the platform-provided developer tools. Additionally, users will determine the operation instance data URL corresponding to each operation (create, read, update, delete) to perform the relevant operations. Since AK / SK authentication is performed before using the application model to ensure the security of the URL call, users will also configure environment authentication AK / SK information.

[0089] S302, based on the first template, determine the second declaration data corresponding to the first declaration data. The second declaration data is used to declare the characteristics of the model field on the second platform. The characteristics of the model field on the second platform are different from the characteristics of the model field on the first platform.

[0090] Since the process of transforming different first declaration data in the first metadata is similar, the following explanation will use any one first declaration data as an example. The processing device can determine the second declaration data corresponding to the first declaration data using the first template in two ways, including but not limited to the following.

[0091] Method 1: When the syntax structures of the first metadata and the second metadata are different, the first metadata is converted into the third metadata based on the first template. The syntax structure of the third metadata is the same as that of the second metadata. The amount of data in the declared data in the third metadata is less than the amount of data in the declared data in the first metadata. The third metadata includes the first declared data. The position of the first declared data in the third metadata is found from the first template based on the position of the first declared data in the first metadata. The second declared data is determined based on the position of the first declared data in the third metadata.

[0092] For example, the third metadata is the metadata fragment where the first declared data is located. The process of the processing device converting to obtain the third metadata includes: determining the first declared data in the first metadata based on the first template; determining the position of the second declared data from the first template based on the position of the first declared data in the first metadata; generating a metadata fragment based on the position of the second declared data and the first declared data, wherein the position of the first declared data in the metadata fragment is the position of the second declared data.

[0093] In one possible implementation, the first metadata includes multiple metadata fragments, but not all metadata fragments are used in the transformation of the first declared data. This can be understood as the first metadata including unnecessary metadata fragments. Unnecessary metadata fragments can be metadata fragments not located in the first declared data. For example, as shown in Figure 5(1), there are other metadata fragments under the fields in the first metadata, indicated by ellipses in the figure. Since the location of the first declared data is based on the metadata indication of the metadata fragment where the first declared data is located, metadata fragments not located in the first declared data are considered unnecessary metadata fragments. Based on this, the processing device can use the first template to clean the first metadata and remove unnecessary metadata fragments.

[0094] For example, the processing device locates the first declaration data from the first metadata based on the position of the first declaration data in the first template. Taking the position of the first declaration data as $fields[“”].name in the above embodiment as an example, the processing device locates the first declaration data as nwrFYLGC_tSinx_CST from (2) in Figure 5.

[0095] Since the syntax structure of the second metadata on the second platform is fixed, it can be understood that the declared data at the same position in different second metadata on the second platform is the same data. The processing device can determine the second declared data corresponding to the first declared data based on the position of the first declared data in the second metadata. Based on this, the processing device can perform structural transformation based on the first declared data. First, it searches for the first template based on the position of the first declared data in the first metadata, and obtains the position of the second declared data that has a mapping relationship with that position in the second metadata. The position of the second declared data indicates the metadata corresponding to the second declared data in the second metadata. The processing device can generate third metadata based on the position of the second declared data. The declared data corresponding to the metadata in the third metadata is the unconverted first declared data.

[0096] Figure 7 is a schematic diagram of a data processing process provided in an embodiment of this application. In Figure 7, the zero-code template corresponds to the first template, the zero-code platform corresponds to the first platform, the application model is a user information form, and the DSL description is metadata on a low-code platform, which serves as the second platform. In Figure 7, the business developers select the first platform as the zero-code platform and the second platform as the Flow platform. By selecting the first platform and the second platform, the zero-code template used for conversion between the first platform and the second platform can be determined.

[0097] Subsequently, the business developers selected the user information form as the data source, thus determining that the first declared data to be converted is the declared data of the user information form. Based on the business developers' operations, the processing device uses a zero-code template to convert the first metadata of the user information form. The first declared data in this first metadata is the nwrFYLGC of the declared field name. Based on the position of nwrFYLGC in the first metadata, the processing device determines the positional mapping relationship between the first declared data and the second declared data as shown in the above embodiment: $.field["].name : $.result.fields[*].name. Thus, the position of the second declared data is determined to be $.result.fields[*].name. The third metadata generated based on the position of the second declared data is shown in the generated DSL description in Figure 7. In Figure 7, since the name in the DSL description is the field to be mapped, it is identified using a source key (sK).

[0098] After acquiring the third metadata, the processing device can determine the second declared data based on the location of the first declared data in the third metadata through methods including but not limited to the following two approaches.

[0099] Method 1: Transform the third metadata into text to obtain text data. The text data is used to describe the first declaration data included in the third metadata and the position of the first declaration data in the third metadata. Input the text data into the mapping model, and use the mapping model to generate second declaration data based on the position of the first declaration data in the third metadata. The grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata.

[0100] Method one involves using a mapping model to automatically generate second declaration data based on the position of the first declaration data. In some cases, because the third metadata is in a structured language with a syntactic structure, which the mapping model cannot understand, the processing device will first textualize the third metadata into text data that the mapping model can understand before inputting the text data into the mapping model. Since the mapping model has already used the metadata from the second platform during training, it has learned the syntactic structure of the metadata on the second platform and can determine the second declaration data based on the position of the first declaration data in the third metadata.

[0101] Continuing with the example of the DSL description shown in Figure 7, the mapping model is based on the metadata fragment where the first declared data nwrFYLGC is located, which is the metadata fragment corresponding to the name component. The first declared data is located in the metadata fragment as the name metadata under the fields metadata. Since the declared data in $.result.fields[*].name of the learned second metadata are all name, the mapping model determines that the second declared data corresponding to the first declared data nwrFYLGC is name.

[0102] This application's embodiments are not limited to a mapping model; it can be a large model, such as the chat generative pre-trained transformer (ChatGPT) shown in Figure 7, or other large models. Figure 7 also shows a DSL description generated based on the output data of the mapping model. Referring to the recommended DSL description in Figure 7, this DSL description indicates that the second declared data corresponding to nwrFYLGC is name. This name declares that the model field means name on the second platform. In addition, the DSL description also includes the model name generated based on the model label of the application model, which is UserInfoModel.

[0103] Method 2: When the location of the first declared data as the third metadata is the first location, the processing device obtains the historical metadata processed by the second platform; and determines the second declared data corresponding to the first location from the historical metadata.

[0104] Optionally, the historical metadata can be metadata generated during the development of any model on the second platform, or metadata obtained by the processing device based on metadata fragments corresponding to various components on the second platform. The processing device can locate the first position in the historical metadata and determine the declared data corresponding to the first position as the second declared data. Continuing with the first position as $.result.fields[*].name, the historical metadata as (1) in Figure 5, the processing device determines the second declared data as name based on the declared data located at the first position as name.

[0105] Method 2: Determine the first declaration data from the first metadata based on the first template; based on the position of the first declaration data in the first metadata, find the position of the second declaration data that has a mapping relationship with the position of the first declaration data in the first template, and determine the second declaration data located at the found position from the historical metadata, where the historical metadata is the metadata processed by the second platform.

[0106] Optionally, the process of determining the first declared data from the first metadata based on the first template is similar to the process of determining the first declared data from the first metadata based on the first template in Method 1. The process of finding the position of the second declared data in the first template based on the position of the first declared data is similar to the process of finding the position of the second declared data in Method 1. The description of the historical metadata is similar to the description of the historical metadata in Method 2 in Method 1. The process of determining the second declared data located at the found position from the historical metadata is similar to the process of determining the second declared data located at the first position in Method 2 in Method 1. Please refer to the relevant descriptions, which will not be repeated here.

[0107] In some cases, the processing device can also determine the type of the first declared data from the first template based on the location of the first declared data in the first metadata, and thus obtain the second declared data. For example, if the component corresponding to the first declared data is single-line text, the processing device can search for single-line text in the first template, determine that the type corresponding to the single-line text is input, and thus determine that the second declared data corresponding to the first declared data is input.

[0108] In one possible implementation, after determining the second declared data corresponding to the first declared data, the processing device also provides a mapping display page, which includes the first declared data and the second declared data; if a modification instruction for the second declared data is received based on the mapping display page, the second declared data is modified to the third declared data indicated by the modification instruction.

[0109] If the processing device has a display function, such as a terminal equipped with a display screen, it can directly display the mapping display page so that the user understands what kind of second-claimed data corresponds to the first-claimed data. If the processing device does not have a display function, such as a server, it can send the mapping display page to a display device with a display function so that the mapping display page can be displayed on the display device.

[0110] Figure 7 provides a mapping display page, where the first and second declared data are presented in a table structure. Both the target key (tK) and model name in this mapping display interface are editable. Business developers can adjust the target key based on their needs. For example, considering the large number of names in the application model, the second declared data being "name" might not be distinguishable from other names. Therefore, business developers can edit the mapping display page to change the target key from "name" to "user name".

[0111] In one possible scenario, since the purpose of the processing device transforming the first declared data is to assist users in adjusting the application model using the second platform, the processing device, in addition to determining the second or third declared data corresponding to the first declared data, will also transform the syntax structure of the first metadata to adapt it into metadata that the second platform can process. Regarding the first determination method, since the processing device has already performed a structure transformation on the first metadata before determining the second declared data, the resulting third metadata can be processed by the second platform, and the processing device does not need to perform additional structure transformation.

[0112] Regarding method two, since the processing device does not adjust the structure of the first metadata, it can convert the first metadata into fourth metadata based on the location of the second declaration data after determining the second declaration data. The fourth metadata includes the second declaration data, and its syntax structure is the same as that of the second metadata. The fourth metadata is used to adjust the application model on the second platform. The process of converting to obtain the fourth metadata is similar to the process of converting to obtain the third metadata in method one, and will not be repeated here. Furthermore, the fourth metadata may or may not include the first declaration data in addition to the second declaration data.

[0113] Figure 8 is a schematic diagram of a conversion provided by an embodiment of this application. The first platform in Figure 8 is a zero-code platform, and the second platform is a low-code platform. The conversion layer is configured with a first template, which is used to define DSL mapping data according to the generated model. Referring to Figure 8, when the model field is a field name and the variable defined by the field name is Zhang San, the first declared data is nwrFYGC. Based on the first template, the first declared data on the zero-code platform can be converted into the second declared data name on the low-code platform, realizing the conversion between instance data on the zero-code side and instance data on the low-code side. Afterwards, the low-code editor provided by the low-code platform can be used to write code on the converted instance data, for example, changing Zhang San to Li Si.

[0114] Furthermore, the first and second platforms in the above embodiments are intended to illustrate the process of converting first declaration data using a first template, rather than to limit the conversion direction. Besides converting first declaration data on the first platform to second declaration data on the second platform, the same applies to converting second declaration data on the second platform back to first declaration data on the first platform. Continuing with Figure 8 as an example, the conversion layer between the zero-code platform and the low-code platform supports bidirectional conversion. This can be understood as the conversion layer in Figure 8 including an input conversion layer and an output conversion layer. Besides using the input conversion layer to convert first declaration data on the zero-code platform to second declaration data on the low-code platform, the output conversion layer can also convert second declaration data on the low-code platform back to first declaration data on the zero-code platform. For example, the first declaration data is used to declare the definition or type of model fields, and the second declaration data includes a random string generated by the zero-code platform.

[0115] In summary, the data processing method provided in this application has a fixed syntax structure for metadata created by the same software development platform, and the location of declared data in the metadata is also fixed. Therefore, when the first template indicates the positional mapping relationship between the first and second declared data, for the first metadata of any application model developed on the first platform, the second declared data corresponding to the first declared data in the first metadata can be determined using the first template. This method is applicable to any application model on the first platform and has wide versatility. Furthermore, this application does not limit the positional mapping relationship indicated in the first template; it can be a direct mapping relationship or an indirect mapping relationship, offering high flexibility. If the first template implements an indirect mapping relationship through the second template of the first platform and the third template of the second platform, even if the integrated software development platform changes, for example, from the second platform to the third platform, it is not necessary to rebuild the mapping relationship. Instead, the indirect mapping relationship can be obtained based on the second template and the fourth template of the third platform.

[0116] The data processing method of this application embodiment has been described above. Corresponding to the above method, this application embodiment also provides a data processing device. Figure 9 is a schematic diagram of the structure of a data processing device provided in this application embodiment. Based on the multiple modules shown in Figure 9, the data processing device shown in Figure 9 can perform all or part of the operations shown in Figure 3 above. It should be understood that the device may include more additional modules than the modules shown or omit some of the modules shown, and this application embodiment does not limit this. As shown in Figure 9, the device is applied to a processing device providing cloud services, and the device includes:

[0117] The acquisition module 901 is used to acquire a first template and first metadata. The first metadata is used to describe an application model developed based on a first platform. The first metadata includes first declaration data of model fields in the application model. The model fields are used to determine at least one of the types or formats of data processed by the application model. The first declaration data is used to declare the characteristics of the model fields on the first platform. The processing of data by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation. The first template indicates the mapping relationship between the position of the first declaration data and the position of the second declaration data. The position of the first declaration data is the position of the first declaration data in the first metadata. The position of the second declaration data is the position of the second declaration data in the second metadata. The second metadata is processed by a second platform. The second platform and the first platform are different platforms.

[0118] The determination module 902 is used to determine the second declaration data corresponding to the first declaration data based on the first template. The second declaration data is used to declare the characteristics of the model field on the second platform. The characteristics of the model field on the second platform are different from the characteristics of the model field on the first platform.

[0119] In one possible implementation, the syntax structure of the first metadata is different from that of the second metadata. The determining module 902 is used to convert the first metadata into third metadata based on the first template. The syntax structure of the third metadata is the same as that of the second metadata. The amount of data of the declared data in the third metadata is less than that of the declared data in the first metadata. The third metadata includes the first declared data. The position of the first declared data in the third metadata is obtained from the first template based on the position of the first declared data in the first metadata. The second declared data is determined based on the position of the first declared data in the third metadata.

[0120] In one possible implementation, the third metadata is the metadata fragment where the first declared data is located. The determining module 902 is used to determine the first declared data in the first metadata based on the first template; determine the position of the second declared data from the first template based on the position of the first declared data in the first metadata; generate a metadata fragment based on the position of the second declared data and the first declared data, wherein the position of the first declared data in the metadata fragment is the position of the second declared data.

[0121] In one possible implementation, a determining module 902 is used to perform text conversion on the third metadata to obtain text data, which describes the first declaration data included in the third metadata and the position of the first declaration data in the third metadata; the text data is input into a mapping model, and the mapping model generates second declaration data based on the position of the first declaration data in the third metadata, wherein the grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata.

[0122] In one possible implementation, the first declaration data is located at the first position in the third metadata. The determining module 902 is used to obtain the historical metadata processed by the second platform and determine the second declaration data corresponding to the first position from the historical metadata.

[0123] In one possible implementation, the determining module 902 is used to determine first declared data from first metadata based on a first template; based on the position of the first declared data in the first metadata, to find the position of second declared data that has a mapping relationship with the position of the first declared data in the first template; and to determine the second declared data located at the found position from historical metadata, wherein the historical metadata is metadata processed by the second platform.

[0124] In one possible implementation, the syntax structure of the first metadata is different from that of the second metadata. The apparatus further includes a conversion module for converting the first metadata into fourth metadata based on the location of the second declared data. The fourth metadata includes the second declared data. The syntax structure of the fourth metadata is the same as that of the second metadata. The fourth metadata is used to adjust the application model on the second platform.

[0125] In one possible implementation, the apparatus further includes: a modification module for providing a mapping display page, the mapping display page including first declaration data and second declaration data; and modifying the second declaration data to third declaration data indicated by the modification instruction upon receiving a modification instruction based on the mapping display page.

[0126] In one possible implementation, the first platform includes a zero-code platform, the second platform includes at least one of a low-code platform or a high-code platform, the first declaration data includes a random string generated by the zero-code platform, and the second declaration data is used to declare the definition or type of the model field.

[0127] In one possible implementation, the first platform includes at least one of a low-code platform or a high-code platform, the second platform includes a zero-code platform, the first declaration data is used to declare the definition or type of the model field, and the second declaration data includes a random string generated by the zero-code platform.

[0128] In one possible implementation, the definition includes at least one of field name, field label, model label, or field type, where the type includes at least one of numeric, character, input, or single-line input.

[0129] In one possible implementation, the first and second platforms are deployed in cloud devices within a cloud computing network.

[0130] Because the syntax structure of the first metadata created by the first platform is fixed, and the position of the first declaration data in the first metadata is fixed, and the syntax structure of the second metadata created by the second platform is fixed, and the position of the second declaration data in the second metadata is also fixed, when the first template indicates the positional mapping relationship between the first declaration data and the second declaration data, for the first metadata of any application model developed by the first platform, the second declaration data corresponding to the first declaration data in the first metadata can be determined using the first template. This makes it applicable to any application model on the first platform and has wide versatility.

[0131] Both the acquisition module 901 and the determination module 902 can be implemented in software or in hardware. For example, the implementation of the acquisition module 901 will be described below. Similarly, the implementation of the determination module 902 can be referenced to that of the acquisition module 901.

[0132] As an example of a software functional unit, module 901 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, module 901 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed within the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed within the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0133] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0134] As an example of a hardware functional unit, the acquisition module 901 may include at least one computing device, such as a server. Alternatively, the acquisition module 901 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0135] The multiple computing devices included in the acquisition module 901 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the acquisition module 901 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the acquisition module 901 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0136] It should be noted that, in other embodiments, the acquisition module 901 and the determination module 902 can be used to execute any step in the data processing method. The steps that the acquisition module 901 and the determination module 902 are responsible for implementing can be specified as needed. By implementing different steps in the data processing method through the acquisition module 901 and the determination module 902 respectively, all functions of the data processing device can be realized.

[0137] This application also provides a computing device 1000. As shown in FIG10, the computing device 1000 includes: a bus 1002, a processor 1004, a memory 1006, and a communication interface 1008. The processor 1004, the memory 1006, and the communication interface 1008 communicate with each other via the bus 1002. The computing device 1000 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 1000.

[0138] Bus 1002 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 10, but this does not imply that there is only one bus or one type of bus. Bus 1002 can include pathways for transmitting information between various components of computing device 1000 (e.g., memory 1006, processor 1004, communication interface 1008).

[0139] The processor 1004 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0140] The memory 1006 may include volatile memory, such as random access memory (RAM). The processor 1004 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0141] The memory 1006 stores executable program code, and the processor 1004 executes the executable program code to implement the functions of the aforementioned acquisition module or determination module, thereby realizing the data processing method. That is, the memory 1006 stores instructions for executing the data processing method.

[0142] The communication interface 1008 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 1000 and other devices or communication networks.

[0143] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0144] Figure 11 is a schematic diagram of a computing device cluster provided in an embodiment of this application. As shown in Figure 11, the computing device cluster includes at least one computing device 1000. The memory 1006 of one or more computing devices 1000 in the computing device cluster may store the same instructions for executing data processing methods.

[0145] In some possible implementations, the memory 1006 of one or more computing devices 1000 in the computing device cluster may also store partial instructions for executing data processing methods. In other words, a combination of one or more computing devices 1000 can jointly execute instructions for executing data processing methods.

[0146] It should be noted that the memory 1006 in different computing devices 1000 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the data processing device. That is, the instructions stored in the memory 1006 of different computing devices 1000 can implement the functions of one or more modules in the acquisition or determination module.

[0147] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 12 illustrates one possible implementation. As shown in Figure 12, two computing devices 1200A and 1200B are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this type of possible implementation, computing devices 1200A and 1200B include a bus 1202, a processor 1204, a memory 1206, and a communication interface 1208. The memory 1206 in computing device 1200A stores instructions for executing the functions of the acquisition module. Simultaneously, the memory 1206 in computing device 1200B stores instructions for executing the functions of the determination module.

[0148] The connection method between the computing device clusters shown in Figure 12 can be considered as follows: In the data processing method provided in this application, the determination module needs to rely on the second declaration data corresponding to the first declaration data in the first metadata based on the first template, which has high operation complexity. Therefore, it is considered to delegate the function implemented by the determination module to the computing device 1500B, so that the functions corresponding to the acquisition module and the determination module are executed through different computing devices, thereby improving the execution efficiency.

[0149] It should be understood that the functions of computing device 1200A shown in Figure 12 can also be performed by multiple computing devices 1200. Similarly, the functions of computing device 1200B can also be performed by multiple computing devices 1200.

[0150] This application also provides a communication device, which includes a transceiver, a memory, and a processor. The transceiver, the memory, and the processor communicate with each other via an internal connection path. The memory stores instructions, and the processor executes the instructions stored in the memory to control the transceiver to receive and transmit signals. When the processor executes the instructions stored in the memory, it causes the processor to perform the data processing method shown in FIG3.

[0151] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting the Advanced Reduced Instruction Set Computing (RISC) machine (ARM) architecture.

[0152] Furthermore, in an alternative embodiment, the memory described above 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.

[0153] The memory can be volatile or non-volatile, or may include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which serves as an external cache. Many forms of RAM are available by way of example, but not limitation. Examples include static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0154] This application also provides a computer program (product) containing instructions. The computer program (product) may be software or a program (product) containing instructions, capable of running on a computing device or stored on any available medium. When the computer program (product) is run on at least one computing device, it causes the at least one computing device to perform the data processing method shown in FIG3.

[0155] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to perform the data processing method shown in FIG3.

[0156] This application also provides a chip, including a processor, for calling and running instructions stored in a memory, causing a communication device equipped with the chip to perform the data processing method shown in Figure 3 above.

[0157] This application embodiment also provides another chip, including: 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. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the data processing method shown in Figure 3 above.

[0158] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk).

[0159] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the first metadata involved in this application was obtained with full authorization.

[0160] To clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0161] Computer program code used to implement the methods of the embodiments of this application may be written in one or more programming languages. This computer program code may be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable rule-finding device, such that when executed by the computer or other programmable rule-finding device, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a computer, partially on a computer, as a standalone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0162] In the context of the embodiments of this 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, etc. Examples of signals may include electrical, optical, radio, sound, or other forms of propagation signals, such as carrier waves, infrared signals, etc.

[0163] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be found in the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0164] In the embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or modules, or they may be electrical, mechanical, or other forms of connection.

[0165] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0166] Furthermore, the functional modules in the various embodiments of this application can be integrated into one module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module.

[0167] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the metadata involved in this application was obtained with full authorization.

[0168] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items that have substantially the same function and purpose. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor does it limit the quantity or execution order. It should 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 merely used to distinguish one element from another. For example, without departing from the scope of the various examples described, a first link can be referred to as a second link, and similarly, a second link can be referred to as a first link.

[0169] It should also be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0170] In this application, the term "at least one" means one or more, and the term "multiple" means two or more. For example, multiple second messages refer to two or more second messages. The terms "system" and "network" are often used interchangeably in this document.

[0171] It should be understood that the terminology used in the description of the various examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0172] It should also be understood that the term “comprising” (also referred to as “includes”, “including”, “comprises” and / or “comprising”) as used in this specification specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0173] It should also be understood that, depending on the context, the phrase “if it is determined that…” or “if [the stated condition or event] is detected” can be interpreted as “when it is determined that…” or “in response to determining that…” or “when [the stated condition or event] is detected” or “in response to detecting [the stated condition or event]”.

[0174] It should be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0175] It should also be understood that the phrases "an embodiment," "an embodiment," and "a possible implementation" used throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment or implementation is included in at least one embodiment of this application. Therefore, the phrases "in an embodiment," "an embodiment," or "a possible implementation" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0176] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of this application.

Claims

1. A data processing method, characterized in that, The method is performed by a processing device that provides cloud services, and the method includes: Obtain a first template and first metadata. The first metadata is used to describe an application model developed based on a first platform. The first metadata includes first declaration data of model fields in the application model. The model fields are used to determine at least one of the types or formats of data processed by the application model. The data processing by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation. The first declaration data is used to declare the characteristics of the model fields on the first platform. The first template indicates the mapping relationship between the position of the first declaration data and the position of the second declaration data. The position of the first declaration data is the position of the first declaration data in the first metadata. The position of the second declaration data is the position of the second declaration data in the second metadata. The second metadata is processed by a second platform. The second platform and the first platform are different platforms. Based on the first template, the second declaration data corresponding to the first declaration data is determined. The second declaration data is used to declare the characteristics of the model field on the second platform. The characteristics of the model field on the second platform are different from the characteristics of the model field on the first platform.

2. The method according to claim 1, characterized in that, The syntax structures of the first metadata and the second metadata are different. Determining the second declaration data corresponding to the first declaration data based on the first template includes: Based on the first template, the first metadata is converted into third metadata. The syntax structure of the third metadata is the same as that of the second metadata. The amount of data in the third metadata is less than the amount of data in the first metadata. The third metadata includes the first declared data. The position of the first declared data in the third metadata is obtained from the first template based on the position of the first declared data in the first metadata. The second declaration data is determined based on the location of the first declaration data in the third metadata.

3. The method according to claim 2, characterized in that, The third metadata is the metadata fragment containing the first declared data, and the conversion of the first metadata into third metadata based on the first template includes: The first declaration data is determined from the first metadata based on the first template; Based on the location of the first declaration data in the first metadata, the location of the second declaration data is determined from the first template; The metadata fragment is generated based on the location of the second declaration data and the first declaration data, wherein the location of the first declaration data in the metadata fragment is the location of the second declaration data.

4. The method according to claim 2 or 3, characterized in that, Determining the second declaration data based on the location of the first declaration data in the third metadata includes: The third metadata is converted into text to obtain text data, which is used to describe the first declaration data included in the third metadata and the position of the first declaration data in the third metadata. The text data is input into a mapping model, and the mapping model generates the second declaration data based on the position of the first declaration data in the third metadata. The grammatical structure of the training data of the mapping model is the same as the grammatical structure of the second metadata.

5. The method according to claim 2 or 3, characterized in that, The first declaration data is located at a first position in the third metadata. Determining the second declaration data based on the position of the first declaration data in the third metadata includes: Obtain historical metadata processed by the second platform; The second declaration data corresponding to the first position is determined from the historical metadata.

6. The method according to claim 1, characterized in that, The step of determining the second declaration data corresponding to the first declaration data based on the first template includes: The first declaration data is determined from the first metadata based on the first template; Based on the location of the first declaration data in the first metadata, the location of the second declaration data that has a mapping relationship with the location of the first declaration data is found in the first template, and the second declaration data located at the found location is determined from the historical metadata, wherein the historical metadata is the metadata processed by the second platform.

7. The method according to claim 6, characterized in that, The syntax structure of the first metadata is different from that of the second metadata. After determining the second declaration data corresponding to the first declaration data based on the first template, the method further includes: Based on the location of the second declaration data, the first metadata is converted into fourth metadata, which includes the second declaration data. The syntax structure of the fourth metadata is the same as that of the second metadata. The fourth metadata is used to adjust the application model on the second platform.

8. The method according to any one of claims 1-7, characterized in that, After determining the second declaration data corresponding to the first declaration data based on the first template, the method further includes: A mapping display page is provided, which includes the first declaration data and the second declaration data; Upon receiving a modification instruction for the second declaration data based on the mapping display page, the second declaration data is modified to the third declaration data indicated by the modification instruction.

9. The method according to any one of claims 1-8, characterized in that, The first platform includes a zero-code platform, and the second platform includes at least one of a low-code platform or a high-code platform. The first declaration data includes a random string generated by the zero-code platform, and the second declaration data is used to declare the definition or type of the model field.

10. The method according to any one of claims 1-8, characterized in that, The first platform includes at least one of a low-code platform or a high-code platform, the second platform includes a zero-code platform, the first declaration data is used to declare the definition or type of the model field, and the second declaration data includes a random string generated by the zero-code platform.

11. The method according to claim 9 or 10, characterized in that, The definition includes at least one of field name, field label, model label, or field type, where the type includes at least one of numeric, character, input, or single-line input.

12. The method according to any one of claims 1-11, characterized in that, The first platform and the second platform are deployed in cloud devices within a cloud computing network.

13. A data processing apparatus, characterized in that, The apparatus is used in a processing device that provides cloud services, and the apparatus includes: An acquisition module is used to acquire a first template and first metadata. The first metadata describes an application model developed based on a first platform. The first metadata includes first declaration data of model fields in the application model. The model fields are used to determine at least one of the types or formats of data processed by the application model. The data processing by the application model includes at least one of data analysis, data collection, data filtering, or data aggregation. The first declaration data is used to declare the characteristics of the model fields on the first platform. The first template indicates the mapping relationship between the positions of the first declaration data and the second declaration data. The position of the first declaration data is the position of the first declaration data in the first metadata. The position of the second declaration data is the position of the second declaration data in the second metadata. The second metadata is processed by a second platform, and the second platform and the first platform are different platforms. The determination module is used to determine the second declaration data corresponding to the first declaration data based on the first template. The second declaration data is used to declare the characteristics of the model field on the second platform, and the characteristics of the model field on the second platform are different from the characteristics of the model field on the first platform.

14. The apparatus according to claim 13, characterized in that, The syntax structure of the first metadata is different from that of the second metadata. The determining module is used to convert the first metadata into third metadata based on the first template. The syntax structure of the third metadata is the same as that of the second metadata. The amount of data of the declared data in the third metadata is less than that of the declared data in the first metadata. The third metadata includes the first declared data. The position of the first declared data in the third metadata is obtained from the first template based on the position of the first declared data in the first metadata. The second declaration data is determined based on the location of the first declaration data in the third metadata.

15. The apparatus according to claim 14, characterized in that, The third metadata is the metadata fragment in which the first declaration data is located, and the determining module is used to determine the first declaration data in the first metadata based on the first template; Based on the location of the first declaration data in the first metadata, the location of the second declaration data is determined from the first template; The metadata fragment is generated based on the location of the second declaration data and the first declaration data, wherein the location of the first declaration data in the metadata fragment is the location of the second declaration data.

16. The apparatus according to claim 14 or 15, characterized in that, The determining module is used to perform text conversion on the third metadata to obtain text data, the text data being used to describe the first declaration data included in the third metadata and the position of the first declaration data in the third metadata; the text data is input into a mapping model, and the mapping model is used to generate second declaration data based on the position of the first declaration data in the third metadata, the grammatical structure of the training data of the mapping model being the same as the grammatical structure of the second metadata.

17. The apparatus according to claim 14 or 15, characterized in that, The first declaration data is located at the first position in the third metadata. The determining module is used to obtain the historical metadata processed by the second platform and determine the second declaration data corresponding to the first position from the historical metadata.

18. The apparatus according to claim 13, characterized in that, The determining module is configured to determine the first declaration data from the first metadata based on the first template; based on the position of the first declaration data in the first metadata, find the position of the second declaration data that has a mapping relationship with the position of the first declaration data from the first template; and determine the second declaration data located at the found position from historical metadata, wherein the historical metadata is metadata processed by the second platform.

19. The apparatus according to claim 18, characterized in that, The first metadata has a different syntax structure than the second metadata. The device further includes a conversion module for converting the first metadata into fourth metadata based on the location of the second declaration data. The fourth metadata includes the second declaration data. The syntax structure of the fourth metadata is the same as that of the second metadata. The fourth metadata is used to adjust the application model on the second platform.

20. The apparatus according to any one of claims 13-19, characterized in that, The device further includes: a modification module, configured to provide a mapping display page, the mapping display page including the first declaration data and the second declaration data; and, upon receiving a modification instruction for the second declaration data based on the mapping display page, modifying the second declaration data to the third declaration data indicated by the modification instruction.

21. The apparatus according to any one of claims 13-20, characterized in that, The first platform includes a zero-code platform, the second platform includes at least one of a low-code platform or a high-code platform, the first declaration data includes a random string generated by the zero-code platform, and the second declaration data is used to declare the definition or type of the model field.

22. The apparatus according to any one of claims 13-20, characterized in that, The first platform includes at least one of a low-code platform or a high-code platform, the second platform includes a zero-code platform, the first declaration data is used to declare the definition or type of the model field, and the second declaration data includes a random string generated by the zero-code platform.

23. The apparatus according to claim 21 or 22, characterized in that, The definition includes at least one of field name, field label, model label, or field type, where the type includes at least one of numeric, character, input, or single-line input.

24. The apparatus according to any one of claims 13-23, characterized in that, The first platform and the second platform are deployed in cloud devices within a cloud computing network.

25. A computing device cluster, characterized in that, The computing device cluster includes at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform the data processing method as described in any one of claims 1-12.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer program instructions that, when executed by a cluster of computing devices, perform the data processing method according to any one of claims 1-12.

27. A chip, characterized in that, The chip includes a processor for running program instructions or code that cause a device containing the chip to perform the data processing method as described in any one of claims 1-12.

28. A computer program product, characterized in that, The computer program product includes a computer program / instruction that is executed by a processor to cause a computer to perform the data processing method as described in any one of claims 1-12.

Images