Business data processing method and device, equipment, medium and program product

Abstract

The embodiment of the invention discloses a business data processing method and device, equipment, a medium and a program product. The method comprises the following steps: obtaining business data materialization configuration information corresponding to a business data table, wherein the business data materialization configuration information is obtained through configuration based on an urban knowledge system and metadata of the business data table; based on the service data materialization configuration information, performing materialization processing on each piece of service data in the service data table to obtain entity data, entity relationship data, an entity data index and an entity relationship data index corresponding to the service data; and storing the entity data, the entity relationship data, the entity data index and the entity relationship data index corresponding to the business data into a search database. Through the technical scheme of the embodiment of the invention, the business data can be automatically materialized into the entity data meeting the urban knowledge system, so that the general processing of different types of business data is realized, and the development cost is reduced.

Description

Technical Field

[0001] The embodiments of the present invention relate to computer technology, and in particular to a business data processing method, device, equipment, medium and program product. Background Art

[0002] With the rapid development of technology, there are various business scenarios in cities, which will generate various business data. It is usually necessary to store each type of business data generated so that subsequent data searches can be performed to obtain the business data of interest.

[0003] At present, the business data that needs to be processed is usually stored and searched by building a data warehouse platform and business system. For example, the data warehouse first performs data access and governance and provides external data search services, and then builds the corresponding business system based on scenario requirements, calling the data warehouse capabilities to implement scenario applications.

[0004] However, in the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0005] Different data warehouse platforms and business systems need to be developed for different types of business data, which greatly increases development costs. Summary of the invention

[0006] The embodiments of the present invention provide a business data processing method, apparatus, equipment, medium and program product to automatically materialize business data into entity data that satisfies the city knowledge system, thereby realizing universal processing of different types of business data without the need to develop different data warehouse platforms and business systems, thereby reducing development costs.

[0007] In a first aspect, an embodiment of the present invention provides a method for processing business data, including:

[0008] Obtaining business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class, and relationships between entity classes, wherein the entity class is obtained by classifying city data;

[0009] Based on the business data entity configuration information, each business data in the business data table is entity processed to obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data;

[0010] The entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index are stored in a search database.

[0011] In a second aspect, an embodiment of the present invention further provides a service data processing device, including:

[0012] The entity configuration information acquisition module is used to acquire the business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and the metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class and relationships between entity classes, wherein the entity class is obtained by classifying the city data;

[0013] A business data entity processing module, used to perform entity processing on each business data in the business data table based on the business data entity configuration information, and obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data;

[0014] The entity data storage module is used to store the entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index in a search database.

[0015] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0016] one or more processors;

[0017] A memory for storing one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the business data processing method provided by any embodiment of the present invention.

[0019] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the business data processing method provided by any embodiment of the present invention is implemented.

[0020] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements a business data processing method as provided in any embodiment of the present invention.

[0021] One embodiment of the above invention has the following advantages or beneficial effects:

[0022] By obtaining the business data entity configuration information corresponding to the business data table, the business data entity configuration information is obtained by configuration based on the city knowledge system and the metadata of the business data table, and different business data tables are used to store different types of business data. Based on the business data entity configuration information, each business data in the business data table is automatically entityized to obtain the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data, so that each business data in the business data table is automatically entityized into entity data that meets the city knowledge system, and the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data are stored in the search database, so as to perform a fast search of the full amount of data in the search database based on the entity data index and entity relationship data index. By configuring different business data entity configuration information for different business data tables, universal processing of different types of business data is achieved, without the need to develop different data warehouse platforms and business systems, thereby reducing development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 is a flow chart of a business data processing method provided by an embodiment of the present invention;

[0025] Figure 2 It is a structural example diagram of an entity relationship tree involved in an embodiment of the present invention;

[0026] Figure 3 is a flow chart of another business data processing method provided by an embodiment of the present invention;

[0027] Figure 4 It is a structural schematic diagram of a business data processing device provided by an embodiment of the present invention;

[0028] Figure 5 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0030] Figure 1 This is a flowchart of a business data processing method provided by an embodiment of the present invention. This embodiment is applicable to the case where business data is automatically converted into entity data that satisfies the city knowledge system. The method can be executed by a business data processing device, which can be implemented by software and / or hardware and integrated into an electronic device. Figure 1 As shown, the method specifically comprises the following steps:

[0031] S110. Obtain the business data entity configuration information corresponding to the business data table. The business data entity configuration information is obtained by configuring based on the city knowledge system and the metadata of the business data table. The city knowledge system includes multiple entity classes, field attributes of each entity class and relationships between entity classes, wherein the entity class is obtained by classifying the city data.

[0032] Among them, the business data table can be a data table used to store business data generated in a business scenario. Different types of business data correspond to different business data tables, that is, different business data tables are used to store different types of business data. The business fields in the business data table are set based on business requirements. The metadata of the business data table is data used to describe the business data table itself, such as content, structure, format and other data. The metadata of the business data table may include all column field information in the business data table, that is, business field information.

[0033] Among them, the urban knowledge system can refer to the knowledge expression of entities in the city, the relationship between entities and their related field attributes, as well as the connotation extracted and the extension evolved from them by structured and systematic means. Urban data can refer to the data generated by everything. Urban data can include dimensional data such as people, places, things, objects, emotions and organizations in the city. Data of various dimensions can be abstracted into various entities, and each type of entity is an entity class, such as people entity class, land entity class, etc. Different entity classes are used to represent urban data in different dimensions. There is a root entity class in the urban knowledge system, and there are six sub-entity classes under the root entity class: people, places, things, objects, emotions and organizations. The root entity class is the parent class of these six entity classes, and these six entity classes are sub-classes of the root entity class. People, places, things, objects, emotions and organizations can be further divided and derived into more sub-classes according to the urban knowledge system to form an entity class tree. The parent class is a more abstract expression of the sub-class, and the sub-class is a more specific expression of the parent class. The parent class has multiple sub-classes, and the sub-class has only one parent class. The last layer (i.e., leaf node) in the entity class tree is a specific entity. For example, an analog camera belongs to the video surveillance equipment in the object entity class, so a link from top to bottom in the entity class tree is: object entity class → video surveillance equipment → analog camera. In terms of data expression, an entity class can be composed of a uniquely identified entity class code, entity class name, and parent entity class code.

[0034] Each entity class has multiple entity fields, which are used to describe the meaning information of the entity class from multiple dimensions. For example, the entity fields corresponding to the object entity class may include: object name, object number, object size, object type, item function and item brand, etc. The field attributes of the entity class are the specific attribute information used to describe each entity field of the entity class. For example, the attribute information of the entity field includes: entity field code, field name and Chinese name, etc. The root entity class has only two entity fields: entity identification information (i.e. entity id) and entity name. Entity identification information is the unique identifier of the entity, which can be composed of the key field of the entity and the entity class code. Different entity classes correspond to different entity key fields. For example, the key field of the camera entity can be the national standard code, and the key field of the scenic spot entity is the place name and detailed address. The entity name is the display name of the entity. The subclass inherits the entity field of the parent class, and the inherited field can have a field description that is more suitable for the subclass. For example, the person entity class inherits the entity id and entity name of the root entity class, but the field description of the entity name in the person entity is name. In addition to inheriting the attributes of the parent class, the subclass may also have attributes that the parent class does not have. For example, in addition to the entity id and name fields, the person entity also has gender and age fields. In terms of data expression, each entity field consists of a uniquely identifiable entity field code, entity field name, and the entity class code of the entity class to which it belongs.

[0035] The relationship between entity classes can refer to the existence of one or more relationships between any two entity classes, such as the service relationship and kinship relationship between people, and the residential relationship between people and places. In terms of data expression, entity relationships can be expressed by a uniquely identified entity relationship code, entity relationship name, starting entity class code, end entity class code and relationship direction (i.e. one-way or two-way). Each entity relationship has multiple fields, for example, each entity relationship includes a starting entity id and an end entity id. The employment relationship between a person and an organization can also include fields such as start time and end time. In terms of data expression, the fields of each entity relationship can be composed of a uniquely identified entity relationship field code, an entity relationship field name and the entity relationship code of the entity relationship to which it belongs.

[0036] The business data entity configuration information may be used to describe the conversion relationship required when business data is converted into entity data. Exemplarily, the business data entity configuration information may include: form item configuration information, index configuration information, and entity relationship configuration information corresponding to each business field in the business data table.

[0037] Among them, the form item configuration information is used to describe the mapping of business fields to entity field information in the urban knowledge system. Each business field in the business data table is defined as a form item. By configuring the form item, a mapping relationship between the business field and the entity field in the urban knowledge system is established to determine which entity field under which entity in the urban knowledge system the business field belongs to. For example, the business field "camera name" is mapped to the entity field in the urban knowledge system as: the name field in the object entity class, that is, "name". The form item configuration information may include multiple configuration items for describing various attribute information of the entity field to which the business field is mapped. It should be noted that the representation of the business field and the font field can be the same or different. Exemplarily, the form item configuration information may include: the entity and entity field attribute information to which the business field is mapped in the urban knowledge system. Among them, the entity field attribute information may include: at least one of the entity field identification information, the entity field name, the entity field Chinese name, the entity field data type information, the entity field display name and the entity field display control type information. The entity field name refers to the name used to characterize the corresponding business field in the urban knowledge system. The entity field name is usually an English name named using letters. The entity field Chinese name refers to the Chinese meaning of the entity field name. The entity field data type information is used to represent the data type of the corresponding business field. The entity field display name is used to represent the display name used when displaying the corresponding business field on the interface. The entity field display control type information is used to represent the control type when displaying the corresponding business field on the interface, such as a text box or a drop-down list.

[0038] Among them, the index configuration information is used to describe the mapping relationship between the index field and the business field. The index field refers to the entity field that creates the index in the search server Elasticsearch, so that the index field can be used to quickly search the full amount of data. The index field may include fixed index fields and search index fields. Fixed index fields are used to map the business fields contained in each type of business data. Fixed index fields may refer to fixed fields in the index structure of the search server, which are used to map fields that exist in each type of business data, such as entity identification information, entity field name, creation time, and update time. Search index fields refer to dynamic fields in the index structure of the search server, which are used to map business fields that can support dynamic search in each type of business data. In different business data, the same fixed index field is mapped to the same business field, and the same search index field can be mapped to different business fields.

[0039] For example, the search index field may include at least one of at least one keyword index field, at least one time index field, and at least one space index field. The keyword index field refers to the index field corresponding to the business field that supports keyword search. The time index field refers to the index field corresponding to the business field that supports time search. The space index field refers to the index field corresponding to the business field that supports spatial location search. Correspondingly, the index configuration information may include: the mapping relationship between the fixed index field and the business field and the mapping relationship between the search index field and the business field. For example, the camera data includes business fields such as camera name name, camera code code, production time production_date, and installation address address. Among them, the mapping relationship between the fixed index field and the business field may include: fixed index field sense_name <-> camera name name, fixed index field sense_code <-> camera code code, etc.; the mapping relationship between the search index field and the business field may include: keyword index field sense_keyword1 <-> camera name name, keyword index field sense_keyword2 <-> installation address address, time index field sense_time1 <-> production_date, etc. By utilizing index configuration information, business data with different data structures can be mapped to search index data with a unified data structure, thereby retaining the semantic differences between different business data while smoothing out their differences in data structure, thereby achieving high-performance search requirements for different business data based on multiple dimensions such as keywords, time and space.

[0040] Among them, the entity relationship configuration information can be used to describe the association relationship between various entities in the business data table. Each business data in the business data table may include information of multiple entities. For example, the camera business data may include camera entity information (object entity), installation location entity information (location entity), entity information of the organization to which it belongs (organization entity), and entity information of the organization that also contains contacts (person entity). There is usually one main entity in the business data, and 0 to multiple associated entities, forming an entity relationship tree. For example, the relationship structure tree formed in the above example is as follows: Figure 2 As shown, the main entity is a camera, the associated entities include the installation location, the organization to which it belongs and the contact person, and the entity relationship includes the installation relationship, the belonging relationship and the organization contact person. The entity relationship configuration information corresponding to each entity relationship in the business data table may include multiple configuration items for describing the entity relationship. For example, the entity relationship configuration information may include: the main entity information, the associated entity information and the entity relationship information corresponding to each two entities in the business data table that have an associated relationship. Among them, the main entity and the associated entity refer to the two entities in the associated relationship. The main entity information may include the entity type (such as an object, a place or an organization, etc.), the entity identification information and the entity name. The associated entity information may also include the entity type (such as an object, a place or an organization, etc.), the entity identification information and the entity name. The entity relationship information may include the entity relationship identification information, the entity relationship name and the entity relationship direction (such as one-way or two-way), etc. It should be noted that the entity relationship configuration is the key configuration information for realizing entity association search and building an entity knowledge graph, so that when searching for a certain entity data, other entity data that has an associated relationship with the entity can also be searched out. For example, when searching for camera information, detailed information of the maintenance personnel other than the camera can also be searched.

[0041] Specifically, developers can configure according to the metadata of the city knowledge system and business data tables based on actual business needs to obtain the business data entity configuration information corresponding to the business data table. Alternatively, developers use visualization tools to configure the configuration template information corresponding to the business data table, and the configuration template information includes: metadata and entity relationship data of the business data table. The template parsing engine can automatically generate the business data entity configuration information corresponding to the business data table based on the basic data of the city knowledge system and the configuration template information corresponding to the business data table. For example, form item configuration information corresponding to each business field in the business data table is generated based on the metadata of the business data table, fixed index fields and search index fields are identified based on the basic data of the city knowledge system, index configuration information is constructed, and entity relationship configuration information is constructed based on entity relationship data, thereby improving the generation efficiency of business data entity configuration information.

[0042] S120 . Based on the business data entity configuration information, entity data in the business data table are entityized to obtain entity data, entity relationship data, entity data index, and entity relationship data index corresponding to the business data.

[0043] Among them, business data may refer to unmaterialized business records stored in a business data table. Each row of data in a business data table represents a piece of business data, that is, a business record. Entity data refers to the data form after the business data entity, and corresponds one to one with the business data. In other words, entity data may refer to the data obtained by expressing business data according to the urban knowledge system. Entity relationship data is data used to describe the entity relationships existing in business data. An entity data index may be an index structure for storing entity data after an entity, so as to facilitate subsequent rapid searches of entity data. An entity relationship data index may be an index structure for storing entity relationship data after an entity, so as to facilitate subsequent rapid searches of entity relationship data.

[0044] Exemplarily, the entity data may include: entity field data corresponding to each business field data in the business data, entity identification information of each entity, and entity data identification information of the entire entity data. Among them, the entity field data refers to the data obtained after the business field data is materialized, that is, the field data that meets the urban knowledge system. The entity identification information can be determined based on the field value of the entity key field and the entity class identification information to which it belongs. For example, the field value of the entity key field and the entity class identification information to which it belongs are spliced ​​to obtain the entity identification information. If there is no field value of the entity key field, the entity identification information cannot be generated, and the entity relationship data corresponding to the entity will not be generated at this time. The entity data identification information can be used to globally uniquely identify the entire entity data. The same entity identification information may exist in different entity data. For example, if the business data of the same person exists in the maintenance personnel business table and the resident business table, the entity data identification information of the two entity data after materialization is different, but the entity identification information is the same.

[0045] Exemplarily, the entity relationship data may include: entity relationship data corresponding to each two entities having an association relationship in the business data and entity relationship data identification information of each entity relationship data. The entity relationship data may include entity relationship identification information, starting point entity identification information and end point entity identification information. The entity relationship data identification information may be used to globally uniquely identify the entire entity relationship data.

[0046] Specifically, based on the business data entity configuration information, each business data in the business data table is entity processed, so that each business data is converted into entity data, entity relationship data, entity data index and entity relationship data index that meet the urban knowledge system, thereby realizing unified processing and storage of business data.

[0047] Exemplarily, step S120 may include: for each piece of business data in the business data table, based on the form item configuration information, processing the business data to determine the entity data corresponding to the piece of business data; based on the entity relationship configuration information, determining the entity relationship data corresponding to the piece of business data; based on the index configuration information, determining the entity data index corresponding to the entity data and the entity relationship data index corresponding to the entity relationship data.

[0048] Specifically, for each piece of business data in the business data table, based on the form item configuration information corresponding to each business field in the business data table, all mapping fields and field values ​​related to the urban knowledge system are extracted from the business data and spliced ​​to obtain the entity field data corresponding to each business field data in the business data. Based on the field value of the entity key field and the entity class identification information to which it belongs, the entity identification information of each entity in the business data is generated. The extracted entity field data and the entity identification information of each entity are assembled to obtain the entity data corresponding to the business data, and the entity data identification information corresponding to the entity data is generated. Based on the entity relationship configuration information corresponding to the business data table and in combination with the generated entity data, the entity relationship data is assembled and generated, that is, the entity relationship data corresponding to each two entities with an association relationship in the business data and the entity relationship data identification information of each entity relationship data are generated. Based on the index configuration information corresponding to the business data table, the entity data and the entity relationship data are indexed and constructed to generate the entity data index and the entity relationship data index.

[0049] S130: Store the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data into a search database.

[0050] Specifically, all entity data, entity relationship data, entity data indexes, and entity relationship data indexes after entityization are stored in the search database of the search server, thereby completing the entityization process of business data. The subsequent search server can quickly search the entire data based on the entity data indexes and entity relationship data indexes in the search database. It should be noted that the entity data index corresponds to part of the entity data for indexing, and the entity relationship data index corresponds to part of the entity relationship data for indexing. When searching, if detailed and comprehensive entity data and entity relationship data are required, the entity data identification information and entity relationship data identification information searched from the entity data index and entity relationship data index can be determined, and based on the entity data identification information and entity relationship data identification information, comprehensive entity data and entity relationship data can be determined from all entity data and all entity relationship data stored in the search database, thereby meeting personalized business needs.

[0051] It should be noted that since different types of business data will be automatically materialized into entity data that meets the city knowledge system according to the corresponding business data materialization configuration information, and all materialized entity data will be stored in the same search database, the universal processing of different types of business data is achieved. There is no need to develop different data warehouse platforms and business systems, which reduces development costs and also achieves high-performance search of the entire amount of entity data.

[0052] The technical solution of this embodiment is to obtain the business data entity configuration information corresponding to the business data table. The business data entity configuration information is obtained by configuring based on the city knowledge system and the metadata of the business data table. Different business data tables are used to store different types of business data. Based on the business data entity configuration information, each business data in the business data table is automatically entityized to obtain the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data, so that each business data in the business data table is automatically entityized into entity data that meets the city knowledge system, and the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data are stored in the search database, so as to quickly search the full amount of data in the search database based on the entity data index and entity relationship data index. By configuring different business data entity configuration information for different business data tables, universal processing of different types of business data is achieved, without the need to develop different data warehouse platforms and business systems, thereby reducing development costs.

[0053] Based on the above technical solution, the business data entity configuration information may also include: at least one of business field statistical indicator information and business field filter item information in the business data table; wherein the field statistical indicator information is used to characterize the business field and perform numerical statistics according to the statistical indicator; the field filter item information is used to characterize the business field as a filter item for data filtering.

[0054] Among them, field statistical indicator information is used to configure business fields in business data tables that need to be numerically counted according to statistical indicators. For example, in a city resident data table, summation statistics are performed according to the age field so that the number of residents of different age groups can be obtained during search, thereby realizing multi-dimensional statistical capabilities of entity data, such as enumeration value aggregation, range aggregation, maximum value, minimum value, sum and average statistical calculations. Field filter item information is used to configure business fields in business data tables that need to be filtered, so that the data of the business field can be filtered during search, thereby meeting user-specific search needs and further improving search efficiency and experience.

[0055] Figure 3 This is a flowchart of another business data processing method provided by an embodiment of the present invention. Based on the above embodiments, this embodiment describes the data search process in detail. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here.

[0056] See also Figure 3 Another service data processing method provided in this embodiment specifically includes the following steps:

[0057] S310. Obtain the business data entity configuration information corresponding to the business data table. The business data entity configuration information is obtained by configuring based on the city knowledge system and the metadata of the business data table. The city knowledge system includes multiple entity classes, field attributes of each entity class and the relationship between entity classes, wherein the entity class is obtained by classifying the city data.

[0058] S320: Based on the business data entity configuration information, each business data in the business data table is entityized to obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data.

[0059] S330: Store the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data into a search database.

[0060] S340, obtaining current search conditions.

[0061] Among them, the current search condition may refer to the search condition input by the user based on the search requirement. For example, the current search condition may be a condition for searching based on a search term. Among them, the search term may include at least one of: keywords, time, and space. For example, the current search condition is: keyword = "Jingjing".

[0062] Alternatively, the current search condition may also be a condition for searching based on the complete business field information. When searching based on the complete business field information, it is necessary to input the configuration identification information template_id corresponding to the business data materialization configuration information at the same time, so as to determine the corresponding business data materialization configuration information based on the template_id, and use the business data materialization configuration information to parse and convert the retrieved index data to obtain the business data finally presented on the interface. Exemplarily, the current search condition includes the complete business field information that needs to be searched currently and the current configuration identification information template_id for limiting the current search scope. For example, for example, the current search condition is: owner = "Zhang San", template_id = "100xx", which means that the business data materialization configuration information is determined based on the template_id, and the index data with the shop owner owner being Zhang San retrieved is parsed based on the business data materialization configuration information to obtain the final business data, that is, entity data.

[0063] S350. Convert the current search condition to obtain a target index condition for searching, and search in the search database based on the target index condition to obtain target index data.

[0064] Specifically, since the search is performed in the entity data index and the entity relationship data index, it is necessary to convert the current search condition into a target index condition for index search. The search server can search in the entity data index and the entity relationship data index based on the target index condition to obtain the retrieved target index data.

[0065] Exemplarily, when the current search condition is a condition for searching based on a search term, "Convert the current search condition to obtain a target index condition for searching" in step S350 may include: using the search term as the field value of the search index field in each business to obtain a target index condition including search index field information.

[0066] Specifically, the search term is used as the field value of all search index fields in each service and concatenated to obtain a target index condition containing search index field information. For example, if the input keyword = "Jingdong", and there are 3 keyword index fields, the converted target index condition is: "sense_keyword1 = Jingdong or sense_keyword2 = Jingdong or sense_keyword3 = Jingdong".

[0067] Exemplarily, when the current search condition is a condition for searching based on complete service field information, step S350 may include: determining the current service data materialization configuration information corresponding to the current search condition based on the current configuration identification information in the current search condition; converting the service field information in the current search condition based on the mapping relationship between the service fields and the index fields in the current service data materialization configuration information to obtain a target index condition containing index field information; and searching the entity data index and the entity relationship data index in the search database based on the target index condition to obtain target index data.

[0068] Specifically, based on the current configuration identification information template_id in the current search condition, determine the current service data materialization configuration information corresponding to the current search condition, obtain the mapping relationship between the service fields and the index fields from the current service data materialization configuration information, and convert the service field information in the current search condition into the corresponding index field information according to the mapping relationship to obtain the converted target index condition. Based on the target index condition, search in the entity data index and the entity relationship data index in the search database to obtain the target index data that meets the target search condition.

[0069] S360. Convert the target index data based on the service data materialization configuration information corresponding to the target index data to determine the target search result data.

[0070] Specifically, since the fields in the target index data are all index fields, it is necessary to use the service data materialization configuration information corresponding to the target index data to convert the index fields in the target index data into the Chinese names of entity fields that users can understand to obtain the converted target search result data, and display the target search result data on the user interface. By using the service data materialization configuration information corresponding to the target index data, the target index data with a general data structure is translated into service display data with a personalized service semantic data structure. The service display data may include a general data part and a personalized data part. The general data part corresponds to general fields such as entity names and creation times, and the personalized data part corresponds to personalized fields of different service data.

[0071] Exemplarily, when the current search condition is a condition for searching based on a search term, step S360 may include: determining the attribute information of the target entity field corresponding to the keyword index field in the target index data based on the business data entity configuration information corresponding to the target index data; based on the attribute information of the target entity field, converting the target index data to determine the target search result data.

[0072] Specifically, since each target index data searched out contains configuration identification information corresponding to the business data entity configuration information, the business data entity configuration information corresponding to each target index data can be determined based on the configuration identification information in the searched out target index data, and the index field information in the corresponding target index data is converted based on the business data entity configuration information to obtain the converted target search result data. For example, if there are multiple target index data, the business data entity configuration information corresponding to each searched out business can be obtained by aggregation based on the configuration identification information in each target index data, and the target index data corresponding to each searched out business can be converted according to the business data entity configuration information to obtain the business data to be displayed, that is, the target search result data. The target search result data is rendered to be displayed on the search result interface.

[0073] For example, the form item configuration information corresponding to a certain business data is: [{"Chinese name": store name; "field name": name; ...},{"Chinese name": store type; "field name": type; ...},{"Chinese name": store owner; "field name": owner; ...}].

[0074] The index configuration information is: [name->sense_name; type->first_header1; owner->first_header2; name->sense_keyword1; …].

[0075] If a target index data obtained when searching with keyword = "Jingjing" is: sense_name = "Jingjing Supermarket (XX Road Store)", first_header1 = "Supermarket", "first_header2" = Zhang San", sense_keyword1 = "Jingjing Supermarket (XX Road Store), then after index field conversion based on the above form item configuration information and index mapping configuration, the target search result data obtained is: store name = "Jingjing Supermarket (XX Road Store)", store type = "Supermarket", owner = Zhang San, thereby obtaining the entire business data containing the keyword "Jingjing".

[0076] Exemplarily, when the current search condition is a condition for searching based on complete business field information, the business data entity configuration information corresponding to the target index data is determined directly based on the current configuration identification information template_id in the current search condition, and the index fields of the target index data are converted according to the form item configuration information and index configuration information in the business data entity configuration information to obtain the target search result data that can be finally displayed.

[0077] Exemplarily, if the business field entered in the current search condition is configured with a statistical function, the target search result includes statistical results. For example, the enumeration values ​​of the camera type field include ball camera, gun camera, and hemispherical camera, etc. When the number of cameras of each type needs to be counted according to this field, the current search condition entered can be: "stat_type = group & stat_field = camera_type & schemaId = camera schemaId". Based on the schemaId in the current search condition, the business data entity configuration information corresponding to the camera data can be determined. If the index field corresponding to the camera type field in the configuration information is sense_text1, the current search condition is converted into a target index condition, that is, "stat_type = group & stat_field = sense_text1 & schemaId = camera schemaId". By searching in the search database based on the target index condition, sense_text1 is aggregated as an aggregation item in the searched target index data, and an aggregation result is obtained, such as {gun camera: 12, ball camera: 10, hemispherical camera: 0}, and the aggregation result is displayed as the target search result data, thereby realizing rapid statistics of business data.

[0078] The technical solution of this embodiment converts the current search conditions to obtain the target index conditions for the search, searches in the search database based on the target index conditions to obtain the target index data, converts the target index data based on the business data entity configuration information corresponding to the target index data, and determines the target search result data, thereby realizing a multi-dimensional rapid search of the entire data set for different types of business data, thereby improving the search efficiency and search experience.

[0079] The following is an embodiment of a business data processing device provided in an embodiment of the present invention. The device and the business data processing methods of the above-mentioned embodiments belong to the same inventive concept. For details not described in detail in the embodiment of the business data processing device, please refer to the embodiment of the above-mentioned business data processing method.

[0080] Figure 4This is a schematic diagram of the structure of a business data processing device provided by an embodiment of the present invention. This embodiment is applicable to the case where business data is automatically converted into entity data that satisfies the city knowledge system. Figure 4 As shown, the device specifically includes: an entity configuration information acquisition module 410, a business data entity processing module 420 and an entity data storage module 430.

[0081] Among them, the entity configuration information acquisition module 410 is used to obtain the business data entity configuration information corresponding to the business data table, and the business data entity configuration information is obtained by configuration based on the city knowledge system and the metadata of the business data table. The city knowledge system includes multiple entity classes, field attributes of each entity class and the relationship between entity classes, wherein the entity class is obtained by classifying city data; the business data entity processing module 420 is used to entity process each business data in the business data table based on the business data entity configuration information, and obtain the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data; the entity data storage module 430 is used to store the entity data, the entity relationship data, the entity data index and the entity relationship data index corresponding to the business data in the search database.

[0082] The technical solution of this embodiment is to obtain the business data entity configuration information corresponding to the business data table. The business data entity configuration information is obtained by configuration based on the city knowledge system and the metadata of the business data table. Different business data tables are used to store different types of business data. Based on the business data entity configuration information, each business data in the business data table is automatically entityized to obtain the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data, so that each business data in the business data table is automatically entityized into entity data that meets the city knowledge system, and the entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data are stored in the search database, so as to perform a fast search of the full amount of data in the search database based on the entity data index and the entity relationship data index. By configuring different business data entity configuration information for different business data tables, universal processing of different types of business data is achieved, without the need to develop different data warehouse platforms and business systems, thereby reducing development costs.

[0083] Optionally, the business data entity configuration information includes: form item configuration information, index configuration information and entity relationship configuration information corresponding to each business field in the business data table; wherein,

[0084] The form item configuration information is used to describe the mapping of business fields to entity field information in the city knowledge system;

[0085] The index configuration information is used to describe the mapping relationship between the index field and the business field;

[0086] The entity relationship configuration information is used to describe the association relationship between various entities existing in the business data table.

[0087] Optionally, the form item configuration information includes: the entity to which the business field is mapped in the city knowledge system and entity field attribute information; wherein the entity field attribute information includes: at least one of entity field identification information, entity field name, entity field Chinese name, entity field data type information, entity field display name and entity field display control type information;

[0088] The index configuration information includes: a mapping relationship between a fixed index field and a business field and a mapping relationship between a search index field and a business field, wherein the fixed index field is used to map a business field included in each business data, and the search index field includes: at least one of a keyword index field, a time index field, and a space index field;

[0089] The entity relationship configuration information includes: main entity information, associated entity information and entity relationship information corresponding to every two entities having an associated relationship in the business data table.

[0090] Optionally, the business data entity configuration information further includes: at least one of business field statistical indicator information and business field filter item information in the business data table; wherein,

[0091] The field statistical indicator information is used to represent the numerical statistics of the business field according to the statistical indicator;

[0092] The field filter item information is used to represent the business field as a filter item for data filtering.

[0093] Optionally, the business data entity processing module 420 is specifically used to:

[0094] For each business data in the business data table, the business data is processed based on the form item configuration information to determine the entity data corresponding to the business data; based on the entity relationship configuration information, the entity relationship data corresponding to the business data is determined; based on the index configuration information, the entity data index corresponding to the entity data and the entity relationship data index corresponding to the entity relationship data are determined.

[0095] Optionally, the entity data includes: entity field data corresponding to each business field data in the business data, entity identification information of each entity, and entity data identification information of the entire entity data; wherein the entity identification information is determined based on the field value of the entity key field and the entity class identification information to which it belongs;

[0096] The entity relationship data includes: entity relationship data corresponding to every two entities having an association relationship in the business data and entity relationship data identification information of each entity relationship data.

[0097] Optionally, the device further comprises:

[0098] The current search condition acquisition module is used to obtain the current search condition;

[0099] A current search condition conversion module, used to convert the current search condition to obtain a target index condition for searching, and search in the search database based on the target index condition to obtain target index data;

[0100] The target index data conversion module is used to convert the target index data based on the business data entity configuration information corresponding to the target index data to determine the target search result data.

[0101] Optionally, the current search condition is a condition for searching based on a search term, wherein the search term includes: at least one of a keyword, time and space;

[0102] The current search condition conversion module is specifically used to: use the search term as the field value of the search index field in each business to obtain a target index condition containing the search index field information;

[0103] The target index data conversion module is specifically used to: determine the attribute information of the target entity field corresponding to the keyword index field in the target index data based on the business data entity configuration information corresponding to the target index data; based on the attribute information of the target entity field, convert the target index data to determine the target search result data.

[0104] Optionally, the current search condition is a condition for searching based on complete business field information;

[0105] The current search condition conversion module is specifically used to: determine the current business data entity configuration information corresponding to the current search condition based on the current configuration identification information in the current search condition; convert the business field information in the current search condition based on the mapping relationship between the business field and the index field in the current business data entity configuration information to obtain the target index condition containing the index field information; based on the target index condition, search the entity data index and the entity relationship data index in the search database to obtain the target index data.

[0106] The business data processing device provided in the embodiment of the present invention can execute the business data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the business data processing method.

[0107] It is worth noting that in the embodiment of the above-mentioned business data processing device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0108] Figure 5 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. Figure 5 A block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 5 The electronic device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0109] like Figure 5 As shown, the electronic device 12 is in the form of a general purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0110] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0111] The electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0112] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory 30 (RAM) and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 5 not shown, usually called a "hard drive"). Although Figure 5 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0113] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0114] The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 12, and / or may communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. Furthermore, the electronic device 12 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0115] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing a business data processing method provided by any embodiment of the present invention, the method comprising:

[0116] Obtaining business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class, and relationships between entity classes, wherein the entity class is obtained by classifying city data;

[0117] Based on the business data entity configuration information, each business data in the business data table is entity processed to obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data;

[0118] The entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index are stored in a search database.

[0119] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the business data processing method provided by any embodiment of the present invention.

[0120] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the business data processing method provided in any embodiment of the present invention are implemented. The method includes:

[0121] Obtaining business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class, and relationships between entity classes, wherein the entity class is obtained by classifying city data;

[0122] Based on the business data entity configuration information, each business data in the business data table is entity processed to obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data;

[0123] The entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index are stored in a search database.

[0124] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0125] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0126] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0127] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0128] An embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements the business data processing method provided by any embodiment of the present invention.

[0129] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0130] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0131] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A business data processing method, characterized in that: include: Obtaining business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class, and relationships between entity classes, wherein the entity class is obtained by classifying city data; Based on the business data entity configuration information, each business data in the business data table is entity processed to obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data; The entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index are stored in a search database.

2. The method according to claim 1, characterized in that The business data entity configuration information includes: form item configuration information, index configuration information and entity relationship configuration information corresponding to each business field in the business data table; wherein, The form item configuration information is used to describe the mapping of business fields to entity field information in the city knowledge system; The index configuration information is used to describe the mapping relationship between the index field and the business field; The entity relationship configuration information is used to describe the association relationship between various entities existing in the business data table.

3. The method according to claim 2, characterized in that The form item configuration information includes: the entity to which the business field is mapped in the city knowledge system and the entity field attribute information; wherein the entity field attribute information includes: at least one of entity field identification information, entity field name, entity field Chinese name, entity field data type information, entity field display name and entity field display control type information; The index configuration information includes: a mapping relationship between a fixed index field and a business field and a mapping relationship between a search index field and a business field, wherein the fixed index field is used to map a business field included in each business data, and the search index field includes: at least one of a keyword index field, a time index field, and a space index field; The entity relationship configuration information includes: main entity information, associated entity information and entity relationship information corresponding to every two entities having an associated relationship in the business data table.

4. The method according to claim 2, characterized in that: The business data entity configuration information also includes: at least one of business field statistical indicator information and business field filter item information in the business data table; wherein, The field statistical indicator information is used to represent the numerical statistics of the business field according to the statistical indicator; The field filter item information is used to represent the business field as a filter item for data filtering.

5. The method according to claim 2, characterized in that: The step of performing entity processing on each piece of business data in the business data table based on the business data entity configuration information to obtain entity data, entity data index, entity relationship data and entity relationship data index corresponding to the business data includes: For each piece of business data in the business data table, based on the form item configuration information, the business data is processed to determine the entity data corresponding to the piece of business data; Based on the entity relationship configuration information, determine the entity relationship data corresponding to the business data; Based on the index configuration information, an entity data index corresponding to the entity data and an entity relationship data index corresponding to the entity relationship data are determined.

6. The method according to claim 5, characterized in that The entity data includes: entity field data corresponding to each business field data in the business data, entity identification information of each entity and entity data identification information of the entire entity data; wherein the entity identification information is determined based on the field value of the entity key field and the entity class identification information to which it belongs; The entity relationship data includes: entity relationship data corresponding to every two entities having an association relationship in the business data and entity relationship data identification information of each entity relationship data.

7. The method according to any one of claims 1 to 6, characterized in that: After storing the entity data, the entity relationship data, the entity data index and the entity relationship data index corresponding to the business data in a search database, the method further includes: Get the current search criteria; Converting the current search condition to obtain a target index condition for searching, and searching in the search database based on the target index condition to obtain target index data; Based on the business data entity configuration information corresponding to the target index data, the target index data is converted to determine the target search result data.

8. The method according to claim 7, characterized in that The current search condition is a condition for searching based on a search term, wherein the search term includes: at least one of a keyword, time and space; The converting the current search condition to obtain a target index condition for searching includes: Using the search term as the field value of the search index field in each business, obtaining a target index condition containing the search index field information; The converting the target index data based on the business data entity configuration information corresponding to the target index data to determine the target search result data includes: Determining attribute information of a target entity field corresponding to a keyword index field in the target index data based on the business data entity configuration information corresponding to the target index data; Based on the attribute information of the target entity field, the target index data is converted to determine the target search result data.

9. The method according to claim 7, characterized in that: The current search condition is a condition for searching based on complete business field information; The converting the current search condition to obtain a target index condition for searching, and searching the search database based on the target index condition to obtain target index data, includes: Based on the current configuration identification information in the current search condition, determine the current business data entity configuration information corresponding to the current search condition; Based on the mapping relationship between the business field and the index field in the current business data entity configuration information, the business field information in the current search condition is converted to obtain a target index condition containing the index field information; Based on the target index condition, the entity data index and the entity relationship data index in the search database are searched to obtain the target index data.

10. A business data processing device, characterized in that: include: The entity configuration information acquisition module is used to acquire the business data entity configuration information corresponding to the business data table, wherein the business data entity configuration information is obtained by configuring based on the city knowledge system and the metadata of the business data table, wherein the city knowledge system includes multiple entity classes, field attributes of each entity class and relationships between entity classes, wherein the entity class is obtained by classifying the city data; A business data entity processing module, used to perform entity processing on each business data in the business data table based on the business data entity configuration information, and obtain entity data, entity relationship data, entity data index and entity relationship data index corresponding to the business data; The entity data storage module is used to store the entity data corresponding to the business data, the entity relationship data, the entity data index and the entity relationship data index in a search database.

11. An electronic device, characterized in that: The electronic device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the business data processing method as described in any one of claims 1-9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the business data processing method as described in any one of claims 1 to 9 is implemented.

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the business data processing method as described in any one of claims 1 to 9.

Images