Social interaction system

Through modular construction and standardization of data models, combined with adaptation layer and task management subsystem, the flexibility, concurrent processing and data reliability of the existing social interaction platform are solved, and the user experience and platform stability are improved.

CN119045786AInactive Publication Date: 2024-11-29HEBEI TONGFU SHARING TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411181338.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-11-29
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing social interaction platforms face difficulties in the system to quickly adapt to new needs, insufficient concurrency processing capabilities, problems of data consistency and reliability, and insufficient real-time and accuracy of message push, which affects user experience and platform stability.

Method used

Modular construction is adopted to build a common underlying data model, define and standardize the data structure association, establish an adaptation layer to achieve efficient interaction, introduce a task management subsystem, diversify configuration templates, design functional switches and downgrade strategies, and improve system flexibility and stability .

Benefits of technology

It significantly improves user experience and platform stability, enhances system flexibility, scalability and data reliability, and improves task processing automation level and message delivery efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119045786A_ABST
    Figure CN119045786A_ABST
Patent Text Reader

Abstract

The invention relates to a social interaction system which comprises the following steps: firstly, analyzing prd and dividing functional modules, and distributing input and output parameters and permission constraints for each module; then, constructing a data interaction framework between the modules, and determining data transmission conditions; on the basis, a front-end system framework is built; configuring a social activity playing method template, and verifying through the user behavior simulation data set; an operation end management interface is created, an adaptation layer is set up, and smooth interaction among the management interface, the playing method template and the front-end framework is achieved through an adapter. According to the method, flexible iteration is supported through modular construction and a general underlying data model, data structure association is defined and standardized, an adaptation layer is established to achieve efficient interaction, a task management subsystem is introduced to improve the automation level, template diversification is configured to enhance flexibility, and a function switch and a degradation strategy are designed to guarantee stability and expandability of the system; therefore, efficient, flexible and reliable social interaction experience is provided, and user experience and stickiness are remarkably improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, in particular to a social interaction system. Background Art

[0002] Existing social interaction platforms face many challenges in their technical implementation.

[0003] First, due to the frequent iteration of social platform gameplay, the existing system is difficult to quickly adapt to new needs, affecting development efficiency and online speed. It is necessary to optimize this to enhance the flexibility and scalability of the system;

[0004] Secondly, the system's insufficient high-concurrency processing capability is also a major problem. Especially during large-scale events, the system is prone to slow response or even crash due to overload, which poses a serious threat to user experience and business continuity. Therefore, the system architecture needs to be optimized to improve concurrent processing capabilities, and it is also necessary to consider how to strengthen monitoring and early warning mechanisms.

[0005] Thirdly, the data consistency and reliability of the system should not be ignored. Especially in key links such as task execution and reward distribution where the amount of interactive information is huge, a sound data management and verification mechanism must be established to ensure the integrity, consistency and reliability of the data and avoid damage caused by data errors or loss.

[0006] Finally, the real-time and accuracy of the system's message push is also the key to improving user experience. Users need to obtain task progress, reward notifications and other information in a timely and accurate manner, so we need to continuously optimize the message push mechanism to ensure the effective communication of information.

[0007] To sum up, to solve the technical problems of existing social interaction platforms, we need to start from multiple aspects such as enhancing system flexibility, improving concurrent processing capabilities, ensuring data reliability, and optimizing message push mechanisms, so as to comprehensively improve user experience and platform stability.

[0008] The information disclosed in this background technology section is only intended to deepen the understanding of the overall background technology of the present invention, and should not be regarded as acknowledging or suggesting in any form that the information constitutes the prior art already known to those skilled in the art. Summary of the invention

[0009] In view of the defects existing in the prior art, the purpose of the present invention is to provide a social interaction system, which supports flexible iteration through modular construction and a common underlying data model, defines and normalizes data structure associations, establishes an adaptation layer to achieve efficient interaction, introduces a task management subsystem to improve the level of automation, diversifies configuration templates to enhance flexibility, and designs function switches and degradation strategies to ensure system stability and scalability, thereby providing an efficient, flexible and reliable social interaction experience and significantly improving user experience and stickiness.

[0010] In order to achieve the above purpose, the technical solution adopted by the present invention is:

[0011] A social interaction system, characterized in that the system is constructed according to the following steps:

[0012] Parse the functional division and create functional module nodes based on the product requirement document PRD;

[0013] Assign input parameter attributes, output parameter attributes and usage permission constraints to function module nodes;

[0014] Create edges between functional module nodes to form a data interaction framework, and then add data transmission constraints to the edges;

[0015] Build the front-end system framework based on functional module nodes and edges;

[0016] Configure social activity gameplay templates and perform logic verification;

[0017] During the verification process, the user behavior simulation data set is input into the social activity gameplay template, and the response data to the data set is collected to form a data set to be verified;

[0018] Parse the dataset to be verified and compare it with the task sequence in the social activity gameplay template. If a task sequence has no corresponding response data, prompt the corresponding task item;

[0019] Create an operations management interface for rule configuration;

[0020] An adaptation layer is established between the operation management interface, social activity gameplay template and front-end system framework, and the interaction between the various parts is realized through several adapters.

[0021] On the basis of the above technical solution, the functional module nodes are constructed based on a common underlying data model to support frequent iterations of social activity gameplay.

[0022] Based on the above technical solutions, the underlying data model defines the data structures that the system needs to process and the relationships between these data structures, including:

[0023] The data structure definition layer defines the various data types that need to be processed in the system; each data type contains a series of attributes;

[0024] Data association setting layer, which defines the relationship between data types;

[0025] Entity recognition layer, identifying entity objects in the system;

[0026] The entity attribute definition layer defines attributes for each entity based on the information of the entity identification layer matching the data structure definition layer and the data association setting layer, and clarifies the data type and constraints of each attribute;

[0027] Entity relationship definition layer, which defines the relationship between entities;

[0028] The data standardization layer normalizes entities and eliminates redundant data and non-compliant entities;

[0029] The data population layer is used to create instances of the underlying data model for system testing.

[0030] Based on the above technical solution, the adapter of the adaptation layer is connected by default through the http protocol or the message queue MQ.

[0031] On the basis of the above technical solution, when the message queue MQ is used, the configuration information of MQ is first pulled, and the status change items in the configuration are marked after parsing;

[0032] Based on the analysis of the configuration information, further determine whether the MQ service needs to be enabled. If not, destroy the MQ consumer listener. If necessary, create an MQ consumer listener.

[0033] After the system is started, the MQ configuration information is loaded and the currently available MQ consumer listener is obtained. After successful acquisition, the timer is started to regularly receive and process messages.

[0034] On the basis of the above technical solution, when configuring the social activity gameplay template, a group configuration mechanism is adopted to divide the task into several stages. Each stage includes several default group templates. After the group template is selected in the current stage, the templates that are mutually exclusive with the selected group template in the next stage are hidden and cannot be selected. By maintaining a configuration list, the group templates selected in each stage of the social activity are saved, output and published as social activity gameplay templates.

[0035] Based on the above technical solution, the social activity gameplay template includes a task management subsystem, which specifically includes:

[0036] The access layer is used to uniformly manage API interfaces and respond to the caller's interface access request;

[0037] The task engine is used to parse the request data, parse the domain-specific language element Dsl and determine whether it is hit, manage the task node data and task orchestration data, generate the task flow and implement task scheduling, process the task data, respond to the remote procedure call (RPC) of the task, and manage the task plug-in.

[0038] Based on the above technical solution, the task engine obtains a request to create a task template, parses the request to obtain task attributes, and generates task scheduling data based on the task attributes. The task scheduling data includes:

[0039] Task node information, used to set the key points of the task;

[0040] Node parameter information, used to constrain the execution order between nodes;

[0041] A rule set is used to detect whether the conditions given by the parameters are met;

[0042] In the task verification process, after the task engine saves the task node information, it first verifies whether the task flow consisting of the task key points can be executed correctly according to the default values ​​of the given parameters. If it cannot be executed correctly, it prompts manual inspection of the task node information;

[0043] In the parameter verification process, the task engine detects each task key point separately to see whether the correct subsequent task key points can be triggered when the given conditions of the parameters are met or not. If it cannot be triggered correctly, it prompts manual inspection of the task node information.

[0044] On the basis of the above technical solution, the task node data is created based on a data configuration template, and the data configuration template includes:

[0045] The default configuration template is used to store the business line to which the task belongs and the common basic data of the business;

[0046] Customized configuration templates are used to store task group identifiers, modification permission identifiers, and exclusive configuration parameters, and store optional extended data for services;

[0047] Task template, used to store task information, which includes at least: task name, task start time, task end time, task status, and task sequence number;

[0048] The task configuration template is used to store the configuration parameter information of the task. The configuration parameter information at least includes: task code, custom key, operation input value, group key, and group value.

[0049] On the basis of the above technical solution, the task scheduling data is created based on a task configuration template, and the task configuration template includes:

[0050] Task templates are used to store the business line to which the task belongs, the template status of the business, the task version, and the path to obtain the process orchestration description file;

[0051] Task node template, used to store the node number, input source type and input port ID of the node, and to store the node type. The node types are divided into start node, progress node and end node.

[0052] Task node data verification template, used to store node data verification rules, including: node code, number of input fields, input field name, input field type, input field description, number of return fields, return field name, return field type, return field description, verification type, verification rules;

[0053] Dynamic data source configuration template, used to store name server address, consumer group, consumer MQ name, consumer status, MQ tag;

[0054] Node relationship template, used to store the previous node information and the next node information;

[0055] Process orchestration configuration template, used to store node name, node type, node description information, and node script;

[0056] Task judgment template, used to store node number, function set or rule set, function input parameter, and function result parameter name;

[0057] Function set or rule set template, used to store rule code, rule type, access number, call path, expression, input parameter list, return value type, and return value name;

[0058] Context function configuration template, used to store context KEY, context VALUE, and context description.

[0059] The social interaction system described in the present invention can be applied to the construction of social platforms for activities and user tasks, and has the following beneficial effects:

[0060] 1. Modular construction ensures the maintainability and flexibility of the system:

[0061] Functional module division: By parsing the product requirement document (PRD), the system is divided into multiple functional module nodes, which improves the maintainability and scalability of the system.

[0062] Iteration support: Functional module nodes are built based on a common underlying data model, supporting frequent iterations of social activity gameplay, allowing the system to quickly adapt to changes in market demand.

[0063] 2. Ensure data association and normalization by defining a clear data structure and designing a data model:

[0064] Data structure definition: It defines in detail the various data types and their attributes that need to be processed in the system, such as user information, task information, reward information, etc., providing a solid foundation for data processing.

[0065] Data association and normalization: Through the data association setting layer, entity identification layer, entity attribute definition layer, entity relationship definition layer and data normalization layer, data normalization processing is achieved, redundant data is eliminated, and data consistency and accuracy are ensured.

[0066] 3. Propose the use of adaptation layer to meet the efficient interaction between various parts:

[0067] Adaptation layer design: Establish an adaptation layer between the operation management interface, social activity gameplay template and the front-end system framework, and realize the interaction between the various parts through adapters, thereby improving the system's integration and interaction efficiency.

[0068] Protocol support: The adapter of the adaptation layer connects via HTTP protocol or message queue MQ by default, which can be flexibly selected according to actual conditions to ensure the reliability and efficiency of data transmission.

[0069] 4. Implemented task management and automation:

[0070] Task management subsystem: including access layer, task engine and other components, realizes unified management, analysis, arrangement, scheduling and execution of tasks, and improves the automation level of task processing.

[0071] Task scheduling and verification: The task engine can generate task scheduling data based on task attributes and perform task verification to ensure the correct execution of the task process, reducing manual intervention and error rates.

[0072] 5. The flexibility of task creation can be improved by configuring templates:

[0073] Diversified configuration templates: Provides multiple templates such as default configuration templates, custom configuration templates, task templates, and task configuration templates to support task configuration requirements in different scenarios.

[0074] Group configuration mechanism: The group configuration mechanism is adopted to divide the task into several stages. Each stage includes several default group templates, which improves the flexibility and convenience of task configuration.

[0075] 6. The system has better stability and takes into account the scalability of the system:

[0076] Function switch and downgrade switch: Through the design of function switch and downgrade switch, you can flexibly enable or disable various functions in the task, and ensure the stable operation of core business by downgrading non-core functions when system pressure increases.

[0077] Scalability of the system framework: Based on the construction method of functional module nodes and edges, as well as the design of the adaptation layer, the system framework has good scalability and can support the addition and expansion of more functions in the future. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The present invention has the following accompanying drawings:

[0079] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0080] Figure 1 A schematic diagram of system construction of a social interaction system described in the present invention.

[0081] Figure 2 Schematic diagram of the underlying data model.

[0082] Figure 3 MQ consumption monitoring diagram.

[0083] Figure 4 Schematic diagram of configuring social activity gameplay template.

[0084] Figure 5 Schematic diagram of the task management subsystem architecture. DETAILED DESCRIPTION

[0085] The present invention is further described in detail below in conjunction with the accompanying drawings. The detailed description is an explanation made in conjunction with the exemplary embodiments of the present invention, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0086] like Figure 1 As shown, the present invention provides a social interaction system, and the system is constructed according to the following steps:

[0087] Parse the functional division and create functional module nodes based on the product requirement document PRD;

[0088] Assign input parameter attributes, output parameter attributes and usage permission constraints to function module nodes;

[0089] Create edges between functional module nodes to form a data interaction framework, and then add data transmission constraints to the edges;

[0090] Build the front-end system framework based on functional module nodes and edges;

[0091] Configure social activity gameplay templates and perform logic verification;

[0092] During the verification process, the user behavior simulation data set is input into the social activity gameplay template, and the response data to the data set is collected to form a data set to be verified;

[0093] Parse the dataset to be verified and compare it with the task sequence in the social activity gameplay template. If a task sequence has no corresponding response data, prompt the corresponding task item;

[0094] Create an operations management interface for rule configuration;

[0095] An adaptation layer is established between the operation management interface, social activity gameplay template and front-end system framework, and the interaction between the various parts is realized through several adapters.

[0096] This embodiment proposes a construction scheme for a social interaction system. The scheme starts with demand analysis and refines complex functional requirements into specific functional module nodes by analyzing the product requirement document (PRD) in detail. Subsequently, input parameter attributes, output parameter attributes and strict usage permission constraints are accurately assigned to each node to ensure the security and accuracy of data circulation within the system. A data interaction framework is cleverly constructed between functional modules, and data transmission constraints are carefully set to achieve flexible, efficient and safe flow of data within the system. Next, based on the front-end system framework, a user interaction interface is constructed to ensure that users can interact with the system smoothly and intuitively. In addition, the scheme also focuses on configuring social activity gameplay templates and performs logical verification through user behavior simulation data sets to ensure that the template design is both in line with actual needs and attractive. During the verification process, response data is collected in real time and carefully compared with the task sequence to promptly discover and solve problems and ensure the integrity and reliability of system functions. Finally, by creating an operation-side management interface and adaptation layer, seamless docking and efficient interaction between system components are achieved, providing strong support for flexible configuration, rapid iteration and expansion of the system. This embodiment significantly improves system development efficiency, user experience, system stability and maintainability, while enhancing the flexibility and scalability of the system through modular design, strict data interaction control, flexible social activity configuration, real-time data verification and feedback, convenient operation management tools, and efficient component interaction mechanism.

[0097] On the basis of the above technical solution, the functional module nodes are constructed based on a common underlying data model to support frequent iterations of social activity gameplay.

[0098] In the design of social interaction systems, the underlying data model is a core component that defines the data structures that the system needs to process and the relationships between these data structures, such as Figure 2 As shown, specifically including:

[0099] The data structure definition layer defines the various data types that need to be processed in the system, such as user information, task information, and reward information; each data type contains a series of attributes, such as user ID, user name, task status, and reward type;

[0100] Data association setting layer, which defines the relationship between data types. For example, a user can participate in multiple tasks, and each task can have multiple reward items.

[0101] Entity recognition layer, which identifies entity objects in the system, such as users, tasks, rewards, etc.

[0102] The entity attribute definition layer defines attributes for each entity based on the information of the entity identification layer matching the data structure definition layer and the data association setting layer, and clarifies the data type and constraints of each attribute;

[0103] Entity relationship definition layer, which defines the relationship between entities, such as one-to-one, one-to-many, and many-to-many;

[0104] The data standardization layer normalizes entities and eliminates redundant data and non-compliant entities;

[0105] The data population layer is used to create instances of the underlying data model for system testing.

[0106] Based on the above technical solution, the adapter of the adaptation layer is connected by default through the http protocol or the message queue MQ.

[0107] Based on the above technical solution, Figure 3 As shown, when the message queue MQ is used, the configuration information of MQ is first pulled, and the status change items in the configuration are marked after parsing;

[0108] Based on the analysis of the configuration information, further determine whether the MQ service needs to be enabled. If not, destroy the MQ consumer listener. If necessary, create an MQ consumer listener.

[0109] After the system is started, the MQ configuration information is loaded and the currently available MQ consumer listener is obtained. After successful acquisition, the timer is started to regularly receive and process messages.

[0110] The system first automatically pulls and parses the configuration information of MQ, and marks any status change items in real time. This instant perception capability enables the system to quickly adapt to changes in the external environment; then, the system intelligently determines the necessity of MQ services based on the parsed results of the configuration information. If it is not needed, the MQ consumption monitor is destroyed in time, thereby effectively avoiding resource waste; if it is needed, the MQ consumption monitor is quickly created to ensure that the data channel is unobstructed; after the system is started, it will load the latest MQ configuration information and start the timer to regularly receive and process messages. This mechanism ensures the timeliness and accuracy of the data and avoids system problems caused by message delays or losses. This series of dynamic management operations not only significantly improves the flexibility and responsiveness of the social interaction system, enabling it to quickly adapt to changes in market demand and user behavior; at the same time, by optimizing resource allocation, it improves the resource utilization of the system and reduces operating costs; the regular processing of messages also greatly enhances the stability and reliability of the system, ensuring the continuity of business logic and the integrity of data.

[0111] Based on the above technical solution, Figure 4 As shown, when configuring the social activity gameplay template, a group configuration mechanism is used to divide the task into several stages. Each stage includes several default group templates. After the group template is selected in the current stage, the templates that are mutually exclusive with the selected group template in the next stage are hidden and cannot be selected. By maintaining a configuration list, the group templates selected in each stage of the social activity are saved, output and published as social activity gameplay templates.

[0112] Figure 4 In the example shown, the task is divided into n stages, each stage includes m group templates, group template 2 is selected in task stage 1, group template 2 and group template 3 are mutually exclusive with the selected group template and are hidden in task stage 2, group template m is selected in task stage 2, and so on, group template 3 is selected in task stage n, and the selected group templates are saved in the configuration list, and finally output through the configuration list and published as social activity gameplay templates.

[0113] Based on the above technical solution, the social activity gameplay template includes a task management subsystem, such as Figure 5 As shown, the task management subsystem specifically includes:

[0114] The access layer is used to uniformly manage API interfaces and respond to the caller's interface access request;

[0115] The task engine is used to parse the request data, parse the domain-specific language element Dsl and determine whether it is hit, manage the task node data and task orchestration data, generate the task flow and implement task scheduling, process the task data, respond to the remote procedure call (RPC) of the task, and manage the task plug-in.

[0116] Based on the above technical solution, the task engine obtains a request to create a task template, parses the request to obtain task attributes, and generates task scheduling data based on the task attributes. The task scheduling data includes:

[0117] Task node information, used to set the key points of the task;

[0118] Node parameter information, used to constrain the execution order between nodes;

[0119] A rule set is used to detect whether the conditions given by the parameters are met.

[0120] In the task verification process, after the task engine saves the task node information, it first verifies whether the task flow consisting of the task key points can be executed correctly according to the default values ​​of the given parameters. If it cannot be executed correctly, it prompts manual inspection of the task node information;

[0121] In the parameter verification process, the task engine detects each task key point separately to see whether the correct subsequent task key points can be triggered when the given conditions of the parameters are met or not. If it cannot be triggered correctly, it prompts manual inspection of the task node information.

[0122] In the task execution process, the task engine first determines the task key point as the starting node, then verifies the data to be executed, and further obtains the task flow composed of the task key points after verification, and then calls the data node, judgment node, data node, processing node, and data node in sequence from the task key point as the starting node according to the task flow, until it reaches the task key point as the end node;

[0123] At the data node, the processing template is called to complete one or more operations of data acquisition, data forwarding, and data storage;

[0124] At the judgment node, the processing template is called to complete one or more operations of comparing data constraints and routing to the next node;

[0125] At the processing node, the processing template is called to complete one or more operations of data preprocessing, data parsing, and data conversion.

[0126] On the basis of the above technical solution, the task node data is created based on a data configuration template, and the data configuration template includes:

[0127] The default configuration template is used to store the business line to which the task belongs and the common basic data of the business;

[0128] Customized configuration templates are used to store task group identifiers, modification permission identifiers, and exclusive configuration parameters, and store optional extended data for services;

[0129] Task template, used to store task information, which includes at least: task name, task start time, task end time, task status, and task sequence number;

[0130] The task configuration template is used to store the configuration parameter information of the task. The configuration parameter information at least includes: task code, custom key, operation input value, group key, and group value.

[0131] On the basis of the above technical solution, the task scheduling data is created based on a task configuration template, and the task configuration template includes:

[0132] Task templates are used to store the business line to which the task belongs, the template status of the business, the task version, and the path to obtain the process orchestration description file;

[0133] Task node template, used to store the node number, input source type and input port ID of the node, and to store the node type. The node types are divided into start node, progress node and end node.

[0134] Task node data verification template, used to store node data verification rules, including: node code, number of input fields, input field name, input field type, input field description, number of return fields, return field name, return field type, return field description, verification type, verification rules;

[0135] Dynamic data source configuration template, used to store name server address, consumer group, consumer MQ name, consumer status, MQ tag;

[0136] Node relationship template, used to store the previous node information and the next node information;

[0137] Process orchestration configuration template, used to store node name, node type, node description information, and node script;

[0138] Task judgment template, used to store node number, function set or rule set, function input parameter, and function result parameter name;

[0139] Function set or rule set template, used to store rule code, rule type, access number, call path, expression, input parameter list, return value type, and return value name;

[0140] Context function configuration template, used to store context KEY, context VALUE, and context description.

[0141] On the basis of the above technical solutions, it also includes:

[0142] Function switches are used to enable and disable various functions in the task to facilitate grayscale release and failure rollback;

[0143] The downgrade switch is used to ensure the stable operation of core business by downgrading non-core functions according to the set downgrade strategy when the system pressure increases.

[0144] The contents not described in detail in this specification belong to the prior art known to professional and technical personnel in this field.

[0145] The above description is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiment. Any equivalent modifications or changes made by those skilled in the art based on the contents disclosed by the present invention should be included in the protection scope recorded in the claims.

Claims

1. A social interaction system, It is characterized in that Follow the steps below to build the system: Parse the functional division and create functional module nodes based on the product requirement document PRD; Assign input parameter attributes, output parameter attributes and usage permission constraints to function module nodes; Create edges between functional module nodes to form a data interaction framework, and then add data transmission constraints to the edges; Build the front-end system framework based on functional module nodes and edges; Configure social activity gameplay templates and perform logic verification; During the verification process, the user behavior simulation data set is input into the social activity gameplay template, and the response data to the data set is collected to form a data set to be verified; Parse the dataset to be verified and compare it with the task sequence in the social activity gameplay template. If a task sequence has no corresponding response data, prompt the corresponding task item; Create an operations management interface for rule configuration; An adaptation layer is established between the operation management interface, social activity gameplay template and front-end system framework, and the interaction between the various parts is realized through several adapters.

2. A social interaction system as claimed in claim 1, It is characterized in that The functional module nodes are constructed based on a common underlying data model to support frequent iterations of social activity gameplay.

3. A social interaction system as claimed in claim 3, It is characterized in that The underlying data model defines the data structures that the system needs to process and the relationships between these data structures, including: The data structure definition layer defines the various data types that need to be processed in the system; each data type contains a series of attributes; Data association setting layer, which defines the relationship between data types; Entity recognition layer, identifying entity objects in the system; The entity attribute definition layer defines attributes for each entity based on the information of the entity identification layer matching the data structure definition layer and the data association setting layer, and clarifies the data type and constraints of each attribute; Entity relationship definition layer, which defines the relationship between entities; The data standardization layer normalizes entities and eliminates redundant data and non-compliant entities; The data population layer is used to create instances of the underlying data model for system testing.

4. A social interaction system as claimed in claim 1, It is characterized in that The adapter of the adaptation layer is connected through the http protocol or the message queue MQ by default.

5. A social interaction system as claimed in claim 4, It is characterized in that When using the message queue MQ, first pull the MQ configuration information, parse it, and mark the status change items in the configuration; Based on the analysis of the configuration information, further determine whether the MQ service needs to be enabled. If not, destroy the MQ consumer listener. If necessary, create an MQ consumer listener. After the system is started, the MQ configuration information is loaded and the currently available MQ consumer listener is obtained. After successful acquisition, the timer is started to regularly receive and process messages.

6. A social interaction system as claimed in claim 1, It is characterized in that When configuring social activity gameplay templates, a group configuration mechanism is used to divide the task into several stages. Each stage includes several default group templates. After a group template is selected in the current stage, the templates that are mutually exclusive with the selected group template in the next stage are hidden and cannot be selected. By maintaining a configuration list, the group templates selected in each stage of the social activity are saved, output and published as social activity gameplay templates.

7. A social interaction system as claimed in claim 1, It is characterized in that The social activity gameplay template includes a task management subsystem, which specifically includes: The access layer is used to uniformly manage API interfaces and respond to the caller's interface access request; The task engine is used to parse the request data, parse the domain-specific language element Dsl and determine whether it is hit, manage the task node data and task orchestration data, generate the task flow and implement task scheduling, process the task data, respond to the remote procedure call (RPC) of the task, and manage the task plug-in.

8. A social interaction system as claimed in claim 7, It is characterized in that The task engine obtains a request to create a task template, parses the request to obtain task attributes, and generates task scheduling data based on the task attributes. The task scheduling data includes: Task node information, used to set the key points of the task; Node parameter information, used to constrain the execution order between nodes; A rule set is used to detect whether the conditions given by the parameters are met; In the task verification process, after the task engine saves the task node information, it first verifies whether the task flow consisting of the task key points can be executed correctly according to the default values ​​of the given parameters. If it cannot be executed correctly, it prompts manual inspection of the task node information; In the parameter verification process, the task engine detects each task key point separately to see whether the correct subsequent task key points can be triggered when the given conditions of the parameters are met or not. If it cannot be triggered correctly, it prompts manual inspection of the task node information.

9. A social interaction system as claimed in claim 7, It is characterized in that The task node data is created based on a data configuration template, and the data configuration template includes: The default configuration template is used to store the business line to which the task belongs and the common basic data of the business; Customized configuration templates are used to store task group identifiers, modification permission identifiers, and exclusive configuration parameters, and store optional extended data for services; Task template, used to store task information, which includes at least: task name, task start time, task end time, task status, and task sequence number; The task configuration template is used to store the configuration parameter information of the task. The configuration parameter information at least includes: task code, custom key, operation input value, group key, and group value.

10. A social interaction system as claimed in claim 7, It is characterized in that The task scheduling data is created based on a task configuration template, and the task configuration template includes: Task templates are used to store the business line to which the task belongs, the template status of the business, the task version, and the path to obtain the process orchestration description file; Task node template, used to store the node number, input source type and input port ID of the node, and to store the node type. The node types are divided into start node, progress node and end node. Task node data verification template, used to store node data verification rules, including: node code, number of input fields, input field name, input field type, input field description, number of return fields, return field name, return field type, return field description, verification type, verification rules; Dynamic data source configuration template, used to store name server address, consumer group, consumer MQ name, consumer status, MQ tag; Node relationship template, used to store the previous node information and the next node information; Process orchestration configuration template, used to store node name, node type, node description information, and node script; Task judgment template, used to store node number, function set or rule set, function input parameter, and function result parameter name; Function set or rule set template, used to store rule code, rule type, access number, call path, expression, input parameter list, return value type, and return value name; Context function configuration template, used to store context KEY, context VALUE, and context description.