Data processing method and device and cluster

By storing business data on the horizontal table and combining the reserved fields of the business meaning record table, the problems of poor user experience and large storage resource occupation after the expansion of the existing event model are solved, and efficient data query and user-friendly interface are realized.

CN119003514APending Publication Date: 2024-11-22HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310796799.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2023-06-30
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing event model is not user friendly after expansion, and business data records occupy a lot of storage resources, poor data readability, making it difficult to adapt to business data recording needs of different matters.

Method used

The horizontal table is used to store business data and combine the business meaning record table to associate the business meanings in different scenarios through reserved fields to ensure data query efficiency and storage resources savings. At the same time, the business meaning is intuitively displayed in the user interface and improve user experience.

Benefits of technology

It realizes the readability of business data and the saving of storage resources when expanding the event model, and improves the convenience of user interface and data query efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003514A_ABST
    Figure CN119003514A_ABST
Patent Text Reader

Abstract

A method, device and cluster for processing data by using an event model can be applied to the technical field of computers. The method comprises the following steps: receiving a first service meaning in a first scene; recording the first service meaning and a first scene associated with the first service meaning in a service meaning record table; associating the first service meaning with the first reserved field; and displaying the first business meaning at the position of the first reserved field in the user interface in the first scene based on the business meaning record table. According to the method, when the event model is expanded to a new service scene, the readability of service data can be ensured, the occupied storage resources are less, and a user can conveniently process related services.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device and cluster. Background Art

[0002] Government affairs processing, mine monitoring and other businesses require the processing of many matters. Usually, the matter processing is associated with an event model, which is used to process matters, such as recording business data, verifying business data, etc. Among them, the processing process of a matter instance can be called an event, and the event model defines the recording, reading, displaying and other methods of the event's business data and the flow of business data.

[0003] Different matters in the same field need to record different business data. In particular, after the event model is launched, new matters that need to be processed with the help of the event model may appear. Therefore, the event model needs to be expanded to adapt to different matters and record the business data of different matters. After the expansion, the current event model is not user-friendly, resulting in inconvenience for users; or, the business data records of the event model occupy a lot of storage resources, and the readability of the business data is poor. Summary of the invention

[0004] The present application provides a method, device and cluster for processing data using an event model. When the event model is extended to a new business scenario, it can ensure the readability of business data, reduce the storage resource usage, and facilitate users to process related business.

[0005] In a first aspect, a method for processing data using an event model is provided, wherein the event model includes a data recording table and a business meaning recording table, wherein the data recording table is a horizontal table for storing business data, and a header of the data recording table includes a first reserved field, and the business meaning recording table is used to record business meanings in different scenarios; the method includes: receiving a first business meaning in a first scenario; recording the first business meaning and a first scenario associated with the first business meaning in the business meaning recording table; associating the first business meaning with the first reserved field; and based on the business meaning recording table, displaying the first business meaning at the position of the first reserved field in a user interface in the first scenario.

[0006] The first scenario may be a business scenario, wherein the business meaning under the first scenario refers to the business meaning set by the user and corresponding to the first scenario.

[0007] In this method, business data is stored in a horizontal table so that all data corresponding to the same identity (ID) can be recorded in the same row, which ensures data query efficiency, readability and maintainability. In addition, the data under one ID only occupies one row, which takes up less storage resources and saves storage resources.

[0008] While using a data record table implemented in the form of a horizontal table to store business data, a business meaning record table is used to record the business meaning of the business scenario and the business scenario associated with the business meaning; and the business meaning is associated with the reserved field in the table header. Therefore, whenever the event model is extended to a new business scenario, the business meaning record table can be used to record the business meaning under the new business scenario and the business scenario associated with the business meaning (i.e., the new business scenario); and the business meaning is associated with the reserved field in the table header. In this way, when the data record table needs to be used in a certain business scenario, for example, when it needs to be used in the aforementioned new business scenario, the business meaning under the new business scenario can be obtained based on the business meaning record table, and then the business meaning can be displayed at the position of the reserved field associated with the business meaning in the user interface under the new business scenario. Therefore, when the user uses the user interface to perform business under the business scenario, the business meaning of the reserved field under the business scenario can be intuitively understood, which is convenient for the user to perform business and improves the user experience.

[0009] In one possible implementation, the business meaning record table is a vertical table, and the header of the data record table also includes a second reserved field; the method also includes: receiving a second business meaning in a first scenario; recording the second business meaning and the first scenario associated with the second business meaning in the business meaning record table, the second business meaning and the first business meaning are located in different rows in the business meaning record table; associating the second business meaning with the second reserved field; based on the business meaning record table, displaying the second business meaning at the position of the second reserved field on the user interface in the first scenario.

[0010] In this implementation, the business meaning record table can be a vertical table. In this way, when multiple business meanings need to be set for a certain business scenario, different business meanings can be recorded by adding rows in the business meaning record table, that is, different business meanings are recorded in different rows. By adding rows to record business meanings, there is no need to destroy the structure of the business meaning record table, which facilitates the management and maintenance of the business meaning record table. And the business meaning record table records business meanings, not business data. It can be understood that compared with business data, the number of business meanings is small. Therefore, using a vertical table in the business meaning record table will not consume too many storage resources.

[0011] In one possible implementation, the business meaning record table is a vertical table; the method also includes: receiving a third business meaning under a second scenario; recording the third business meaning and the second scenario associated with the third business meaning in the business meaning record table, the third business meaning and the first business meaning are located in different rows in the business meaning record table; associating the third business meaning with the first reserved field; based on the business meaning record table, displaying the third business meaning at the position of the first reserved field on the user interface under the second scenario.

[0012] In this implementation, the business meaning record table can be a vertical table. In this way, when it is necessary to set the business meaning for a new business scenario, the business meaning under the new business scenario can be recorded by adding rows in the business meaning record table, that is, the business meanings of different business scenarios are recorded in different rows. By adding rows, the business meaning of the new business scenario can be recorded without destroying the structure of the business meaning record table, which facilitates the management and maintenance of the business meaning record table. And the business meaning record table records the business meaning, not the business data. It can be understood that compared with the business data, the amount of business meaning data is small. Therefore, using a vertical table in the business meaning record table will not consume too many storage resources.

[0013] In a possible implementation, recording the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table includes: recording a scenario identifier of the first scenario in a row where the first business meaning is located in the business meaning recording table.

[0014] In this implementation, the scenario identifier and the business meaning of the scenario are recorded in the same row of the business meaning record table, so that the scenario and the business meaning are associated, and the association relationship between the business meaning and the business scenario is recorded in the business meaning record table.

[0015] In one possible implementation, the business meaning record table records a fourth business meaning and a third scenario associated with the fourth business meaning; wherein the first scenario is a subset of the third scenario, and the header of the data record table also includes a third reserved field associated with the fourth business meaning; the method also includes: based on the business meaning record table, in the user interface under the first scenario, displaying the fourth business meaning at the position of the third reserved field.

[0016] In this implementation, when generating a user interface for a business scenario, the business meaning of the business scenario under the previous level business scenario can be displayed on the user interface, thereby realizing the sharing of business meaning, saving the setting operation of business meaning, and facilitating the expansion operation of the event model.

[0017] In a possible implementation, the third scene is represented by scene attribute information of a first dimension, and the first scene is represented by both the scene attribute information of the first dimension and the scene attribute information of the second dimension.

[0018] In a second aspect, a device for processing data using an event model is provided, wherein the event model includes a data recording table and a business meaning recording table, wherein the data recording table is a horizontal table for storing business data, and the table header of the data recording table includes a first reserved field, and the business meaning recording table is used to record business meanings in different scenarios; the device includes: a receiving module, used to receive a first business meaning in a first scenario; a recording module, used to record the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table; an associating module, used to associate the first business meaning with the first reserved field; and a display module, used to display the first business meaning at the position of the first reserved field in a user interface in the first scenario based on the business meaning recording table.

[0019] In one possible implementation, the business meaning record table is a vertical table, and the header of the data record table also includes a second reserved field; the receiving module is also used to receive the second business meaning under the first scenario; the recording module is also used to record the second business meaning and the first scenario associated with the second business meaning in the business meaning record table, and the second business meaning and the first business meaning are located in different rows in the business meaning record table; the association module is also used to associate the second business meaning with the second reserved field; the display module is also used to display the second business meaning at the position of the second reserved field on the user interface under the first scenario based on the business meaning record table.

[0020] In one possible implementation, the business meaning record table is a vertical table; the receiving module is also used to receive the third business meaning under the second scenario; the recording module is also used to record the third business meaning and the second scenario associated with the third business meaning in the business meaning record table, and the third business meaning and the first business meaning are located in different rows in the business meaning record table; the association module is also used to associate the third business meaning with the first reserved field; the display module is also used to display the third business meaning at the position of the first reserved field on the user interface under the second scenario based on the business meaning record table.

[0021] In a possible implementation manner, the recording module is further configured to record a scenario identifier of the first scenario in a row where the first business meaning is located in the business meaning recording table.

[0022] In one possible implementation, the business meaning record table records a fourth business meaning and a third scenario associated with the fourth business meaning; wherein the first scenario is a subset of the third scenario, and the header of the data record table also includes a third reserved field associated with the fourth business meaning; the display module is also used to display the fourth business meaning at the position of the third reserved field in the user interface under the first scenario based on the business meaning record table.

[0023] In a possible implementation, the third scene is represented by scene attribute information of a first dimension, and the first scene is represented by both the scene attribute information of the first dimension and the scene attribute information of the second dimension.

[0024] In a third aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the method provided in the first aspect.

[0025] In a fourth aspect, a computer-readable storage medium is provided, comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method provided in the first aspect.

[0026] In a fifth aspect, a computer program product comprising instructions is provided. When the instructions are executed by a computer device cluster, the computer device cluster executes the method provided in the first aspect.

[0027] The beneficial effects of the second to fifth aspects can be referred to the above introduction to the beneficial effects of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1A A schematic diagram of a horizontal table involved in an embodiment of the present application;

[0029] Figure 1B A schematic diagram of an event interface involved in an embodiment of the present application;

[0030] Figure 2 A schematic diagram of a longitudinal table involved in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of an event model provided in an embodiment of the present application;

[0032] Figure 4A A schematic diagram of a data recording table provided in an embodiment of the present application;

[0033] Figure 4B A schematic diagram of another data recording table provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of a scene recording table provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of a business meaning record table provided in an embodiment of the present application;

[0036] Figure 7 A schematic diagram of an event logic model interface provided in an embodiment of the present application;

[0037] Figure 8 A schematic diagram of an association relationship table provided in an embodiment of the present application;

[0038] Fig. 9 A schematic diagram of the structure of a computing system provided in an embodiment of the present application;

[0039] Fig.10 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0040] Fig.11 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0041] Fig.12 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0042] Fig.13 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0043] Fig.14 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0044] Fig.15 One of the flowcharts of a data processing method provided in an embodiment of the present application;

[0045] Fig.16 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0046] Fig.17 A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0047] Fig.18 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0048] Fig.19 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following will describe the solution provided by the embodiment of the present application in conjunction with the accompanying drawings. In the embodiment of the present application, "multiple" refers to two or more than two.

[0050] To facilitate understanding of the solutions of the embodiments of the present application, the technical terms involved in this document are first explained below.

[0051] Matter: A business process with a specific processing procedure. An issue can be understood as a specific business, such as traffic violation handling, driver's license processing, and birth certificate processing.

[0052] Event: A specific instance of a matter. A specific matter can be called an event.

[0053] Scenario attribute information: information used to characterize or describe business scenarios. Business scenarios can be defined through scenario attribute information.

[0054] Event interface: an interface used to access the data record table. The event interface can be used to read the data recorded in the data record table, such as reading the table header and the field values ​​of the cell records under the table header.

[0055] With the development of computer technology, many matters in government affairs have been transferred online for processing. Whenever the processing of a matter is transferred online, the online event model needs to be expanded online so that the event model can be used for the matter.

[0056] The event model associated with the event records the business data in the data table of the database (data base), and reads the business data from the data table when the business data is needed. One of the difficulties in online expansion of the event model is to enable the data table of the event model to record the business data of events under different events.

[0057] In one solution, the data table used by the event model is a horizontal table. In the horizontal table, all data corresponding to the same ID are recorded in the same row, that is, all values ​​of a key are recorded in the same row of the same data table. In an example, Figure 1A As shown, the header of the data table includes ID, name, submitter, submission event, and multiple reserved fields. Each header is located at the top of a column and is used to indicate the business meaning of the business data recorded in the column. The business data recorded in the same row belongs to the same ID and the same event instance.

[0058] In addition, the reserved fields are used to record business data with different business meanings under different matters to achieve the expansion of the event model.

[0059] like Figure 1BAs shown, the event interface for accessing the data table directly reads each header when accessing the data table, that is, the header of the ID read is the ID, the header of the reserved field read is the reserved field, .... The header of the reserved field has no business meaning, which makes it impossible for users to identify what kind of business data the column corresponding to the reserved field is used to store or what kind of business meaning the business data read from the column corresponding to the reserved field has. Although in this scheme, the administrator of the event model can record the business meaning of the reserved fields under different matters, when using the data table, the user needs to find the business meaning represented by a reserved field according to the information recorded by the administrator, which is inconvenient to use and has a poor user experience. Among them, the administrator can also be called the user, which refers to the party that manages the event model (for example, defines or interprets the business meaning of the reserved field, etc.). Taking government affairs processing as an example, the user is specifically the government affairs management personnel.

[0060] In another solution, the data table used by the event model is a vertical table. In the vertical table, each row records only one piece of data, that is, one value of a key occupies one row, and multiple values ​​occupy multiple rows. In an example, Figure 2 As shown, for an event under the birth certificate application, different data occupy different rows, for example, the name occupies one row, the gender occupies another row, and the birthday occupies another row.

[0061] Although the vertical table is easy to expand the event model, since one piece of data occupies one row, the data volume of the data table is very large, occupying a lot of storage resources. In addition, since different data with the same ID are located in different rows, the data query efficiency, readability and maintainability are low.

[0062] The embodiment of the present application provides a method for data processing using an event model including a data record table and a business meaning record table. In this method, the data record table is a horizontal table for storing business data. Using a horizontal table to store business data means that all data records corresponding to the same ID are in the same row, which ensures data query efficiency, readability and maintainability, and does not require excessive storage resources. The business meaning record table is used to record the business meaning of the header of the data record table in different business scenarios. Whenever the event model needs to be extended to a new business scenario, the business meaning under the new business scenario is recorded in the business meaning record table, as well as the business scenario associated with the business meaning (that is, the association relationship or mapping relationship between the business meaning and the new business scenario is recorded). The business meaning is also associated with the reserved field in the header of the data record table, that is, the association relationship between the business meaning and the reserved field is established. When the data record table needs to be used in a certain business scenario, the business meaning under the business scenario can be obtained based on the business meaning record table. Then, when generating the user interface under the business scenario, the business meaning can be displayed at the position of the reserved field associated with the business meaning in the business interface, so that the user can intuitively see the business meaning of the reserved field in the corresponding business scenario on the user interface, thereby improving the user experience.

[0063] In addition, the business meaning record table can be implemented as a vertical table. Whenever the event model needs to be expanded to a new business scenario, a new row can be added to the business meaning record table. The business meaning of the table header under the new business scenario and the business scenario associated with the business meaning can be recorded in the new row, so that the event model can be expanded to multiple business scenarios. In other words, the event model can be expanded to multiple business scenarios by adding rows. This expansion method does not need to destroy the structure of the table, which facilitates the management of the table. In addition, the business meaning record table records the business meaning of the table header of the horizontal table, and there is no need to record business data. Therefore, the business meaning record table records a small amount of data, does not consume more storage resources, and is also convenient for data query.

[0064] Next, the data processing method provided in the embodiment of the present application is described.

[0065] In the embodiment of the present application, the business scenario can be characterized or described by scenario attribute information.

[0066] In some embodiments, the business scenario can be represented by single-dimensional scenario attribute information. For example, the field can be used as single-dimensional scenario attribute information to represent the business scenario. For example, the field includes the traffic management field to be introduced below.

[0067] Business scenarios can also be represented by multi-dimensional scenario attribute information. For example, if the domain and the matter are two-dimensional scenario attribute information, the business scenario can be represented by the multi-dimensional scenario attribute information composed of the domain and the matter. Among them, the matter can be a sub-dimension of the domain, that is, the matter is specifically a matter under the domain. Correspondingly, the multi-dimensional scenario attribute information composed of the domain and the matter represents that the business scenario is a business scenario for carrying out the matter under the domain. For example, the domain includes the traffic management domain, etc. The matters include violation handling matters, driver's license application matters, etc. Among them, violation handling matters and driver's license application matters are two matters under the traffic management domain. The traffic management domain and driver's license application matters can jointly represent the driver's license application business scenario. The traffic management domain and violation handling matters can jointly represent the violation handling business scenario.

[0068] Among them, the business scenario represented by the multi-dimensional scenario attribute information can be a subset of the business scenario represented by a single dimension. That is, business scenarios can have levels, that is, one business scenario can be a subset of another business scenario. Specifically, when the multi-dimensional scenario attribute information includes a single-dimensional scenario attribute information, the business scenario represented by the multi-dimensional scenario attribute information is a subset of the business scenario represented by the single-dimensional information. Specifically, the business scenario represented by the multi-dimensional scenario attribute information composed of fields and matters is a subset of the business scenario represented by the field.

[0069] Taking government affairs processing as an example, government affairs processing can be divided into different fields, such as traffic management field, population management field, business administration field, etc. The traffic management field, population management field, and business administration field can represent different business scenarios respectively.

[0070] Among them, there can be multiple matters under one field. For example, there are violation handling matters and driver's license handling matters under the traffic management field. Among them, combined with traffic management, violation handling matters and driver's license handling matters can represent different business scenarios respectively. Specifically, the traffic management field represents the business scenario of traffic management. The traffic management field and violation handling matters jointly represent the business scenario of violation handling. The traffic management field and driver's license handling matters jointly represent the business scenario of driver's license handling. The business scenario of traffic management is the superior business scenario of driver's license handling and the business scenario of violation handling. It can also be said that the business scenario of driver's license handling and the business scenario of violation handling are sub-scenarios of the business scenario of traffic management.

[0071] For another example, under the population management domain, there are birth certificate processing matters, household registration transfer matters, etc. Among them, the population management domain represents the business scenario of population management. The population management domain and birth certificate processing matters jointly represent the business scenario of birth certificate processing. The population management domain and household registration transfer matters jointly represent the business scenario of household registration transfer. Among them, the business scenario of population management is the superior business scenario of the business scenario of birth certificate processing and the business scenario of household registration transfer. It can also be said that the business scenario of birth certificate processing and the business scenario of household registration transfer are sub-scenarios of the business scenario of population management.

[0072] Taking mine monitoring as an example, mine monitoring can be divided into the aboveground monitoring field and the underground monitoring field. The aboveground monitoring field and the underground monitoring field can represent different business scenarios respectively. Under the underground monitoring field, there are gas monitoring items, temperature monitoring items, water level monitoring items, etc. Combined with the underground monitoring field, gas monitoring items, temperature monitoring items, and water level monitoring items can represent different business scenarios respectively. For example, the underground monitoring field represents the business scenario of underground monitoring, and the underground monitoring field and gas monitoring items jointly represent the business scenario of gas monitoring. The business scenario of underground monitoring is the superior business scenario of the gas monitoring scenario.

[0073] In addition, in the embodiments of the present application, the business scenario can be simply referred to as the scenario.

[0074] This embodiment of the application provides an event model 100. Figure 3 As shown, the event model 100 includes an event physical model 110 and an event logic model 120. The event physical model 110 can be implemented as a data record table 110. The event logic model 120 can include a business meaning record table 121. The data record table 110 can be a horizontal table in a database. In some embodiments, the business meaning record table 121 can be a vertical table in a database. In some embodiments, the business meaning record table 121 can be implemented as a horizontal table in a database. That is, the data record table 110 and the business meaning record table 121 are managed in a manner that a database manages data.

[0075] The data recording table 110 is used to record business data in business scenarios. Figure 4A An example of a data record table 110 is shown. Figure 4AAs shown, the header of the data record table 110 can be divided into a fixed header and a reserved header. Among them, the fixed header is also called a fixed field, such as ID, name, submitter, submission time, etc., and their business meaning is fixed, that is, in different business scenarios, their business meaning remains unchanged. The reserved header is also called a reserved field, such as reserved field 1, reserved field 2, reserved field 3, reserved field 4, etc. The business meaning of them in the business scenario can be defined by the user, so their business meaning in different business scenarios may be different.

[0076] In the following description, when not specifically stated, the reserved field refers to the reserved field in the header of the data record table 110 .

[0077] The reserved fields in the header of the data record table 110 can be divided into scene attribute information of at least one dimension. When the at least one dimension is multiple dimensions, the scene attribute information of each dimension corresponds to at least one reserved field, and different reserved fields correspond to scene attribute information of different dimensions. The reserved field corresponding to the scene attribute information of a certain dimension can be called the reserved field of the dimension. Among them, the multiple dimensions are hierarchical, and the upper dimension includes the lower dimension, that is, the lower dimension is a subset of the upper dimension. Figure 4B Another example of a data log table 110 is shown. Figure 4B As shown, the reserved fields in the header of the data record table 110 can be set to be divided into the scene attribute information of the first-level dimension (such as field) and the second-level dimension (such as matter), and the scene attribute information of each dimension corresponds to multiple reserved fields. For example, the scene attribute information of the first-level dimension corresponds to reserved field 11, reserved field 12, reserved field 13, and reserved field 14, and the scene attribute information of the second-level dimension corresponds to reserved field 21, reserved field 22, reserved field 23, and reserved field 24. Among them, the reserved fields corresponding to the scene attribute information of the first-level dimension can be called the reserved fields of the first-level dimension, and the reserved fields corresponding to the scene attribute information of the second-level dimension can be called the reserved fields of the second-level dimension. Among them, the scene attribute information of the first-level dimension can represent a business scenario alone. The scene attribute information of the second-level dimension needs to be combined with the first-level dimension information to represent a business scenario. In other words, the scene attribute information of the second dimension and the scene attribute of the first dimension jointly represent a business scenario.

[0078] In addition, the business meaning of a field can also be referred to as the field value of the field. For a fixed field, the name of the fixed field itself represents or indicates the business meaning of the field, that is, the name of the fixed field can be used as the field value of the fixed field.

[0079] Each header corresponds to a column, and the column corresponding to the header is used to record business data. The header is used to indicate the business meaning of the business data recorded in the column corresponding to the header. Among them, the business data recorded in the column corresponding to the header can be called the field value under the header. The business meaning of the field as the header is the business meaning of the field value recorded in the column corresponding to the header. In other words, the header indicates what kind of data the field value recorded in the column corresponding to the header is. For example, if the field value of the header is the ID number, then the field value recorded in the column corresponding to the header is the ID number, and the field value recorded in a cell in the column is an ID number instance, that is, a specific ID number.

[0080] In some embodiments, the event logic model 120 may include a scenario record table 122. The scenario record table 122 is also called the event logic model definition table 122, which is used to record the metadata of the business meaning record table 121 and the metadata of the scenario. The metadata of the business meaning record table 121 refers to the data used to describe the business meaning record table 121 or the data to be queried or indexed in the business meaning record table 121, such as the scenario identifier of the business scenario, the scenario identifier of the parent business scenario of the business scenario, etc. The parent business scenario of the business scenario refers to another business scenario that contains the business scenario. That is, the business scenario is a subset of the parent business scenario of the business scenario. The subset of the business scenario can also be called a sub-business scenario of the business scenario. The metadata of the scene refers to the data used to characterize the scene, that is, the scene attribute information.

[0081] The scenario attribute information of the business scenario and the scenario identifier of the business scenario can be associated through the event logic model definition table 122. That is to say, the user can query the scenario identifier of the business scenario in the event logic model definition table 122 through the scenario attribute information of the business scenario, and then can query the business meaning of the reserved field under the business scenario in the business meaning record table 121 based on the scenario identifier of the business scenario.

[0082] Exemplarily, the event logic model definition table 122 also includes the business meaning of the fixed fields in the header of the data record table 110 , that is, the field value or name of the fixed field.

[0083] In one example, the event logic model definition table 122 may be implemented as a vertical table. In another example, the event logic model definition table 122 may also be implemented as a horizontal table.

[0084] In an example, Figure 5As shown, the header of the event logic model definition table 122 may include a scenario identifier and a value of at least one dimension. The column corresponding to the scenario identifier is used to record the scenario identifier of the business scenario, and the column corresponding to the value of the dimension is used to record the scenario attribute information of the dimension. For example, the at least one dimension includes a first-level dimension (e.g., a field) and a second-level dimension (e.g., an event), and the column corresponding to the value of the first-level dimension is used to record the scenario attribute information of the first dimension, and the column corresponding to the value of the second-level dimension is used to record the scenario attribute information of the second dimension.

[0085] Exemplarily, the header of the event logic model definition table 122 also includes the scene identifier of the parent scene. The business scenario identified by the scene identifier in the same row as the scene identifier of the parent scene is a subset of the parent scene. For example, the business scenario identified by Aa100 is a subset of the business scenario identified by A1000. In addition, some scenes do not have a parent scene, that is, the scene does not belong to a subset of any scene, then in the row where the scene identifier of the scene is located, the cell with the scene identifier of the parent scene in the table header is empty.

[0086] Exemplarily, the table header of the event logic model definition table 122 also includes a scenario name, where the scenario name refers to the name of the business scenario identified by the scenario identifier in the same row as the scenario name.

[0087] Exemplarily, the header of the event logic model definition table 122 also includes the business meaning of the fixed fields of the data record table 110, such as the business meaning of the event ID, the business meaning of the event name, the business meaning of the submitter, the business meaning of the submission time, etc. Among them, the business meaning of the fixed fields in different business scenarios is the same, so the field values ​​recorded in the corresponding columns of the business meaning of the fixed fields of the event logic model definition table 122 are the same. Among them, the event ID can be referred to as ID, and the event name can be referred to as name.

[0088] The business meaning record table 121 in the event logic model 120 may be referred to as an event logic model field table 121 , which is used to explain the business meaning of the header of the data record table 110 in a business scenario.

[0089] In some embodiments, Figure 6As shown, the business meaning record table 121 can be implemented as a vertical table, and the header of the business meaning record table 121 can include a scenario identification field and a business meaning field. Among them, the column corresponding to the scenario identification field is used to record the scenario identification of the business scenario, and the column corresponding to the business meaning field is used to record the business meaning under different business scenarios, and the business meaning can be associated with the reserved field of the data record table 110. Among them, the business meaning in the same row as a certain scenario identification refers to the business meaning under the business scenario identified by the scenario identification. For example, the business scenario identified by A1000 is population management. In the column corresponding to the business meaning field, the field value recorded in the cell in the same row as A1000 is native place, which means that the native place recorded in the cell is the business meaning under the scenario of population management.

[0090] In some embodiments, the header of the business meaning record table 121 may also include a field attribute field. The field attribute is used to restrict or explain the value of the reserved field, such as limiting the type and length of the value of the field. For another example, it indicates whether the value of the field must be filled in, the specific meaning, etc.

[0091] Specifically, field attributes include any one or more combinations of field type, field length, whether a field is required, field description, etc.

[0092] The field type is used to record or restrict the field type of the value of the corresponding reserved field. For example, if the business meaning is place of origin, the reserved field associated with the business meaning should be text. For another example, if the business meaning is date of birth, the value of the reserved field associated with the business meaning should be a number.

[0093] The value of the reserved field refers to the field value recorded in the column corresponding to the reserved field in the data record table 110 .

[0094] The field length is used to record or limit the length of the value of the reserved field associated with the corresponding business meaning. For example, the value of the reserved field shall not exceed 256 characters.

[0095] Required is used to record or restrict whether the value of the reserved field associated with the corresponding business meaning is a required item.

[0096] The field description is used to further explain the filling requirements of the reserved field value associated with the corresponding business meaning. For example, if the business meaning is native place, the field description can be "fill in to the county-level administrative division".

[0097] In some embodiments, the event model 100 further includes an event logic interface for accessing the event logic model 120. Through the event logic interface, the event logic model 120 can be accessed to obtain the business meaning of the reserved fields of the data record table 110 in a certain business scenario.

[0098] In one example, the event logic interface can be as follows Figure 7 As shown, it includes an interface for accessing the business meaning of fixed fields such as ID, name, submitter, submission time, time status, etc., and scene attribute information for accessing the business meaning of reserved fields. As mentioned above, the scene attribute information is used to characterize the business scenario. Inputting the scene attribute information in the event logic model interface indicates that the event physical model 110 needs to be used in the business scenario represented by the scene attribute information. Then, the business meaning of the reserved field in the business scenario can be queried in the event logic model 120.

[0099] In some embodiments, the business meaning and the reserved field can be associated through a table. Specifically, Figure 3 As shown, the event model 100 may further include an association table 130. The association table 130 may be referred to as an association table of business meanings and reserved fields, and is used to record reserved fields associated with business meanings in a certain scenario, that is, to record the association between business scenarios, reserved fields, and business meanings. In this way, when the data recording table 110 needs to be used in a certain business scenario, the reserved fields associated with the business meaning may be obtained based on the association, the business scenario, and the business meaning.

[0100] In one example of this embodiment, the association table 130 may be implemented as a data table. Figure 8 As shown, the header of the association table 130 may include a scenario identifier, a business meaning, and a reserved field. Among them, the column corresponding to the scenario identifier is used to record the business identifier of the business scenario, the column corresponding to the business meaning is used to record the business meaning under the corresponding business scenario, and the column corresponding to the reserved field is used to record the reserved field in the event physical model 110. The scenario identifier, business meaning, and reserved field of the business scenario with an associated relationship may be recorded in the same row, that is, the scenario identifier, business meaning, and reserved field in the same row in the association table 130 have an associated relationship.

[0101] In some embodiments, the business meaning and the reserved field may be associated in other ways, such as by associating the business meaning and the reserved field through a data structure, etc. The embodiments of the present application do not limit the meaning of associating the business meaning and the reserved field.

[0102] The above example introduces the implementation of the event model 100. Next, in conjunction with the event model 100, the data processing method provided by the embodiment of the present application is introduced.

[0103] The data processing method provided in the embodiments of the present application can be executed by any device, equipment, cluster or platform with data processing capabilities.

[0104] In some embodiments, the data processing method provided in the embodiments of the present application may be executed by the computing system 900. Fig. 9 As shown, the computing system 900 may include a service management device 910 , a data entry device 920 , and a data viewing device 930 .

[0105] The business management device 910 is used to record the business meanings in different business scenarios in the business meaning record table 121 (i.e., record the business meanings and the business scenarios associated with the business meanings), and associate the business meanings in the business scenarios with the reserved fields in the header of the data record table 110. The business management device 910 can also generate user interfaces in different business scenarios based on the business meaning record table 121 and the header of the data record table 110. In the generated user interface in the business scenario, the business meaning in the business scenario is displayed at the position of the reserved field associated with the business meaning.

[0106] The user interface may include a data entry interface. The data entry device 920 is used to display the data entry interface and input business data through the user interface. The input business data may be recorded in the data recording table 110.

[0107] The user interface may include a data viewing interface. The data viewing device 920 is used to display the data viewing interface and display the business data on the data viewing interface to facilitate users to view the business data.

[0108] For different businesses, the business management device 910, the data entry device 920, and the data viewing device 930 have different forms of expression. For example, for a business handled by government affairs, the business management device 910 can be a government affairs implementation management platform, the data entry device 920 can be a matter reporting terminal, and the data viewing device 920 can be an event approval terminal.

[0109] In some embodiments, the business management device 910, the data entry device 920, or the data viewing device 930 may be implemented in hardware, such as a server. In some embodiments, the business management device 910, the data entry device 920, or the data viewing device 930 may be implemented in software, such as a virtual machine (VM) or a container. The embodiments of the present application do not specifically limit the specific implementation of the business management device 910, the data entry device 920, or the data viewing device 930.

[0110] Next, combine Fig.10 , introduces the execution flow of the data processing method provided in the embodiment of the present application.

[0111] like Fig.10As shown, the administrator can input the scenario attribute information of the business scenario A1 to the business management device 910 through step 1001. That is, the business scenario represented by the scenario attribute information input in step 1001 is business scenario A1. For example, the scenario attribute information input by the administrator in step 1001 is population management and birth certificate, and the business scenario represented by the scenario attribute information is birth certificate processing, that is, business scenario A1 is birth certificate processing.

[0112] The scenario attribute information of the business scenario A1 is used to instruct the business management device 910 to create the business scenario A1. The administrator inputting the scenario attribute information of the business scenario A1 to the business management device 910 can also be referred to as: the administrator sending an operation for creating the business scenario A1 to the business management device 910.

[0113] When the business management device 910 receives the scene attribute information of the business scenario A1, that is, when the operation for creating the business scenario A1 is received, the business management device 910 can execute step 1002 to generate a scene identifier for the business scenario A1. The business management device 910 receives the scene attribute information of the business scenario A1, which can trigger the business management device 910 to generate a scene identifier for the business scenario (that is, the business scenario A1) represented by the scene attribute information. In other words, the business management device 910 generates a scene identifier for the business scenario A1 in response to the operation for creating the business scenario A1.

[0114] The scenario identifier is unique, that is, the scenario identifiers of different business scenarios are different, and the business scenario can be identified by the scenario identifier. In one example, the scenario identifier can be a set number, which can be composed of numbers and / or letters. For example, Aa100 is the scenario identifier of the business scenario of applying for a birth certificate.

[0115] In step 1002, the scene attribute information of business scene A1 and the scene identifier of business scene A1 can also be recorded in the same row of the scene record table 122 to store the correspondence between the scene identifier of business scene A1 and the scene attribute information of business scene A1. For example, business scene A1 can be set as birth certificate application, the scene attribute information of business scene A1 is population management and birth certificate, and the scene identifier of business scene A1 is Aa100. Figure 5 As shown, Aa100 is recorded in the same row of the event logic model definition table 122 as the population management and birth certificate records.

[0116] In some embodiments, see Fig.11Before executing step 1002, the business management device 910 may also execute step 1101 to determine whether the scene identifier of the business scenario A1 has been recorded in the scene record table 122, or in other words, to determine whether the row where the scene attribute information of the business scenario A1 is located has recorded the scene identifier before step 1002. If the scene identifier of the business scenario A1 has been recorded in the event logic model definition table 122, it means that the scene identifier has been generated for the business scenario A1 in the previous operation and does not need to be generated again. In this case, the process can be terminated. If the judgment result of step 1101 is no, step 1002 is executed.

[0117] The administrator may input an operation to the business management device 910 through step 1003, and the operation is used to set the business meaning under the business scenario A1. In other words, the operation includes sending the set business meaning to the business management device 910 under the business scenario A1, and the set business meaning may be set as the business meaning B1. That is, through step 1003, the business management device 910 may receive the business meaning B1 under the business scenario A1.

[0118] In some embodiments, the operation input in step 1003 includes the scenario attribute information and the business meaning B1 of the business scenario A1. The scenario attribute information of the business scenario A1 is used to characterize the business scenario A1, so that the business management device 910 perceives that the business meaning B1 is received under the business scenario A1. The business management device 910 uses the business meaning B1 received in the business scenario A1 as the business meaning under the business scenario A1.

[0119] When receiving the business meaning (ie, business meaning B1) set by the administrator, the business management device 910 may execute step 1004 to record the set business meaning into the business meaning record table 121 and establish an association relationship.

[0120] The association relationship includes the association relationship between business meaning and business scenario, and the association relationship indicates that the business meaning is the business meaning under the business scenario. Figure 6 , a row can be added to the business meaning record table 121, and the business meaning B1 can be recorded in the added row. Specifically, the business meaning B1 is recorded in the cell constrained by the column corresponding to the business meaning field in the added row, that is, the cell where the business meaning B1 is located is in the column corresponding to the business meaning field.

[0121] In step 1004, a correlation relationship may be specifically established between the position of the business meaning B1 in the business meaning record table 121 and the business scenario A1. In some embodiments, the correlation relationship between the position of the business meaning B1 in the business meaning record table 121 and the business scenario A1 is specifically: the correlation relationship between the position of the business meaning B1 in the business meaning record table 121 and the scenario identifier of the business scenario A1. The position of the business meaning B1 in the business meaning record table 121 includes the row where the business meaning B1 is located in the business meaning record table 121, that is, the row where the business meaning B1 is recorded. The scenario identifier of the business scenario A1 may be recorded in the row where the business meaning B1 is located in the business meaning record table 121, that is, the scenario identifier of the business scenario A1 and the business meaning B1 may be recorded in the same row in the business meaning record table, so as to establish a correlation relationship between the scenario identifier of the business scenario A1 and the position of the business meaning B1 in the business meaning record table 121. For example, Figure 6 As shown, the business meaning B1 can be set as "native place", and the scenario identifier of the business scenario A1 can be set as "A1000", then "A1000" can be recorded in the row where "native place" is located. In this way, an association relationship between "native place" and "A1000" can be established.

[0122] In step 1004, the business meaning B1 can also be associated with the reserved field in the header of the data record table 110, that is, the association relationship between the business meaning B1 and the reserved field is established. Among them, the business field B1 can be associated with the reserved field whose value is empty under the business scenario A1. The value of empty under the business scenario A1 refers to the reserved field that has not been associated with the business meaning under the business scenario A1. For example, "native place" and "gender" are both business meanings under the business scenario A1, and the reserved field 11 and the reserved field 12 are reserved fields in the header of the data record table 110. When associating "gender" with the reserved field, if the reserved field 11 has been associated with "native place", and the reserved field 12 has not been associated with the business meaning under the business scenario A1. That is, the value of the reserved field 11 under the business scenario A1 is "native place" and is not empty, and the value of the reserved field 12 under the business scenario A1 is empty, then the "gender" can be associated with the reserved field 12.

[0123] In some embodiments, the association relationship between the business meaning and the reserved fields under the business scenario A1 may be recorded in the association relationship table 130. Figure 8 As shown, the business meaning and the reserved field can be recorded in the same row in the association table to establish an association relationship between the business meaning and the reserved field, that is, the business meaning and the reserved field in the same row have an association relationship. Exemplarily, the scenario identifier can be recorded in the row where the business meaning is located to indicate that the business meaning is the business meaning under the business scenario identified by the scenario identifier.

[0124] In some embodiments, before associating the business meaning B1 with the reserved field, it can be determined whether there is a reserved field with an empty value under the business scenario A1 in the header of the data record table 110. If not, associating the business meaning B1 with the reserved field fails. If so, the business industry B1 is associated with the reserved field with an empty value under the business scenario A1.

[0125] In one example, as described above, the scenario attribute information has multiple dimensions, and the scenario attribute information of different dimensions corresponds to different levels of business scenarios. In the header of the data record table 110, a preset number of reserved fields can be set for each level of business scenario. The reserved fields for different levels of business scenarios are used to associate the meanings of fields under different levels of business scenarios. Therefore, before associating the business meaning B1 with the reserved fields, it can be confirmed whether there are reserved fields with empty values ​​under business scenario A1 in the reserved fields corresponding to the business scenarios of business meaning B1. If not, the business meaning B1 fails to associate with the reserved fields. If it exists, the business industry B1 is associated with the reserved field with an empty value under business scenario A1.

[0126] In one example, the business scenario can be set to have a first-level business scenario and a second-level business scenario. For example, the first-level business scenario is represented by the scenario attribute information of the domain dimension, and the second-level business scenario is represented by the scenario attribute information of the event dimension. Fig.12 Before executing step 1004, the business management device 910 may first execute step 1201 to determine the scene level to which the business scene A1 belongs.

[0127] If the scenario level to which business scenario A1 belongs is the first-level business scenario, step 1202a is executed to determine whether there is a reserved field whose value is empty under business scenario A1 in the reserved fields corresponding to the first level. If not, the association of field meaning B1 fails. If so, an association relationship between field meaning B1 and the reserved field is established.

[0128] If the scenario level to which business scenario A1 belongs is a second-level business scenario, step 1202b is executed to determine whether there is a reserved field with an empty value under business scenario A1 in the reserved fields corresponding to the second level. If not, the association of field meaning B1 fails. If so, an association relationship between field meaning B1 and the reserved field is established.

[0129] With reference to the above steps, the business meaning B2 under the business scenario A1 can also be set, and the business meaning B2 can be associated with the reserved field in the header of the data table 110. Specifically, the business management device 910 can also receive the business meaning B2 under the business scenario A1, and record the business meaning B2 in the business meaning record table 121, and establish an association relationship between the position of the business meaning B2 in the business meaning record table and the business scenario A1, and establish an association relationship between the business meaning B2 and the reserved field in the header of the data table 110.

[0130] Among them, the reserved field associated with the business meaning B2 and the reserved field associated with the business meaning B1 are different reserved fields.

[0131] In some embodiments, the business meaning record table 121 is a vertical table, and the business meaning B2 and the business meaning B1 are in different rows in the business meaning record table. By using the vertical table to record different business meanings, whenever a new business meaning is set, the new business meaning can be recorded by adding a row, which facilitates the recording of business meanings and further facilitates the online expansion of the event model.

[0132] With reference to the above steps, the business meanings in other business scenarios can also be set, and the business meanings can be associated with the reserved fields in the header of the data record table 110. Specifically, taking the business meaning B3 in the business scenario A2 as an example, the business management device 910 can also receive the business meaning B3 in the business scenario A2, and record the business meaning B3 in the business meaning record table 121, and establish an association relationship between the position of the business meaning B3 in the business meaning record table and the business scenario A2, and establish an association relationship between the business meaning B3 and the reserved fields in the header of the data record table 110.

[0133] The reserved field associated with the business meaning B3 and the reserved field associated with the business meaning B1 can be the same reserved field or different reserved fields. In other words, the reserved fields in the header of the data record table 110 can be reused in different business scenarios, and are respectively associated with the field meanings in different business scenarios. The business meaning B3 and the business meaning B1 are recorded in different rows of the business meaning record table 121.

[0134] In the above manner, the reserved fields in the header of the data record table 110 can be associated with business meanings in different business scenarios. When the data record table is used in a certain business scenario, the business meaning of the reserved fields can be displayed in the user interface of the business scenario based on the business meaning of the reserved fields in the business scenario. By displaying the business meaning at the position of the reserved fields in the user interface, the user can understand the business meaning of the field value corresponding to the reserved fields, which facilitates the user to enter business data or approve business data (for example, fill in data or approve data).

[0135] Next, an example is given to illustrate how to display business meanings in the reserved space in the user interface.

[0136] Continue reading Fig.10 The administrator may input a usage scenario indication of the data record table 110 in step 1005. The usage scenario indicates in which business scenario the data record table 110 needs to be used.

[0137] Take the case where the data record table needs to be used in business scenario A1. In step 1005, the administrator may input a usage scenario indication of the data record table 110 to the business management device 910, and the usage scenario indication includes the scenario attribute information of the business scenario A1. As described above, the scenario attribute information of the business scenario A1 is used to characterize the business scenario A1. When the business management device 910 receives the usage scenario indication including the scenario attribute information of the business scenario A1, it may confirm that the usage scenario of the data record table 110 is the business scenario A1, that is, the data record table 110 is used in the business scenario A1.

[0138] When confirming that the data record table 110 is used in the business scenario A1, the business management device 910 may execute step 1006 to generate a user interface in the business scenario A1. The user interface in the business scenario A1 may be generated based on the header of the data record table 110. Specifically, the business meaning in the business scenario A1 associated with the reserved field in the header of the data record table 110 may be obtained, and the business meaning of the user interface of the reserved field in the business scenario A1 may be displayed based on the business meaning, and the business meaning may be displayed at the position of the reserved field in the user interface.

[0139] Specifically, taking the business meaning B1 as an example, as described above, in step 1004, through the business meaning record table 121, an association relationship between the business meaning B1 and the business scenario A1 is established in the business meaning record table 121. Through this association relationship, the business meaning B1 can be obtained in the business meaning record table 121. Specifically, through this association relationship, the position of the business meaning B1 in the business meaning record table 121 can be queried in the business meaning record table 121, and the business meaning at the position can be obtained, thereby obtaining the business meaning B1.

[0140] In some embodiments, the association relationship between the business meaning B1 and the business scenario A1 may specifically be the association relationship between the position of the business meaning B1 in the business meaning record table 121 and the scene identifier of the business scenario A1. In this way, the position of the business meaning B1 in the business meaning record table 121 can be queried through the scene identifier of the business scenario A1, and the business meaning at the position can be obtained, thereby obtaining the business meaning B1.

[0141] In an example of this embodiment, as described above, the scenario identifier of the business scenario A1 and the business meaning B1 are in the same row in the business meaning record table 121. Thus, the row where the scenario identifier of the business scenario A1 is located can be queried in the business meaning record table 121, and the business meaning can be obtained from the row, thereby obtaining the business meaning B1.

[0142] In some embodiments, see Fig.13 , step 1006 may include step 1301, obtaining a scenario identifier of the business scenario A1 according to the scenario attribute information of the business scenario A1. As described above, the scenario identifier of the business scenario A1 and the scenario attribute information of the business scenario A1 are recorded in the same row of the event logic model definition table 122. When the business management device 910 receives the use scenario indication including the scenario attribute information of the business scenario A1, it may obtain the scenario identifier of the business scenario A1 from the event logic model definition table 122 based on the scenario attribute information of the business scenario A1.

[0143] See also Fig.13 , step 1006 also includes step 1302, obtaining the business meaning under the business scenario A1 according to the scenario identifier of the business scenario A1.

[0144] In the above manner, the business management device 910 can obtain the business meaning B1 under the business scenario A1 when the data record table 110 is used under the business scenario A1.

[0145] See also Fig.13 Step 1006 further includes step 1303, obtaining the reserved field associated with the business meaning under the business scenario A1 according to the association relationship between the business meaning and the reserved field. For example, after obtaining the business meaning B1 under the business scenario A1, the business management device 910 can obtain the reserved field associated with the business meaning B1 based on the association relationship between the business meaning B1 and the reserved field, thereby obtaining the business meaning of the reserved field under the business scenario A1.

[0146] See also Fig.13 , step 1006 also includes step 1304, generating the business meaning of the associated reserved field according to the business meaning under the business scenario A1. Specifically, when the business meaning of the reserved field under the business scenario A1 is obtained, the business meaning of the reserved field can be displayed in the user interface under the business scenario A1. For example, if the business meaning under the business scenario A1 to which a reserved field in the data record table 110 is associated is business meaning B1, then the business meaning B1 can be displayed at the position of the reserved field on the user interface. By displaying the business meaning B1 at the position of the reserved field on the user interface, the user can see the business meaning of the reserved field on the user interface.

[0147] With reference to the method of obtaining the reserved fields associated with the business meaning B1, the reserved fields associated with other business meanings under the business scenario A1 can also be obtained, and based on the business meaning, the business meaning of the reserved fields associated with the business meaning can be displayed on the user interface. For example, when confirming that the data record table 110 is used in the business scenario A1, the business meaning B2 can be obtained from the business meaning record table 121 based on the position of the business meaning B2 in the business meaning record table 121 and the scenario identifier of the business scenario A1. Then, based on the association between the business meaning B2 and the reserved fields, the reserved fields associated with the business meaning B2 are obtained. And based on the business meaning B2, the business meaning of the reserved fields associated with the business meaning B2 is displayed on the user interface. In this way, the business meaning B2 can be displayed at the position of the reserved field in the user interface.

[0148] Referring to the method of generating the user interface of business scenario A1, user interfaces for other business scenarios can also be generated. Taking business scenario A2 as an example, when confirming that the data record table 110 is used in business scenario A2, the user interface for business scenario A2 can be generated based on the header of the data record table 110.

[0149] Among them, the business meaning under the business scenario A2 associated with the reserved field in the header of the data record table 110 can be obtained, and the business meaning of the reserved field under the business scenario A2 can be displayed on the user interface based on the business meaning. Taking the business meaning B3 as an example, the business meaning B3 can be obtained from the business meaning record table 121 based on the position of the business meaning B3 in the business meaning record table 121 and the scene identifier of the business scenario A2. Then, based on the association relationship between the business meaning B3 and the reserved field, the reserved field associated with the business meaning B3 is obtained. Then, the business meaning of the reserved field associated with the business meaning B3 can be displayed in the user interface under the business scenario A2 using the business meaning B3, and the business meaning B3 is displayed at the position of the reserved field in the user interface.

[0150] In some embodiments, as shown above, business scenarios may have multiple levels, and business scenarios are subsets of the business scenarios of the upper level. For example, the business scenario of birth certificate processing is a subset of the business scenario of population management. The business meaning under the business scenario includes the business meaning under the business scenario of the upper level of the business scenario, that is, the business meaning of the business scenario can be adopted by the sub-business scenario of the business scenario. When generating a user interface under a business scenario, the business meaning of the reserved field associated with the business meaning of the upper level business scenario can be generated on the user interface based on the business meaning of the upper level business scenario of the business scenario. For example, the business scenario of population management is the upper level business scenario of the business scenario of birth certificate processing, that is, birth certificate processing is a subset of population management. When the data record table 110 is used under birth certificate processing, the user interface under birth certificate processing is generated based on the header of the data record table 110. Among them, when generating the user interface under birth certificate processing, the business meaning under population management can be obtained, and based on the business meaning under population management, the business meaning of the reserved field associated with the business meaning under population management is generated on the user interface. In this way, the business meaning under population management can be displayed in the position of the reserved field in the user interface.

[0151] In an example, taking business scenario A1 as a subset of business scenario A2, the business meaning under business scenario A2 can be obtained in the following manner when generating a user interface under business scenario A1.

[0152] The scenario identifier of business scenario A1 and the scenario identifier of business scenario A2 are associated. In one example, the scenario identifier of the upper-level business scenario of business scenario A1 (i.e., business scenario A2) and the scenario identifier of business scenario A1 can be recorded in the same row in the event logic model definition table 122 to establish an associated relationship between the scenario identifier of business scenario A1 and the scenario identifier of business scenario A2. For example, the scenario identifier of business scenario A1 can be set to Aa100, and the scenario identifier of business scenario A2 can be set to A1000, such as Figure 5 As shown, A1000 may be recorded in the row where Aa100 is located in the event logic model definition table 122 .

[0153] When confirming that the data record table 110 is used in the business scenario A1, the scenario identifier of the business scenario A2 can be obtained based on the association relationship between the scenario identifier of the business scenario A1 and the scenario identifier of the business scenario A2. Then, based on the scenario identifier of the business scenario A2 and the position of the business meaning under the business scenario A2 in the business meaning record table 121, the business meaning under the business scenario A2 is obtained. Next, based on the association relationship between the business meaning under the business scenario A2 and the reserved field, the reserved field associated with the business meaning under the business scenario A2 is obtained.

[0154] In this way, when the user interface under business scenario A1 is generated, the business meaning under business scenario A2 can be obtained. Then, based on the business meaning under business scenario A2, the business meaning of the reserved field associated with the business meaning under business scenario A2 on the user interface under business scenario A1 can be generated, and the business meaning under business scenario A2 can be generated at the position of the reserved field associated with the business meaning in the user interface under business scenario A1.

[0155] In this way, when generating the user interface of the business scenario, the business meaning of the superior business scenario of the business scenario can be used, and the business meaning is shared. There is no need to set the business meaning shared by the business scenario and the superior business scenario for the business scenario, which can save the setting operation of the business meaning and facilitate the expansion operation of the event model. In particular, the superior business scenario may have other scenarios, that is, the superior business scenario has multiple sub-scenarios. These sub-scenarios can all use the business meaning of the superior business scenario, and there is no need to set the business meaning for each sub-scenario separately.

[0156] For example, for the business scenario of traffic management, the business meaning of "name" is defined. The business scenarios of traffic violation handling and driver's license application also require the business meaning of "name". The business scenario of traffic management is the superior business scenario of the business scenarios of traffic violation handling and driver's license application. In the above way, you only need to set "name" for traffic management, and traffic violation handling and driver's license application can use their superior business scenarios, that is, "name" of traffic management.

[0157] In some embodiments, the event logic model 120 (ie, the business meaning record table 121 and the event logic model definition table 122) is stored in a database, and the business management device 910 can use Figure 7 The event logic model interface shown calls the event logic model 120 to obtain the business meaning of the header of the data record table 110. For example, see Fig.14, the scenario attribute information can be set to include the scenario attribute information of the first-level dimension and the scenario attribute information of the second-level dimension. Among them, the scenario attribute information of the first-level dimension is "population management", and the scenario attribute information of the second-level dimension is "birth certificate". Among them, the scenario attribute information of the first-level dimension represents the first-level business scenario, and the scenario attribute information of the first dimension and the scenario attribute information of the second-level dimension jointly represent the second business scenario. The first-level business scenario belongs to a certain field, and the second-level business scenario belongs to a certain matter under the field. Among them, the second-level business scenario is a subset of the first-level business scenario. Through the association relationship between business meaning and reserved fields, it can be obtained that the business meaning under the first-level business scenario is "gender", and the reserved field associated with "gender" is reserved field 12; the business meaning under the second-level business scenario is "newborn name", and the reserved field associated with "newborn name" is reserved field 21.

[0158] In this way, the business meanings of the headers of the data record table 110 in the second-level business scenario are: "ID", "Name", "Submitter", "Submission Time", "Event Status", "Gender", and "Newborn Name". In the data record table 110, the column corresponding to "ID" is used to store the event ID value, the column corresponding to "Name" is used to store the event name value, the column corresponding to "Submitter" is used to store the event submitter value, the column corresponding to "Submission Time" is used to store the event submission time value, the column corresponding to "Event Status" is used to store the event status value, the column corresponding to "Gender" is used to store the gender value, and the column corresponding to "Newborn Name" is used to store the newborn name value.

[0159] In the above manner, a user interface in a business scenario can be generated, and the corresponding business meaning can be displayed at the position of the reserved field in the user interface. For example, "newborn's name" is displayed at the position of the reserved field 21; and "gender" is displayed at the position of the reserved field 12.

[0160] The user interface can be used to perform operations such as business data entry and business data viewing. Next, the user interface in business scenario A1 is taken as an example to illustrate the role of the user interface.

[0161] In some embodiments, the user interface under the business scenario A1 may be or include a data entry interface. The reserved field associated with the business meaning B1 corresponds to an edit box C1. The data entry operator may enter business data in the edit box C1 to store the business data in the data record table 110. The details are as follows.

[0162] Continue reading Fig.10, the data entry operator can input a data entry request to the data entry device 920 in step 1007, and the data entry request is used to request to enter business data under the business scenario A1. The data entry device 920 can respond to the data entry request, obtain the data entry interface from the business management device 910 in step 1008, and display the data entry interface in step 1009. The data entry operator can perform data entry operation in step 1010 to enter business data in the edit box C1. The data entry device 920 can detect the data in the edit box C1, and send the data detected in the edit box C1 (the business data entered in the edit box C1) to the business management device 910 in step 1011. The business management device 910 can execute step 1012 to store the business data in the column corresponding to the reserved field corresponding to the edit box C1 (the reserved field associated with the business meaning B1) in the data record table 110. Thereby, the entry and storage of the business data corresponding to the business meaning B1 is completed.

[0163] In some embodiments, the user interface in the business scenario A1 may be or include a data viewing interface. Through the data viewing interface, the business data corresponding to the business meaning B1 stored in the data record table 110 may be viewed. The details are as follows.

[0164] Continue reading Fig.10 , the viewer can input a data viewing request to the data viewing device 930 in step 1013, and the data viewing request is used to request to view business data under business scenario A1. The data viewing device 930 can respond to the data viewing request, obtain a data viewing interface from the business management device 910 in step 1014, and display the data viewing interface in step 1015. In step 1016, the data viewing device 930 can obtain the business data stored in the data record table 110 from the business management device 910. The business data to be viewed can be set as the business data of the business meaning B1, and then in step 1016, the business data is obtained from the column corresponding to the reserved field associated with the business meaning B1 in the data record table 110. When the data viewing device 930 obtains the business data of the business meaning B1, it can display the business data in the data viewing interface in step 1017. Specifically, the business data can be displayed in the display area corresponding to the business meaning B1 in the data viewing interface. Among them, the display area corresponding to the business meaning B1 specifically refers to the display area corresponding to the reserved field associated with the business meaning B1. Thus, the business data can be viewed.

[0165] In the data processing method provided in the embodiment of the present application, the data recording table used to record business data is a horizontal table, which ensures data query efficiency, readability and maintainability, and does not consume too much storage resources. In addition, while using a horizontal table to record business data, it is allowed to set the business meaning under different business scenarios, and the business meaning, business scenario and the reserved field in the header of the horizontal table can be associated. In this way, when the data recording table is used in a certain business scenario, the business meaning under the business scenario and the reserved field associated with the business meaning are obtained, and then the business meaning of the reserved field can be displayed as the business meaning under the business scenario on the user interface, so that the user can intuitively see the business meaning of the reserved field under the business superior, which improves the user experience.

[0166] In summary, the embodiment of the present application provides a method for processing data using an event model, wherein the event model includes a data record table and a business meaning record table, wherein the data record table is a horizontal table for storing business data, and the header of the data record table includes a first reserved field, and the business meaning record table is used to record business meanings in different scenarios. Fig.15 , the method comprising:

[0167] Step 1501: Receive a first service meaning in a first scenario. Fig.10 The introduction of step 1003 is implemented.

[0168] Step 1502: Record the first business meaning and the first scenario associated with the first business meaning in the business meaning record table. Fig.10 The introduction of step 1004 is implemented.

[0169] Step 1503: associate the first service meaning with the first reserved field. Fig.10 The introduction of step 1004 is implemented.

[0170] Step 1504: Based on the business meaning record table, the first business meaning is displayed in the user interface under the first scenario at the location of the first reserved field. Fig.10 The introduction and implementation of steps 1005 and 1006.

[0171] In some embodiments, the business meaning record table is a vertical table, and the header of the data record table also includes a second reserved field; the method also includes: receiving a second business meaning in a first scenario; recording the second business meaning and the first scenario associated with the second business meaning in the business meaning record table, the second business meaning and the first business meaning being located in different rows in the business meaning record table; associating the second business meaning with a second reserved field; based on the business meaning record table, displaying the second business meaning at the location of the second reserved field on the user interface in the first scenario. For details, please refer to the above description of Fig.10 The introduction and implementation of steps 1003-1006 in FIG.

[0172] In some embodiments, the business meaning record table is a vertical table; the method further includes: receiving a third business meaning in a second scenario; recording the third business meaning and the second scenario associated with the third business meaning in the business meaning record table, wherein the third business meaning and the first business meaning are located in different rows in the business meaning record table; associating the third business meaning with the first reserved field; based on the business meaning record table, displaying the third business meaning in the position of the first reserved field on the user interface in the second scenario. For details, please refer to the above description of Fig.10 The introduction and implementation of steps 1003-1006 in FIG.

[0173] In some embodiments, recording the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table includes: recording the scenario identifier of the first scenario in the row where the first business meaning is located in the business meaning recording table. Fig.10 The introduction of step 1002 is implemented.

[0174] In some embodiments, the business meaning record table records a fourth business meaning and a third scenario associated with the fourth business meaning; wherein the first scenario is a subset of the third scenario, and the header of the data record table also includes a third reserved field associated with the fourth business meaning; the method further includes: based on the business meaning record table, in the user interface under the first scenario, displaying the fourth business meaning at the position of the third reserved field. For details, please refer to the above description of Fig.10 The introduction of step 1006 is implemented.

[0175] In an example of this embodiment, the third scene is represented by scene attribute information of a first dimension, and the first scene is represented by both the scene attribute information of the first dimension and the scene attribute information of a second dimension.

[0176] In some embodiments, the user interface in the first scenario includes a data entry interface, the first reserved field corresponds to an edit box, and the method further includes: receiving a data entry request, the data entry request is used to request to enter business data in the first scenario; responding to the data entry request, displaying the data entry interface; obtaining the input content in the edit box, and storing the input content in the column corresponding to the first reserved field in the data record table. For details, please refer to the above Fig.10 The introduction and implementation of steps 1007-1012 in FIG.

[0177] In some embodiments, the user interface in the first scenario includes a data viewing interface; receiving a data viewing request, the data viewing request is used to view business data in the first scenario; responding to the data viewing request, displaying the data viewing interface; obtaining business data from the column corresponding to the first reserved field in the data record table, and displaying the obtained business data in the display area corresponding to the first reserved field. For details, please refer to the above Fig.10 The introduction and implementation of steps 1013-1017 in .

[0178] In the data processing method provided in the embodiment of the present application, the data record table for recording business data is a horizontal table, which ensures data query efficiency, readability and maintainability, and does not consume too much storage resources. In addition, while using a horizontal table to record business data, it is allowed to set the business meaning in different business scenarios, and the business meaning, business scenario and the reserved field in the header of the horizontal table can be associated. In this way, when the data record table is used in a certain business scenario, the business meaning in the business scenario and the reserved field associated with the business meaning are obtained, and then the business meaning in the business scenario can be displayed at the position of the reserved field on the user interface in the business scenario, so that the user can intuitively see the business meaning of the reserved field under the business superior, which improves the user experience.

[0179] The embodiment of the present application also provides a device 1600 for processing data using an event model. The event model includes a data record table and a business meaning record table, wherein the data record table is a horizontal table for storing business data, and the header of the data record table includes a first reserved field, and the business meaning record table is used to record business meanings in different scenarios. Fig.16 As shown, the apparatus 1600 includes:

[0180] A receiving module 1610, configured to receive a first service meaning in a first scenario;

[0181] A recording module 1620, configured to record the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table;

[0182] An associating module 1620, configured to associate the first service meaning with the first reserved field;

[0183] The display module 1640 is configured to display the first business meaning at the location of the first reserved field in the user interface in the first scenario based on the business meaning record table.

[0184] Among them, the receiving module 1610, the recording module 1620, the association module 1630 and the display module 1640 can all be implemented by software, or can be implemented by hardware. Exemplarily, the following takes the receiving module 1610 as an example to introduce the implementation of the receiving module 1610. Similarly, the implementation of the recording module 1620, the association module 1630 and the display module 1640 can refer to the implementation of the receiving module 1610.

[0185] As an example of a software functional unit, the receiving module 1610 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the receiving module 1610 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including a data center or multiple data centers with similar geographical locations. Among them, usually a region may include multiple AZs.

[0186] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

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

[0188] The multiple computing devices included in the receiving module 1610 can be distributed in the same region or in different regions. The multiple computing devices included in the receiving module 1610 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the receiving module 1610 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0189] It should be noted that, in other embodiments, the receiving module 1610 may be used to execute Fig.15 In any step of the method shown, the recording module 1620 can be used to perform Fig.15 For any step in the method shown, the association module 1630 can be used to perform Fig.15 For any step in the method shown, the display module 1640 can be used to perform Fig.15 The steps implemented by the receiving module 1610, the recording module 1620, the associating module 1630 and the display module 1640 can be specified as needed, and the steps implemented by the receiving module 1610, the recording module 1620, the associating module 1630 and the display module 1640 can be specified as needed. Fig.15 The different steps in the method shown are used to implement the overall functions of the apparatus 1600 .

[0190] The present application also provides a computing device 1700. Fig.17As shown, computing device 1700 includes: bus 1702, processor 1704, memory 1706 and communication interface 1708. Processor 1704, memory 1706 and communication interface 1708 communicate through bus 1702. Computing device 1700 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in computing device 1700.

[0191] The bus 1702 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.17 The bus 1702 may include a path for transmitting information between various components of the computing device 1700 (eg, the memory 1706, the processor 1704, and the communication interface 1708).

[0192] The processor 1704 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

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

[0194] The memory 1706 stores executable program codes, and the processor 1704 executes the executable program codes to respectively implement the functions of the aforementioned receiving module 1610, the recording module 1620, the association module 1630, and the display module 1640, thereby implementing Fig.15 That is, the memory 1706 stores the method for executing Fig.15 Instructions for the method shown.

[0195] The communication interface 1708 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 1700 and other devices or communication networks.

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

[0197] like Fig.18 As shown, the computing device cluster includes at least one computing device 1700. The memory 1706 in one or more computing devices 1700 in the computing device cluster may store the same Fig.15 Instructions for the method shown.

[0198] In some possible implementations, the memory 1706 of one or more computing devices 1700 in the computing device cluster may also store a program for executing Fig.15 In other words, the combination of one or more computing devices 1700 can jointly execute instructions for executing Fig.15 Instructions for the method shown.

[0199] It should be noted that the memory 1706 in different computing devices 1700 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the apparatus 1600. That is, the instructions stored in the memory 1706 in different computing devices 1700 may implement the functions of one or more modules of the receiving module 1610, the recording module 1620, the associating module 1630 and the display module 1640.

[0200] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.19 A possible implementation is shown. Fig.19 As shown, two computing devices 1700A and 1700B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 1706 in the computing device 1700A stores instructions for executing the functions of the receiving module 1610, the recording module 1620, and the association module 1630. At the same time, the memory 1706 in the computing device 1700B stores instructions for executing the functions of the display module 1640.

[0201] It should be understood that Fig.19 The functionality of the computing device 1700A shown in FIG. 1700A may also be implemented by multiple computing devices 1700. Similarly, the functionality of the computing device 1700B may also be implemented by multiple computing devices 1700.

[0202] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Fig.18 and Fig.19 The difference is that the memory 1706 in one or more computing devices 1700 in the computing device cluster may store the same memory for executing Fig.15 Instructions for the method shown.

[0203] In some possible implementations, the memory 1706 of one or more computing devices 1700 in the computing device cluster may also store a program for executing Fig.15 In other words, the combination of one or more computing devices 1700 can jointly execute instructions for executing Fig.15 Instructions for the method shown.

[0204] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes Fig.15 The method shown.

[0205] The present application also provides a computer-readable storage medium. The computer-readable storage medium may be any available medium that can be stored by a computing device or a host migration device such as a data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute Fig.15 The method shown.

[0206] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing data using an event model, It is characterized in that The event model includes a data record table and a business meaning record table, wherein the data record table is a horizontal table for storing business data, and the table header of the data record table includes a first reserved field, and the business meaning record table is used to record business meanings in different scenarios; the method includes: Receiving a first business meaning in a first scenario; Recording the first service meaning and the first scenario associated with the first service meaning in the service meaning record table; Associating the first service meaning with the first reserved field; Based on the business meaning record table, in the user interface under the first scenario, the first business meaning is displayed at the position of the first reserved field.

2. The method according to claim 1, It is characterized in that The business meaning record table is a vertical table, and the header of the data record table further includes a second reserved field; the method further includes: Receiving a second business meaning under the first scenario; Recording the second business meaning and the first scenario associated with the second business meaning in the business meaning recording table, wherein the second business meaning and the first business meaning are located in different rows in the business meaning recording table; Associating the second service meaning with the second reserved field; Based on the business meaning record table, the second business meaning is displayed at the position of the second reserved field on the user interface in the first scenario.

3. The method according to claim 1 or 2, It is characterized in that The business meaning record table is a vertical table; the method further includes: Receive the third service meaning in the second scenario; Recording the third business meaning and the second scenario associated with the third business meaning in the business meaning recording table, wherein the third business meaning and the first business meaning are located in different rows in the business meaning recording table; Associating the third service meaning with the first reserved field; Based on the business meaning record table, the third business meaning is displayed at the position of the first reserved field on the user interface in the second scenario.

4. The method according to any one of claims 1 to 3, It is characterized in that The recording of the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table includes: In the row where the first business meaning is located in the business meaning record table, the scenario identifier of the first scenario is recorded.

5. The method according to any one of claims 1 to 4, It is characterized in that The business meaning record table records a fourth business meaning and a third scenario associated with the fourth business meaning; wherein the first scenario is a subset of the third scenario, and the header of the data record table further includes a third reserved field associated with the fourth business meaning; The method further includes: based on the business meaning record table, in the user interface under the first scenario, displaying the fourth business meaning at the position of the third reserved field.

6. The method according to claim 5, It is characterized in that The third scene is represented by scene attribute information of a first dimension, and the first scene is represented by both the scene attribute information of the first dimension and the scene attribute information of a second dimension.

7. A device for processing data using an event model, It is characterized in that The event model includes a data record table and a business meaning record table, wherein the data record table is a horizontal table for storing business data, and the header of the data record table includes a first reserved field, and the business meaning record table is used to record business meanings in different scenarios; the device includes: A receiving module, used for receiving a first service meaning in a first scenario; A recording module, configured to record the first business meaning and the first scenario associated with the first business meaning in the business meaning recording table; An associating module, used to associate the first service meaning with the first reserved field; A display module is configured to display the first business meaning at a position of the first reserved field in a user interface in the first scenario based on the business meaning record table.

8. The device according to claim 7, It is characterized in that The business meaning record table is a vertical table, and the header of the data record table further includes a second reserved field; The receiving module is further used to receive a second service meaning in the first scenario; The recording module is further used to record the second business meaning and the first scenario associated with the second business meaning in the business meaning recording table, wherein the second business meaning and the first business meaning are located in different rows in the business meaning recording table; The association module is further used to associate the second service meaning with the second reserved field; The display module is further configured to display the second business meaning at the position of the second reserved field on the user interface in the first scenario based on the business meaning record table.

9. The device according to claim 7 or 8, It is characterized in that The business meaning record table is a vertical table; The receiving module is further used to receive a third service meaning in the second scenario; The recording module is further used to record the third business meaning and the second scenario associated with the third business meaning in the business meaning recording table, wherein the third business meaning and the first business meaning are located in different rows in the business meaning recording table; The association module is further used to associate the third service meaning with the first reserved field; The display module is further configured to display the third business meaning at the position of the first reserved field on the user interface in the second scenario based on the business meaning record table.

10. The device according to any one of claims 7 to 9, It is characterized in that The recording module is further configured to record a scenario identifier of the first scenario in a row where the first business meaning is located in the business meaning recording table.

11. The device according to any one of claims 7 to 10, It is characterized in that The business meaning record table records a fourth business meaning and a third scenario associated with the fourth business meaning; wherein the first scenario is a subset of the third scenario, and the header of the data record table further includes a third reserved field associated with the fourth business meaning; The display module is further configured to display the fourth business meaning at the position of the third reserved field in the user interface under the first scenario based on the business meaning record table.

12. The device according to claim 11, It is characterized in that The third scene is represented by scene attribute information of a first dimension, and the first scene is represented by both the scene attribute information of the first dimension and the scene attribute information of a second dimension.

13. A computing device cluster, It is characterized in that comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 6.

14. A computer-readable storage medium, It is characterized in that The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 6.

15. A computer program product comprising instructions, It is characterized in that When the instructions are executed by a computer device cluster, the computer device cluster is caused to perform the method according to any one of claims 1 to 6.