A general event processing method and system based on game data operation analysis

Abstract

The present invention provides a general event processing method and system based on game data operation analysis, the method comprising: defining a general format applicable to a variety of general events; receiving general event data, recording the general event data using the general format to obtain a general event original record; converting the general event original record according to a preset conversion format to obtain a general event conversion record; saving the general event conversion record; obtaining a general event to be analyzed, reading the corresponding general event conversion record according to the general event to be analyzed, and restoring the general event conversion record. The method realizes the standardized storage and standardized use of general events, and assists in improving the efficiency of data operation analysis.

Description

Technical Field

[0001] The present invention belongs to the field of game technology, and specifically relates to a general event processing method and system based on game data operation analysis. Background Art

[0002] Data operation in games refers to modifying some configuration data of games (such as mobile games) and checking the changes in various analytical indicator data. The analytical indicator data can be changes in user retention rate, changes in the number of user game times, and changes in the number of user ad viewing times. Data operation can perform digital updates on games without modifying the game logic to obtain changes in analytical indicator data. General events in games refer to various events that occur during the game data operation analysis process for users of different types of games while playing the game.

[0003] In the process of game data operation analysis, various events that occur during the game play of users of different types of games will be recorded for data operation. Game types include but are not limited to: parkour, elimination, card, simulation, racing, competitive, etc. Common game events include but are not limited to registration, login, online, active, online, offline, etc. When performing data operation analysis, the existing technology will use a series of standard analysis reports for analysis, such as "user registration report", "user activity report", "user retention report", etc. for analysis.

[0004] For different types of events in different games, operators will also put forward various specific report analysis requirements, including but not limited to: "enter the room", "start the game", "end the card dealing", "buy gold coins", "consume props", "pass the level", "fail the level", "obtain a title", "buy equipment", "equipment synthesis", etc. Because the type of game cannot be determined in advance, various general events cannot be determined in advance, so the event type, specific content, and type of different types of each game cannot be determined in advance.

[0005] As new games are continuously launched, the types of games will continue to expand. New types of games will lead to a large expansion of new universal event types. In the process of continuous operation and function iteration of each game, various universal events of the game will continue to appear. Even the same event of the same game may change the format and increase the content in the later stage. For example, new props are added, and these props need to correspond to new attribute content: immunity.

[0006] Therefore, for these common events, back-end developers must create independent database tables for each common event for storage, and must know the specific format of each common event in advance, which will reduce the flexibility of adding new events. That is, new common events and changes in the format of common events require front-end developers and back-end developers to define and communicate the specific formats. New common events and changes in the format of common events cannot be saved before back-end developers create or update the database table. New common events will lead to new tables, resulting in an unlimited surge in the number of database tables, complicating and delaying the workflow, and greatly increasing the error rate.

[0007] At the same time, in response to these common events, operations personnel will constantly put forward some statistical analysis report requirements. These statistical analysis requirements surrounding each new game and each new event require developers to develop separately, resulting in an unlimited surge in development workload. Summary of the invention

[0008] In view of the defects in the prior art, the present invention provides a general event processing method and system based on game data operation analysis, which realizes the standardized storage and standardized use of general events, and helps to improve the efficiency of data operation analysis.

[0009] In the first aspect, a general event processing method based on game data operation analysis includes:

[0010] Define a common format applicable to multiple common events;

[0011] receiving general event data, and recording the general event data in a general format to obtain original records of the general event;

[0012] Converting the original general event record according to a preset conversion format to obtain a general event conversion record;

[0013] Keep records of common event conversions;

[0014] Obtain the general event to be analyzed, read the corresponding general event conversion record according to the general event to be analyzed, and restore the general event conversion record.

[0015] In the second aspect, a general event processing system based on game data operation analysis includes:

[0016] Template unit: used to define common formats applicable to a variety of common events;

[0017] Recording unit: used for receiving common event data and recording the common event data in a common format to obtain the original record of the common event;

[0018] Conversion unit: used for converting the original record of the general event according to a preset conversion format to obtain a general event conversion record;

[0019] Storage unit: used to save general event conversion records;

[0020] Usage unit: used to obtain the general event to be analyzed, read the corresponding general event conversion record according to the general event to be analyzed, and restore the general event conversion record.

[0021] It can be seen from the above technical scheme that the general event processing method and system provided by the present invention first defines a general format applicable to a variety of general events, which is convenient for describing and recording general events, and uses the general format to record general event data to obtain the original record of the general event. Then, in order to facilitate the storage of general events in the database, the original record of the general event is converted to obtain a general event conversion record, which is more suitable for storage and use. Then, the general event conversion record is saved in the database, and the database is automatically maintained. Finally, when performing data operation analysis, the data saved in the database is restored, and the restored data is used to perform data operation analysis to obtain the data operation analysis results. This method and system realize the standardized storage and standardized use of general events, and assist in improving the efficiency of data operation analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following is a brief introduction to the drawings required for the specific embodiments or the description of the prior art. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn according to the actual scale.

[0023] Figure 1 This is a flowchart of a general event processing method provided in this embodiment.

[0024] Figure 2 A flowchart of the general event original record conversion method provided in this embodiment.

[0025] Figure 3 This is a flowchart of the general event conversion record preservation method provided in this embodiment.

[0026] Figure 4 This is a flowchart of the general event conversion record restoration method provided in this embodiment.

[0027] Figure 5 This is a module block diagram of the general event processing system provided in this embodiment. DETAILED DESCRIPTION

[0028] The embodiments of the technical solution of the present invention will be described in detail below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and are therefore only used as examples, and the protection scope of the present invention cannot be limited thereto. It should be noted that, unless otherwise specified, the technical terms or scientific terms used in this application should be the common meanings understood by those skilled in the art to which the present invention belongs.

[0029] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0030] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0031] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0032] Embodiment 1:

[0033] A general event processing method based on game data operation analysis, see Figure 1 ,include:

[0034] S1: Define a common format applicable to multiple common events;

[0035] S2: receiving the general event data, and recording the general event data in a general format to obtain the original record of the general event;

[0036] S3: converting the general event original record according to a preset conversion format to obtain a general event conversion record;

[0037] S4: Save the general event conversion record;

[0038] S5: Obtain the general event to be analyzed, read the corresponding general event conversion record according to the general event to be analyzed, and restore the general event conversion record.

[0039] In this embodiment, the method first defines a general format applicable to a variety of general events to facilitate the description and recording of general events. The general format can be a standard json format. The method first uses a general format to record general event data to obtain the original record of the general event, and then, in order to facilitate the storage of the general event in the database, the original record of the general event is converted to obtain a general event conversion record, and the general event conversion record is more suitable for storage and use. Then, the general event conversion record is saved in the database, and the database is automatically maintained. Finally, when performing data operation analysis, the data saved in the database is restored, and the restored data is used to perform data operation analysis to obtain the data operation analysis results. This method realizes the standardized storage and standardized use of general events, and assists in improving the efficiency of data operation analysis.

[0040] Preferably, the general format includes a time field, a game field, an event field and a content field; the content field includes a plurality of content data.

[0041] In this embodiment, the general format can be defined as:

[0042]

[0043]

[0044] The time field is the specific time when the event occurred, and the content field is the specific information of the content. The content field is a single-layer structure and cannot be nested with more layers of information. The content field can be defined by the front-end developer according to different events of different games, so that the flexibility of the general format can be guaranteed. For example, taking the event "enter the room" of the game "card elimination" as an example, the original record of the general event is:

[0045] {

[0046] Time: 2021-12-02 23:13:17,

[0047] Game: "Card Elimination",

[0048] Event: "Enter room",

[0049] content:

[0050] {

[0051] Room name: "Presidential Suite",

[0052] Room level: 3,

[0053] Room number: "3023",

[0054] Capacity: 15,

[0055] Current number of people: 6,

[0056] Created: 2021-12-02 19:03:22,

[0057] }

[0058] }

[0059] Taking the event "obtain title" in the game "Everyday Parkour" as an example, the original record of the general event obtained is:

[0060] {

[0061] Time: 2021-12-02 23:13:17,

[0062] Game: "Daily Parkour",

[0063] Event: "Get title",

[0064] content:

[0065] {

[0066] Title: "Super Liu Xiang",

[0067] Title level: 3,

[0068] Title bonus: 5000,

[0069] Title duration: "15 days",

[0070] }

[0071] }

[0072] Preferably, see Figure 2 , converting the general event original record according to the preset conversion format to obtain the general event conversion record specifically including:

[0073] S11: define the time field, game field and event field in the general event original record as the time field, game field and event field in the general event conversion record;

[0074] S12: Create N json structures in the general event conversion record according to the number N of content data in the general event original record, and fill each content data in the general event original record into the json structure corresponding to the general event conversion record; the json structure includes a name field, a type field and a data field.

[0075] In this embodiment, the conversion of the general event original record is only for the content field, wherein the conversion idea is mainly: copy the event as a new event, and set the new event.content = [], where the initial value of [] is empty, and the symbol "." represents the subordinate field, for example, new event.content represents the content field of the new event, and take out each content data in the general event original record in turn to create the following json structure:

[0076] {

[0077] Name: Field name,

[0078] Type: the type of (field value),

[0079] Data: Field value

[0080] }

[0081] Finally, fill the content data in the original record of the general event into the new event.content. For example, the conversion format can be the following json format:

[0082]

[0083] The time field is the specific time when the event occurred, the content field uses a list to describe each specific content, the type field takes values ​​from "integer", "floating point", "string", "date", and "time", and the data field stores the value of the field. For example, taking the above general event original record obtained from the event "obtaining a title" of the game "Everyday Parkour", the general event conversion record obtained is as follows:

[0084]

[0085]

[0086] Preferably, see Figure 3 , saving general event conversion records specifically includes:

[0087] S21: Create an event table and an event name type table;

[0088] S22: Create name type information according to the general event conversion record, and fill the name type information into the event name type table;

[0089] S23: Create event information according to the general event conversion record, and fill the event information into the event table.

[0090] In this embodiment, the event name type table is mainly used to store the name and type of the event, and the event table is mainly used to store the data of the event. For example, the event name type table and event table created are as follows:

[0091] <Event List>:

[0092]

[0093] Among them, subsequent fields in the event table can be dynamically added and modified during subsequent use.

[0094] <Event name type table>:

[0095]

[0096]

[0097] Among them, the subsequent fields in the event name type table can be dynamically added and modified during subsequent use. The index items contained in the above two tables can be game fields + event fields. It can be seen that the same game + event can only appear once in the above two tables. The method can also automatically maintain the above two tables to ensure that the two tables are sufficient to store general event conversion records. When updating the above two tables, the general event that appears for the first time in the above two tables is an insert, and the general event that appears subsequently in the above two tables is an update. This method can save the general event conversion records in the above two tables.

[0098] Preferably, creating name type information according to the general event conversion record specifically includes:

[0099] Define the game field in the name type information to be equal to the game field in the general event conversion record; define the event field in the name type information to be equal to the event field in the general event conversion record; define the name field of the Nth data in the name type information to be equal to the name field of the Nth json structure in the general event conversion record; define the type field of the Nth data in the name type information to be equal to the type field of the Nth json structure in the general event conversion record.

[0100] In this embodiment, the name type information is information extracted from the general event conversion record that conforms to the event name type table. When creating the name type information, define the game field in the name type information to be equal to the game field in the general event conversion record, define the event field in the name type information to be equal to the event field in the general event conversion record, set the field counter to 1, define the name field of the Nth data in the name type information to be equal to the name field of the Nth json structure in the general event conversion record, expressed as name type information (field counter)_name=general event conversion record.name, define the type field of the Nth data in the name type information to be equal to the type field of the Nth json structure in the general event conversion record, expressed as name type information (field counter)_type=general event conversion record.type. Taking the above-mentioned general event conversion record obtained by the event "obtaining a title" of the game "Everyday Parkour" as an example, the name type information obtained is:

[0101]

[0102] Preferably, filling the name type information into the event name type table specifically includes:

[0103] When the event name type table does not have the game field and event field of the name type information, the game field in the newly added event name type table is equal to the game field in the name type information; the event field in the newly added event name type table is equal to the event field in the name type information; the name field of the Nth data in the newly added event name type table is equal to the name field of the Nth data in the name type information; the type field of the Nth data in the newly added event name type table is equal to the type field of the Nth data in the name type information;

[0104] When the event name type table has the game field and event field of the name type information, the event name type table is updated according to the name type information.

[0105] In this embodiment, when the method stores the name type information into the event name type table, the number of table data fields is defined as the number of fields starting with "data" in the <event name type table> field / 2, the number of contents is defined as the number of content data, and the number difference is defined as the number of contents-the number of table data fields. If the number difference>0, it means that the event name type table cannot store all the content data. At this time, the field counter is defined to accumulate from the number of table data fields+1 to the number of contents, and the following two fields are added to the event name type table:

[0106]

[0107] For example, take the above general event conversion record obtained from the event "obtain title" of the game "Everyday Parkour" as an example, assuming that the initial event name type table is an empty table, as follows:

[0108]

[0109] At this time, the number of table data fields = the number of fields starting with "data" in the event name type table / 2 = 0, the number of contents = 4, and the number difference = the number of contents - the number of table data fields = 4-0 = 4. At this time, the number difference = 4>0, so the event name type table cannot save the names and types of 4 content data. Therefore, it is necessary to add fields to the event name type table, and the field counter is accumulated from 1 to 4. The following fields are added to the event name type table:

[0110] Data1_Name

[0111] Data1_Type

[0112] Data2_Name

[0113] Data2_Type

[0114] Data3_Name

[0115] Data3_Type

[0116] Data4_Name

[0117] Data4_Type

[0118] At this point, the event name type table is as follows:

[0119]

[0120] In this way, the event name type table can save the names and types of the four content data of the Tiantian Parkour-Get Title event.

[0121] For example, the above general event conversion record obtained by the event "obtain title" of the game "Everyday Parkour" is taken as an example. Assume that the initial event name type table includes 3 content data, as follows:

[0122]

[0123] At this time, the number of table data fields = the number of fields starting with "data" in the event name type table / 2 = 3, the number of contents = 4, and the number difference = the number of contents - the number of table data fields = 4-3 = 1. At this time, the number difference = 1>0, so the event name type table cannot save the names and types of 4 content data. Therefore, it is necessary to add fields to the event name type table, and the field counter is accumulated from 4 to 4. The following fields are added to the event name type table:

[0124] Data4_Name

[0125] Data4_Type

[0126] At this point, the event name type table is as follows:

[0127]

[0128] In this way, the event name type table can save the names and types of the four content data of the Tiantian Parkour-Get Title event.

[0129] At this point, the format of the name type information and the event name type table are consistent. This method stores the name type information in the event name type table, including the following two cases:

[0130] a. If the event name type table does not contain information with the same game field + event field, insert the name type information into the event name type table.

[0131] b. If the event name type table contains information of the same game field + event field, update the corresponding fields in the event name type table.

[0132] Taking the above general event conversion record obtained from the event "obtain title" of the game "Everyday Parkour" as an example, the last data stored in the event name type table is:

[0133]

[0134] Preferably, creating event information according to the general event conversion record specifically includes:

[0135] Define the time field in the event information to be equal to the time field in the general event conversion record; define the game field in the event information to be equal to the game field in the general event conversion record; define the event field in the event information to be equal to the event field in the general event conversion record; define the data field of the Nth data in the event information to be equal to the data field of the Nth data in the general event conversion record.

[0136] In this embodiment, the event information is information that is extracted from the general event conversion record that conforms to the event table. When creating event information, let the time field in the event information be equal to the time field in the general event conversion record, expressed as event information.time = general event conversion record.time; define the game field in the event information to be equal to the game field in the general event conversion record, expressed as event information.game = general event conversion record.game; define the event field in the event information to be equal to the event field in the general event conversion record, expressed as event information.event = general event conversion record.event, set the field counter to 1, let the data field of the Nth data in the event information be equal to the data field of the Nth data in the general event conversion record, expressed as event information.data (field counter)_(general event conversion record.type) = general event conversion record.data, field counter + 1. Taking the above-mentioned general event conversion record obtained by the event "obtaining a title" of the game "Everyday Parkour" as an example, the event information obtained is:

[0137]

[0138] Preferably, filling the event information into the event table specifically includes:

[0139] When the event table does not have the game field and event field of the event information, the game field in the newly added event table is equal to the game field in the event information; the event field in the newly added event table is equal to the event field in the event information; the data field of the Nth data in the newly added event table is equal to the data field of the Nth data in the event information;

[0140] When the event table contains the game field and event field of event information, the event table is updated according to the event information.

[0141] In this embodiment, the method also needs to maintain the event table when in use, ensure that the event table is sufficient to store event information, obtain each name field in the event information, if the name field does not exist in the event table, set the type field = the second half of the data field separated by "_", and add the following fields to the event table:

[0142]

[0143] At this point, the formats of event information and event table are basically the same. Event information is inserted into the event table. Taking the above general event conversion record obtained by the event "obtain title" of the game "Everyday Parkour" as an example, the last data stored in the event table is:

[0144]

[0145] In summary, this method saves the name field and type field of the content field in the event information independently in the event name type table, because this part is unchanged for the same game and the same event, which can reduce the repeated storage of data names and types. In addition, this method saves the data field of the content field in the event information in the event table, and does not save the field name, which ensures the maximum utilization of the field for different games and different events.

[0146] Preferably, see Figure 4 , obtain the general event to be analyzed, read the corresponding general event conversion record according to the general event to be analyzed, and restore the general event conversion record specifically including:

[0147] S31: Searching the event name type table according to the game field and event field of the general event to be analyzed to obtain corresponding name type information;

[0148] S32: Search the event table according to the name type information to obtain corresponding event information.

[0149] In this embodiment, when it is necessary to read the general event conversion record for data operation analysis, the name field is obtained through the event name type table, and the data field corresponding to the name field is read in the event table, so as to restore the general event conversion record to the original general event record. Taking the above general event conversion record obtained by the event "obtaining a title" of the game "Tiantian Parkour" as an example, the method first obtains the name field of a specific game + event through the event name type table. For example, in the event name type table, the following query statement (SQL statement) is entered with the game field = "Tiantian Parkour" and the event field = "obtaining a title":

[0150] select

[0151] *

[0152] from

[0153] <Event name type table>

[0154] where

[0155] Game = "Daily Parkour" and

[0156] Event = "Get title"

[0157] The output result is:

[0158]

[0159] Then select all the information of game field = "Tiantian Parkour", event field = "Get Title" and name field = "Super Liu Xiang", and enter the following query statement (SQL statement):

[0160] select

[0161] time,

[0162] game,

[0163] event,

[0164] Title Name,

[0165] Title level,

[0166] Title Bonus,

[0167] Title period

[0168] from

[0169] <Event Table>

[0170] where

[0171] Game = "Daily Parkour" and

[0172] Event = "Get title" and

[0173] Title = "Super Liu Xiang"

[0174] The output result is:

[0175]

[0176] In addition, in actual use, because the event name type table changes very rarely for the same game field and the same event field, this method can also construct a field correspondence information table and refresh the field correspondence information table regularly, avoiding searching the name field from the event name type table every time. The field correspondence information table is expressed as follows:

[0177]

[0178] It can be seen that the name in the field correspondence information table = (data) + "_" + (type), so this method can also use the field correspondence information table to search directly, for example, enter the following query statement (SQL statement):

[0179] select

[0180] time,

[0181] game,

[0182] event,

[0183] Data 1_ string as title name,

[0184] Data 2_integer as title level,

[0185] Data 3_Integer as Title Bonus,

[0186] Data 4_ string as title expiration

[0187] from

[0188] <Event Table>

[0189] where

[0190] Game = "Daily Parkour" and

[0191] Event = "Get title" and

[0192] Data1_String = "Super Liu Xiang"

[0193] The output result is:

[0194]

[0195] Embodiment 2:

[0196] A general event processing system based on game data operation analysis, see Figure 5 ,include:

[0197] Template unit 1: used to define a common format applicable to a variety of common events;

[0198] Recording unit 2: used for receiving general event data and recording the general event data in a general format to obtain original records of the general event;

[0199] Conversion unit 3: used for converting the general event original record according to a preset conversion format to obtain a general event conversion record;

[0200] Storage unit 4: used to store general event conversion records;

[0201] Using unit 5: used to obtain the general event to be analyzed, read the corresponding general event conversion record according to the general event to be analyzed, and restore the general event conversion record.

[0202] The system provided in the embodiment of the present invention is briefly described. For matters not mentioned in the embodiment part, reference may be made to the corresponding contents in the aforementioned embodiment.

[0203] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and specification of the present invention.

Claims

1. A general event processing method based on game data operation analysis, characterized in that: include: Define a general format applicable to a variety of general events, the general format includes a time field, a game field, an event field and a content field, the content field includes a plurality of content data; Receiving general event data, and recording the general event data using the general format to obtain a general event original record; The general event original record is converted according to a preset conversion format to obtain a general event conversion record; wherein the time field, game field and event field in the general event original record are defined as the time field, game field and event field in the general event conversion record, and N json structures in the general event conversion record are created according to the number N of content data in the general event original record, and each content data in the general event original record is filled into the json structure corresponding to the general event conversion record; the json structure includes a name field, a type field and a data field; The general event conversion record is saved, which includes: creating an event table and an event name type table, creating name type information according to the general event conversion record, filling the name type information into the event name type table, creating event information according to the general event conversion record, and filling the event information into the event table; wherein, the creation of name type information according to the general event conversion record specifically includes: defining the game field in the name type information to be equal to the game field in the general event conversion record, defining the event field in the name type information to be equal to the event field in the general event conversion record, defining the name field of the Nth data in the name type information, etc. In the name field of the Nth json structure in the general event conversion record, define the type field of the Nth data in the name type information to be equal to the type field of the Nth json structure in the general event conversion record; wherein, filling the name type information into the event name type table specifically includes: when the game field and event field of the name type information do not exist in the event name type table, add a game field in the event name type table equal to the game field in the name type information, add an event field in the event name type table equal to the event field in the name type information, add a name field of the Nth data in the event name type table equal to the name The name field of the Nth data in the type information, the type field of the Nth data in the newly added event name type table is equal to the type field of the Nth data in the name type information, when the game field and event field of the name type information exist in the event name type table, the event name type table is updated according to the name type information; wherein, the creation of event information according to the general event conversion record specifically includes: defining the time field in the event information to be equal to the time field in the general event conversion record, defining the game field in the event information to be equal to the game field in the general event conversion record, defining the event field in the event information to be equal to the general event conversion record The event field in the event table defines that the data field of the Nth data in the event information is equal to the data field of the Nth data in the general event conversion record; wherein, the filling of the event information into the event table specifically includes: when the game field and the event field of the event information do not exist in the event table, adding a game field in the event table equal to the game field in the event information, adding an event field in the event table equal to the event field in the event information, adding a data field of the Nth data in the event table equal to the data field of the Nth data in the event information, and when the game field and the event field of the event information exist in the event table, updating the event table according to the event information;The obtaining of the general event to be analyzed, reading the corresponding general event conversion record according to the general event to be analyzed, and restoring the general event conversion record specifically includes: searching the event name type table according to the game field and the event field of the general event to be analyzed to obtain the corresponding name type information, and searching the event table according to the name type information to obtain the corresponding event information; The general event to be analyzed is obtained, the corresponding general event conversion record is read according to the general event to be analyzed, and the general event conversion record is restored.

2. A general event processing system based on game data operation analysis, characterized in that: include: Template unit: used to define a general format applicable to a variety of general events, the general format includes a time field, a game field, an event field and a content field, the content field includes a plurality of content data; Recording unit: used for receiving the general event data, and recording the general event data in the general format to obtain the general event original record; A conversion unit: used for converting the general event original record according to a preset conversion format to obtain a general event conversion record; wherein the time field, game field and event field in the general event original record are defined as the time field, game field and event field in the general event conversion record, and N json structures in the general event conversion record are created according to the number N of content data in the general event original record, and each content data in the general event original record is filled into the json structure corresponding to the general event conversion record; the json structure includes a name field, a type field and a data field; Storage unit: used to store the general event conversion record; including: creating an event table and an event name type table, creating name type information according to the general event conversion record, filling the name type information into the event name type table, creating event information according to the general event conversion record, and filling the event information into the event table; wherein, creating name type information according to the general event conversion record specifically includes: defining the game field in the name type information to be equal to the game field in the general event conversion record, defining the event field in the name type information to be equal to the event field in the general event conversion record, defining the Nth data in the name type information The name field is equal to the name field of the Nth json structure in the general event conversion record, and the type field of the Nth data in the name type information is defined to be equal to the type field of the Nth json structure in the general event conversion record; wherein, the filling of the name type information into the event name type table specifically includes: when the game field and event field of the name type information do not exist in the event name type table, the game field added to the event name type table is equal to the game field in the name type information, the event field added to the event name type table is equal to the event field in the name type information, and the name field of the Nth data added to the event name type table is equal to the The name field of the Nth data in the name type information is added, and the type field of the Nth data in the event name type table is added to be equal to the type field of the Nth data in the name type information; when the game field and event field of the name type information exist in the event name type table, the event name type table is updated according to the name type information; wherein, the creation of event information according to the universal event conversion record specifically includes: defining the time field in the event information to be equal to the time field in the universal event conversion record, defining the game field in the event information to be equal to the game field in the universal event conversion record, defining the event field in the event information to be equal to the universal event conversion record The event field in the record defines that the data field of the Nth data in the event information is equal to the data field of the Nth data in the general event conversion record; wherein, the filling of the event information into the event table specifically includes: when the game field and the event field of the event information do not exist in the event table, adding a game field in the event table equal to the game field in the event information, adding an event field in the event table equal to the event field in the event information, adding a data field of the Nth data in the event table equal to the data field of the Nth data in the event information, and when the game field and the event field of the event information exist in the event table, updating the event table according to the event information;The obtaining of the general event to be analyzed, reading the corresponding general event conversion record according to the general event to be analyzed, and restoring the general event conversion record specifically includes: searching the event name type table according to the game field and the event field of the general event to be analyzed to obtain the corresponding name type information, and searching the event table according to the name type information to obtain the corresponding event information; Using unit: used for obtaining the general event to be analyzed, and reading the corresponding general event conversion according to the general event to be analyzed.

Images