Master data processing method and system, electronic equipment and storage medium

Abstract

The invention discloses a master data processing method and system, electronic equipment and a storage medium. The method comprises the steps that in response to a received data storage request, first metadata corresponding to the data storage request is obtained, and the data storage request carries main data of a first type; serializing the main data of the first type based on the first metadata to obtain first serialized data; the first serialized data is stored in a preset data table, and different types of main data are stored in the preset data table. The technical problem of low data processing efficiency in related technologies is solved.

Description

Technical Field

[0001] This application relates to the field of data processing, and in particular, to a master data processing method, system, electronic device, and storage medium. Background Art

[0002] Currently, master data management generally consists of a master data network application and a master data service application. Among them, the master data service application mainly provides corresponding services for different master data. In the underlying storage, different master data correspond to separate task tables to facilitate the management and access of master data. However, due to the large variety of master data, every time a new type of master data is added, a new table needs to be created to store the corresponding data, resulting in low data processing efficiency.

[0003] In response to the above problems, no effective solution has been proposed yet. Summary of the Invention

[0004] Embodiments of this application provide a master data processing method, system, electronic device, and storage medium to at least solve the technical problem of low data processing efficiency in related technologies.

[0005] According to one aspect of the embodiments of this application, a master data processing method is provided, including: in response to receiving a data storage request, obtaining first metadata corresponding to the data storage request, where the data storage request carries master data of a first type; serializing the master data of the first type based on the first metadata to obtain first serialized data; storing the first serialized data in a preset data table.

[0006] According to another aspect of the embodiments of this application, a master data processing method is further provided, including: in response to receiving a data access request, obtaining second metadata corresponding to the data access request, where the data access request is used to access master data of a second type; obtaining second serialized data corresponding to the data access request from the preset data table; deserializing the second serialized data based on the second metadata to obtain master data of the second type; sending the master data of the second type to the client device corresponding to the data access request.

[0007] According to another aspect of the embodiments of this application, a master data processing method is further provided, including: in response to an input instruction acting on an operation interface, displaying on the operation interface master data of a first type corresponding to the input instruction; in response to a data storage instruction acting on the operation interface, displaying on the operation interface a data storage result corresponding to the data storage instruction, where the data storage result is the result generated by storing the first serialized data corresponding to the master data of the first type in the preset data table, and the first serialized data is data obtained by serializing the master data of the first type based on the first metadata corresponding to the first type.

[0008] According to another aspect of the embodiments of the present application, a main data processing method is further provided, including: obtaining a data storage request by calling a first interface, where the first interface includes a first parameter, the parameter value of the first parameter is the data storage request, and the data storage request carries main data of a first type; obtaining first metadata corresponding to the data storage request; serializing the main data of the first type based on the first metadata to obtain first serialized data; storing the first serialized data in a preset data table to obtain a data storage result; and outputting the data storage result by calling a second interface, where the second interface includes a second parameter, and the parameter value of the second parameter is the data storage result.

[0009] According to another aspect of the embodiments of the present application, a main data processing system is further provided, including: a preset application for receiving a data storage request, where the data storage request carries main data of a first type; a database for storing a preset data table; and service applications corresponding to multiple types, and the service applications corresponding to different types are used to process main data of different types. Among them, the service application corresponding to the first type or the preset application is used to call a metadata software package to obtain first metadata corresponding to the data storage request, serialize the main data of the first type based on the first metadata to obtain first serialized data, and store the first serialized data in the preset data table.

[0010] According to another aspect of the embodiments of the present application, an electronic device is further provided, including: a memory storing an executable program; and a processor for running the program, where when the program runs, it executes the method described in any one of the above embodiments.

[0011] According to another aspect of the embodiments of the present application, the computer-readable storage medium includes a stored executable program, where when the executable program runs, it controls the device where the storage medium is located to execute the method described in any one of the above embodiments.

[0012] In the embodiments of the present application, in response to receiving a data storage request, first metadata corresponding to the data storage request is obtained, where the data storage request carries main data of a first type; the main data of the first type is serialized based on the first metadata to obtain first serialized data, and the first serialized data is stored in a preset data table, which realizes the improvement of data processing efficiency; it is easy to notice that when storing the main data, the main data can be serialized for unified storage of the main data, and the serialized main data can be stored in the same data table by constructing metadata, avoiding the need to construct separate task tables for different main data, reducing the storage of underlying tables to improve development efficiency, thereby improving data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0013] It is easy to notice that the above general description and the following detailed description are only for exemplifying and explaining the present application, and do not constitute a limitation to the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application, and constitute a part of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation to the present application. In the drawings:

[0015] Figure 1 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing the main data processing method according to an embodiment of the present application;

[0016] Figure 2 is a structure block diagram of a computing environment according to an embodiment of the present application;

[0017] Figure 3 is a structure block diagram of a service mesh according to an embodiment of the present application;

[0018] Figure 4 is a flowchart of the main data processing method according to Embodiment 1 of the present application;

[0019] Figure 5 is a schematic structural diagram of a unified storage main data management method according to an embodiment of the present application;

[0020] Figure 6 is a schematic structural diagram of another main data management method according to an embodiment of the present application;

[0021] Figure 7 is a schematic diagram of a procurement scenario according to an embodiment of the present application;

[0022] Figure 8 is a schematic structural diagram of an implementation method of a metadata software development kit according to an embodiment of the present application;

[0023] Figure 9 is a flowchart of a main data processing method according to Embodiment 2 of the present application;

[0024] Figure 10 is a flowchart of a main data processing method according to Embodiment 3 of the present application;

[0025] Figure 11 is a schematic diagram of a main data processing device according to Embodiment 4 of the present application;

[0026] Figure 12 is a schematic diagram of a main data processing device according to Embodiment 5 of the present application;

[0027] Figure 13 is a schematic diagram of a master data processing device according to Embodiment 6 of the present application;

[0028] Figure 14 is a structural diagram of a master data processing system according to Embodiment 7 of the present application;

[0029] Figure 15 is a flowchart of a master data processing method according to Embodiment 8 of the present application;

[0030] Figure 16 is a schematic diagram of a master data processing device according to Embodiment 9 of the present application;

[0031] Figure 17 is a structural block diagram of a computer terminal according to an embodiment of the present application. Detailed implementation manners

[0032] In order to enable those skilled in the art of the present technology to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present application.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0034] First, some nouns or terms that appear in the process of describing the embodiments of the present application are applicable to the following explanations:

[0035] Master data may refer to data that is long-term stable, used by multiple systems, and shared by multiple parts;

[0036] Enterprise master data can refer to the enterprise master data needed in the process of enterprise operation and management. Among them, the enterprise master data with higher frequency can be company, factory, company factory, cost center, material, address, invoice, accounting subject, budget subject;

[0037] Metadata can refer to data that describes data, such as the form data submitted at a certain time. The actual data in the form is called data, and the description of the form itself is considered metadata.

[0038] Example 1

[0039] According to an embodiment of the present application, a master data processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical sequence is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than that shown here.

[0040] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a master data processing method according to an embodiment of the present application. Figure 1 As shown in , the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate in the figure) processors 102, and the processor 102 may include but is not limited to a processing device such as a microprocessor (Microcontroller Unit, referred to as MCU) or a programmable logic device (Field-Programmable Gate Array, referred to as FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (Universal Serial Bus, USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. For example, the computer terminal 10 may also include Figure 1 More or fewer components than shown in , or with the same Figure 1 Different configurations shown.

[0041] ​​It should be noted that one or more of the above-mentioned processors 102 and / or other data processing circuits can generally be referred to as "data processing circuits" herein. The data processing circuit can be embodied in software, hardware, firmware, or any combination thereof, in whole or in part. In addition, the data processing circuit can be a single independent processing module, or be incorporated in whole or in part into any one of other elements in the computer terminal 10 (or mobile device). As involved in the embodiments of the present application, the data processing circuit is a kind of processor control (such as the selection of a variable resistor terminal path connected to an interface).

[0042] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage devices corresponding to the main data processing method in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the above-mentioned main data processing method. The memory 104 can include high-speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 can further include a memory remotely set relative to the processor 102, and these remote memories can be connected to the computer terminal 10 through a network. Examples of the above-mentioned network include but are not limited to the Internet, enterprise intranet, local area network, mobile communication network, and combinations thereof.

[0043] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network can include the wireless network provided by the communication provider of the computer terminal 10. In one instance, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station and thus communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0044] The display can be, for example, a touch-screen liquid crystal display (Liquid Crystal Display, LCD), which enables the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0045] Figure 1 The shown hardware structure block diagram can not only be used as an exemplary block diagram of the above-mentioned computer terminal 10 (or mobile device), but also as an exemplary block diagram of a server. In an alternative embodiment, Figure 2 is shown in a block diagram using the above Figure 1The illustrated computer terminal 10 (or mobile device) is an example of a computing node in the computing environment 201. Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application, as Figure 2 shown, the computing environment 201 includes a plurality of (shown as 210-1, 210-2, … in the figure) computing nodes (such as servers) running on a distributed network. Each computing node contains local processing and memory resources, and end users 202 can remotely run applications or store data in the computing environment 201. The applications can be provided as a plurality of services 220-1, 220-2, 220-3, and 220-4 in the computing environment 201, representing services "A", "D", "E", and "H" respectively.

[0046] End users 202 can provide and access services through a web browser or other software applications on the client side. In some embodiments, the provision and / or requests of end users 202 can be provided to the ingress gateway 230. The ingress gateway 230 can include a corresponding proxy to handle the provision and / or requests for services (one or more services provided in the computing environment 201).

[0047] Services are provided or deployed according to various virtualization technologies supported by the computing environment 201. In some embodiments, services can be provided based on virtual machine (VM)-based virtualization, container-based virtualization, and / or similar means. VM-based virtualization can simulate a real computer by initializing a virtual machine and execute programs and applications without directly accessing any actual hardware resources. While the virtual machine virtualizes the machine, according to container-based virtualization, containers can be launched to virtualize the entire operating system (OS) so that multiple workloads can run on a single operating system instance.

[0048] In one embodiment of container-based virtualization, several containers of a service can be assembled into a Pod (for example, a Kubernetes Pod). For example, as Figure 2 shown, the service 220-2 can be equipped with one or more Pods 240-1, 240-2, …, 240-N (collectively referred to as Pods). A Pod can include a proxy 245 and one or more containers 242-1, 242-2, …, 242-M (collectively referred to as containers). One or more containers in the Pod handle requests related to one or more corresponding functions of the service, and the proxy 245 generally controls network functions related to the service, such as routing, load balancing, etc. Other services can also be equipped with similar Pods.

[0049] During operation, executing a user request from the end user 202 may require invoking one or more services in the computing environment 201, and executing one or more functions of a service may require invoking one or more functions of another service. As Figure 2 shown, service "A" 220-1 receives a user request from the end user 202 from the ingress gateway 230. Service "A" 220-1 may invoke service "D" 220-2, and service "D" 220-2 may request service "E" 220-3 to execute one or more functions.

[0050] The computing environment described above may be a cloud computing environment where the allocation of resources is managed by a cloud service provider, allowing the development of functions without considering the implementation, adjustment, or expansion of servers. This computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be divided into a set of functions that can be automatically and independently scaled, rather than expanding a single hardware device to handle potential loads.

[0051] In another alternative embodiment, Figure 3 A block diagram shows an embodiment of using the computer terminal 10 (or mobile device) as described above Figure 1 as a service mesh. Figure 3 It is a structural block diagram of a service mesh according to an embodiment of the present application. As Figure 3 shown, the service mesh 300 is mainly used to facilitate secure and reliable communication between multiple microservices. A microservice refers to decomposing an application into multiple smaller services or instances and running them on different clusters / machines.

[0052] As Figure 3 shown, the microservices may include application service instance A and application service instance B, and application service instance A and application service instance B form the functional application layer of the service mesh 300. In one implementation, application service instance A runs in the form of a container / process 308 in the machine / workload container group 314 (Pod), and application service instance B runs in the form of a container / process 310 in the machine / workload container group 316 (Pod).

[0053] In one implementation, application service instance A may be a product query service, and application service instance B may be a product ordering service.

[0054] As Figure 3As shown, application service instance A and mesh proxy (sidecar) 303 coexist in machine / workload container group 314, and application service instance B and mesh proxy 305 coexist in machine workload container 314. Mesh proxy 303 and mesh proxy 305 form the data plane layer (dataplane) of service mesh 300. Among them, mesh proxy 303 and mesh proxy 305 run in the form of container / process 304 and container / process 306 respectively, and can receive requests 312 for commodity query services. In addition, two-way communication can be carried out between mesh proxy 303 and application service instance A, and between mesh proxy 305 and application service instance B. Furthermore, two-way communication can also be carried out between mesh proxy 303 and mesh proxy 305.

[0055] In one implementation, the traffic of application service instance A is routed to the appropriate destination through mesh proxy 303, and the network traffic of application service instance B is routed to the appropriate destination through mesh proxy 305. It should be noted that the network traffic mentioned here includes but is not limited to forms such as Hyper Text Transfer Protocol (abbreviated as HTTP), Representational State Transfer (abbreviated as REST), google Remote Procedure Call (gRPC), an open-source in-memory data structure storage system (Redis), etc.

[0056] In one implementation, the function of the extended data plane layer can be realized by writing a custom filter (Filter) for the proxy (Envoy) in service mesh 300. The service mesh proxy configuration can be used to correctly proxy service traffic in the service mesh, and to achieve service interconnection and service governance. Mesh proxy 303 and mesh proxy 305 can be configured to perform at least one of the following functions: service discovery, health checking, routing, load balancing, authentication and authorization, and observability.

[0057] As Figure 3 shown, the service mesh 300 also includes a control plane layer. Among them, the control plane layer can be a group of services running in a dedicated namespace, and these services are hosted by the managed control plane component 301 in machine / workload container group (machine / Pod) 302. AsFigure 3 As shown, the managed control plane component 301 communicates bidirectionally with the grid agents 303 and 305. The managed control plane component 301 is configured to perform some control management functions. For example, the managed control plane component 301 receives the telemetry data transmitted by the grid agents 303 and 305, and can further aggregate this telemetry data. For these services, the managed control plane component 301 can also provide user-facing application programming interfaces (APIs) to more easily manipulate network behavior and provide configuration data to the grid agents 303 and 305, etc.

[0058] In the above operating environment, the present application provides the main data processing method as Figure 4 shown. Figure 4 is a flowchart of the main data processing method according to Embodiment 1 of the present application. As Figure 4 shown, the server 10 can be connected to one or more client devices 20 through a local area network connection, a wide area network connection, an Internet connection, or other types of data networks. Here, the client devices 20 can include, but are not limited to: smart phones, tablet computers, laptop computers, handheld computers, personal computers, smart home devices, in-vehicle devices, etc. The client device 20 can interact with the user through a graphical user interface. The method includes:

[0059] Step S402, in response to receiving a data storage request, obtain the first metadata corresponding to the data storage request.

[0060] Among them, the data storage request carries the main data of the first type.

[0061] The above data storage request can be a request sent by the user when they need to store data.

[0062] The above main data of the first type can refer to the main data that the user needs to store and will subsequently be used through the main data service.

[0063] The above main data can refer to the core data that is widely used, shared, and long-term stable. The main data can be a key component in the data management process. Among them, long-term stability means data that exists for a long time and is relatively stable, not easily changing frequently. The data used by multiple systems can be used by multiple systems or application programs. The data shared by multiple departments refers to data that is shared and used across departments, not limited to a specific department or application area; optionally, the main data can be the core data in an organization or enterprise, including but not limited to customer, supplier, product, employee, etc. data.

[0064] The above-mentioned first metadata may refer to data used to describe the characteristics, attributes, and relationships of data, and the first metadata can be used to help users understand and use the master data.

[0065] In an alternative embodiment, after receiving a data storage request, the first metadata can be determined according to the first type of master data carried in the data storage request, so as to uniformly store the first type of master data through the first metadata, thereby improving the storage efficiency of the master data.

[0066] Step S404: Serialize the first type of master data based on the first metadata to obtain first serialized data.

[0067] The above-mentioned first metadata is mainly used to represent data describing the master data. The first metadata can include information such as the structure, attributes, relationships, and constraints of the master data. By using metadata, serialization operations can be performed on the master data.

[0068] The above-mentioned serialization refers to converting the master data into a serialized format. Among them, this format can be binary, script, etc. The serialization operation saves the attribute values of the master data and the relevant metadata information together so that the original master data can be restored when needed.

[0069] In an alternative embodiment, the first serialized data obtained by serializing the first type of master data based on the first metadata can be more conveniently stored and transmitted. The first serialized data can be saved to a file, a database, or transmitted over the network; the first serialized data can be more conveniently shared and integrated, so that the first serialized data can be easily shared for use by other systems or applications, and can also be integrated into different platforms; the first serialized data can be data-persisted, and the serialized data can be stored for a long time so that it can be reloaded and used when needed.

[0070] The operation of serializing the master data through the first metadata can conveniently store, transmit, and share data, and can retain the structure and attribute information of the master data, enabling the data to be effectively used and managed in different environments.

[0071] Step S406: Store the first serialized data into a preset data table.

[0072] Among them, different types of master data are stored in the preset data table.

[0073] The above-mentioned preset data table can be a table predefined in the database for storing data. Among them, the preset data table generally has a fixed structure and contains some common metadata fields, such as table name, column name, data type, length, index, etc.

[0074] In an alternative embodiment, the first serialized data can be stored in a preset data table, and subsequently, the user can query the master data by accessing the preset data table.

[0075] Figure 5 It is a schematic structural diagram of a master data management method with unified storage according to an embodiment of the present application. As Figure 5 shown, in implementing master data management, a structure of a master data network application and a master data service application is adopted. This can keep the architecture layering clear, so that each application can perform its own functions and data processing can be carried out more efficiently. The master data service application includes Service 1, Service 2, Service 3, Service 4, Service 5, Service 6, Service 7, etc. The master data can be serialized through a Software Development Kit (SDK) for metadata, so as to facilitate the unified storage and access of the underlying storage of the master data, and avoid the need for each different master data service to build a set of database tables to implement the storage and access of the database tables. In the underlying storage of the master data, the master data is stored through a metadata table. Compared with the conventional master data management method, in the present application, the unified data can be stored in the metadata table through the metadata SDK method to reduce the storage of the underlying tables and improve the development efficiency.

[0076] Figure 6 It is a schematic structural diagram of another master data management method according to an embodiment of the present application. As Figure 6 shown, in master data management, the master data network application and the metadata SDK can be retained, and the unified storage and access of the underlying storage of the master data can be achieved by calling the metadata SDK. In the underlying storage of the master data, the master data is stored through a metadata table. Since there is no layer of master data service application, a large amount of logic is required to encapsulate the access logic to the metadata SDK in this solution.

[0077] For the related art where each different master data service needs to create a separate master data task table, and each different master data service needs to implement a set of storage and access logics for the database, in the present application, the unified storage and access of the underlying storage of the master data can be achieved through the metadata SDK. Different master data services do not need to concern themselves with the underlying database tables, so as to reduce the maintenance of the underlying database tables and thus improve the overall development and maintenance efficiency of master data management.

[0078] Figure 7 It is a schematic diagram of a procurement scenario according to an embodiment of the present application. As Figure 7As shown in the figure, in the software service system (Software as a Service, abbreviated as SaaS) of the procurement scenario, it includes a master data layer, a task support layer, and an upper task layer. Among them, the master data included in the master data layer includes, but is not limited to, companies, factories, system domains, procurement centers, procurement groups, measurement units, regions, cost centers, and procurement centers; the task support layer includes supplier management, configuration centers, and employee permissions; the upper tasks include requisition, inquiry, bidding, auction, mall, order, evaluation, performance, and contract. In the procurement scenario, there are many types of master data, but generally it is relatively stable and the degree of change is small. The data model of the master data is relatively simple and there will be no complex state transitions. In the process of managing the master data for the procurement scenario, the method of uniformly storing the master data proposed in this application can combine the characteristics of less change and simple model of the master data, and achieve unified storage and access through the method of the metadata SDK, which can improve the overall development management efficiency.

[0079] Through the above steps, in response to receiving a data storage request, obtain the first metadata corresponding to the data storage request, where the data storage request carries the master data of the first type; serialize the master data of the first type based on the first metadata to obtain the first serialized data, and store the first serialized data in a preset data table, where different types of master data are stored in the preset data table, achieving the improvement of data processing efficiency; it is easy to notice that when storing the master data, by serializing the master data for unified storage, the serialized master data can be stored in the same data table by constructing metadata, avoiding the need to build separate task tables for different master data, reducing the storage of the underlying tables to improve development efficiency, thereby improving data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0080] In the above embodiment of this application, in response to receiving a data storage request, obtaining the first metadata corresponding to the data storage request includes: in response to a preset application receiving a data storage request, parsing the data storage request through the service application corresponding to the first type or the preset application to obtain the master data of the first type; calling the metadata software toolkit to obtain the first metadata corresponding to the first type from multiple metadata, where different metadata corresponds to different types of master data.

[0081] The above-mentioned preset application can be a master data web application. The above-mentioned service application can be a master data service application.

[0082] The above-mentioned service application corresponding to the first type can be an application for providing relevant services for the master data of the first type. The service application of the first type can include, but is not limited to, the service applications corresponding to companies, factories, regions, and procurement centers.

[0083] In an alternative embodiment, when the preset application receives a data storage request and is in a scenario where a service application is included in the structure, the service application corresponding to the first type can be used to parse the data storage request to obtain the master data of the first type; when in a scenario where no service application is included in the structure, the preset application corresponding to the first type can be used to parse the data storage request to obtain the master data of the first type.

[0084] The above-mentioned multiple metadata includes descriptions and attribute information of different master data. Among them, the multiple metadata can be used as the basis for guiding the serialization of the corresponding multiple master data.

[0085] In an alternative embodiment, the first type of the master data can be used to determine the first metadata so that the first metadata can correctly serialize and parse the master data subsequently.

[0086] Figure 8 It is a schematic structural diagram of an implementation method of a metadata software development kit according to an embodiment of the present application. As Figure 8 shown, the processing process of metadata includes a storage layer, a metadata management layer, an engine layer, a protocol layer, and a metadata interface. Among them, the storage layer includes database storage (MySQL), cache server (Redis), Elasticsearch (abbreviated as ES), and Open Data Processing Service (abbreviated as ODPS); the metadata management layer includes model definition, rule definition, storage management, and index management; the engine layer includes parsing, merging, routing, and searching; the protocol layer includes High Speed Framework (abbreviated as HSF), Remote Call Framework (DUBBO), Hypertext Transfer Protocol (HTTP), and Service Provider Interface (SPI); the metadata interface includes Query Application Programming Interface (abbreviated as Query API), Batch Application Programming Interface (abbreviated as Batch API), Save Application Programming Interface (abbreviated as Save API), and Open Application Programming Interface (abbreviated as Open API).

[0087] In the above embodiments of the present application, serializing the first type of master data based on the first metadata to obtain the first serialized data includes: serializing the first type of master data based on the first metadata through the service application or preset application corresponding to the first type to obtain the first serialized data.

[0088] In an alternative embodiment, in a scenario including a service application, the first type of master data can be serialized in the service application based on the first metadata to ensure the correct transmission and parsing of the master data between different systems or platforms, thereby realizing the effective sharing and utilization of data. In a scenario without a service application, the first type of master data can be serialized in the preset application based on the first metadata to ensure the correct transmission and parsing of the master data between different systems or platforms, thereby realizing the effective sharing and utilization of data.

[0089] In the above embodiments of the present application, storing the first serialized data in a preset data table includes: obtaining the first type name and the first identification information of the first type; associatively storing the first serialized data, the first identification information, and the first type name in the preset data table.

[0090] The above first type name and first identification information can be set by the user himself. The first type name and first identification information of the first type can also be set by the system itself. Exemplarily, the first type name can be a company, a factory, a procurement center, etc., and the first identification information can be numbers, letters, etc. This is only an example here and is not subject to any limitation.

[0091] In an alternative embodiment, the first serialized data, the first identification information, and the first type name can be associatively stored in the preset data table, so that the user can subsequently query the first serialized data based on the first identification information or the first type.

[0092] By uniformly storing the first serialized data in the preset data table, the maintenance efficiency of the data table in the underlying database can be improved, thereby improving the overall development and maintenance efficiency in the data management process.

[0093] In the above embodiments of the present application, the method further includes: in response to receiving a data access request, obtaining the second metadata corresponding to the data access request, where the data access request is used to access the second type of master data; obtaining the second serialized data corresponding to the data access request from the preset data table; deserializing the second serialized data based on the second metadata to obtain the second type of master data; sending the second type of master data to the client device corresponding to the data access request.

[0094] The above data access request can be initiated by the user, and the user can access the data in the database according to needs.

[0095] The above-mentioned client device can be the client device used by a user who needs to access the master data. Among them, the client device can have the permission to access the master data.

[0096] The role of the above deserialization is to convert the serialized data back into an object or data structure that can be used by the program.

[0097] In an alternative embodiment, the second metadata may include information such as the structure, type, and attributes of the second serialized data. The deserialization process uses the metadata to parse the second serialized data and restore the second serialized data back to the form of the master data, and the second type of master data can be sent to the client device that issues the output data access request so that the user can view the second type of master data on the client device.

[0098] In the above embodiments of the present application, in response to receiving a data access request, obtaining the second metadata corresponding to the data access request includes: in response to a preset application receiving a data access request, calling a metadata software toolkit to obtain the second metadata corresponding to the second type from multiple metadata.

[0099] In an alternative embodiment, after the preset application receives a data access request, it can call a metadata software tool to obtain the second metadata corresponding to the second type from multiple metadata, so as to parse the second serialized data according to the information such as the structure, type, and attributes of the second serialized data through the second metadata, thereby restoring the second serialized data to the second type of master data.

[0100] In the above embodiments of the present application, obtaining the second serialized data corresponding to the data access request from a preset data table includes: obtaining the second type name and the second identification information of the second type through the service application or the preset application corresponding to the second type; obtaining the serialized data corresponding to the second type name and the second identification information from the preset data table through the service application or the preset application corresponding to the second type to obtain the second serialized data.

[0101] The above second type name and second identification information can be set by the user himself. The second type name and second identification information of the second type can also be set by the system itself. Exemplarily, the second type name can be company, factory, procurement center, etc., and the second identification information can be numbers, letters, etc. This is only an example here and is not subject to any limitation.

[0102] In an alternative embodiment, the serialized data corresponding to the second type name and the second identification information can be queried from the preset data table, and the serialized data is determined as the second serialized data.

[0103] In the above embodiments of the present application, deserializing the second serialized data based on the second metadata to obtain the master data of the second type includes: deserializing the second serialized data based on the second metadata through the service application or preset application corresponding to the second type to obtain the master data of the second type.

[0104] In an alternative embodiment, in the case of including a service application, the second serialized data can be deserialized based on the second metadata through the service application corresponding to the second type to obtain the master data of the second type; in the case of not including a service application, the second serialized data can be deserialized based on the second metadata through the preset application corresponding to the second type to obtain the master data of the second type.

[0105] In the above embodiments of the present application, the method further includes: in response to receiving a metadata configuration instruction, obtaining the third metadata corresponding to the metadata configuration instruction, where the metadata configuration instruction is used to configure the third metadata; and calling a metadata software toolkit to store the third metadata.

[0106] The above-mentioned third metadata can be metadata to be configured.

[0107] In an alternative embodiment, if there is no service application for the master data, it is necessary to configure the third metadata to facilitate unified storage and access through the third metadata. The third metadata can be stored by calling a metadata software toolkit, or can be encapsulated through a preset logic and then the encapsulated data can be stored.

[0108] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. And the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0109] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0110] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of the present application.

[0111] Embodiment 2

[0112] According to an embodiment of the present application, there is also provided a master data processing method. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than this.

[0113] Figure 9 is a flowchart of a master data processing method according to Embodiment 2 of the present application. As Figure 9 shown, the method includes the following steps:

[0114] Step S902, in response to an input instruction acting on the operation interface, display the first type of master data corresponding to the input instruction on the operation interface.

[0115] The above operation interface can be used to display master data. Among them, the operation interface can include various different controls for the user to operate, so as to display the master data on the operation interface.

[0116] Step S904, in response to a data storage instruction acting on the operation interface, display the data storage result corresponding to the data storage instruction on the operation interface.

[0117] Among them, the data storage result is the result generated by storing the first serialized data corresponding to the first type of master data into a preset data table. The first serialized data is the data obtained by serializing the first type of master data based on the first metadata corresponding to the first type. Different types of master data are stored in the preset data table.

[0118] The above data storage result can be a result used to indicate whether the master data is successfully stored.

[0119] Through the above steps, in response to an input instruction acting on the operation interface, the first type of master data corresponding to the input instruction is displayed on the operation interface; in response to a data storage instruction acting on the operation interface, the data storage result corresponding to the data storage instruction is displayed on the operation interface, where the data storage result is the result generated by storing the first serialized data corresponding to the first type of master data into a preset data table, the first serialized data is data obtained by serializing the first type of master data based on the first metadata corresponding to the first type, and different types of master data are stored in the preset data table; it is easy to notice that the efficiency of data processing is improved; it is easy to notice that when storing the master data, by serializing the master data for unified storage, the serialized master data can be stored in the same data table by constructing metadata, avoiding the need to construct a separate task table for different master data, reducing the storage of underlying tables to improve development efficiency, thereby improving the data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0120] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0121] Embodiment 3

[0122] According to an embodiment of the present application, a master data processing method is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than this.

[0123] Figure 10 is a flowchart of a master data processing method according to Embodiment 3 of the present application. As Figure 10 shown, the method includes the following steps:

[0124] Step S1002, obtaining a data storage request by calling a first interface;

[0125] Among them, the first interface includes a first parameter, and the parameter value of the first parameter is the data storage request, and the data storage request carries the first type of master data.

[0126] The first interface in the above steps can be an interface for data interaction between a cloud server and a client. The client can pass an access request into an interface function as the first parameter of the interface function to achieve the purpose of uploading the data storage request to the cloud server.

[0127] Step S1004, obtain the first metadata corresponding to the data storage request;

[0128] Step S1006, serialize the primary data of the first type based on the first metadata to obtain the first serialized data;

[0129] Step S1008, store the first serialized data into a preset data table to obtain a data storage result;

[0130] Among them, different types of primary data are stored in the preset data table.

[0131] Step S1010, output the data storage result by calling the second interface.

[0132] Among them, the second interface includes a second parameter, and the parameter value of the second parameter is the data storage result.

[0133] The above-mentioned second interface can be an interface for data interaction between the cloud server and the client. The cloud server can pass the data storage result into the interface function as the second parameter of the interface function, so as to achieve the purpose of sending the data storage result to the client.

[0134] Through the above steps, obtain the data storage request by calling the first interface. Among them, the first interface includes a first parameter, and the parameter value of the first parameter is the data storage request, and the data storage request carries the primary data of the first type; obtain the first metadata corresponding to the data storage request; serialize the primary data of the first type based on the first metadata to obtain the first serialized data; store the first serialized data into a preset data table to obtain a data storage result. Among them, different types of primary data are stored in the preset data table; output the data storage result by calling the second interface. Among them, the second interface includes a second parameter, and the parameter value of the second parameter is the data storage result, which improves the efficiency of data processing; it is easy to notice that when storing the primary data, the primary data can be serialized for unified storage of the primary data, and the serialized primary data can be stored in the same data table by constructing metadata, avoiding the need to build separate task tables for different primary data, reducing the storage of underlying tables to improve development efficiency, thereby improving the data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0135] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0136] Embodiment 4

[0137] According to an embodiment of the present application, there is also provided a data processing device for implementing the above-mentioned master data processing method. Figure 11 It is a schematic diagram of a master data processing device according to Embodiment 4 of the present application. As Figure 11 shown, the device 1100 includes: a first acquisition module 1102, a serialization module 1104, and a storage module 1106.

[0138] The first acquisition module 1102 is configured to obtain first metadata corresponding to a data storage request in response to receiving the data storage request, where the data storage request carries master data of a first type.

[0139] The serialization module 1104 serializes the master data of the first type based on the first metadata to obtain first serialized data.

[0140] The storage module 1106 stores the first serialized data in a preset data table.

[0141] It should be noted here that the above-mentioned first acquisition module 1102, serialization module 1104, and storage module 1106 correspond to steps S402 to S406 in Embodiment 1. The instances and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above-mentioned Embodiment 1. It should be noted that the above-mentioned module or unit may be a hardware component or a software component stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n). The above-mentioned module may also be a part of the device and may run in the computer terminal 10 provided in Embodiment 1.

[0142] In the above embodiments of the present application, the first acquisition module is further configured to, in response to a data storage request received by a preset application, parse the data storage request through a service application corresponding to the first type or the preset application to obtain master data of the first type, and call a metadata software toolkit to obtain first metadata corresponding to the first type from multiple metadata, where different metadata correspond to different types of master data.

[0143] In the above embodiments of the present application, the serialization module is further configured to serialize the master data of the first type based on the first metadata through a service application corresponding to the first type or the preset application to obtain first serialized data.

[0144] In the above embodiments of the present application, the storage module is further configured to obtain a first type name and first identification information of the first type, and store the first serialized data, the first identification information, and the first type name in an associated manner in a preset data table.

[0145] In the above embodiments of the present application, the device includes: a deserialization module and a sending module.

[0146] Among them, the first acquisition module is used to acquire the second metadata corresponding to the data access request in response to receiving the data access request, where the data access request is used to access the master data of the second type; the first acquisition module is used to acquire the second serialized data corresponding to the data access request from the preset data table; the deserialization module is used to deserialize the second serialized data based on the second metadata to obtain the master data of the second type; the sending module is used to send the master data of the second type to the client device corresponding to the data access request.

[0147] In the above embodiments of the present application, the first acquisition module is further used to call the metadata software toolkit to acquire the second metadata corresponding to the second type from multiple metadata in response to the preset application receiving the data access request.

[0148] In the above embodiments of the present application, the first acquisition module is further used to acquire the second type name and the second identification information of the second type based on the data access request through the service application or the preset application corresponding to the second type; through the service application or the preset application corresponding to the second type, acquire the serialized data corresponding to the second type name and the second identification information from the preset data table to obtain the second serialized data.

[0149] In the above embodiments of the present application, the deserialization module is used to deserialize the second serialized data based on the second metadata through the service application or the preset application corresponding to the second type to obtain the master data of the second type.

[0150] In the above embodiments of the present application, the device includes: a calling module.

[0151] Among them, the first acquisition module is used to acquire the third metadata corresponding to the metadata configuration instruction in response to receiving the metadata configuration instruction, where the metadata configuration instruction is used to configure the third metadata; the calling module is used to call the metadata software toolkit to store the third metadata.

[0152] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0153] Embodiment 5

[0154] According to an embodiment of the present application, there is also provided a master data processing device for implementing the above master data processing method. Figure 12 It is a schematic diagram of a master data processing device according to Embodiment 5 of the present application, as Figure 12 shown, the device 1200 includes: a first display module 1202 and a second display module 1204.

[0155] Among them, the first display module is used to respond to an input instruction acting on the operation interface and display the first type of master data corresponding to the input instruction on the operation interface; the second display module is used to respond to a data storage instruction acting on the operation interface and display the data storage result corresponding to the data storage instruction on the operation interface, where the data storage result is the result generated by storing the first serialized data corresponding to the first type of master data into a preset data table, and the first serialized data is the data obtained by serializing the first type of master data based on the first metadata corresponding to the first type.

[0156] It should be noted here that the above first display module 1202 and second display module 1204 correspond to steps S902 to S904 in Embodiment 2. The instances and application scenarios implemented by the two modules and the corresponding steps are the same, but are not limited to the content disclosed in the above Embodiment 1. It should be noted that the above modules or units can be hardware components or software components stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n), and the above modules can also be part of a device and can run in the computer terminal 10 provided in Embodiment 1.

[0157] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0158] Embodiment 6

[0159] According to an embodiment of the present application, there is also provided a master data processing device for implementing the above master data processing method. Figure 13 It is a schematic diagram of a master data processing device according to Embodiment 6 of the present application, as Figure 13 shown. The device 1300 includes: a call module 1302, a second acquisition module 1304, a serialization module 1306, a storage module 1308, and an output module 1310.

[0160] Among them, the call module is used to obtain a data storage request by calling a first interface. The first interface includes a first parameter, and the parameter value of the first parameter is the data storage request, and the data storage request carries the first type of master data; the second acquisition module is used to acquire the first metadata corresponding to the data storage request; the serialization module is used to serialize the first type of master data based on the first metadata to obtain the first serialized data; the storage module is used to store the first serialized data into a preset data table to obtain a data storage result; the output module is used to output the data storage result by calling a second interface. The second interface includes a second parameter, and the parameter value of the second parameter is the data storage result.

[0161] It should be noted that the above-mentioned calling module 1302, second obtaining module 1304, serialization module 1306, storage module 1308, and output module 1310 correspond to steps S1002 to S1010 in Embodiment 3. The instances and application scenarios implemented by the five modules and the corresponding steps are the same, but are not limited to the content disclosed in the above-mentioned Embodiment 1. It should be noted that the above-mentioned module or unit can be a hardware component or a software component stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n). The above-mentioned module can also be part of a device and can run in the computer terminal 10 provided in Embodiment 1.

[0162] It should be noted that the preferred implementation schemes involved in the above-mentioned embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0163] Embodiment 7

[0164] According to an embodiment of the present application, there is also provided a system for implementing the above-mentioned master data processing system. Figure 14 It is a structural diagram of a master data processing system according to Embodiment 7 of the present application, as Figure 14 shown. The master data processing system 1400 includes: a preset application 1402, a database 1404, and a service application corresponding to the first type 1406.

[0165] The preset application is used to receive a data storage request, where the data storage request carries master data of the first type; the database is used to store a preset data table, where different types of master data are stored in the preset data table; the service application corresponding to the first type is used to process different types of master data, where it is used to call a metadata software package to obtain first metadata corresponding to the data storage request, serialize the master data of the first type based on the first metadata to obtain first serialized data, and store the first serialized data in the preset data table.

[0166] It should be noted that the preferred implementation schemes involved in the above-mentioned embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0167] Embodiment 8

[0168] According to an embodiment of the present application, a master data processing method is further provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than this.

[0169] Figure 15 FIG. 4 is a flowchart of a master data processing method according to Embodiment 8 of the present application. As Figure 15 shown, the method includes the following steps:

[0170] Step S1502, in response to receiving a data access request, obtain second metadata corresponding to the data access request;

[0171] wherein, the data access request is used to access master data of a second type.

[0172] Step S1504, obtain second serialized data corresponding to the data access request from a preset data table;

[0173] Step S1506, deserialize the second serialized data based on the second metadata to obtain master data of the second type;

[0174] Step S1508, send the master data of the second type to the client device corresponding to the data access request.

[0175] In an alternative embodiment, the second metadata may include information such as the structure, type, and attributes of the second serialized data. The deserialization process uses the metadata to parse the second serialized data and restore the second serialized data back to the form of master data, and the master data of the second type can be sent to the client device that outputs the data access request so that the user can view the master data of the second type on the client device.

[0176] Through the above steps, in response to receiving a data access request, the second metadata corresponding to the data access request is obtained, where the data access request is used to access the master data of the second type; the second serialized data corresponding to the data access request is obtained from a preset data table; the second serialized data is deserialized based on the second metadata to obtain the master data of the second type; and the master data of the second type is sent to the client device corresponding to the data access request, which improves the efficiency of data processing. It is easy to note that when accessing the master data, the second metadata can be deserialized to obtain the master data of the second type. When storing the master data of the second type, the serialized master data can be stored in the same data table by constructing metadata, avoiding the need to construct separate task tables for different master data, reducing the storage of underlying tables to improve development efficiency, thereby improving the data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0177] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0178] Embodiment 9

[0179] According to an embodiment of the present application, there is also provided a master data processing device for implementing the above master data processing method. Figure 16 It is a schematic diagram of a master data processing device according to Embodiment 9 of the present application. As Figure 16 shown, the device 1600 includes: a third acquisition module 1602, a fourth acquisition module 1604, a deserialization module 1606, and a sending module 1608.

[0180] Among them, the third acquisition module is configured to obtain the second metadata corresponding to the data access request in response to receiving the data access request, where the data access request is used to access the master data of the second type; the fourth acquisition module is configured to obtain the second serialized data corresponding to the data access request from a preset data table; the deserialization module is configured to deserialize the second serialized data based on the second metadata to obtain the master data of the second type; and the sending module is configured to send the master data of the second type to the client device corresponding to the data access request.

[0181] It should be noted that the above-mentioned third acquisition module 1602, fourth acquisition module 1604, deserialization module 1606, and sending module 1608 correspond to steps S1502 to S1508 in Embodiment 8. The instances and application scenarios implemented by the four modules and the corresponding steps are the same, but are not limited to the content disclosed in the above-mentioned Embodiment 1. It should be noted that the above-mentioned modules or units can be hardware components or software components stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n). The above-mentioned modules can also be part of a device and can run in the computer terminal 10 provided in Embodiment 1.

[0182] It should be noted that the preferred implementation schemes involved in the above-mentioned embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0183] Embodiment 10

[0184] An embodiment of the present application can provide a computer terminal, and the computer terminal can be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the above-mentioned computer terminal can also be replaced with a terminal device such as a mobile terminal.

[0185] Optionally, in this embodiment, the above-mentioned computer terminal can be located in at least one of multiple network devices in a computer network.

[0186] In this embodiment, the above-mentioned computer terminal can execute program codes of the following steps in the main data processing method: in response to receiving a data storage request, obtain first metadata corresponding to the data storage request, where the data storage request carries first-type main data; serialize the first-type main data based on the first metadata to obtain first serialized data; store the first serialized data in a preset data table, where different types of main data are stored in the preset data table.

[0187] Optionally, Figure 17 is a structural block diagram of a computer terminal according to an embodiment of the present application. As Figure 17 shown, the computer terminal A may include: one or more (only one is shown in the figure) processors 102, a memory 104, a storage controller, and a peripheral interface, where the peripheral interface is connected to a radio frequency module, an audio module, and a display.

[0188] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the main data processing method and device in the embodiments of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, to implement the above-mentioned main data processing method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory may further include a memory remotely set relative to the processor, and these remote memories can be connected to terminal A through a network. Examples of the above network include but are not limited to the Internet, enterprise intranet, local area network, mobile communication network, and their combinations.

[0189] The processor can call the information and application programs stored in the memory through the transmission device to execute the following steps: in response to receiving a data storage request, obtain the first metadata corresponding to the data storage request, where the data storage request carries the main data of the first type; serialize the main data of the first type based on the first metadata to obtain the first serialized data; store the first serialized data in a preset data table.

[0190] Optionally, the above processor can also execute the program code of the following steps: in response to a preset application receiving a data storage request, parse the data storage request through the service application or preset application corresponding to the first type to obtain the main data of the first type; call the metadata software toolkit to obtain the first metadata corresponding to the first type from multiple metadata, where different metadata correspond to different types of main data.

[0191] Optionally, the above processor can also execute the program code of the following steps: serialize the main data of the first type based on the first metadata through the service application or preset application corresponding to the first type to obtain the first serialized data.

[0192] Optionally, the above processor can also execute the program code of the following steps: obtain the first type name and the first identification information of the first type; store the first serialized data, the first identification information, and the first type name in an associated manner in a preset data table.

[0193] Optionally, the above processor can also execute the program code of the following steps: in response to receiving a data access request, obtain the second metadata corresponding to the data access request, where the data access request is used to access the main data of the second type; obtain the second serialized data corresponding to the data access request from the preset data table; deserialize the second serialized data based on the second metadata to obtain the main data of the second type; send the main data of the second type to the client device corresponding to the data access request.

[0194] Optionally, the above-mentioned processor may also execute the program code of the following steps: in response to a data access request received by a preset application, call a metadata software toolkit to obtain second metadata corresponding to a second type from multiple metadata.

[0195] Optionally, the above-mentioned processor may also execute the program code of the following steps: through a service application or a preset application corresponding to the second type, obtain a second type name and second identification information of the second type based on the data access request; through a service application or a preset application corresponding to the second type, obtain serialized data corresponding to the second type name and the second identification information from a preset data table to obtain second serialized data.

[0196] Optionally, the above-mentioned processor may also execute the program code of the following steps: through a service application or a preset application corresponding to the second type, deserialize the second serialized data based on the second metadata to obtain main data of the second type.

[0197] Optionally, the above-mentioned processor may also execute the program code of the following steps: in response to receiving a metadata configuration instruction, obtain third metadata corresponding to the metadata configuration instruction, where the metadata configuration instruction is used to configure the third metadata; call a metadata software toolkit to store the third metadata.

[0198] The processor may call the information and application programs stored in the memory through a transmission device to execute the following steps: in response to an input instruction acting on an operation interface, display main data of a first type corresponding to the input instruction on the operation interface; in response to a data storage instruction acting on the operation interface, display a data storage result corresponding to the data storage instruction on the operation interface, where the data storage result is a result generated by storing first serialized data corresponding to the main data of the first type into a preset data table, and the first serialized data is data obtained by serializing the main data of the first type based on first metadata corresponding to the first type.

[0199] The processor may call the information and application programs stored in the memory through a transmission device to execute the following steps: obtain a data storage request by calling a first interface, where the first interface includes a first parameter, and the parameter value of the first parameter is the data storage request, and the data storage request carries main data of a first type; obtain first metadata corresponding to the data storage request; serialize the main data of the first type based on the first metadata to obtain first serialized data; store the first serialized data into a preset data table to obtain a data storage result; output the data storage result by calling a second interface, where the second interface includes a second parameter, and the parameter value of the second parameter is the data storage result.

[0200] The processor can call the information and application programs stored in the memory through the transmission device to execute the following steps: in response to receiving a data access request, obtain the second metadata corresponding to the data access request, where the data access request is used to access the second type of main data; obtain the second serialized data corresponding to the data access request from the preset data table; deserialize the second serialized data based on the second metadata to obtain the second type of main data; and send the second type of main data to the client device corresponding to the data access request.

[0201] By adopting the embodiment of the present application, in response to receiving a data storage request, obtain the first metadata corresponding to the data storage request, where the first type of main data is carried in the data storage request; serialize the first type of main data based on the first metadata to obtain the first serialized data, and store the first serialized data in the preset data table, which realizes the improvement of data processing efficiency; it is easy to notice that when storing the main data, the main data can be serialized for unified storage, avoiding the need to construct separate task tables for different main data, which can reduce the storage of underlying tables to improve development efficiency, thereby improving data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0202] Those of ordinary skill in the art can understand that Figure 15 The structure shown is only schematic, and the computer terminal can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, and a mobile Internet device (Mobile Internet Devices, MID), a PAD and other terminal devices. Figure 15 It does not limit the structure of the above electronic device. For example, computer terminal A may further include more or fewer components (such as a network interface, a display device, etc.) than those shown Figure 15 in the figure, or have a different configuration from that shown Figure 15 in the figure.

[0203] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium can include: a flash drive, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disc, etc.

[0204] Embodiment 11

[0205] Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the above storage medium may be used to store the program code executed by the main data processing method provided in the first embodiment above.

[0206] Optionally, in this embodiment, the above storage medium may be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.

[0207] Optionally, in this embodiment, the storage medium is set to store program code for performing the following steps: in response to receiving a data storage request, obtain first metadata corresponding to the data storage request, where the data storage request carries first-type main data; serialize the first-type main data based on the first metadata to obtain first serialized data; store the first serialized data in a preset data table.

[0208] Optionally, the above storage medium is also set to store program code for performing the following steps: in response to a preset application receiving a data storage request, parse the data storage request through a service application corresponding to the first type or the preset application to obtain first-type main data; call a metadata software toolkit to obtain first metadata corresponding to the first type from multiple metadata, where different metadata corresponds to different types of main data.

[0209] Optionally, the above storage medium is also set to store program code for performing the following steps: serialize the first-type main data based on the first metadata through a service application corresponding to the first type or the preset application to obtain first serialized data.

[0210] Optionally, the above storage medium is also set to store program code for performing the following steps: obtain the first type name and first identification information of the first type; store the first serialized data, the first identification information, and the first type name in an associated manner in a preset data table.

[0211] Optionally, the above storage medium is also set to store program code for performing the following steps: in response to receiving a data access request, obtain second metadata corresponding to the data access request, where the data access request is used to access second-type main data; obtain second serialized data corresponding to the data access request from a preset data table; deserialize the second serialized data based on the second metadata to obtain second-type main data; send the second-type main data to the client device corresponding to the data access request.

[0212] Optionally, the above storage medium is further configured to store program code for performing the following steps: in response to a data access request received by a preset application, call a metadata software toolkit to obtain second metadata corresponding to a second type from multiple metadata.

[0213] Optionally, the above storage medium is further configured to store program code for performing the following steps: through a service application or a preset application corresponding to the second type, obtain a second type name and second identification information of the second type based on the data access request; through a service application or a preset application corresponding to the second type, obtain serialized data corresponding to the second type name and the second identification information from a preset data table to obtain second serialized data.

[0214] Optionally, the above storage medium is further configured to store program code for performing the following steps: through a service application or a preset application corresponding to the second type, deserialize the second serialized data based on the second metadata to obtain main data of the second type.

[0215] Optionally, the above storage medium is further configured to store program code for performing the following steps: in response to receiving a metadata configuration instruction, obtain third metadata corresponding to the metadata configuration instruction, where the metadata configuration instruction is used to configure the third metadata; call a metadata software toolkit to store the third metadata.

[0216] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: in response to an input instruction acting on an operation interface, display main data of a first type corresponding to the input instruction on the operation interface; in response to a data storage instruction acting on the operation interface, display a data storage result corresponding to the data storage instruction on the operation interface, where the data storage result is a result generated by storing first serialized data corresponding to the main data of the first type into a preset data table, and the first serialized data is data obtained by serializing the main data of the first type based on first metadata corresponding to the first type.

[0217] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: obtain a data storage request by calling a first interface, where the first interface includes a first parameter, and the parameter value of the first parameter is the data storage request, and the data storage request carries main data of a first type; obtain first metadata corresponding to the data storage request; serialize the main data of the first type based on the first metadata to obtain first serialized data; store the first serialized data into a preset data table to obtain a data storage result, where different types of main data are stored in the preset data table; output the data storage result by calling a second interface, where the second interface includes a second parameter, and the parameter value of the second parameter is the data storage result.

[0218] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: in response to receiving a data access request, obtain second metadata corresponding to the data access request, where the data access request is used to access second-type master data; obtain second serialized data corresponding to the data access request from a preset data table; deserialize the second serialized data based on the second metadata to obtain second-type master data; and send the second-type master data to a client device corresponding to the data access request.

[0219] Adopting the embodiment of the present application, in response to receiving a data storage request, obtain first metadata corresponding to the data storage request, where the data storage request carries first-type master data; serialize the first-type master data based on the first metadata to obtain first serialized data, and store the first serialized data in a preset data table, which realizes the improvement of data processing efficiency; it is easy to notice that when storing master data, by serializing the master data for unified storage, it is possible to avoid constructing separate task tables for different master data, reduce the storage of underlying tables to improve development efficiency, thereby improving data processing efficiency, and further solving the technical problem of low data processing efficiency in the related art.

[0220] The serial numbers of the above embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0221] In the above embodiments of the present application, the descriptions of each embodiment have their own emphases. For parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0222] In several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces, and the indirect coupling or communication connection of units or modules can be in an electrical or other form.

[0223] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0224] In addition, in each embodiment of the present application, each functional unit can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0225] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs.

[0226] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A master data processing method, characterized in that: include: In response to receiving a data storage request, obtaining first metadata corresponding to the data storage request, wherein the data storage request carries master data of the first type; Serializing the first type of primary data based on the first metadata to obtain first serialized data; The first serialized data is stored in a preset data table.

2. The method according to claim 1, characterized in that: In response to receiving a data storage request, obtaining first metadata corresponding to the data storage request includes: In response to the preset application receiving the data storage request, the service application corresponding to the first type or the preset application is used to parse the data storage request to obtain the master data of the first type; A metadata software toolkit is called to obtain first metadata corresponding to the first type from multiple metadata.

3. The method according to claim 2, characterized in that Serializing the first type of primary data based on the first metadata to obtain first serialized data includes: The first type of master data is serialized based on the first metadata through the service application corresponding to the first type or the preset application to obtain the first serialized data.

4. The method according to claim 1, characterized in that: Storing the first serialized data in a preset data table includes: Obtain a first type name and first identification information of the first type; The first serialized data, the first identification information and the first type name are associated and stored in the preset data table.

5. The method according to claim 1, characterized in that: The method further comprises: In response to receiving a data access request, obtaining second metadata corresponding to the data access request, wherein the data access request is used to access master data of a second type; Acquire second serialized data corresponding to the data access request from the preset data table; Deserialize the second serialized data based on the second metadata to obtain the second type of primary data; The master data of the second type is sent to the client device corresponding to the data access request.

6. The method according to claim 5, characterized in that In response to receiving a data access request, obtaining second metadata corresponding to the data access request includes: In response to the preset application receiving the data access request, the metadata software toolkit is called to obtain the second metadata corresponding to the second type from multiple metadata.

7. The method according to claim 6, characterized in that Acquiring second serialized data corresponding to the data access request from the preset data table includes: acquiring, through the service application corresponding to the second type or the preset application, a second type name and second identification information of the second type based on the data access request; The second serialized data is obtained by acquiring the second type name and the serialized data corresponding to the second identification information from the preset data table through the service application corresponding to the second type or the preset application, thereby obtaining the second serialized data.

8. The method according to claim 6, characterized in that Deserializing the second serialized data based on the second metadata to obtain the second type of primary data includes: The second serialized data is deserialized based on the second metadata through the service application corresponding to the second type or the preset application to obtain the master data of the second type.

9. The method according to claim 1, characterized in that: The method further comprises: In response to receiving the metadata configuration instruction, acquiring third metadata corresponding to the metadata configuration instruction, wherein the metadata configuration instruction is used to configure the third metadata; The metadata software toolkit is called to store the third metadata.

10. A master data processing method, characterized in that: include: In response to receiving a data access request, obtaining second metadata corresponding to the data access request, wherein the data access request is used to access master data of a second type; Acquire second serialized data corresponding to the data access request from the preset data table; Deserialize the second serialized data based on the second metadata to obtain the second type of primary data; The master data of the second type is sent to the client device corresponding to the data access request.

11. A master data processing method, characterized in that: include: In response to an input instruction acting on an operation interface, displaying on the operation interface the master data of the first type corresponding to the input instruction; In response to a data storage instruction applied on the operation interface, a data storage result corresponding to the data storage instruction is displayed on the operation interface, wherein the data storage result is a result generated by storing first serialized data corresponding to the first type of master data in a preset data table, and the first serialized data is data obtained by serializing the first type of master data based on first metadata corresponding to the first type.

12. A master data processing method, characterized in that: include: Acquire a data storage request by calling a first interface, wherein the first interface includes a first parameter, a parameter value of the first parameter is the data storage request, and the data storage request carries master data of the first type; Acquire first metadata corresponding to the data storage request; Serializing the first type of primary data based on the first metadata to obtain first serialized data; The first serialized data is stored in a preset data table to obtain a data storage result; The data storage result is output by calling a second interface, wherein the second interface includes a second parameter, and a parameter value of the second parameter is the data storage result.

13. A master data processing system, characterized in that: include: A preset application, used to receive a data storage request, wherein the data storage request carries master data of the first type; A database, used to store preset data tables; A plurality of service applications corresponding to different types are used to process the different types of master data, wherein the service application corresponding to the first type or the preset application is used to call a metadata software package to obtain first metadata corresponding to the data storage request, serialize the first type of master data based on the first metadata to obtain first serialized data, and store the first serialized data in the preset data table.

14. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 12 when running.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the storage medium is located is controlled to execute the method according to any one of claims 1 to 12.

Images