Multi-message touch communication metadata management platform and use method thereof

Abstract

The invention discloses a multi-message touch communication metadata management platform and a use method thereof. The platform comprises a storage layer, a configuration layer and a service layer. Wherein the storage layer is used for storing customer data; a metadata field configuration table and a metadata engine are arranged in the configuration layer; the configuration layer is used for calling a metadata engine to query the client data stored in the storage layer according to a metadata field configuration table according to an input instruction, and generating a corresponding output response; and the business layer is used for providing a front-end interaction interface to receive an input instruction and display an output response. According to the platform, basic information, service attributes and contact information of clients are stored in a sub-table mode, and meanwhile, definitions of different extension fields and message fields are established through an independent metadata field configuration table, so that the service attributes and the contact information conforming to the definitions can be obtained through searching of the same metadata; the method adapts to standardized access of various business attributes and contact information, and provides omni-channel message touch service.

Description

Technical Field

[0001] This invention relates to the field of communication management technology, specifically to a communication metadata management platform with multiple message reach and its usage method. Background Technology

[0002] In the wave of digital transformation, enterprise communication systems face multiple technical challenges. First, the extended identifiers used by customers in different industries vary significantly. For example, the financial industry commonly uses account numbers, while the government sector typically uses national ID numbers. These industry differences easily lead to inconsistent customer identification systems, further increasing the complexity of integrating communication management systems.

[0003] Secondly, a communication management system needs to simultaneously access multiple heterogeneous contact methods such as 5G-RCS, SMS, and WeChat. Each customer may have more than ten different terminal types, which will further increase the difficulty of communication data access and maintenance.

[0004] Furthermore, weak dynamic scalability is also a key issue. Traditional address books use a fixed table structure to store customer information. Adding new fields, such as age or 5G terminal number, requires modifying the table structure definition language, and may even require system downtime for maintenance. This not only increases the development and maintenance costs of the system, but may also affect the system's stability and availability. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a communication metadata management platform with multiple message reach and a method for using it.

[0006] The first aspect of this invention provides a communication metadata management platform with multiple message reach, including a storage layer, a configuration layer, and a business layer; The storage layer is used to store customer data; The configuration layer includes a metadata field configuration table and a metadata engine. The configuration layer is used to call the metadata engine to query the customer data stored in the storage layer based on the metadata field configuration table according to the input command, and generate the corresponding output response. The business layer is used to provide a front-end interactive interface for receiving input commands and displaying output responses.

[0007] Furthermore, the storage layer includes a main table, an extended table, and a terminal table; The main table stores the customer's basic information. The extended table stores the customer's business attributes; The terminal table stores the customer's contact information.

[0008] Furthermore, the customer's basic information consists of an ID field, a name field, and a status field; wherein, the ID field is used to record the customer's ID, the name field is used to record the customer's name, and the status field is used to record the customer's status. The customer's extended attributes consist of an ID field and multiple extended fields; wherein, the ID field is used to record the customer's ID, and each of the extended fields records different business attributes of the customer. The customer's contact information consists of an ID field and multiple message fields; wherein, the ID field is used to record the customer's ID, and each message field records a different contact method for the customer.

[0009] Furthermore, the metadata field configuration table records the metadata and corresponding definitions of various extended fields and message fields in the storage layer; the metadata engine queries the corresponding metadata from the storage layer according to the metadata field configuration table, and then obtains the corresponding customer data.

[0010] Another aspect of the present invention discloses a communication data retrieval method, applied to the aforementioned multi-message delivery communication metadata management platform, comprising the following steps: Get input commands; The input instruction is parsed to determine the target metadata corresponding to the input instruction; Based on the target metadata, the metadata engine is used to query the customer data stored in the storage layer and generate a corresponding output response. The output response is displayed.

[0011] Furthermore, the step of parsing the input instruction to determine the target metadata corresponding to the input instruction specifically includes the following steps: The input command is parsed to determine its key fields; The key fields are used to match the metadata field configuration table to determine the degree of matching between the key fields and the corresponding definition of each metadata. Metadata with a matching degree higher than a preset threshold will be used as target metadata.

[0012] Furthermore, the step of querying the customer data stored in the storage layer using the metadata engine based on the target metadata and generating a corresponding output response specifically includes the following steps: Traverse the extended tables of the storage layer based on the target metadata; determine the target extended field pointed to by the target metadata; Determine the target customer number based on the target extended field; The target customer number is used to look up the message field corresponding to the target customer number in the terminal table of the storage layer. Based on the metadata of the message fields, determine the customer's target contact information; The customer's target contact information is encapsulated into an output response and returned to the business layer.

[0013] Another aspect of this invention discloses a communication data extension method, applied to the aforementioned multi-message delivery communication metadata management platform, comprising the following steps: Identify the target customer data to be expanded; Select the target extended field metadata and / or target message field metadata corresponding to the target customer data in the metadata field configuration table; The target customer data is encapsulated using the target extended field metadata and / or target message field metadata, and a customer number is added to form the target extended field and / or target message field; Add the target extended fields and / or target message fields to the extended tables and / or terminal tables of the storage layer under the corresponding customer's extended attributes and / or contact information.

[0014] Furthermore, in the step of selecting the target extended field metadata and / or target message field metadata corresponding to the target customer data in the metadata field configuration table, if the corresponding target extended field metadata and / or target message field metadata does not exist in the metadata field configuration table, new metadata is added as the target extended field metadata and / or target message field metadata.

[0015] Furthermore, the addition of new metadata as target extended field metadata and / or target message field metadata specifically includes the following steps: Determine the metadata available in the extended table and / or terminal table; Select the target metadata from the available metadata and set the corresponding definition for the target metadata; Write the target metadata and its definition into the metadata field configuration table.

[0016] This invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the aforementioned method.

[0017] The embodiments of the present invention have the following beneficial effects: The communication metadata management platform and its usage method provided by the present invention offer a conveniently expandable communication management platform design. The platform stores customer basic information, business attributes, and contact information in separate tables, making it easy to modify customer business attributes and contact information without having to modify them along with the customer's basic information. Simultaneously, the present invention establishes definitions for different extended fields and message fields through independent metadata field configuration tables, allowing business attributes and contact information that conform to the definitions to be found through the same metadata. Furthermore, it can also point to new business attributes and contact information by adding new definitions to available metadata, adapting to standardized access for various business attributes and contact information, and providing omnichannel message delivery services. Finally, the learning cost of this application is low; business personnel can complete field and message channel management through a visual interface without writing code, effectively improving operational convenience and efficiency.

[0018] Additional aspects and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description or may be learned by practice of the invention. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of the basic architecture of a multi-message delivery communication metadata management platform according to the present invention; Figure 2 This is a schematic diagram of the message interaction process of a communication data retrieval method according to the present invention; Figure 3 This is a schematic diagram of the message interaction process of a communication data extension method according to the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0022] like Figure 1 As shown, the first embodiment of the present invention provides a communication metadata management platform for multi-message delivery, including a storage layer, a configuration layer and a business layer; The storage layer stores customer data; the configuration layer contains a metadata field configuration table and a metadata engine; the configuration layer uses the metadata engine to query the customer data stored in the storage layer based on the metadata field configuration table according to the input command, and generates the corresponding output response; the business layer provides a front-end interactive interface for receiving input commands and displaying output responses.

[0023] The following is a detailed description of each logical level of the present invention: Storage layer: In this embodiment of the invention, the storage layer includes a main table, an extended table, and a terminal table.

[0024] Main table: The main table in the storage layer stores basic customer information, such as customer ID (generated using the Snowflake ID algorithm when the customer is created, serving as a globally unique identifier for the customer, hereinafter referred to as code), customer name, and customer status (e.g., activated, deactivated, etc.). It should be noted that basic customer information can also include the customer's activation time, registration address, etc., and is not limited to the information mentioned above.

[0025] In the main table, different basic information is recorded through different fields. For example, the customer ID is recorded in the ID field, the name field records the customer's name, and the status field records the customer's status. Since the information in the main table is the most core identity information of the customer and is usually not easily modified, modifications to the basic customer information in the main table must be performed in a static environment, and cannot be dynamically modified through the business layer frontend.

[0026] Extended Tables: The extended tables in the storage layer store customer business attributes. Due to industry differences, customers in different industries typically have different business attributes. For example, the business attribute for financial industry customers is their account number; the business attribute for government industry customers is their ID card number, etc. Different types of business attributes are encapsulated in different extended fields.

[0027] Specifically, each extended field in the extended table is represented as "code, ext_type: data". This includes the customer ID (e.g., code=bcas) and specific business attributes (e.g., ext_1: abcXXXXefgh). The extended fields themselves are characterized through metadata. The customer ID is used to join with the main table, thereby indexing the corresponding customer, while the metadata is used to index the definitions of the business attributes.

[0028] For different types of business attributes, this embodiment of the invention distinguishes them by extending the metadata of the fields, such as ext_1 representing the customer's fund account number, ext_2 representing the customer's ID number, etc.; different types of business attributes are distinguished by metadata.

[0029] Terminal Table: The terminal table in the storage layer stores customer contact information. Since a customer may have multiple contact methods from different channels, the terminal table records these different contact methods through different message fields.

[0030] Specifically, each message field is represented in the terminal table as "code, terminal_type: terminal". This includes the customer ID (e.g., code=bcas) and specific contact information (e.g., terminal_1: 123XXXX7890). The specific type of contact information is distinguished through the metadata of the message field; for example, terminal_1 represents the customer's mobile phone number, terminal_2 represents the customer's WeChat ID, and terminal_3 represents the customer's communication account, etc.

[0031] The above design allows for separate storage of basic customer information, business attributes, and contact information. This simplifies the modification of customer business attributes and contact information without affecting the platform's ability to retrieve customer communication data, and facilitates the expansion of more customer business attributes and contact information.

[0032] Configuration Layer: In this embodiment of the invention, the configuration layer consists of a metadata field configuration table and a metadata engine. The metadata field configuration table records the metadata and corresponding definitions of various extended fields and message fields in the storage layer; the metadata engine queries the corresponding metadata from the storage layer based on the metadata field configuration table to obtain the corresponding customer data.

[0033] For example, the metadata field corresponding to an extended field is represented in the metadata field configuration table as "field_name, field_category, field_mapping", where "field_name" is the display name of the metadata field in the metadata field configuration table, "field_category" is the definition of the metadata field in the metadata field configuration table, and "field_mapping" is the metadata corresponding to the metadata field in the metadata field configuration table, which is associated with the corresponding extended field.

[0034] The metadata definition of message fields is similar to that of extended fields. For example, for the metadata field "Preferred contact method, mobile number, terminal_1", "Preferred contact method" represents the display name of this metadata field in the metadata field configuration table, "mobile number" represents the definition of this metadata field in the metadata field configuration table, and "terminal_1" represents the metadata corresponding to this metadata field. Therefore, the field "terminal_1: 123XXXX7890" in the storage layer terminal table represents the mobile number in the customer's contact information.

[0035] In this embodiment of the invention, the metadata engine searches the extended table and terminal table in the storage layer based on the metadata field configuration table to obtain the corresponding customer data. For example, if the metadata engine parses the input command to find the customer's mobile phone number, it will search the metadata field configuration table for definitions related to "mobile phone number" to find the corresponding metadata field (e.g., "preferred contact method, mobile phone number, terminal_1"). From this metadata field, it determines that the metadata corresponding to the mobile phone number is "terminal_1". Finally, it searches the terminal table for the message field corresponding to "terminal_1" to obtain the customer's mobile phone number.

[0036] Business layer: In this embodiment of the invention, the business layer is used to provide a message interface, through which business personnel send input commands and receive corresponding output responses.

[0037] In summary, the multi-message reach communication metadata management platform provided by the embodiments of the present invention has a metadata-driven address book architecture, supports the differences in account systems across multiple industries, can quickly adapt to the customized needs of industries such as finance and government, and reduce development and maintenance costs.

[0038] like Figure 2 As shown, the second embodiment of the present invention provides a communication data retrieval method, applied to the multi-message-reaching communication metadata management platform of the first embodiment, including the following steps: S101. Obtain input instructions.

[0039] This embodiment of the invention uses finding customer contact information based on business attributes as an example. The platform's input instructions include the customer's business attributes, such as "ID number: 123XXXX7890, mobile phone number required".

[0040] S102. Parse the input command and determine the target metadata corresponding to the input command; Specifically, step S102 parses the input instruction to determine the target metadata corresponding to the input instruction, which includes the following steps: S102-1. Parse the input command to determine its key fields; After obtaining the input command, in this embodiment of the invention, a text parsing algorithm is applied at the business layer to parse the text and split the input command into multiple key fields, such as "ID number", "123XXXX7890", "mobile phone number", etc.

[0041] S102-2. Use key fields to match in the metadata field configuration table to determine the degree of matching between the key fields and the corresponding definitions of each metadata.

[0042] S102-3. Use metadata with a matching degree higher than a preset threshold as target metadata.

[0043] After splitting the key fields, this embodiment of the invention matches the metadata field configuration table based on the key fields, and selects metadata with a matching degree higher than a preset threshold as target metadata. For example, for the key field "ID number", there is a metadata field with a high matching degree of "government customer business, ID number, ext_2" in the metadata field configuration table, while the matching degree of the other metadata fields is low; the key field "mobile phone number" corresponds to the metadata field "preferred contact method, mobile phone number, terminal_1"; while "123XXXX7890" does not have a metadata field with a high matching degree.

[0044] S103. Based on the target metadata, use the metadata engine to query the customer data stored in the storage layer and generate the corresponding output response; Specifically, step S103 uses the metadata engine to query the customer data stored in the storage layer based on the target metadata and generates the corresponding output response, which includes the following steps: S103-1. Traverse the extended tables of the storage layer based on the target metadata; determine the target extended field pointed to by the target metadata.

[0045] In this embodiment of the invention, after determining the target metadata, the extended tables of the storage layer are traversed using the target metadata to obtain the target extended field pointed to by the extended tables. For example, the metadata engine can determine the extended field indicating the ID number in the extended table through the metadata of "ext_2", and then determine the target extended field through an exact match of "123XXXX7890".

[0046] S103-2. Determine the target customer number based on the target extended field.

[0047] After determining the target extended field, since the target extended field contains the customer ID "code", the target customer ID can be obtained.

[0048] S103-3. Use the target customer number to search in the terminal table of the storage layer to determine the message field corresponding to the target customer number; S103-4. Determine the customer's target contact information based on the metadata of the message fields.

[0049] After obtaining the target customer ID, the metadata engine can determine the corresponding message field through the customer ID "code", and then obtain the customer's target contact information through the metadata "terminal_1" of the message field.

[0050] S103-5. Encapsulate the customer's target contact information into an output response and return it to the business layer.

[0051] S104. Display the output response.

[0052] After obtaining the contact information, the business layer frontend assembles the target contact information into a standard format data object and returns it to the business interface that initiated the request. The contact information is then presented at the business interface, completing the communication data search process.

[0053] like Figure 3 As shown, the third embodiment of the present invention discloses a communication data extension method, applied to the multi-message delivery communication metadata management platform of the first embodiment, including the following steps: S201. Identify the target customer data to be expanded.

[0054] This embodiment of the invention is illustrated by adding a new customer contact method as an example. It is assumed that the added contact method is "Dashu Company, WeChat account, da_shu".

[0055] S202. In the metadata field configuration table, select the target extended field metadata and / or target message field metadata corresponding to the target customer data.

[0056] After determining the target customer data, this embodiment of the invention selects the corresponding target message field metadata in the metadata field configuration table. For example, if the metadata field corresponding to a WeChat account is "WeChat contact information, WeChat, terminal_2", then the target message field metadata corresponding to the target customer data is determined to be "terminal_2".

[0057] S203. Encapsulate the target customer data using the target extended field metadata and / or target message field metadata, and add a customer number to form the target extended field and / or target message field.

[0058] After determining the target message field metadata, this embodiment of the invention obtains the customer number "btre" corresponding to "Dashu Company" from the main table, and then encapsulates the target customer data in the format of the extended table and / or terminal table to form the target extended field and / or target message field, such as "btre, terminal_2: da_shu".

[0059] S204. Add the target extended field and / or target message field to the extended attributes and / or contact information of the corresponding customer in the extended table and / or terminal table of the storage layer.

[0060] Finally, the data records encapsulated by S203 are routed according to their type and customer code using a hash sharding algorithm and then persistently inserted into the corresponding physical database table.

[0061] In some embodiments, the added customer data may lack a corresponding definition in the metadata field configuration table. When the corresponding target extended field metadata and / or target message field metadata does not exist in the metadata field configuration table, this embodiment of the invention adds new metadata as the target extended field metadata and / or target message field metadata.

[0062] Adding new metadata as target extended field metadata and / or target message field metadata includes the following steps: S202-1. Determine the metadata available in the extended table and / or terminal table; S202-2. Select the target metadata from the available metadata and set the corresponding definition for the target metadata; S202-3. Write the target metadata and its definition into the metadata field configuration table.

[0063] For example, the message field metadata supported by the terminal table includes terminal_1~10, where terminal_1~9 are already occupied by other contact methods, and terminal_10 is the metadata available in the terminal table. In this embodiment of the invention, "terminal_10" is used as the target metadata, and a metadata field of "WeChat contact method, WeChat, terminal_10" is added to the metadata field configuration table of the configuration layer, so that message fields with WeChat as the contact method can be added to the terminal table.

[0064] In summary, the embodiments of the present invention have at least the following beneficial effects: The communication metadata management platform and its usage method for multi-message reach of the present invention store customer data in separate tables and assemble it with customer number as a feature value, making it easy to modify the business attributes and contact information of customers without having to modify them together with the customer's basic information.

[0065] Meanwhile, this invention establishes definitions for different extended fields and message fields through an independent metadata field configuration table, so that business attributes and contact information that conform to the definition can be found through the same metadata. In addition, it can also point to new business attributes and contact information by adding new definitions to available metadata, adapting to the standardized access of multiple business attributes and contact information, and providing omnichannel message delivery services.

[0066] Finally, this application has a low learning curve, and business personnel can manage fields and message channels through a visual interface without writing code, which can effectively improve the ease of operation and efficiency.

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

[0068] Those skilled in the art will understand that modules in the device of the embodiments of the present invention can be adaptively modified and placed in one or more devices different from those embodiments. Modules, units, or components in the embodiments of the present invention can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the corresponding claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the corresponding claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0069] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0070] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0071] Furthermore, the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. In particular, for embodiments such as apparatus and devices, since they are basically similar to the method embodiments, the relevant parts can be referred to the description of the method embodiments. The apparatus, devices, and other embodiments described above are merely illustrative, and the modules, units, etc., described as separate components may or may not be physically separate, that is, they may be located in one place or distributed in multiple places, such as nodes in a system network. Specifically, some or all of the modules and units can be selected according to actual needs to achieve the purpose of the above-described embodiment solutions. Those skilled in the art can understand and implement this without creative effort.

[0072] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0073] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0074] Furthermore, the terms "first," "second," etc., used in the embodiments of this invention are for descriptive purposes only and should not be construed as indicating or implying relative importance, or implicitly specifying the number of technical features indicated in this embodiment. Therefore, features defined with terms such as "first" and "second" in the embodiments of this invention can explicitly or implicitly indicate that the embodiment includes at least one of those features. In the description of this invention, the word "multiple" means at least two or more, such as two, three, four, etc., unless otherwise explicitly specified in the embodiments.

[0075] In embodiments of the present invention, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of the present invention may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0076] Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention. Other embodiments of the present invention will readily conceive of by considering the specification and practicing the invention. This application is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

Claims

1. A communication metadata management platform with multi-message reach, characterized in that, It includes a storage layer, a configuration layer, and a business layer; The storage layer is used to store customer data; The configuration layer includes a metadata field configuration table and a metadata engine. The configuration layer is used to call the metadata engine to query the customer data stored in the storage layer based on the metadata field configuration table according to the input command, and generate the corresponding output response. The business layer is used to provide a front-end interactive interface for receiving input commands and displaying output responses.

2. The communication metadata management platform for multi-message delivery according to claim 1, characterized in that, The storage layer includes a main table, an extended table, and a terminal table. The main table stores the customer's basic information. The extended table stores the customer's business attributes; The terminal table stores the customer's contact information.

3. The communication metadata management platform for multi-message delivery according to claim 2, characterized in that, The customer's basic information consists of an ID field, a name field, and a status field; wherein, the ID field is used to record the customer's ID, the name field is used to record the customer's name, and the status field is used to record the customer's status. The customer's extended attributes consist of an ID field and multiple extended fields; wherein, the ID field is used to record the customer's ID, and each of the extended fields records different business attributes of the customer. The customer's contact information consists of an ID field and multiple message fields; wherein, the ID field is used to record the customer's ID, and each message field records a different contact method for the customer.

4. A communication metadata management platform for multi-message delivery according to claim 3, characterized in that, The metadata field configuration table records the metadata and corresponding definitions of various extended fields and message fields in the storage layer; the metadata engine queries the corresponding metadata from the storage layer based on the metadata field configuration table to obtain the corresponding customer data.

5. A communication data retrieval method, applied to a multi-message delivery communication metadata management platform as described in any one of claims 1-4, characterized in that, Includes the following steps: Get input commands; The input instruction is parsed to determine the target metadata corresponding to the input instruction; Based on the target metadata, the metadata engine is used to query the customer data stored in the storage layer and generate a corresponding output response. The output response is displayed.

6. The communication data retrieval method according to claim 5, characterized in that, The step of parsing the input instruction to determine the target metadata corresponding to the input instruction specifically includes the following steps: The input command is parsed to determine its key fields; The key fields are used to match the metadata field configuration table to determine the degree of matching between the key fields and the corresponding definition of each metadata. Metadata with a matching degree higher than a preset threshold will be used as target metadata.

7. The communication data retrieval method according to claim 5, characterized in that, The process of querying customer data stored in the storage layer using the metadata engine based on the target metadata and generating a corresponding output response specifically includes the following steps: Traverse the extended tables of the storage layer based on the target metadata; determine the target extended field pointed to by the target metadata; Determine the target customer number based on the target extended field; The target customer number is used to look up the message field corresponding to the target customer number in the terminal table of the storage layer. Based on the metadata of the message fields, determine the customer's target contact information; The customer's target contact information is encapsulated into an output response and returned to the business layer.

8. A communication data extension method, applied to a multi-message delivery communication metadata management platform as described in any one of claims 1-4, characterized in that, Includes the following steps: Identify the target customer data to be expanded; Select the target extended field metadata and / or target message field metadata corresponding to the target customer data in the metadata field configuration table; The target customer data is encapsulated using the target extended field metadata and / or target message field metadata, and a customer number is added to form the target extended field and / or target message field; Add the target extended fields and / or target message fields to the extended tables and / or terminal tables of the storage layer under the corresponding customer's extended attributes and / or contact information.

9. A communication data extension method according to claim 8, characterized in that, In the step of selecting the target extended field metadata and / or target message field metadata corresponding to the target customer data in the metadata field configuration table, if the corresponding target extended field metadata and / or target message field metadata does not exist in the metadata field configuration table, new metadata is added as the target extended field metadata and / or target message field metadata.

10. A communication data extension method according to claim 9, characterized in that, The process of adding new metadata as target extended field metadata and / or target message field metadata specifically includes the following steps: Determine the metadata available in the extended table and / or terminal table; Select the target metadata from the available metadata and set the corresponding definition for the target metadata; Write the target metadata and its definition into the metadata field configuration table.

Images