CN112818176A

CN112818176A - Data processing method, device, equipment and storage medium

Info

Publication number: CN112818176A
Application number: CN202110196579.3A
Authority: CN
Inventors: 胡钦骋; 唐济民
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-02-08
Filing date: 2021-02-08
Publication date: 2021-05-18
Anticipated expiration: 2041-02-08
Also published as: CN112818176B

Abstract

The application relates to a data processing method, a device, equipment and a storage medium, wherein the method comprises the following steps: acquiring a protocol file, wherein the protocol file is a definition file of protocol data; compiling the protocol file to obtain a first file and a second file corresponding to the protocol file, wherein the first file is a source code file, and the second file is a binary file; performing data structure conversion on the protocol data according to a first file and a second file corresponding to the protocol file to generate a first type of file; and displaying a first operation interface of the protocol data at the client based on the first type of file. The method and the device can avoid the complex operation that editor codes need to be modified to adapt to different data structures, reduce development and maintenance cost and improve data configuration efficiency.

Description

Data processing method, device, equipment and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data processing method, apparatus, device, and storage medium.

Background

Protocol buffers (Google open source) is a data exchange format similar to Json, XML, and the like, and is a binary data transmission format with excellent efficiency and compatibility, and can be applied to various fields such as network transmission, communication protocols, data storage, and the like.

In the related art, a format of Protobuf data is often generated by editing a text file such as Json or XML, and then converting the edited text file using a conversion tool, or by separately developing a binary editor. The mode of conversion by using the conversion tool does not need additional development support due to universal format, but because the service logic is not very intuitive, error configuration files which meet the basic standard but do not meet the logic are easily configured, errors are difficult to eliminate, the maintenance cost is high, and the data configuration efficiency is influenced. And the binary editor is developed independently, the structured display of the data is popular and easy to understand, and the data can be displayed by being attached to logic, but the development cost is high, when the data structure changes, the code of the editor also needs to be modified adaptively, otherwise, error reporting or unavailability can be caused, the operation is complex, and further, the data configuration efficiency is influenced.

Disclosure of Invention

The application provides a data processing method, a data processing device, data processing equipment and a data processing storage medium, which can avoid the complex operation that editor codes need to be modified to adapt to different data structures, reduce development and maintenance cost and improve data configuration efficiency.

In one aspect, the present application provides a data processing method, including:

acquiring a protocol file, wherein the protocol file is a definition file of protocol data;

compiling the protocol file to obtain a first file and a second file corresponding to the protocol file, wherein the first file is a source code file, and the second file is a binary file;

performing data structure conversion on the protocol data according to a first file and a second file corresponding to the protocol file to generate a first type of file;

and displaying a first operation interface of the protocol data at the client based on the first type of file.

Another aspect provides a data processing apparatus, the apparatus comprising:

the file acquisition module is used for acquiring a protocol file, wherein the protocol file is a definition file of protocol data;

the compiling module is used for compiling the protocol file to obtain a first file and a second file corresponding to the protocol file, wherein the first file is a source code file, and the second file is a binary file;

the class generation module is used for carrying out data structure conversion on the protocol data according to a first file and a second file corresponding to the protocol file to generate a first class file;

and the interface generation module is used for displaying a first operation interface of the protocol data on the client side based on the first type of file.

Another aspect provides an electronic device, which includes a processor and a memory, where at least one instruction or at least one program is stored in the memory, and the at least one instruction or at least one program is loaded by the processor and executes the data processing method described above.

Another aspect provides a computer-readable storage medium having at least one instruction or at least one program stored therein, the at least one instruction or the at least one program being loaded and executed by a processor to implement the data processing method as described above.

According to the method and the device, the protocol file is automatically read, an operation interface for displaying the protocol data is provided, whether the stored protocol data is correct or not is conveniently checked, the protocol data is conveniently edited, and a quick repairing means is provided for the protocol data at an emergency; the structured display of the protocol data is obtained based on the definition file, when the data structure changes, the automatic identification can be carried out according to the definition file without changing the code of an editor, the operation is convenient, the development and maintenance cost is reduced, and the data configuration efficiency is further improved.

Drawings

In order to more clearly illustrate the technical solutions and advantages of the embodiments of the present application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is an exemplary diagram of a configuration using the Json format according to an embodiment of the present disclosure.

Fig. 2 is a schematic architecture diagram of a data processing system according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application.

Fig. 4 is a schematic flowchart of generating a first type of file according to an embodiment of the present application.

Fig. 5 is an exemplary diagram for generating a first type of file according to an embodiment of the present application.

Fig. 6 is a schematic flowchart of generating a first operation interface according to an embodiment of the present application.

Fig. 7 is an exemplary diagram of interface control generation provided in an embodiment of the present application.

Fig. 8 is an exemplary diagram of a first operation interface provided in an embodiment of the present application.

Fig. 9 is a schematic flowchart of another process for generating a first operation interface according to an embodiment of the present application.

Fig. 10 is a schematic flowchart of another data processing method according to an embodiment of the present application.

Fig. 11a is a diagram of an example structure of a nest provided by an embodiment of the present application.

Fig. 11b is an exemplary diagram of a quadratic expansion recursion provided in an embodiment of the present application.

Fig. 12 is an example of a second operation interface provided in the embodiment of the present application.

Fig. 13 is another example of the second operation interface provided in the embodiment of the present application.

Fig. 14 is a schematic flowchart of another data processing method according to an embodiment of the present application.

Fig. 15 is an exemplary diagram of a verification control provided in an embodiment of the present application.

Fig. 16 is an exemplary diagram of a verification display panel provided in an embodiment of the present application.

Fig. 17 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.

Fig. 18 is a schematic structural diagram of a class generation module according to an embodiment of the present application.

Fig. 19 is a schematic structural diagram of a variable declaration unit provided in an embodiment of the present application.

Fig. 20 is a schematic structural diagram of an interface generating module according to an embodiment of the present application.

Fig. 21 is a schematic structural diagram of another interface generation module provided in the embodiment of the present application.

Fig. 22 is a schematic structural diagram of another data processing apparatus according to an embodiment of the present application.

Fig. 23 is a schematic structural diagram of another data processing apparatus according to an embodiment of the present application.

Fig. 24 is a view of an embodiment of the present application. The hardware structure of the device for implementing the method provided by the embodiment of the application is schematic.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings. It is to be understood that the described embodiments are merely a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, the following explanations are made with respect to the terms involved in the embodiments of the present specification:

unity3D (also known as Unity engine): the game development tool is an engine developed by Unity Technologies and applied to three-dimensional scenes, is a comprehensive game development tool which can enable players to easily create multi-platform interactive contents such as three-dimensional video games, building visualizations, real-time three-dimensional animations and the like, and is a professional game engine which is comprehensively integrated.

Protocol buffer: the method is a data exchange format similar to Json, XML and the like of Google open source, and the internal data of the method is in a pure binary format.

Protobuf is a binary data transmission format with excellent efficiency and compatibility, and can be applied to various fields such as network transmission, communication protocols, data storage and the like. In order to construct Protobuf data, the related art mainly adopts two ways: the method comprises the steps that firstly, text files such as Json or XML are edited, and then the text files obtained through editing are converted through a conversion tool; mode two, a binary editor is developed separately.

For the first mode, text editing is intuitive to the structure of source data, errors of the data are easy to check, and low-level errors such as format errors can be directly checked by code checking; and because the format is universal, the existing editing tool is mature, additional development support is not needed, the conversion tool can be developed for the second time by virtue of some open-source libraries, and the development is relatively easy and efficient. However, the threshold for non-programmers is high, and some content even needs to plan art; logic is not very intuitive, for example, in the field of games, the checkpoint logic and the skill execution sequence both need logic imagination, and sufficient time cost and labor cost are needed for understanding the specific logic through text editing; because the format is universal, some basic error configuration files which meet the standard but do not meet the logic can be easily prepared; debugging and troubleshooting errors are inconvenient, and the efficiency is low for the development process. As shown in fig. 1, which is an exemplary diagram configured using the Json format.

For the second mode, programmers are required to assist in developing independent binary editors, and due to the fact that the independently developed binary editors enable data structure editing to be completely customized, extra checking tools can be developed for checking, and correctness of data is guaranteed at the first time of editing; the structured display of the data is popular and easy to understand, and can be displayed by attaching logic; generally, the options and the control content are filled, the editing threshold is low, and the code file does not need to be edited. However, the development cost is very high, the humanization is higher, and when the data structure is modified, the editor code needs to be modified in time, otherwise, error reporting or unavailability can be caused.

Based on the above description, embodiments of the present application provide a data processing method to reduce development and maintenance costs and improve data configuration efficiency. Referring to fig. 2, a schematic structural diagram of a data processing system according to an embodiment of the present application is shown, where the system can implement the data processing method according to the embodiment of the present application. As shown in fig. 2, the system may include a client 10 and a server 20.

The client 10 may be a smartphone, desktop computer, tablet computer, notebook computer, digital assistant, smart wearable device, monitoring device, voice interaction device, or the like. The client 10 may store a protocol file 11 and a running tool script 12. Specifically, the client 10 provides an operation interface of protocol data (Protobuf data) by running the tool script 12, and sends a corresponding data instruction to the server 20 based on an operation of the user in the operation interface.

The server 20 may be an independently operating server, or a distributed server, or a server cluster composed of a plurality of servers, or may be a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform. The server 20 can read the protocol file (Proto file) 11, provide editing modes of the protocol data and each data field in the protocol data in the operation interface, and perform corresponding data processing based on the data instruction of the client 10. The server 20 and the client 10 may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

Referring to fig. 3, a flow chart of a data processing method according to an embodiment of the present application is shown, where the method can be applied to the system shown in fig. 2. It is noted that the present specification provides the method steps as described in the examples or flowcharts, but may include more or less steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. In practice, the system or server product may be implemented in a sequential or parallel manner (e.g., parallel processor or multi-threaded environment) according to the embodiments or methods shown in the figures. Specifically, as shown in fig. 3, the method may include:

s301, acquiring a protocol file, wherein the protocol file is a definition file of protocol data.

The protocol file refers to a Proto file, that is, a file with Proto as a suffix, and the protocol data refers to Protobuf data. After the user writes the protocol file, the protocol file can be stored to a preset path, the protocol file under the preset path is automatically acquired by running a tool script in the client, and then an operation interface of protocol data is provided for the user based on the protocol file. It can be understood that the preset path is generally a path specified in the tool script, and once the preset path is changed, the path specified in the tool script is also modified adaptively, and the setting of the preset path is not specifically limited in the present application.

S303, compiling the protocol file to obtain a first file and a second file corresponding to the protocol file, wherein the first file is a source code file, and the second file is a binary file.

After the server obtains the protocol file, the first file and the second file can be obtained by executing a compiling statement or running a compiling tool to compile the protocol file, for example, executing a protoc. The source code file may be a Java source code file, a C # source code file, or a C + + source code file, that is, the first file may be a cs file (a file suffixed in cs), a Java file (a file suffixed in Java), or a cpp file (a file suffixed in cpp), and the second file refers to a binary file generated by compilation, that is, a pb file (a file suffixed in pb).

S305, carrying out data structure conversion on the protocol data according to the first file and the second file corresponding to the protocol file to generate a first type file.

The first file and the second file record the native data structure of the Protobuf data, and in order to convert the native data structure and the required data structure, the native data structure can be repackaged, and the first type of file, namely the Wrapper type file, is established for realization.

In one possible embodiment, referring to fig. 4, step S305 may include:

s3051, obtaining a namespace and a data structure corresponding to the protocol data according to the second file corresponding to the protocol file.

In order to avoid naming conflict and quickly search for protocol data, different naming spaces are generated for different protocol data in the embodiment of the application, and the naming spaces can be obtained by analyzing the second file. In a specific implementation, the name of the namespace may correspond to the name of the item where the protocol file is located, for example, the name of the item where the protocol file is located is FaGame, and the name of the namespace may be formed by adding a preset suffix to the FaGame, for example, FaGame.

The data structure indicates the business logic of the protocol data, and the data structure includes the data type and the defined modifier of each data field. The data type is used to indicate the type of storing the data field and may include a base type and a structure type. The base type means that the data field is a base data type or array type, such as int, string, pool, byte, etc. The structure type means that the data field is a message structure or a reference structure, and in practical applications, a message defined in another proto file can be usually referred to in one proto file, which results in that the data type of the formed data field is the structure type.

The limited modifier refers to a mark for limiting a data field, and the proto file provides three limited modifiers, namely required modifier, optional modifier and required modifier. The data field defined by required is a necessary field, the data field defined by optional is an optional field, the data field defined by required is a field which can contain a plurality of elements, namely, the class member variable corresponding to the data field defined by required needs to store a plurality of values, and the data field defined by required or optional only needs to store one value. It will be appreciated that not every data field may have a qualifier, i.e. the qualifier may be null.

S3053, establishing the first type of file in the name space.

It can be understood that the language type used by the first file is the same as the language type used by the first file, that is, if the first file is a cs file, the first file is also a cs file, and so on.

S3055, traversing each data field in the data structure, determining a target type based on the data type of the data field and the defined modifier, and declaring member variables corresponding to the data field in the first-class file by using the target type.

Because the data types of each data field are different, the data types can be mapped into the types of member variables which can be expressed by the language used by the first type of file, and then the types are further updated according to whether the data fields are limited by predicted, so that the target types are obtained.

In view of this, the step of determining the target type based on the data type of the data field and the qualified modifier may, when implemented, include: if the data type is the basic type, determining the data type as a reference type; if the data type is the structure type, determining a second type file corresponding to the structure type, and determining a type in the second type file as a reference type; and updating the reference type based on whether the limited modifier is a multi-choice modifier to obtain the target type.

That is, if the qualifier is not a multiple choice modifier, when the data type is a basic type, the basic type is taken as the type of the member variable corresponding to the data field; when the data type is the structure type, each structure type corresponds to a second type file, namely a Wrapper type file, and the Wrapper type in the second type file is used as the type of the member variable corresponding to the data field. During specific implementation, a mapping rule is arranged between the name of the structure type and the class name of the Wrapper class in the corresponding Wrapper class file, and the server can obtain the Wrapper class according to the mapping rule. For example, the name of the structure type plus the fixed suffix Wrapper is the corresponding class.

For example, data field CastNums whose data type is int type, the type of the member variable corresponding to the data field generated in the first type file is also int type. For the structure type, for example, the structure type is a faskiltrigger, the class in the second class file corresponding to the structure type is a faskiltrigger wrapper, and the type of the member variable corresponding to the data field generated in the first class file is a faskiltrigger wrapper.

After the reference type is determined, the reference type is adjusted based on the qualified modifier. Specifically, if the qualifier is a multiple choice modifier, the reference type is updated to a list. For example, if the limited modifier of CastNums in the above is a multiple choice modifier, the member variable generated last may be declared as List < int > or ArrayList < int >, etc.

S3057, creating an objective function in the first class of files based on the first file corresponding to the protocol file and each member variable, wherein the objective function is used for converting the data structure of the protocol data.

In the embodiment of the present application, in addition to the functions essential for constituting the class file, for example, the constructor is implemented by adding an objective function to the first class file in order to implement the conversion between the data structure displayed on the interface and the data structure defined in the source code file. The objective function may include at least a first function and a second function, where the first function is used to implement reading of the protocol data, and the second function is used to implement saving of the protocol data. As shown in fig. 5, which is one example of generating files of a first type.

S307, displaying a first operation interface of the protocol data on the client based on the first type of file.

Each member variable in the first type file corresponds to a data field in the protocol data, and the data structure is also kept unchanged, so that a first operation interface can be generated based on the type of each member variable in the first type file, for example, a text box with int type using a restricted integer, a text box with floating point type using a restricted floating point number, and the like.

Based on this, in one possible embodiment, as shown in fig. 6, step S307 may include:

s3071, all member variables in the first type file are obtained.

S3073, for each member variable, generating an interface control of the member variable according to the type of the member variable.

Specifically, for each member variable, if the type of the member variable is a basic data type, a corresponding interface control is directly generated; if the type of the member variable is an array type, traversing each array element according to the length of the member variable, and taking each data element as a member variable to continue to execute the step S3073; if the type of the member variable is the structure type, each sub-structure in the member variable is traversed, and step S307 is continuously executed with each sub-structure as a member variable.

For example, as shown in fig. 7, for a basic data type, if the basic data type is int (integer), then IntField is used to generate a textbox control that restricts integers; if the basic data type is float, using float field to generate a text box control for limiting the float number; if the underlying data type is string, generating an unrestricted text box space using TextField; if the basic data type is a boolean type, generating a switching control by using Toggle; if the basic data type is enum (enumeration type), a drop-down box control is generated by using ComboBox.

S3075, the variable information and the interface control of each member variable are displayed in the first operation interface of the client.

In this embodiment of the application, the variable information at least includes a variable name, and for the member variable of the structure type, the variable information may further include a variable length, and in the first operation interface, the displayed data structure is consistent with the service logic to be represented by the protocol data. As shown in fig. 8, it is an example of a first operation interface of the protocol data. For protocol data named FaGameMapData, Items denotes all data Items of Map Info, Size provides the number of data Items, and for the input Born Actors field, its Size part denotes the number of input Born Actors.

When the source code file is a source code file of C # language, the Unity engine provides a serialization function for a data structure supporting system.

In view of this, as shown in fig. 9, in one embodiment, step S307 may further include:

s3077, storing the first type of files in the first target directory.

S3079, using a file loading mechanism of the preset engine, run the first class of files in the first target directory to add a first operation interface of the protocol data in the attribute panel of the preset engine.

The preset engine refers to an engine applied to a three-dimensional scene, namely a Unity engine. The first target directory refers to a directory in which the Unity engine runtime compiles the C # source code file. The file loading mechanism provided by the Unity engine means that the Unity engine automatically detects C # source code files in the first target directory, automatically recompiles all the C # source code files if changes occur, and then loads corresponding modules based on the compiled result, so that corresponding operation interfaces can be added in the property panel.

Whereas the data structure derived due to the format of the Protobuf data, i.e. the first file, does not support SerializableAttribute. In order to use the serialization function in the property panel, the first file and the data structure in the property panel need to be converted, so that the class corresponding to the first file needs to be a serialization class, that is, the class corresponding to the first file needs to be limited by using the serialization class. For example, if the first type of file is a faskiltraigger wrapper.

An operation control used for operating the protocol data is further provided in the first operation interface, and a user can trigger an operation instruction by clicking the operation control. The operation controls at least include a creation control, a storage control, an upload control and a deletion control, the creation control is used for setting default values for each data field in the protocol data, the storage control is used for storing the value of each data field in the first operation interface, the upload control is used for adding a new data field, and the deletion control is used for deleting a data field. In order to increase user experience, the names of the operation controls can be adjusted for different protocol data.

By automatically reading the protocol file, an operation interface for displaying a data structure of the protocol data is provided, whether the stored protocol data is correct or not is checked conveniently, the protocol data is edited conveniently, and a rapid repairing means is provided for the protocol data at an emergency.

Because the Unity engine has layer number limitation on the automatic serialization of the data, the mode of providing multi-level substructure serialization can be considered for a deep data structure, and the editing of a specific data field is realized. By providing an operation interface for a specific data field, a user does not need to spend more time searching when editing the specific data field, and particularly for protocol data with deeper hierarchy, the quick positioning of the specific data field by the user is more beneficial.

In a possible implementation manner, as shown in fig. 10, the data processing method provided in the foregoing embodiment may further include:

s1001, responding to the query instruction, wherein the query instruction carries target field information.

The user can trigger a query instruction through a query control in the first operation interface, and the target field information is used for indicating the position of a target field to be queried in a data structure of the protocol data.

S1003, analyzing the target field information by using the target function in the first type file to obtain the target field.

The type of the target field information may be a string type and a structure type, the string type indicating that the target field information is a string, and the structure type indicating that the target field information is a message structure.

When the server analyzes the target field information, if the type of the target field information is a character string type, segmenting the target field information according to preset special characters to obtain at least one child node; then for each child node, a look-up is performed using reflection in combination with recursion until the target field is found. When reflection and recursion are used for searching, resolving subscript members for data fields of array types, and calling Item [ Index ] through reflection to obtain values; and for the structure of the byte array which needs further unpacking, the related types can be selected through parameter options for unpacking, and then further analysis is carried out. Since the Protobuf cannot complete the self-nesting or cyclic referencing structure, there is no need to worry about the problem of wireless recursion caused by self-nesting or cyclic referencing, etc.

For byte (bytes) data, since the Protobuf is unable to complete self nesting and circular reference, a mode of twice packing is considered to support the twice expansion recursion of the bytes data. The drawback of typing bytes into a data structure is that more packaging is required for each nested layer. As shown in fig. 11a, which is an exemplary diagram of a nested structure. To this end, some of the packed types are listed by using a white list approach. If the type of the target field information is the structure type, detecting whether the structure type is in a white list; if so, the analysis is performed using a predefined basic data edit class. As shown in fig. 11b, which is an example of a quadratic expansion recursion, in fig. 11b, the BaseDataEditor is the base data editor class.

S1005, displaying a second operation interface of the target field on the client.

As shown in fig. 12, it is an example of the second operation interface. In fig. 12, the target field information is a character string, and a user can input target field information of a target field to be queried, namely Triggers [0] Actions [0] born actor [0], in SearchString, where the target field information indicates that the target field to be queried is the 1 st element of born actors, which is located under the 1 st element of Triggers and the 1 st element of Actions. The user can trigger the query instruction by clicking a Translate button (query control), so that all the child elements of the 1 st born actors [0] are displayed in the second operation interface. In the object-oriented programming language, the point number indicates attribution information, and thus the target field information is preferably divided by using the point number, but may be divided by using a special character such as a semicolon or comma, and the embodiment of the present application is not particularly limited herein.

And fig. 13 shows another example of the second operation interface. In fig. 13, the target field information is a message structure, and a user may select a message structure to be queried, for example, to query the faccherstateful, and then all the member variables in the class file corresponding to the message structure, that is, all the member variables in the faccherstatementwrapper, may be displayed in the second operation interface.

By providing the sub-structure query and display for the protocol data with a deeper hierarchical structure and analyzing the secondary binary packing adopted in part of the sub-structure in a recursive analysis mode, a user can quickly locate the relevant fields of the protocol data to be edited or checked, and the data editing efficiency is further improved.

It can be understood that the second operation interface may be a part of the first operation interface, or may be a regenerated operation interface, and the present specification does not specifically limit the presentation form of the second operation interface.

In practical applications, when deleting data fields in a partial Proto file and reconstructing a data structure of the partial Proto file, since all packed byte data are old, reading cannot be performed by using a new data structure. Although the principle of non-destructive modification is tried to be followed in editing, it is inevitable that there will be variations in development. In order to save time for planning art repeated brushing configuration and implement migration of byte data, as shown in fig. 14, in a possible implementation, the data processing method provided by the foregoing embodiment may further include:

s1401, responding to the upgrading instruction, copying the protocol file to obtain an old protocol file, and copying the byte data file corresponding to the protocol file to obtain the old byte data file.

And S1403, after the protocol file is modified, copying a file formed by modifying the protocol file to obtain a new protocol file.

When protocol data is migrated, the most critical problem is to replace the Byte data file corresponding to the old protocol file with the Byte data file corresponding to the new protocol file, wherein the Byte data file refers to a Byte binary file of data. When the server is executed, the adopted core idea is to transfer out the source code files of the old protocol file and the new protocol file, and reorganize the old byte data file by reading the source code file to obtain the new byte data file. Therefore, the old protocol file, the old byte data file and the new protocol file need to be copied and stored under a specific path.

S1405, compiling the old protocol file and the new protocol file respectively to obtain a first file corresponding to the old protocol file and a first file corresponding to the new protocol file.

In a specific implementation, the first file corresponding to the old protocol file and the first file corresponding to the new protocol file may be obtained in the same manner as in step S303. The first file refers to the source code file, e.g., for C # language, the first file is a cs file.

S1407, based on the first file corresponding to the old protocol file and the first file corresponding to the new protocol file, converting the old byte data file by using the predefined conversion class to obtain the new byte data file.

In the embodiment of the application, the predefined conversion class is used for reading the first file corresponding to the old protocol file and the first file corresponding to the new protocol file, and reorganizing the old byte data file to obtain the new byte data file.

S1409, storing the new byte data file in the second target directory. The second target directory is a directory for storing byte data files corresponding to the new protocol file.

By providing automatic data migration, a new data structure can be edited in an interface without modifying editor codes after a protocol file is modified, namely, the latest data structure can be displayed for a user at each time according to the change of the data structure of configuration data without modifying codes, so that the development and maintenance cost is saved, and the data editing efficiency is improved.

For various protocol data, in order to check data dependency, data consistency, and the like, the data processing method provided by the above method embodiment further includes: responding to a checking instruction, wherein the checking instruction comprises a checking identifier; acquiring data to be checked from the protocol data based on the identification; and verifying the data to be verified according to the verification rule corresponding to the data to be verified.

The check identifier is used for performing uniqueness identification on the data to be checked. As shown in fig. 15, which is an exemplary diagram of a verification control provided for the user in the first operation interface and related to verification, the user may trigger a verification instruction by clicking the verification control. In order to provide the user with an intuitive understanding of whether the data to be verified passes the check, as shown in fig. 16, a verification display panel is further provided for the user, the verification display panel performs real-time dynamic update, and once an item that does not satisfy the verification rule is detected, the item is displayed in the verification display panel.

According to the technical scheme provided by the embodiment of the method, the data processing method provided by the embodiment of the application provides an operation interface for displaying the protocol data by automatically reading the protocol file, so that whether the stored protocol data is correct or not is conveniently checked, the protocol data is conveniently edited, and a quick repairing means is provided for the protocol data at an emergency; the structured display of the protocol data is obtained based on the definition file, when the data structure changes, the automatic identification can be carried out according to the self-defined file without changing the code of an editor, the operation is convenient, the development and maintenance cost is reduced, and the data configuration efficiency is further improved.

In addition, under the condition that no independent editor is developed manually, the configuration and debugging can be rapidly carried out through the operation interface; and in addition, in the case that some complex editor behaviors are not expected, debugging can be assisted by observing and repairing data, and the method has high practicability.

Based on the same inventive concept as the method embodiment, the embodiment of the application also provides a data processing device. As shown in fig. 17, the apparatus 1700 may include:

a file obtaining module 1710, configured to obtain a protocol file, where the protocol file is a definition file of protocol data;

the compiling module 1720 is used for compiling the protocol file to obtain a first file and a second file corresponding to the protocol file, wherein the first file is a source code file, and the second file is a binary file;

the class generating module 1730 is configured to perform data structure conversion on the protocol data according to the first file and the second file corresponding to the protocol file, and generate a first class file;

the interface generating module 1740 is configured to display a first operation interface of the protocol data at the client based on the first type file.

In one possible implementation, as shown in fig. 18, the class generation module 1730 may include:

the file parsing unit 1731 is configured to obtain a namespace and a data structure corresponding to the protocol data according to the second file corresponding to the protocol file;

a class file creating unit 1732 configured to create a first class file in a namespace;

a variable declaring unit 1733, configured to traverse each data field in the data structure, determine a target type based on the data type of the data field and the qualified modifier, and declare a member variable corresponding to the data field in the first class file using the target type;

the function declaring unit 1734 is configured to create an objective function in the first class file based on the first file corresponding to the protocol file and each member variable, where the objective function is used to implement conversion of a data structure of the protocol data.

In one possible implementation, as shown in fig. 19, the variable declaration unit 1733 may include:

a first type determining unit 17331 for determining the data type as a reference type in case that the data type is the basic type;

a second type determining unit 17332, configured to determine, when the data type is the structure type, a second class file corresponding to the structure type, and determine a class in the second class file as a reference type;

a type updating unit 17333, configured to update the reference type based on whether the qualifier is a multi-choice modifier, resulting in the target type.

In one possible implementation, as shown in fig. 20, the interface generating module 1740 may include:

a member variable acquiring unit 1741, configured to acquire all member variables in the first class of files;

a control generating unit 1742, configured to generate, for each member variable, an interface control of the member variable according to the type of the member variable;

and the content filling unit 1743 is configured to display the variable information and the interface control of each member variable in the first operation interface of the client.

In one possible implementation, as shown in fig. 21, the interface generating module 1740 may further include:

a file storage unit 1744, configured to store the first type of file in the first target directory;

an engine running unit 1745, configured to run the first type of file in the first target directory by using a file loading mechanism of a preset engine, so as to add a first operation interface of protocol data in an attribute panel of the preset engine, where the preset engine is an engine applied in a three-dimensional scene.

In one possible embodiment, as shown in fig. 22, the apparatus 1700 may further include:

a first response module 1750, configured to respond to a query instruction, where the query instruction carries target field information;

the field query module 1760 is used for analyzing the target field information by using the target function in the first type of file to obtain a target field;

a field display module 1770, configured to display the second operation interface of the target field on the client.

a second response module 1780, configured to copy the protocol file to obtain an old protocol file in response to the upgrade instruction, and copy the byte data file corresponding to the protocol file to obtain an old byte data file;

the file backup module 1790 is used for copying the file formed by modifying the protocol file after the modification of the protocol file is finished, so as to obtain a new protocol file;

the second compiling module 17100 is configured to compile the old protocol file and the new protocol file respectively to obtain a first file corresponding to the old protocol file and a first file corresponding to the new protocol file;

a byte data generating module 17110, configured to convert the old byte data file by using a predefined conversion class based on the first file corresponding to the old protocol file and the first file corresponding to the new protocol file, to obtain a new byte data file;

a file storage module 17120, configured to store the new byte data file in the second target directory.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

The embodiment of the present application further provides an electronic device, which includes a processor and a memory, where the memory stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded by the processor and executes the data processing method provided by the above method embodiment.

Further, fig. 24 is a schematic hardware structure diagram of an apparatus for implementing the method provided in the embodiment of the present application, and the apparatus may participate in forming or containing the device or system provided in the embodiment of the present application. As shown in fig. 24, device 24 may include one or more (shown here as 2402a, 2402b, … …, 2402 n) processors 2402 (processor 2402 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), memory 2404 for storing data, and a transmission device 2406 for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 24 is merely illustrative and is not intended to limit the structure of the electronic device. For example, the device 24 may also include more or fewer components than shown in FIG. 24, or have a different configuration than shown in FIG. 24.

It should be noted that the one or more processors 2402 and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuitry may be a single, stand-alone processing module, or incorporated in whole or in part into any of the other elements in the device 24 (or mobile device). As referred to in the embodiments of the application, the data processing circuit acts as a processor control (e.g. selection of a variable resistance termination path connected to the interface).

The memory 2404 can be used for storing software programs and modules of application software, such as program instructions/data storage devices corresponding to the methods described in the embodiments of the present application, and the processor 2402 executes various functional applications and data processing by running the software programs and modules stored in the memory 2404, so as to implement one of the data processing methods described above. The memory 2404 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 2404 may further include memory located remotely from the processor 2402, which may be connected to the device 24 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission means 2406 is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by the communication provider of the device 24. In one example, the transmission device 2406 includes a network adapter (NIC) that can be connected to other network devices through a base station so as to communicate with the internet. In one example, the transmission device 2406 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the device 24 (or mobile device).

The embodiment of the present application further provides a computer-readable storage medium, where at least one instruction or at least one program is stored in the computer-readable storage medium, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the data processing method provided by the foregoing method embodiment.

Alternatively, in this embodiment, the computer-readable storage medium may be located on at least one of a plurality of network servers of a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the electronic device to execute the computer-readable storage medium provided by the above-mentioned method embodiment.

It should be noted that: the sequence of the embodiments of the present application is only for description, and does not represent the advantages and disadvantages of the embodiments. And specific embodiments thereof have been described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device and electronic apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.

The foregoing description has disclosed fully embodiments of the present application. It should be noted that those skilled in the art can make modifications to the embodiments of the present application without departing from the scope of the claims of the present application. Accordingly, the scope of the claims of the present application is not to be limited to the particular embodiments described above.

Claims

1. A method of data processing, the method comprising:

2. The method according to claim 1, wherein the performing data structure conversion on the protocol data according to the first file and the second file corresponding to the protocol file to generate a first type file comprises:

obtaining a namespace and a data structure corresponding to the protocol data according to a second file corresponding to the protocol file;

establishing the first type of file in the name space;

traversing each data field in the data structure, determining a target type based on the data type of the data field and a defined modifier, declaring member variables corresponding to the data field in the first class file by using the target type;

and creating an objective function in the first class of files based on the first file corresponding to the protocol file and each member variable, wherein the objective function is used for realizing conversion of a data structure of the protocol data.

3. The method of claim 2, wherein determining a target type based on the data type of the data field and a qualified modifier comprises:

if the data type is the basic type, determining the data type as a reference type;

if the data type is the structure type, determining a second class file corresponding to the structure type, and determining a class in the second class file as the reference type;

and updating the reference type based on whether the limited modifier is a multi-choice modifier to obtain the target type.

4. The method according to claim 1, wherein the presenting the first operation interface of the protocol data at the client based on the first type file comprises:

acquiring all member variables in the first type of file;

for each member variable, generating an interface control of the member variable according to the type of the member variable;

and displaying the variable information and the interface control of each member variable in a first operation interface of the client.

5. The method of claim 1, wherein the source code file is a source code file of C # language, and the first class file corresponding class is a serialization class;

the first operation interface for displaying the protocol data at the client based on the first type of file comprises:

storing the first type of file under a first target directory;

and operating the first type of files under the first target directory by using a file loading mechanism of a preset engine to add a first operation interface of the protocol data in an attribute panel of the preset engine, wherein the preset engine is an engine applied to a three-dimensional scene.

6. The method of claim 1, further comprising:

responding to a query instruction, wherein the query instruction carries target field information;

analyzing the target field information by using a target function in the first type of file to obtain a target field;

and displaying a second operation interface of the target field at the client.

7. The method of claim 1, further comprising:

in response to an upgrading instruction, copying the protocol file to obtain an old protocol file, and copying a byte data file corresponding to the protocol file to obtain an old byte data file;

after the protocol file is modified, copying a file formed by modifying the protocol file to obtain a new protocol file;

compiling the old protocol file and the new protocol file respectively to obtain a first file corresponding to the old protocol file and a first file corresponding to the new protocol file;

converting the old byte data file by using a predefined conversion class based on the first file corresponding to the old protocol file and the first file corresponding to the new protocol file to obtain a new byte data file;

and storing the new byte data file into a second target directory.

8. A data processing apparatus, characterized in that the apparatus comprises:

9. An electronic device, characterized in that the device comprises a processor and a memory, in which at least one instruction or at least one program is stored, which is loaded by the processor and executes the data processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, in which at least one instruction or at least one program is stored, which is loaded and executed by a processor to implement the data processing method according to any one of claims 1 to 7.