Game behavior event processing method, device, equipment and storage medium

Abstract

The present application discloses a method, apparatus, device and storage medium for processing game behavior events, including: obtaining a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, heterogeneously integrating the obtained multiple first behavior events to obtain multiple first event data, and storing the multiple first event data in a preset first event library; obtaining a second behavior event triggered by a third-party application through a third-party embedding point, heterogeneously integrating the obtained multiple second behavior events to obtain multiple second event data, and storing the multiple second event data in a preset second event library; receiving an event query request, and determining a target event library in the first event library and the second event library according to the event source of the event to be queried in the event query request; and querying the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request.

Description

Technical Field

[0001] The present application relates to the field of game technology, and in particular to a method, device, equipment and storage medium for processing game behavior events. Background Art

[0002] With the rapid development of Internet technology and data science, enterprises are able to collect and analyze large-scale user data, such as user behavior logs, transaction records, social networks, etc. Through these user behavior data, enterprises can build complex user portraits and understand multi-dimensional characteristics such as user interests, preferences, consumption habits, and behavior paths. Behavioral event query services have also emerged on this basis. It provides enterprises with fast and efficient behavioral event statistics and analysis, which can help businesses provide support in personalized recommendations, refined operations, user insights, and solution decisions. On the game business side, such as user operations, game interaction strategies, and user insight analysis, there is a need for behavioral event queries.

[0003] In the prior art, the game behavior event query service collects the behavior events of each game user, stores the behavior events in a database, and queries the corresponding behavior event type in the database according to the behavior event type you want to query. However, different game users use different devices to run game applications, and the collected behavior events are multi-terminal heterogeneous data. Therefore, when storing multi-terminal heterogeneous data, it is necessary to store them separately in different databases according to the data type of the behavior event, and when querying the behavior event, it is necessary to query multiple databases one by one. The storage and query operations are relatively complicated, resulting in low storage efficiency and query efficiency of behavior events. Summary of the invention

[0004] The present application provides a game behavior event processing method, device, equipment and storage medium, so as to perform heterogeneous integration processing on the acquired behavior events and then store them in an event library, thereby solving the problem in the prior art that behavior events of different data types need to be stored separately. When subsequently querying behavior events, there is no need to query multiple databases one by one, which reduces the complexity of storage operations and query operations and improves the storage efficiency and query efficiency of behavior events.

[0005] In a first aspect, the present application provides a method for processing a game behavior event, comprising:

[0006] Acquire a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, perform heterogeneous integration processing on the acquired multiple first behavior events to obtain multiple first event data, and store the multiple first event data in a preset first event library;

[0007] Acquire a second behavior event triggered by a third-party application through a third-party tracking point, perform heterogeneous integration processing on the acquired multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library;

[0008] receiving an event query request, and determining a target event repository in the first event repository and the second event repository according to an event source of an event to be queried in the event query request;

[0009] According to the event type, event dimension and event indicator caliber of the event to be queried in the event query request, the target event data of the event to be queried is queried in the target event library.

[0010] In a second aspect, the present application provides a game behavior event processing device, comprising:

[0011] A first event storage module is configured to obtain a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, perform heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and store the multiple first event data in a preset first event library;

[0012] The second event storage module is configured to obtain a second behavior event triggered by a third-party application through a third-party embedding point, perform heterogeneous integration processing on the obtained multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library;

[0013] An event library determination module is configured to receive an event query request, and determine a target event library in the first event library and the second event library according to an event source of an event to be queried in the event query request;

[0014] The target event query module is configured to query the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request.

[0015] In a third aspect, the present application provides a game behavior event processing device, including:

[0016] one or more processors;

[0017] A memory stores one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the game behavior event processing method as described in the first aspect.

[0018] In a fourth aspect, the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the game behavior event processing method as described in the first aspect.

[0019] In the present application, the first behavior event triggered by the game application is obtained through an asynchronous queue or a synchronous interface, and the obtained multiple first behavior events are heterogeneously integrated to obtain multiple first event data, and the multiple first event data are stored in a preset first event library; the second behavior event triggered by the third-party application is obtained through a third-party embedding point, and the obtained multiple second behavior events are heterogeneously integrated to obtain multiple second event data, and the multiple second event data are stored in a preset second event library; an event query request is received, and the target event library is determined in the first event library and the second event library according to the event source of the event to be queried in the event query request; according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request, the target event data of the event to be queried is queried in the target event library. Through the above technical means, the obtained behavior events can be heterogeneously integrated and then stored in the event library, which solves the problem of needing to store behavior events of different data types separately in the prior art. When querying behavior events subsequently, there is no need to query multiple databases one by one, which reduces the complexity of storage operations and query operations, and improves the storage efficiency and query efficiency of behavior events. It can collect behavioral events of game applications and third-party applications, expand the query scope of behavioral events, and meet the vast majority of behavioral event query needs. It can efficiently query target events in the event library based on the event type, event dimension, and event indicator caliber of the query time, improving the query efficiency of behavioral events. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a flowchart of a method for processing game behavior events provided by an embodiment of the present application;

[0021] Figure 2 is a flow chart of performing heterogeneous integration processing on multiple first behavior events provided by an embodiment of the present application;

[0022] Figure 3 is a flowchart of combining first event data to generate first combined event data provided by an embodiment of the present application;

[0023] Figure 4 is a flow chart of combining second event data to generate second combined event data provided by an embodiment of the present application;

[0024] Figure 5 is a flowchart of querying target event data provided by an embodiment of the present application;

[0025] Figure 6It is a structural diagram of a game behavior event processing device provided in an embodiment of the present application;

[0026] Figure 7 It is a structural diagram of a game behavior event processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0028] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0029] In the more common existing implementation methods, the game behavior event query service collects the behavior events of each game user, stores the behavior events in the database, and queries the corresponding behavior event type in the database according to the behavior event type you want to query. However, different game users use different devices to run game applications, and the collected behavior events are multi-terminal heterogeneous data. Therefore, when storing multi-terminal heterogeneous data, it is necessary to store them separately in different databases according to the data type of the behavior event, and when querying the behavior event, it is necessary to query multiple databases one by one. The storage and query operations are relatively complicated, resulting in low storage efficiency and query efficiency of behavior events.

[0030] To solve the above problems, this embodiment provides a game behavior event processing method, which performs heterogeneous integration processing on the acquired behavior events and then stores them in the event library. When querying behavior events subsequently, there is no need to query multiple databases one by one, which reduces the complexity of storage operations and query operations and improves the storage efficiency and query efficiency of behavior events.

[0031] The game behavior event processing method provided in this embodiment can be executed by a game behavior event processing device, which can be implemented by software and / or hardware, and can be composed of two or more physical entities, or one physical entity. For example, the game behavior event processing device can be a query server.

[0032] The game behavior event processing device is installed with at least one type of operating system, wherein the operating system includes but is not limited to Android system, Linux system and Windows system. The game behavior event processing device can install at least one application based on the operating system, and the application can be an application that comes with the operating system, or an application downloaded from a third-party device or server. In this embodiment, the game behavior event processing device has at least an application that can execute the game behavior event processing method.

[0033] For ease of understanding, this embodiment is described by taking the query server as an example of the subject that executes the game behavior event processing method.

[0034] Figure 1 A flowchart of a method for processing a game behavior event provided by an embodiment of the present application is given. Figure 1 , the game behavior event processing method specifically includes:

[0035] S110, obtaining a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, performing heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and storing the multiple first event data in a preset first event library.

[0036] Exemplarily, the business personnel configure the query server to connect to multiple game applications, and configure the behavior event type and corresponding access method generated by each game application accessed by the query server. After the game application generates a behavior event, the behavior event is reported to the query server through the SDK or an asynchronous queue. The query server obtains the first behavior event from the behavior events reported by the game application through an asynchronous queue or a synchronous interface based on the preset behavior event type and the corresponding access method. Among them, when the access method corresponding to the behavior event type is asynchronous access, the first behavior event corresponding to the behavior event type reported by the game application is received through the asynchronous queue; when the access method corresponding to the behavior event type is synchronous access, the first behavior event corresponding to the behavior event type reported by the game application is received through the synchronous interface.

[0037] After obtaining multiple first behavior events reported by various game applications, heterogeneous integration processing is performed on the multiple first behavior events to convert the multiple first behavior events into the same data structure, and the first event data corresponding to each first behavior event is obtained, and the first event data with a unified data structure is stored in a preset first event library. Figure 2 1 is a flowchart of performing heterogeneous integration processing on multiple first behavior events provided by an embodiment of the present application. Figure 2 As shown, the step of performing heterogeneous integration processing on multiple first behavior events specifically includes S1101-S1104:

[0038] S1101. Determine, according to a preset field mapping table, a first field containing the same information in a plurality of acquired first behavior events.

[0039] For example, the field mapping table defines fields containing the same information, such as the field mapping table defines that the information contained in the "UID" and "ID" fields are both game accounts. Therefore, the first fields containing the same information in multiple first behavior events can be determined based on the field mapping table.

[0040] S1102. Determine the field name of each first field according to a preset field naming rule, and create a new data structure according to the field name of each first field; the new data structure includes the first field and redundant fields.

[0041] Exemplarily, the field naming rule defines the field names of fields containing various information, such as the field naming rule defines the field name of the field containing the game account as "UID". Based on the information contained in the first field, the field containing the corresponding information can be queried in the field naming rule, and the field name of the queried field is used as the field name of the first field. If the first field contains the game account, the field name "UID" of the field containing the game account in the field naming rule is determined as the field name of the first field containing the game account. After determining the field name of each first field one by one, a new data structure is constructed according to the field name of each first field. In addition to the first field, the new data structure also includes redundant fields, so that important event attribute information other than the first field can be stored through the redundant fields.

[0042] S1103: Extract a field value corresponding to the first field in the first behavior event, and fill the extracted field value into the first field corresponding to the new data structure.

[0043] Exemplarily, first event data corresponding to the first behavior event is created based on the new data structure, field values ​​in each first field are extracted in the first behavior event, and the extracted field values ​​are filled into the first field corresponding to the first event data. For example, in the case where the first field is a field containing a game account, the game account is extracted from the first field of the first behavior event, and the extracted game account is filled into the first field corresponding to the game account in the first event data.

[0044] S1104: extract event attributes from attribute fields other than the first field of the first behavior event, fill the extracted event attributes into redundant fields corresponding to the new data structure, and obtain first event data corresponding to the first behavior event.

[0045] Exemplarily, event attributes are one of the important information of a behavior event. In order to ensure that the event attributes of the first behavior event can be queried subsequently or a matching first behavior event can be queried based on the event attributes, the event attributes can be extracted from the attribute field of the first behavior event, and the extracted event attributes can be filled into the redundant field corresponding to the first event data to obtain the final generated first event data.

[0046] This embodiment converts each first behavior event into first event data of a new data structure by determining a first field containing the same information in each first behavior event, reconstructing a new data structure based on the first field, thereby integrating multi-terminal heterogeneous first behavior events into first event data of a unified structure, so that the first event data can be uniformly stored in the first event library, and the storage and query efficiency of behavior events can be effectively improved without lacking event information.

[0047] After the first behavior event is converted into the first event data, the first event data is stored in the first event library, so that the first event data that meets the query requirement can be quickly searched in the first event library later.

[0048] In one embodiment, the behavior events continuously triggered by the user in the game application can represent some of the user's habitual preferences and behavior paths, so some continuously triggered behavior events can be combined to generate new combined events, and the user's behavior characteristics can be analyzed through the combined events. Figure 3 FIG. 1 is a flowchart of combining first event data to generate first combined event data provided by an embodiment of the present application. Figure 3 As shown, the step of combining the first event data to generate first combined event data specifically includes S1501-S1503:

[0049] S1501. According to user accounts in a plurality of first event data, first event data corresponding to the same user account are divided into the same first data set.

[0050] Exemplarily, since the combined event is a combination of a series of behavioral events continuously triggered by the user, the corresponding user account can be extracted from the user account field of each first event data, and the corresponding user account of each first event data is compared, and the first event data triggered by the same user account is divided into the same first data set, so as to subsequently generate the combined event triggered by the user account in the first data set. It should be noted that the user account in the first event data is the account used by the user to log in to each game application, which is generally the user's mobile phone number, email address, etc. A user account can correspond to multiple game accounts. The game account is the account belonging to the game character when the game character logs in to the game. The game account is generated by the game server when the user registers the game character. The user account represents the corresponding user. In order to clarify which user triggered each first behavior event, each first behavior event will contain a user account field, so the corresponding user account can be extracted from each event data.

[0051] S1502. According to a preset first event combination rule, a plurality of target event data to be combined is determined in a first data set; the first event combination rule is used to specify the types of the plurality of first behavior events to be combined.

[0052] Exemplarily, the business personnel may filter out the first behavior events that the user will trigger continuously in advance, and define the first event combination rule based on the filtered first behavior events. The first event combination rule specifies which continuously triggered first behavior events can be combined into a combination event. The first event data with continuous triggering time can be determined in the first data set, and at least one group of target event data to be combined can be determined in the first event data with continuous triggering time according to the first event combination rule, and each group of target event data to be combined includes more than two target event data. For example, the first event combination rule defines that the continuously triggered first behavior event A and the first behavior event B can be combined into a combined event, and the triggering time of the first behavior event A, the first behavior event B and the first behavior event C corresponding to the first event data is determined to be continuous in the first data set. Then, the first event data corresponding to the first behavior event A and the first behavior event B can be determined as a group of target event data to be combined according to the first event combination rule. It should be noted that the triggering time of the first behavior event is also one of the important information. Each first behavior event will have a field containing the triggering time, so the first event data corresponding to the first behavior event also contains the triggering time of the corresponding first behavior event.

[0053] S1503: Combine a plurality of target event data to be combined to obtain first combined event data, and store the first combined event data in a preset first combined event library.

[0054] Exemplarily, a plurality of target event data to be combined in a group are combined to obtain corresponding first combined event data, and the combination method may be field concatenation, that is, the first combined event data includes field information of the corresponding combined target event data. The first combined event data is stored in a preset first combined event library, so that the first combined event data that meets the query requirements can be quickly queried in the first combined event library later.

[0055] This embodiment combines continuously triggered first event data that meets the first event combination rule, and stores the combined first combination event data in a first combination event library, so as to query continuously triggered first behavior events in the first combination event library, thereby improving the query capability and query scope of the query service.

[0056] S120: Acquire a second behavior event triggered by a third-party application through a third-party tracking point, perform heterogeneous integration processing on the acquired multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library.

[0057] Exemplarily, business personnel configure multiple third-party applications connected to the query server, and embed points in the third-party applications to collect second behavior events triggered by users. When the user triggers the second behavior event, the third-party application reports the second behavior event to the server, and the server receives the second behavior event reported by the third-party application through an asynchronous queue. Among them, third-party applications are generally game promotion platforms, such as short video platforms and social platforms. The embedding points of third-party applications are used to obtain second behavior events such as users watching, clicking, liking and commenting on game advertisements.

[0058] After obtaining multiple second behavior events reported by each third-party application, the multiple second behavior events are heterogeneously integrated to convert the multiple second behavior events into the same data structure, obtain the second event data corresponding to each second behavior event, and store the second event data with a unified data structure in a preset second event library. The process of heterogeneous integration of the second behavior event is as follows: according to the preset field mapping table, determine the second field containing the same information in the multiple second behavior events obtained; according to the preset field naming rule, determine the field name of each second field, and create a new data structure according to the field name of each second field; the new data structure includes a second field and a redundant field; extract the field value corresponding to the second field in the second behavior event, and fill the extracted field value into the second field corresponding to the new data structure; extract the event attribute from the attribute field other than the second field of the second behavior event, and fill the extracted event attribute into the redundant field corresponding to the new data structure, and obtain the second event data corresponding to the second behavior event. It should be noted that the field mapping table and field naming rule used in the heterogeneous integration process of the first behavior event and the heterogeneous integration process of the second behavior event can be the same or different.

[0059] After the second behavior event is converted into the second event data, the second event data is stored in the second event library, so that the second event data that meets the query requirement can be quickly searched in the first event library later.

[0060] In one embodiment, the behavior events continuously triggered by the user in the third-party application can represent some of the user's habitual preferences and behavior paths, so some continuously triggered behavior events can be combined to generate new combined events, and the user's behavior characteristics can be analyzed through the combined events. Figure 4 FIG. 1 is a flow chart of combining the second event data to generate the second combined event data provided by an embodiment of the present application. Figure 4 As shown, the step of combining the second event data to generate second combined event data specifically includes S1601-S1603:

[0061] S1601. According to user accounts in a plurality of second event data, second event data corresponding to the same user account are divided into the same second data set.

[0062] Exemplarily, the corresponding user account is extracted from the user account field of each second event data, the corresponding user account of each second event data is compared, and the second event data triggered by the same user account is divided into the same second data set, so as to subsequently generate a combined event triggered by the corresponding user account in the second data set. It should be noted that the user account in the second event data is the account used by the user to log in to each third-party application, which is generally the user's mobile phone number, email address, etc. The user account represents the corresponding user. In order to clarify which user triggered each second behavior event, each second behavior event will contain a user account field, so the corresponding user account can be extracted from each second event data.

[0063] S1602. According to a preset second event combination rule, a plurality of target event data to be combined is determined in the second data set; the second event combination rule is used to specify the types of the plurality of second behavior events to be combined.

[0064] Exemplarily, business personnel may screen out second behavior events that will be continuously triggered by users in advance, and define second event combination rules based on the screened second behavior events. The second event combination rules specify which continuously triggered second behavior events can be combined into a combined event. Second event data with continuous triggering times may be determined in the second data set, and at least one group of target event data to be combined may be determined from the second event data with continuous triggering times based on the second event combination rules, and each group of target event data to be combined includes more than two target event data. It should be noted that the triggering time of the second behavior event is also one of the important information, and each second behavior event will have a field containing the triggering time, so the second event data corresponding to the second behavior event also includes the triggering time of the corresponding second behavior event.

[0065] S1603: Combine a plurality of target event data to be combined to obtain second combined event data, and store the second combined event data in a preset second combined event library.

[0066] Exemplarily, a plurality of target event data to be combined in a group are combined to obtain corresponding second combined event data, and the combination method may be field concatenation, that is, the second combined event data includes field information of the corresponding combined target event data. The second combined event data is stored in a preset second combined event library, so that the second combined event data that meets the query requirements can be quickly queried in the second combined event library later.

[0067] This embodiment combines the continuously triggered second event data that meets the second event combination rule, and stores the combined second combination event data in a second combination event library, so as to query the continuously triggered second behavior events in the second combination event library, thereby improving the query capability and query scope of the query service.

[0068] S130: Receive an event query request, and determine a target event repository in the first event repository and the second event repository according to an event source of an event to be queried in the event query request.

[0069] Among them, the event query request is an instruction for requesting the query server to query the corresponding event. Exemplarily, the operation personnel or business personnel can configure the event source, event type, event dimension and event indicator caliber of the event to be queried on the front end of the query server. The front end generates an event query request based on the event source, event type, event dimension and event indicator caliber of the event to be queried, and passes the event query request to the back end of the query server. The back end obtains the event source of the event to be queried in the received event query request. If the event source is a game application, the first event library is determined as the target event library. If the event source is a third-party application, the second event library is determined as the target event library.

[0070] In this embodiment, when creating the first combined event library and the second combined event library, if the number of event types of the event to be queried in the event query request is greater than one, the target event library is determined in the first combined event library and the second combined event library according to the event source of the event to be queried. Exemplarily, when the operator or business personnel want to query the behavior events triggered continuously, the event sources, event types, event dimensions and event indicator calibers of more than two behavior events can be configured at the front end of the query service end, and the front end generates an event query request according to the event sources, event types, event dimensions and event indicator calibers of more than two behavior events configured, and transmits the event query request to the back end. When the number of event types of the event to be queried in the event query request is greater than one, the back end can determine that the event corresponding to the query of the event query request is a combined event, and then determine the target event library in the first combined event library and the second combined event library. When the event source of the event to be queried in the event query request is a game application, the first combined event library is determined as the target event library, and when the event source of the event to be queried in the event query request is a third-party application, the second combined event library is determined as the target event library.

[0071] In one embodiment, the first event library, the second event library, the first combined event library, and the second combined event library all use a distributed database to improve data query efficiency. Alternatively, the first event library, the second event library, the first combined event library, and the second combined event library can also be implemented through redis, and the event data can be cached through caching technology to reduce the number of database accesses.

[0072] S140: Query target event data of the event to be queried in the target event library according to the event type, event dimension, and event indicator caliber of the event to be queried in the event query request.

[0073] Exemplarily, after determining the target event library corresponding to the event to be queried, the target event library can be queried for target event data that matches the event type, event dimension and event indicator caliber according to the event type, event dimension and event indicator caliber of the event to be queried.

[0074] In this embodiment, Figure 5 It is a flowchart of querying target event data provided by an embodiment of the present application.

[0075] like Figure 5 As shown, the step of querying target event data specifically includes S1401-S1403:

[0076] S1401. Acquire corresponding candidate event data in a target event library according to the event type and event dimension of the event to be queried.

[0077] Among them, the event dimensions include triggering time period, game, zone, character, etc. Exemplarily, assuming that the target event library is the first event library, the event type of the event to be queried is a recharge event, and the event dimensions of the event to be queried include triggering time period T1, game A, and zone N, then the first event data of the event type of the recharge event is queried in the first event library, and the first event data of the recharge event triggered by zone N of game A within the triggering time period T is screened out as candidate event data.

[0078] S1402: Determine, based on the user account in the candidate event data, the candidate event data corresponding to the same account.

[0079] Exemplarily, the candidate event data are candidate event data corresponding to multiple users. In order to subsequently determine whether the candidate event data corresponding to each user meets the event statistical caliber, the candidate event data corresponding to the same account can be divided into the same third data set according to the user account in the candidate event data.

[0080] S1403: When the candidate event data corresponding to the same account meets the event indicator caliber, the candidate event data is determined as the target event data of the event to be queried.

[0081] Among them, the event indicator caliber can be understood as the logical conditions for behavioral events to meet the indicators. Candidate event data that meet the event indicator caliber is screened out from the third data set as the target event data of the event to be queried. For example, the event indicator caliber can be that the user recharges for 7 consecutive days, then the candidate event data of the recharge event being triggered for 7 consecutive days is screened out from the third data set as the target event data. If the third data set does not contain candidate event data of the recharge event being triggered for 7 consecutive days, it is determined that the target event data does not exist in the third data set. For the activity operation strategy, if rewards are issued to users who recharge for 7 consecutive days, after obtaining the target event data of the recharge event being triggered for 7 consecutive days, the activity rewards can be issued to the corresponding users who meet the activity award requirements according to the user accounts in the target event data.

[0082] Since the behavior events collected by the query server are specified by business personnel based on business needs, there is a situation where the behavior events that the operator wants to query are not collected and stored by the query server, so the query server cannot query the corresponding behavior events, resulting in query failure. In order to further improve the event query capability and event query scope of the query server, when it is detected that the event type of the event to be queried is not stored in the target event library, the query server can collect the behavior events corresponding to the event type based on the event source of the event to be queried, and then store the collected behavior events to support subsequent queries on behavior events of this event type.

[0083] The specific implementation process is: when the event type of the event to be queried does not match the event type of the data in the target event library, the access method of the event to be queried is determined according to the preset data access rules and the event type of the event to be queried, and the access methods include asynchronous access and synchronous access; when the access method is asynchronous access, the behavior event corresponding to the event to be queried is obtained through the asynchronous queue and the event source of the event to be queried, and the obtained behavior event is heterogeneously integrated and stored in the preset database; when the access method is synchronous access, the behavior event corresponding to the event to be queried is obtained through the synchronous interface and the event source of the event to be queried, and the obtained behavior event is heterogeneously integrated and stored in the preset database. Exemplarily, when the event type of the event to be queried is different from the event type of any event data in the target event library, it indicates that the query server has not collected the event to be queried, so the query server needs to collect the behavior event corresponding to the event type through the data source of the event to be queried. In order to collect the event to be queried, in addition to determining the event source of the event to be queried, the access method of the event to be queried must also be determined. Since the access methods corresponding to various behavior events are defined in the data access rules, the access methods of the events to be queried can be determined in the data access rules according to the event types of the events to be queried. The query server collects the behavior events corresponding to the event types of the events to be queried according to the access methods and event sources of the events to be queried, so as to subsequently filter out the events to be queried from the collected behavior events. The access methods include asynchronous access and synchronous access. When the access method of the events to be queried is asynchronous access, the behavior events corresponding to the event types of the events to be queried are obtained from the behavior events reported by the event sources of the events to be queried, and the obtained behavior events are cached in the asynchronous queue. When the access method of the events to be queried is synchronous access, the behavior events corresponding to the event types of the events to be queried are obtained from the behavior events reported by the event sources of the events to be queried, and the obtained behavior events are passed to the synchronous interface. Regardless of whether the behavior events are obtained by synchronous access or asynchronous access, heterogeneous integration processing must be performed to unify the data structure of the behavior events for the storage and query of the behavior events. The database where the behavior events are stored after heterogeneous integration is determined by the source of the event. If the behavior event is triggered by a game application, it is stored in the first event library after heterogeneous integration. If the behavior event is triggered by a third-party application, it is stored in the second event library after heterogeneous integration. After the behavior events corresponding to the event type of the event to be queried are heterogeneously integrated and stored in the database, the query server can query the event to be queried of the event query request in the database. Even if the subsequent operation personnel want to query the behavior events corresponding to the event type, the query server also supports the query, which effectively improves the query capability and query scope of the query server.

[0084] In summary, the game behavior event processing method provided by the embodiment of the present application obtains the first behavior event triggered by the game application through an asynchronous queue or a synchronous interface, performs heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and stores the multiple first event data in a preset first event library; obtains the second behavior event triggered by the third-party application through a third-party buried point, performs heterogeneous integration processing on the obtained multiple second behavior events to obtain multiple second event data, and stores the multiple second event data in a preset second event library; receives an event query request, and determines the target event library in the first event library and the second event library according to the event source of the event to be queried in the event query request; according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request, the target event data of the event to be queried is queried in the target event library. Through the above technical means, the obtained behavior events can be heterogeneously integrated and then stored in the event library, which solves the problem of storing behavior events of different data types separately in the prior art. When querying behavior events later, there is no need to query multiple databases one by one, which reduces the complexity of storage operations and query operations, and improves the storage efficiency and query efficiency of behavior events. It can collect behavioral events of game applications and third-party applications, expand the query scope of behavioral events, and meet the vast majority of behavioral event query needs. It can efficiently query target events in the event library based on the event type, event dimension, and event indicator caliber of the query time, improving the query efficiency of behavioral events.

[0085] Based on the above embodiments, Figure 6 This is a schematic diagram of the structure of a game behavior event processing device provided in an embodiment of the present application. Figure 6 The game behavior event processing device provided in this embodiment specifically includes: a first event storage module 21, a second event storage module 22, an event library determination module 23 and a target event query module 24.

[0086] The first event storage module 21 is configured to obtain the first behavior event triggered by the game application through an asynchronous queue or a synchronous interface, perform heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and store the multiple first event data in a preset first event library;

[0087] The second event storage module 22 is configured to obtain a second behavior event triggered by a third-party application through a third-party embedding point, perform heterogeneous integration processing on the obtained multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library;

[0088] The event library determination module 23 is configured to receive an event query request, and determine a target event library in the first event library and the second event library according to an event source of an event to be queried in the event query request;

[0089] The target event query module 24 is configured to query the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request.

[0090] Based on the above embodiments, the first event storage module 21 includes: a first field determination unit, configured to determine the first field containing the same information in the multiple first behavior events acquired according to a preset field mapping table; a data structure creation unit, configured to determine the field name of each first field according to a preset field naming rule, and create a new data structure according to the field name of each first field; the new data structure includes a first field and a redundant field; a field information filling unit, configured to extract the field value corresponding to the first field in the first behavior event, and fill the extracted field value into the first field corresponding to the new data structure; an event data generation unit, configured to extract event attributes from the attribute field other than the first field of the first behavior event, and fill the extracted event attributes into the redundant field corresponding to the new data structure to obtain the first event data corresponding to the first behavior event.

[0091] On the basis of the above embodiments, the game behavior event processing device includes a first combination event storage module, and the first combination event storage module includes: a first set division unit, which is configured to, after heterogeneously integrating the acquired multiple first behavior events to obtain multiple first event data, divide the first event data corresponding to the same user account into the same first data set according to the user accounts in the multiple first event data; a first to-be-combined data determination unit, which is configured to determine multiple target event data to be combined in the first data set according to a preset first event combination rule; the first event combination rule is used to specify the types of the combined multiple first behavior events; a first combination event generation unit, which is configured to combine multiple target event data to be combined to obtain first combination event data, and store the first combination event data in a preset first combination event library.

[0092] On the basis of the above embodiment, the game behavior event processing device includes a second combination event storage module, and the second combination event storage module includes: a second set division unit, which is configured to, after heterogeneously integrating the acquired multiple second behavior events to obtain multiple second event data, divide the second event data corresponding to the same user account into the same second data set according to the user accounts in the multiple second event data; a second data to be combined determination unit, which is configured to determine multiple target event data to be combined in the second data set according to a preset second event combination rule; the second event combination rule is used to specify the type of the combined multiple second behavior events; a second combination event generation unit, which is configured to combine at least multiple target event data to be combined to obtain second combination event data, and store the second combination event data in a preset second combination event library.

[0093] Based on the above embodiment, the event library determination module 23 includes: a combined event library determination unit, which is configured to, after receiving an event query request, determine the target event library in the first combined event library and the second combined event library according to the event source of the event to be queried if the number of event types of the event to be queried in the event query request is greater than one.

[0094] On the basis of the above embodiment, the target event query module includes: a candidate event determination unit, configured to obtain corresponding candidate event data in the target event library according to the event type and event dimension of the event to be queried; a candidate event classification unit, configured to determine the candidate event data corresponding to the same account according to the user account in the candidate event data; a target event determination unit, configured to determine the candidate event data as the target event data of the event to be queried when the candidate event data corresponding to the same account meets the event indicator caliber.

[0095] On the basis of the above embodiments, the game behavior event processing device includes an event supplement acquisition module, which includes: an access mode determination unit, which is configured to determine the target event library in the first event library and the second event library, and when the event type of the event to be queried does not match the event type of the data in the target event library, determine the access mode of the event to be queried according to the preset data access rules and the event type of the event to be queried, and the access mode includes asynchronous access and synchronous access; an asynchronous access unit, which is configured to obtain the behavior event corresponding to the event to be queried through the asynchronous queue and the event source of the event to be queried when the access mode is asynchronous access, and store the obtained behavior event in a preset database after performing heterogeneous integration processing; a synchronous access unit, which is configured to obtain the behavior event corresponding to the event to be queried through the synchronous interface and the event source of the event to be queried when the access mode is synchronous access, and store the obtained behavior event in a preset database after performing heterogeneous integration processing.

[0096] As mentioned above, the game behavior event processing device provided by the embodiment of the present application obtains the first behavior event triggered by the game application through an asynchronous queue or a synchronous interface, performs heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and stores the multiple first event data in a preset first event library; obtains the second behavior event triggered by the third-party application through a third-party embedding point, performs heterogeneous integration processing on the obtained multiple second behavior events to obtain multiple second event data, and stores the multiple second event data in a preset second event library; receives an event query request, and determines the target event library in the first event library and the second event library according to the event source of the event to be queried in the event query request; according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request, the target event data of the event to be queried is queried in the target event library. Through the above technical means, the obtained behavior events can be heterogeneously integrated and then stored in the event library, which solves the problem of storing behavior events of different data types separately in the prior art. When querying behavior events later, there is no need to query multiple databases one by one, which reduces the complexity of storage operations and query operations, and improves the storage efficiency and query efficiency of behavior events. It can collect behavioral events of game applications and third-party applications, expand the query scope of behavioral events, and meet the vast majority of behavioral event query needs. It can efficiently query target events in the event library based on the event type, event dimension, and event indicator caliber of the query time, improving the query efficiency of behavioral events.

[0097] The game behavior event processing device provided in the embodiment of the present application can be used to execute the game behavior event processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0098] Figure 7 is a schematic diagram of a game behavior event processing device provided in an embodiment of the present application, with reference to Figure 7 The game behavior event processing device includes: a processor 31, a memory 32, a communication device 33, an input device 34 and an output device 35. The number of processors 31 in the game behavior event processing device can be one or more, and the number of memories 32 in the game behavior event processing device can be one or more. The processor 31, memory 32, communication device 33, input device 34 and output device 35 of the game behavior event processing device can be connected through a bus or other methods.

[0099] The memory 32, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the game behavior event processing method of any embodiment of the present application (for example, the first event storage module 21, the second event storage module 22, the event library determination module 23 and the target event query module 24 in the game behavior event processing device). The memory 32 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to the use of the device, etc. In addition, the memory 32 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0100] The communication device 33 is used for data transmission.

[0101] The processor 31 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 32, that is, implements the above-mentioned game behavior event processing method.

[0102] The input device 34 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 35 may include a display device such as a display screen.

[0103] The game behavior event processing device provided above can be used to execute the game behavior event processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0104] The embodiment of the present application also provides a storage medium containing computer executable instructions, which are used to execute a game behavior event processing method when executed by a computer processor. The game behavior event processing method includes: obtaining a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, heterogeneously integrating the multiple first behavior events obtained to obtain multiple first event data, and storing the multiple first event data in a preset first event library; obtaining a second behavior event triggered by a third-party application through a third-party embedding point, heterogeneously integrating the multiple second behavior events obtained to obtain multiple second event data, and storing the multiple second event data in a preset second event library; receiving an event query request, and determining a target event library in the first event library and the second event library according to the event source of the event to be queried in the event query request; and querying the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request.

[0105] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0106] Of course, the storage medium containing computer executable instructions provided in the embodiment of the present application, whose computer executable instructions are not limited to the above-mentioned game behavior event processing method, can also execute related operations in the game behavior event processing method provided in any embodiment of the present application.

[0107] The game behavior event processing apparatus, storage medium, and game behavior event processing device provided in the above embodiments can execute the game behavior event processing method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the game behavior event processing method provided in any embodiment of the present application.

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

Claims

1. A method for processing game behavior events, characterized in that: include: Acquire a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, perform heterogeneous integration processing on the acquired multiple first behavior events to obtain multiple first event data, and store the multiple first event data in a preset first event library; Acquire a second behavior event triggered by a third-party application through a third-party tracking point, perform heterogeneous integration processing on the acquired multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library; Combining two or more of the first event data to obtain first combined event data, storing the first combined event data in a preset first combined event library, combining two or more of the second event data to obtain second combined event data, storing the second combined event data in a preset second combined event library; receiving an event query request, and if the number of event types of the events to be queried in the event query request is equal to one, determining a target event repository in the first event repository and the second event repository according to event sources of the events to be queried in the event query request; If the number of event types of the events to be queried in the event query request is greater than one, determining a target event library in the first combined event library and the second combined event library according to event sources of the events to be queried; According to the event type, event dimension and event indicator caliber of the event to be queried in the event query request, the target event data of the event to be queried is queried in the target event library.

2. The method for processing game behavior events according to claim 1, characterized in that: The heterogeneous integration processing of the acquired multiple first behavior events to obtain multiple first event data includes: Determining, according to a preset field mapping table, first fields containing the same information in the acquired multiple first behavior events; Determine the field name of each of the first fields according to a preset field naming rule, and create a new data structure according to the field name of each of the first fields; the new data structure includes the first field and the redundant field; Extracting a field value corresponding to the first field in the first behavior event, and filling the extracted field value into the first field corresponding to the new data structure; Event attributes are extracted from attribute fields other than the first field of the first behavior event, and the extracted event attributes are filled into redundant fields corresponding to the new data structure to obtain first event data corresponding to the first behavior event.

3. The game behavior event processing method according to claim 1, characterized in that: The step of combining two or more of the first event data to obtain first combined event data, and storing the first combined event data in a preset first combined event library includes: According to the user accounts in the plurality of first event data, the first event data corresponding to the same user account are divided into the same first data set; According to a preset first event combination rule, a plurality of target event data to be combined is determined in the first data set; the first event combination rule is used to specify the types of the plurality of first behavior events to be combined; The plurality of target event data to be combined are combined to obtain first combined event data, and the first combined event data is stored in a preset first combined event library.

4. The method for processing game behavior events according to claim 1, characterized in that: The step of combining two or more of the second event data to obtain second combined event data, and storing the second combined event data in a preset second combined event library comprises: According to the user accounts in the plurality of second event data, the second event data corresponding to the same user account are divided into the same second data set; According to a preset second event combination rule, a plurality of target event data to be combined is determined in the second data set; the second event combination rule is used to specify the types of the plurality of second behavior events to be combined; The plurality of target event data to be combined are combined to obtain second combined event data, and the second combined event data is stored in a preset second combined event library.

5. The game behavior event processing method according to claim 1, characterized in that: The querying of the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request includes: According to the event type and event dimension of the event to be queried, obtaining corresponding candidate event data in the target event library; Determine, based on the user account in the candidate event data, the candidate event data corresponding to the same account; When the candidate event data corresponding to the same account meets the event indicator caliber, the candidate event data is determined as the target event data of the event to be queried.

6. The method for processing game behavior events according to claim 1, characterized in that: After determining a target event library in the first event library and the second event library, the method further includes: In the case that the event type of the event to be queried does not match the event type of the data in the target event library, determining the access mode of the event to be queried according to the preset data access rule and the event type of the event to be queried, wherein the access mode includes asynchronous access and synchronous access; In the case where the access mode is asynchronous access, the behavior event corresponding to the event to be queried is obtained through the asynchronous queue and the event source of the event to be queried, and the obtained behavior event is heterogeneously integrated and stored in a preset database; In the case where the access mode is synchronous access, the behavior event corresponding to the event to be queried is obtained through the synchronous interface and the event source of the event to be queried, and the obtained behavior event is heterogeneously integrated and stored in a preset database.

7. A gaming behavior event processing device, characterized in that: include: A first event storage module is configured to obtain a first behavior event triggered by a game application through an asynchronous queue or a synchronous interface, perform heterogeneous integration processing on the obtained multiple first behavior events to obtain multiple first event data, and store the multiple first event data in a preset first event library; The second event storage module is configured to obtain a second behavior event triggered by a third-party application through a third-party embedding point, perform heterogeneous integration processing on the obtained multiple second behavior events to obtain multiple second event data, and store the multiple second event data in a preset second event library; an event library determination module configured to receive an event query request, and if the number of event types of the events to be queried in the event query request is equal to one, determine a target event library in the first event library and the second event library according to the event source of the events to be queried in the event query request; A target event query module is configured to query the target event data of the event to be queried in the target event library according to the event type, event dimension and event indicator caliber of the event to be queried in the event query request; The game behavior event processing device is further configured to: after storing the plurality of second event data in a preset second event library, combine two or more of the first event data to obtain first combined event data, store the first combined event data in a preset first combined event library, combine two or more of the second event data to obtain second combined event data, and store the second combined event data in a preset second combined event library; An event query request is received, and if the number of event types of the events to be queried in the event query request is greater than one, a target event library is determined in the first combined event library and the second combined event library according to event sources of the events to be queried.

8. A game behavior event processing device, characterized in that: include: one or more processors; A memory stores one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the game behavior event processing method as described in any one of claims 1-6.

9. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to execute the game behavior event processing method as described in any one of claims 1-6 when executed by a computer processor.

Images