CN114768259A

CN114768259A - Event management method and device, computer readable storage medium and computer equipment

Info

Publication number: CN114768259A
Application number: CN202210442552.2A
Authority: CN
Inventors: 马鸣; 王焱
Original assignee: Netease Hangzhou Network Co Ltd
Current assignee: Netease Hangzhou Network Co Ltd
Priority date: 2022-04-25
Filing date: 2022-04-25
Publication date: 2022-07-22

Abstract

The embodiment of the application discloses an event management method, an event management device, a computer readable storage medium and computer equipment. The method comprises the following steps: receiving an event creation request aiming at a target application from a request terminal through a first server, and acquiring an event template type of an event corresponding to the event creation request and configuration parameter information of the event; generating an event instance of the event according to the event template type and the configuration parameter information; generating an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type; the management of the event is implemented according to the event management instance of the event instance. The embodiment of the application realizes the self-definition of the events, improves the event experience of the user, and improves the efficiency and the applicability of event management.

Description

Event management method and device, computer readable storage medium and computer equipment

Technical Field

The present application relates to the field of data processing technologies, and in particular, to an event management method and apparatus, a computer-readable storage medium, and a computer device.

Background

The rapid development of communication technology brings great improvement to the life of users, and users can install various applications on user equipment for use, such as game applications.

In some applications, various online events can be performed generally, the online events in the current applications are basically small events and the occurrence of large events is small, so in the current design, the management of the online events and the management of the applications themselves are generally coupled together, when the events provided by the applications are small events, no obvious problem generally occurs, and when the events provided by the applications are large events, the management of the events and the management of the applications themselves are coupled together, which reduces the efficiency of event management and the experience of the events.

In addition, the online events in the target application are basically provided by the game, all information such as flow and details of the events are fixed, and the users cannot change the information, so that the event experience of the users is reduced.

Disclosure of Invention

The embodiment of the application provides an event management method and device, a computer-readable storage medium and computer equipment, which can create an event, improve the event experience of a user and simultaneously improve the efficiency and the applicability of event management.

The embodiment of the application provides an event management method, which comprises the following steps:

receiving an event creation request aiming at a target application from a request terminal through a first server, and acquiring an event template type of an event corresponding to the event creation request and configuration parameter information of the event;

generating an event instance of the event according to the event template type and the configuration parameter information;

generating an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type;

and realizing the management of the events according to the event management examples of the event examples.

An embodiment of the present application further provides an event management device, including:

the system comprises an acquisition module, a first server and a second server, wherein the acquisition module is used for receiving an event creating request aiming at a target application from a request terminal through the first server, and acquiring an event template type of an event corresponding to the event creating request and configuration parameter information of the event;

the first generation module is used for generating an event instance of the event according to the event template type and the configuration parameter information;

a second generating module, configured to generate an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type;

and the management module is used for realizing the management of the events according to the event management instances of the event instances.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, where the computer program is suitable for being loaded by a processor to execute steps in the event management method according to any one of the above embodiments.

The embodiment of the present application further provides a computer device, where the computer device includes a memory and a processor, where the memory stores a computer program, and the processor executes the steps in the event management method according to any of the above embodiments by calling the computer program stored in the memory.

The event management method, the device, the computer-readable storage medium and the computer device provided by the embodiments of the present application receive an event creation request from a request end for a target application, acquire an event template type and configuration parameter information of an event corresponding to the event of the target application according to the event creation request, that is, the embodiment of the present application can implement setting of the configuration parameter information of the event, and at the same time, acquire an event template type corresponding to the event, and generate an event instance according to the configuration parameter information and the event template type to create the event, thereby implementing customization/configuration of the event, improving the event experience of a user, and in the embodiment of the present application, create an event management instance for at least one event management component of the event instance, integrate the management of the event in the event management component, implement the management of the event through the event management instance corresponding to the event management component, the efficiency and the applicability of the event management are improved, in addition, the event management is centralized on the first server, the event management and the target application are unrelated, and the efficiency of the event management is further improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic view of an application scenario of the event management method according to the embodiment of the present application.

Fig. 2 is a schematic flow chart of the event management method according to the embodiment of the present application.

Fig. 3 is a schematic diagram of an event management component included in an event example provided in the embodiment of the present application.

Fig. 4 is a schematic diagram of an example of an event provided by an embodiment of the present application.

Fig. 5 is a sub-flow schematic diagram of the event management method according to the embodiment of the present application.

Fig. 6 is a schematic sub-flow chart of the event management method according to the embodiment of the present application.

Fig. 7 is another sub-flow diagram of the event management method according to the embodiment of the present application.

Fig. 8 is a schematic flowchart of a method for event management according to an embodiment of the present application.

Fig. 9 is a schematic diagram of a time axis provided in an embodiment of the present application.

Fig. 10 is a schematic flowchart of a method for event management according to an embodiment of the present application.

Fig. 11 is a schematic structural diagram of an event management device according to an embodiment of the present application.

Fig. 12 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides an event management method, an event management device, a computer readable storage medium and computer equipment. Specifically, the event management method according to the embodiment of the present application may be executed by a computer device, where the computer device may be a server device, for example, a first server. The first server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, big data and artificial intelligence platform.

The target application in the present application may be a learning application, a work application, a game application, or another application providing an event function, and is not limited specifically. For ease of understanding, the embodiments of the present application are described taking a game application as an example.

As shown in fig. 1, an application scenario diagram of an event management method provided in the embodiment of the present application is shown. The event management system comprises a first server, a second server and a third server, wherein the second server and the third server are consistent with the first server, and can be independent physical servers, a server cluster or distributed system formed by a plurality of physical servers, various cloud servers and the like.

The first server may be an event server, the second server may be a game server corresponding to a game application, and the third server may be a server corresponding to an advisory services application platform of a plurality of games, where the event server is communicatively connected to the game server and the third server, respectively. The game client accesses the game server through the network, and the client of the counseling service application (third client) accesses the third server through the network, wherein the third client does not refer to one client but is a generic name of a class of clients. In some cases, the game client may connect to the event server over TCP. The event management method in the embodiment of the application is applied to the event server, and the specific execution of the event is performed in the game server, so that the decoupling of event management and game management is realized, and the efficiency of game management is improved.

It should be noted that fig. 1 is only a schematic view of an application scenario, and the application scenario shown in fig. 1 is taken as an example for description in the embodiment of the present application. The event management method in the embodiment of the application can also be applied to an application scene comprising an event server and a game server, so that the event server corresponds to an event client, the event client is connected with the event server through a network, the game server corresponds to a game client, and the game client is connected with the game server through the network.

An event management method, an event management apparatus, a computer-readable storage medium, and a computer device provided in embodiments of the present application will be described in detail below. The numbers in the following examples are not intended to limit the order of preference of the examples.

Fig. 2 is a schematic flowchart of an event management method according to an embodiment of the present application, where the event management method is applied to a first server, and specifically includes the following steps.

101, receiving an event creation request for a target application from a request end through a first server, and acquiring an event template type of an event corresponding to the event creation request and configuration parameter information of the event.

The first server may be a third server, or an event client, where the first server is an event server. The target applied events are online events, and competitors can carry out remote fight through network connection.

For example, an initiation request for holding/creating an event is initiated on the third client, and a parameter configuration interface is called by the initiation request, and an event template type, such as an event template type of a master cup event system, a ball tournament event system, a card game system, and the like, can be set/selected/input on the parameter configuration interface, and configuration parameter information including a match mode (a team event, a knockout event, and the like), participation conditions of a contest, an event entry number, each team entry number, a waiting time per race period, a match time, a knockout event time, a number of battle fields of a knockout event, final win conditions, and the like can be set/selected/input on the parameter configuration interface.

The configuration parameter information is an option for customizing the events exposed to different games, and if the corresponding option is not set/selected/input on the parameter setting interface, default configuration parameter information is adopted. Or, the corresponding event template type and configuration parameter information may also be obtained by other manners, such as writing the event template type and configuration parameter information into a file, loading the file through a third client, reading the corresponding event template type and configuration parameter information, and the like. Therefore, the custom setting/configuration of the event template type and the configuration parameter information of the event is realized, and a basis is provided for realizing the custom setting of the event.

And after the event template type and the configuration parameter information are set, selected or input, triggering the corresponding control to generate an event creating request for creating the event of the target application, wherein the event creating request comprises the event template type and the configuration parameter information of the event of the target application. The third server receives the event creating request aiming at the target application, does not perform any business processing on the event creating request, and directly forwards the event creating request to the event server, so that the event server receives the event creating request aiming at the target application from the third server and obtains the event template type of the corresponding event and the configuration parameter information of the event in the event creating request.

Wherein, the event creating request also includes the first identification information of the event creating user object, such as the user name and/or number of the event creating user object, after the event server receives the event creating request from the third server for the target application, acquiring event creating user object information corresponding to the first identification information from a second server corresponding to the target application through the first service interface, wherein the event creating user object information comprises information related to creating conditions, such as the level and/or privilege of an event creating user object, and the like, and the event server determines whether the event creating user object meets the creating conditions of the event of the target application according to the event creating user object information, wherein, the creating condition of the event can be set in advance, if the creating condition of the event for creating the target application is satisfied, the following step 102 is executed; if not, prompting is carried out.

And 102, generating an event instance of the event according to the event template type and the configuration parameter information.

One event template type is designed as one event template class (class), and event template classes corresponding to different event template types are designed in the event server in advance. Calling the corresponding event template class according to the event template type, filling the corresponding field in the event template class according to the configuration parameter information, and generating the corresponding event instance according to the event template class filled with the corresponding field.

And after the event instance is generated, recording the event state of the event instance as an entry state, and storing.

103, generating an event management instance corresponding to the event instance according to the at least one event management component corresponding to the event template type.

The event template class corresponding to the event template type generally includes at least one event management component, such as a user object management component, a group management component, a course management component, a time management component, a storage management component, and the like. These event management components are briefly described below, and the event instances include event management components as shown in FIG. 3.

A user object management component: the system comprises a user object entity (MatchUser) and a user object logic component, wherein the user object logic component comprises a series of methods/functions.

A grouping management component: comprises a grouping entity (Matchgroup) and a grouping logic component, wherein the grouping logic component comprises a series of methods/functions.

The course management component: comprises a competition process entity (MatchSchedule) and a competition process logic component, wherein the competition process logic component comprises a series of methods/functions.

A time management component: the event status of the current event, the phase and round information of the team/knockout (which may correspond to the sub-course hereinafter), the timeline information, the timer component, and the related event binding functions for each round of the game, such as accounting logic, score statistics, ranking statistics, etc., are primarily recorded.

A storage management component: and is responsible for storing the event data in the database.

These event management components are also essentially event management template classes (classes). The method comprises the steps of determining at least one event management component corresponding to an event template type, calling an event management template class corresponding to the event management component, generating a corresponding event management instance according to the event management template class, and binding the generated event management instance with an event instance to obtain the event management instance corresponding to the event instance.

For example, the user object management component calls a user object management class corresponding to the user object management class, and generates a user object management instance (UserMgr) according to the user object management class; the grouping management component corresponds to the grouping management class and generates a grouping management instance (GroupMgr) according to the grouping management class; the course management component corresponds to the course management class and generates a course management instance (SchedulMgr) according to the course management class; the time management component corresponds to a time management class, and generates a time management instance (TimeLineMgr) according to the time management class, the time management component can also be called a process management component, and the process management instance is correspondingly generated; the storage management component corresponds to the storage management class and generates a storage management instance (PersistMgr) according to the storage management class.

These event management instances are dynamically generated by the event instances. For example, when an event instance is generated, a currently required user object management instance, a time management instance, a storage management instance, and the like may be automatically generated, and then a grouping management instance and a course management instance of the event instance may be generated according to requirements, because it is considered that if a creator of the event does not meet a creation condition for creating the event, or if the event does not reach the corresponding number of event report persons, the event may be dissuaded, and at this time, the grouping management instance and the course management instance of the event instance do not need to be generated, so as to reduce a storage space occupied by the grouping management instance and the event management instance. Or all required event management instances can be automatically generated when generating the event instances.

The relationship between the event instances and the event management instances may be as shown in fig. 4, where an event instance may include a user object management instance, a grouping management instance, an event schedule management instance, a time management instance, a storage management instance, and configuration parameter information, or may be understood as generating an event instance according to the user object management instance, the grouping management instance, the event schedule management instance, the time management instance, the storage management instance, and the configuration parameter information, or may be understood as including a corresponding event management template class (class) in an event template class (class), such as a user object management class, a grouping management class, an event schedule management class, a time management class, and a storage management class.

In the user object management example, a creator of the event (event creation user object), current entry information of the event, and the like are recorded. The time management component records the creation time of the event, the event status of the current event, the validity period of the event, and other more information in the time management component, which will be described later. The storage management instance stores the event-related data into the database, wherein the event-related data comprises data which needs to be stored and updated in each event management instance.

Management of the event is implemented in accordance with the event management instance of the event instance 104.

In the process of managing the events, the event request of the target application is sent to the second server, so that the second server executes the events of the target application according to the event request, and the execution result of the events of the target application executed by the second server is obtained.

How the event management instance of the event instance implements the management of the event will be described below in terms of some of the major processes performed by the event instance.

After the event instance is created, the client of the advisory services application, i.e., the third client, may query the event portal for an event list of the created event. Specifically, the third client generates an event query request, where the event query request is used to request an event list of the created event, and sends the event query request to the third server, and since the third server does not have event information at this time, the third server forwards the event query request to the event server through the HTTP interface. The event server receives an event query request from a request end, the request end comprises a third server, the event list of the created events is queried according to the event query request, the event list is returned to the request end through a second service interface, and if the event list is returned to the third server, the third server returns the event list to the third client side for displaying. Similarly, the game client may also obtain the corresponding event through the game server. In some embodiments, the third server may periodically retrieve the corresponding event list from the event server, and the game server may periodically retrieve the corresponding event from the event server. Or in one embodiment, push to a third server or game server, etc. after the event creation on the event server is successful.

In one embodiment, as shown in fig. 5, the step 104 includes the following steps.

An event entry request for an event is received 201, the event entry request including second identification information of an event entry user object.

After the event list is displayed in the third client, the user may click/select an event in the event list to perform an event entry, for example, an entry control of the event on the third client is triggered, an event entry request is generated and sent to the third server, the event entry request includes second identification information of an event entry user object, and the third server forwards the event entry request to the event server. The event server receives an event entry request for an event from a requesting end, such as a third server, and obtains second identification information of the event entry user object in the event entry request, where the second identification information may be information such as a nickname and/or a number of the event entry user object.

202, calling the user object logic component in the user object management instance according to the second identification information.

And calling the user object logic component in the user object management instance according to the second identification information, and transmitting the second identification information serving as a parameter into a corresponding method/function in the user object logic component.

And 203, determining whether the event registration user object corresponding to the second identification information meets the participation condition of the event participating in the target application by using the user object logic component.

Accessing a second server such as a game server through a first service interface by using the user object logic component, and acquiring event entry user object information corresponding to the second identification information from the game server, such as information of the level of the event entry user object; the event server determines from the event entry user object information whether the event entry user object fulfils the participation conditions of the event of the target application, which may be set in advance, e.g. fixed for one event template type, or modified, e.g. in the configuration parameter information, etc.

If the event entry user object satisfies the entry condition for the event of the entry target application, step 204 is executed, and if not, step 205 is executed.

And 204, adding the event entry user object as a user object entity into the event queue of the event, and updating the event entry information of the event.

The user object management instance of the event instance adds the event entry user object as a user object entity to the event queue of the event and updates the current entry information in real time, for example, updates the current number of entries, etc. The information included in each user object entity is the same, and includes information such as a nickname, a rating, a user icon, and the like.

The user object entities in the event queue may be added or deleted, for example, when the event entry is cancelled, the corresponding user object entity in the event queue is deleted, and the current entry information is updated in real time.

205, prompt is performed.

If the event entry user object cannot meet the participation condition of the event participating in the target application, a corresponding prompt is made for the event entry user object.

In an embodiment, as shown in fig. 6, the step 104 further includes the following steps.

301, detecting whether the event meets the starting condition.

The registration process of the event registration continues until the registration time is finished or the registration number reaches the upper limit of the preset number of people, when the registration time is finished, whether the registration number of the event registration reaches the preset number of people corresponding to the match-out is detected, if so, the event is determined to meet the match-out condition, and if not, the match-out condition is determined not to be met. And when the registration time is not over and the number of registered people reaches the preset upper limit, determining that the event meets the starting condition. The race conditions of the events can be other conditions, and the race conditions corresponding to different events are different.

If the race start condition is satisfied, go to step 302, if the race start condition is not satisfied, go to step 306.

The event status of the event is modified into a group by the time management instance 302.

303, transmitting the event queue of the user object management instance to the group management instance.

If the grouping management example is not generated when the event example is generated, when the event is determined to meet the match-out condition, the grouping management component is instantiated to obtain the grouping management example. And transmitting the event queue of the user object management instance to the group management instance.

304, invoke the grouping logic component of the grouping management instance. If the corresponding grouping method/function in the grouping logic component is called, the event queue is used as a parameter and is transmitted into the corresponding grouping method/function.

And 305, grouping the user object entities in the event queue by using a grouping logic component to determine a group information list, wherein the group information list comprises the grouping entities corresponding to the grouping management instances, and each grouping entity comprises the user object entities included in each group.

And calculating a group information list (GroupList) by using a grouping method/function in the grouping logic component and corresponding grouping logic and rules, wherein each element in the group information list (GroupList) is a grouping entity (MatchGroup), and the grouping entity comprises a group number ID, a list (MatchUser list) corresponding to the user object entity of the current group and the like.

The event is dismissed 306 by the time management instance based on the event validity period.

The grouping procedure is implemented in this embodiment.

In an embodiment, as shown in fig. 7, the step 104 further includes the following steps.

The event status of the event is modified by the time management component to be in course calculations 401.

402, the list of group information in the group management instance is imported to the course management instance.

If the course management instance is not generated when the event instance is generated, the course management component is instantiated firstly to obtain the course management instance. And transmitting the list of the group information in the group management example to the course management example.

403, call the course logic component in the course management instance.

If the corresponding course computing method/function in the course logic component is called, the group information list is used as a parameter and is transmitted to the corresponding course computing method/function.

And 404, processing the grouping entities in the grouping information list by using the course logic component to determine a course instance corresponding to the event, where the course instance includes a course information list, the course information list includes at least one match run entity, and the match run entity includes match time information and a user object entity of the match.

And generating a course instance corresponding to the event by using a course computing method/function in the course logic component and through corresponding course logic and rules, wherein the course instance comprises a course information list, the course information list comprises at least one competition counterpoint entity, and each competition counterpoint entity comprises information of each competition, such as competition field ID, user object entities of two competition parties, score information of the two competition parties, competition time information and the like.

Generally, the course information corresponding to a large-scale course example can be divided into a group race, an elimination race, a final race and the like, wherein the group race comprises a plurality of competition battle entities, the elimination race also comprises a plurality of competition battle entities, and even some final races also comprise a plurality of competition battle entities. In generating the course instance, the user object entities of the two competition parties in each competition match entity in the first round of the group competition are determined, but the user object entities of the two competition parties in the round, the elimination competition and the final competition behind the group competition cannot be determined because the competition has not started yet. Taking a master cup race as an example, the course information can be divided into a team race, a knockout race and a final race, and the contents of the team race information comprise: grouping information of the group game (which user object entities are grouped into one group), player information of both opponents of each game includes user object entities of both players, game time information, game times (BO3, BO5), and the like. The elimination game information content comprises: match information for each match of the culling game (the user object entity is unknown, but the rank determination, such as which rank's rank and which rank's match is known), match time information, match rank, etc. The final match and the elimination match are consistent.

In some cases, an event may be classified as a group, elimination, semi-final, total final, etc., which may include multiple rounds, even a final may include multiple rounds. For example, the team competition includes 3 rounds, the elimination competition includes 2 rounds, etc., each round has a plurality of competition battle entities for competition, each round of competition is taken as a sub-course, correspondingly, the team competition includes 3 sub-courses, the elimination competition includes 2 sub-courses, etc. The sub-course will be referred to hereinafter.

After the group information list is obtained, the third client and/or the game client can check the grouping information corresponding to the group information list, and correspondingly, after the course instance is generated, the third client and/or the game client can check the course information corresponding to the course instance. Taking the course viewing information as an example, specifically, the third client sends a course viewing request to the third server, the third server forwards the course viewing request to the event server, and after receiving the course viewing request, the event server returns the course information to the third server, so that the third client views the corresponding course information; the game client and the event server can establish TCP connection, the game client can directly acquire corresponding event course information from the event server, or if TCP connection is not established between the game client and the event server, the game server is required to transfer the game, and the specific transfer is consistent with the transfer of the third server.

In some embodiments, after obtaining the group information or the course information, the event server may actively push the group information or the course information to the game server and the third server, or the game server and the third server may periodically obtain the corresponding group information and the course information from the event server.

After the generation of the course instance, the event status is modified by the time management instance to a status waiting for the start of the next round of the match, for example, a status waiting for the start of the group match if the next round of the match is the group match. When the group match starts, the state of the match is modified into the state in the group match, and the state of the match is modified in each subsequent round of match, so that the client can know the state information of the match corresponding to the match in time. The event status will not be described much below.

In one embodiment, as shown in fig. 8, the step 104 further includes the following steps.

The game time information in the course information list of the course management instance is extracted 501 by the time management instance.

Since the course information list includes at least one competition array entity and each competition array entity includes competition time information, the competition time information in each competition array entity of the course management instance is extracted by using the time management instance.

And 502, generating a stage list structure according to the competition time information, wherein the stage list structure comprises at least one time node and an event binding function, the time node is determined about the competition according to the competition time information, and the time nodes are arranged according to the time sequence.

Determining at least one time node for the event based on the event time information, for example the time node comprising: the starting time and the ending time of all round group games, the starting time and the ending time of all round elimination games, the starting time and the ending time of all round decision games, all round group games, all round elimination games and the like. It should be noted that the time nodes for all events may be determined based on the particular event. Each time node and/or the process of reaching the time node has a corresponding event binding function, and the corresponding event binding function is determined as the event binding function corresponding to the time node, which can be understood as that the corresponding event binding function is executed when and/or during reaching a certain time node.

The time nodes and the event binding functions corresponding to the time nodes can be stored in a key-value form, wherein the value corresponding to the key is the time node, and the value corresponding to the value is the event binding function corresponding to the time node.

And taking each round of match (each round of match) as a sub-course, and sequencing the time corresponding to the time nodes according to the time sequence to form a time axis. Correspondingly, the time axis can be as shown in fig. 9. The events comprise a sub-course 1, a sub-course 2, … …, a sub-course N and a total final trial, event binding functions of each sub-course end are executed at the time nodes of each sub-course end, and the event binding functions realize sub-course settlement logic, update next round competition entities, push results and the like.

For example, the sub-course settlement logic includes ranking updates, score updates, etc. of the user object entities; the user object entities in the competition courses except the first sub-competition course are real, other user object entities in the elimination competition are only represented by the user object entities and are not real, and each user object entity in the final elimination competition needs to be filled according to the ranking of the user object entities so as to update the competition entity of the next round of competition; pushing the competition result, the competition asset data of the user object entity to a third server and/or a game server to realize the pushed result, and the like.

503, passing the time node and the event binding function into the timer instance, and triggering the event binding function according to the timer instance.

And generating a timer instance according to the timer class corresponding to the timer component, transmitting the time nodes and the event binding functions corresponding to the time nodes into the timer instance according to the time sequence for each time node in the time axis, and triggering the corresponding event binding functions according to the timer instance. Or determining the time from the beginning of the next event according to the time corresponding to the time node, and transmitting the time from the beginning of the next event and the time binding function corresponding to the time to the timer.

In an embodiment, as shown in fig. 10, the step 503 includes the following steps.

5031, event binding functions corresponding to the time nodes and the time nodes are transmitted into the timer instance to trigger countdown information from the time nodes according to the timer instance.

And taking the time node and the event binding function corresponding to the time node as the parameter of the timer instance, and transmitting the parameter to the timer instance. For example, if the current event state is a state of waiting for the first round of the group game to start, the starting time of the first round of the group game is obtained as a time node, the corresponding event binding function when the starting time of the first round of the group game is reached and/or in the process of reaching the corresponding starting time is determined, the corresponding time binding function is used as the event binding function corresponding to the time node, the starting time of the first round of the group game and the corresponding event binding function are input into the timer instance together, and countdown information from the time node is triggered according to the timer instance. The other time nodes all proceed in the same manner.

5032, triggering the event binding function corresponding to the time node according to the countdown information.

When the time node is the time node corresponding to the starting time of the sub-course of the course instance, step 5032 includes: when the countdown information represents that the current time is a preset time point before a time node, triggering a first server to generate a competition room of a competition arraying entity of the sub-competition process so that a user object entity in the competition arraying entity can enter the competition room; and/or detecting whether the competition room meets the corresponding competition starting conditions or not, and if so, triggering to send an event request of the target application to the second server so that the second server executes the competition between the competition match entities of the target application according to the event request.

For example, when the sub-course is the first round of the group race, the time management instance may start countdown information for the first round of the group race according to the start time of the first round of the group race, and when the countdown information indicates that the current time reaches the first 15 minutes of the start time of the first round of the group race, the event server is triggered to generate a race room for the corresponding user object entity to enter, and the event server detects whether the race room satisfies the corresponding race start condition, for example, the race start condition may be that both user object entities in the race room enter the race room, and the countdown information indicates that the current time reaches the start time of the first round of the group race, and the time management instance may further include other conditions, and if the race start condition is satisfied, an event request of a target application is sent to notify the game server to start a race on the corresponding game server. The competition of the user object entities is performed in a game server, which is a set of servers including competition servers on which the competition is performed.

Wherein, each competition room has a unique room identifier such as a room ID, the user object entity in the competition match entity corresponding to the competition room can see and enter the competition room, and the user object entity can see the competition room in the game client and enter the competition room for preparing the game. And detecting whether the competition room meets the corresponding competition starting conditions, if so, sending an competition request to the game server by the competition server, and executing the corresponding competition in the game server. If the time range of a certain game is exceeded and the game room is not entered and/or the range of the game is ready is regarded as abandoning the local game, the abandoning of the local game can lose the local game according to the default score.

5033, update the timer instance.

And when the countdown information represents that the current time reaches the starting time of the sub-course of the course instance, updating the timer instance, and starting countdown of the maximum duration of the competition battle entity of the sub-course, for example, starting countdown for 20 minutes to prepare settlement statistics.

When the time node is the time node corresponding to the end time of the sub-course of the course instance, that is, when the maximum duration of the match matrix entity of the sub-course, such as the first round of the group match, is reached, correspondingly, the step of triggering the event binding function corresponding to the time node according to the countdown information includes: triggering and calling a grouping logic component of the grouping management instance according to the countdown information; obtaining a competition result between competition array entities according to the grouping logic component; and updating the competition asset data of the user object entity in the competition array entity according to the competition result.

For example, when the maximum duration of a match is 20 minutes, that is, when the match lasts for 20 minutes, all matches in the sub-match process have been completed, the countdown information is 0, a grouping logic component of the grouping management instance, such as a group match settlement function, is called, a match result between the match entities is obtained according to the grouping logic component, such as information about which win and what score the match is divided into, the match result may be obtained from the match server, or the match result may be sent to the match server after the match of the match server is completed, the match server obtains the match result, and the match asset data of each user object entity in the match entities is updated according to the match result, such as updating the score of each user object entity in the match entities, updating the rank of each user object entity, and the like.

In an embodiment, when the time node is a time node corresponding to the end time of the sub-course of the course instance, the step of triggering the event binding function corresponding to the time node according to the countdown information further includes: counting the competition asset data of the user object entity in all competition matchmaking entities of the competition course, and determining the competition matchmaking entity of the next competition course of the competition course according to a preset rule; and filling corresponding fields of the competition array entity of the next sub-competition range in the competition range examples according to the determined competition array entity. Wherein, when the round of competition, i.e. the sub-competition course, is not finished, the user object entity in the competition array entity of the next round of competition, i.e. the next sub-competition course, can not be determined, therefore, when the sub-course is finished, counting the competition asset data between each user object entity in the sub-course, then determining the user object entity in the competition array entity of the next sub-course according to the preset rule, for example, after the first name and the second name of each group game are obtained and the first name and the second name of each group game are sequentially scrambled, then determining the actual user object entity in the match array entity of the next sub-match course according to the preset rule, and populating user object entity fields in the match against entity in the next sub-course based on the determined user object entities, to determine the actual user object entity in each match permutation entity in the next round of the match.

In an embodiment, when the time node is a time node corresponding to the end time of the sub-course of the course instance, the step of triggering the event binding function corresponding to the time node according to the countdown information further includes: the tournament asset data of the user object entity is synchronized to a requesting side such as a third server and a second server such as a game server through a time management instance. Therefore, the third client and the game client can conveniently acquire the match asset data of each user object entity in the corresponding sub-course from the third server and the game server.

After the above operation is completed, the countdown is continuously updated according to the start time of the next round of competition, i.e., the next sub-course.

In the above embodiments, the data relating to the event is stored to the database by the storage management instance throughout the course of the event.

From the information described above, it can be seen that the event server performs all events related to the event, including: create an event, join an event, generate an event schedule, group an event, circulate an event, store an event, update an event result, push an event result (to a third server, game server, or game client directly connected to the event uniform), and the like. In the third server, the server related to the event mainly includes: the method comprises the steps of creating an event request, forwarding the event registration request, viewing event information through a service interface of an event server, and forwarding a pushing result of the event server to a third client, wherein the pushing result comprises event asset data, an event result and the like of a user object entity in the event server. In the game server, the service related to the events mainly includes: providing user object information such as event registration user object information and the like, verifying whether a user object entity has authority to establish and participate in an event, checking the event information through a service interface of an event server, carrying out a specific match process in the event by a player and sending a match result to the event server.

Wherein all content related to the logic of the event is implemented in the event server and the event related data storage is done by the event server. The original game server and the original third server only interact with the event server through the service interface/communication interface. The game server provides the game client and the third client to inquire various information of the game through the service interface, and the specific game process is borne by the game server (such as a competition server) because each game is relatively independent. If a game application wants to use the services of the event server, it only needs to implement the service interface/communication interface with the event server. The third server only undertakes a forwarding entrance, and the main function is to apply for events and inquire the event information, so that the user object entity can also know the event information outside the game.

Therefore, for any type of fighting game, as long as the event server (service interface/communication interface is realized), the services provided by the event service can be used without the need for the game server itself to be developed from the beginning. The event server can support a plurality of games, and the applicability of the event server is improved.

In addition, in the embodiment of the application, an event management instance is created for at least one event management component of the event instance, the management of the event is integrated in the event management component, the management of the event is realized through the event management instance corresponding to the event management component, the efficiency and the applicability of the event management are improved, in addition, the management of the event is centralized on the first server, the management of the event is unrelated to the target application, and the efficiency of the event management is further improved.

All the above technical solutions may be combined arbitrarily to form an optional embodiment of the present application, and are not described in detail herein.

In order to better implement the event management method according to the embodiment of the present application, an event management device is further provided according to the embodiment of the present application. Please refer to fig. 11, which is a schematic structural diagram of an event management device according to an embodiment of the present application, the event management device being integrated in a first server. The event management apparatus 600 may include an acquisition module 601, a first generation module 602, a second generation module 603, and a management module 604.

The obtaining module 601 is configured to receive, by a first server, an event creation request for a target application from a request end, and obtain an event template type of an event corresponding to the event creation request and configuration parameter information of the event.

In an embodiment, the obtaining module 601 is further configured to, after receiving an event creating request for a target application from a requesting end, obtain, through a first service interface, event creating user object information corresponding to the first identification information from a second server corresponding to the target application, and the event server determines, according to the event creating user object information, whether the event creating user object meets a creating condition of an event for creating the target application, and if not, prompt the creating condition.

A first generating module 602, configured to generate an event instance of the event according to the event template type and the configuration parameter information.

In an embodiment, the first generating module 602 is specifically configured to call a corresponding event template class according to the event template type, fill a corresponding field in the event template class according to the configuration parameter information, and generate a corresponding event instance according to the event template class filled with the corresponding field.

A second generating module 603, configured to generate an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type.

In an embodiment, the second generating module 603 is specifically configured to determine at least one event management component corresponding to the event template type, invoke an event management template class corresponding to the event management component, generate a corresponding event management instance according to the event management template class, and bind the generated event management instance and the event instance to obtain the event management instance corresponding to the event instance.

The event management instance comprises a user object management instance, a grouping management instance, a course management instance, a time management instance, a storage management instance and the like.

A management module 604, configured to implement management of the event according to the event management instance of the event instance.

In one embodiment, the management module 604 includes a query management unit. The query unit is used for receiving an event query request from a request end, the request end comprises a third server, querying an event list of the created event according to the event query request, and returning the event list to the request end through a second service interface. The query unit is further configured to query various information in the event server, for which reference is made to the above description.

In one embodiment, the management module 604 includes a user object management unit. The user object management unit is used for receiving an event registration request aiming at the event, wherein the event registration request comprises identification information of an event registration user object; calling a user object logic component in the user object management instance according to the identification information; determining, by using the user object logic component, whether the event entry user object corresponding to the identification information satisfies a participation condition for participating in the event of the target application; and if so, adding the event registration user object as a user object entity into an event queue of the event, and updating the event registration information of the event.

In one embodiment, the management module 604 includes a packet management unit. The group management unit is used for transmitting the event queue of the user object management instance to the group management instance when the event is detected to meet the starting condition; invoking a grouping logic component of the grouping management instance; and grouping the user object entities in the event queue by using the grouping logic component to determine a group information list, wherein the group information list comprises the grouping entities corresponding to the grouping management instances, and each grouping entity comprises the user object entities included in each group.

In one embodiment, the management module 604 includes a course management unit. The course management unit is used for transmitting a group information list in the grouping management example to the course management example; calling a course logic component in the course management instance; and processing the grouping entities in the group information list by using the course logic component to determine a course instance corresponding to the event, wherein the course instance comprises a course information list, the course information list comprises at least one competition arraying entity, and the competition arraying entity comprises competition time information and a competition user object entity.

In one embodiment, the management module 604 includes a time management unit or a process management unit. The time management unit or the process management unit is used for extracting competition time information in a competition progress information list of the competition progress management example through the time management example; generating a stage list structure according to the competition time information, wherein the stage list structure comprises at least one time node of the competition determined according to the competition time information and an event binding function corresponding to the time node, and the time nodes are arranged according to a time sequence; and transmitting the time node and the event binding function into a timer instance, and triggering the event binding function according to the timer instance.

In an embodiment, when the step of transferring the time node and the event binding function into a timer instance and triggering the event binding function according to the timer instance is executed by the time management unit or the process management unit, the following specific steps are executed: transmitting the time node and the event binding function into a timer instance to trigger countdown information from the time node according to the timer instance; triggering the event binding function corresponding to the time node according to the countdown information; the timer instance is updated.

In an embodiment, the course instance includes at least one sub-course, each sub-course includes at least one match battle entity, and when the time node is a time node corresponding to a start time of a sub-course of the course instance, the time management unit or the process management unit specifically executes, when executing the step of triggering the event binding function corresponding to the time node according to the countdown information: when the countdown information represents that the current time is a preset time point before the time node, triggering a first server to generate a competition room of the competition arraying entity of the sub-competition process so that a user object entity in the competition arraying entity can enter the competition room; and/or detecting whether the competition room meets corresponding competition starting conditions or not, and if so, triggering to send an event request of the target application to a second server so that the second server executes the competition between the competition entities of the target application according to the event request.

In an embodiment, when the time node is a time node corresponding to an end time of a sub-course of the course instance, the time management unit specifically executes, when executing the step of triggering the event binding function corresponding to the time node according to the countdown information: triggering and calling a grouping logic component of the grouping management instance according to the countdown information; obtaining a competition result between the competition array entities according to the grouping logic component; and updating the competition asset data of the user object entity in the competition array entity according to the competition result.

When the time node is a time node corresponding to the end time of the sub-course of the course instance, the time management unit further performs statistics on the competition asset data of the user object entity in all the competition array entities of the sub-course, and determines a competition array entity of the next sub-course of the course instance according to a preset rule; and filling corresponding fields of the competition array entity of the next sub-competition-course in the competition-course examples according to the determined competition array entity.

And when the time node is the time node corresponding to the end time of the sub-course of the course instance, the time management unit also synchronizes the competition asset data of the user object entity to the request end and the second server through the time management instance.

In one embodiment, the management module 604 includes a storage management unit. And the storage management unit is used for storing the data related to the events to a database through the storage management example.

All the above technical solutions may be combined arbitrarily to form an optional embodiment of the present application, and are not described in detail herein. The advantageous effects achieved by the corresponding embodiments can be seen as described above.

Correspondingly, the embodiment of the application also provides a computer device, and the computer device can be a first server. As shown in fig. 12, fig. 12 is a schematic structural diagram of a computer device according to an embodiment of the present application. The computer apparatus 700 includes a processor 701 having one or more processing cores, a memory 702 having one or more computer-readable storage media, and a computer program stored on the memory 702 and executable on the processor. The processor 701 is electrically connected to the memory 702. Those skilled in the art will appreciate that the computer device configurations illustrated in the figures are not meant to be limiting of computer devices, and may include more or fewer components than those illustrated, or combinations of certain components, or different arrangements of components.

The processor 701 is a control center of the computer apparatus 700, connects various parts of the entire computer apparatus 700 with various interfaces and lines, performs various functions of the computer apparatus 700 and processes data by running or loading software programs (computer programs) and/or modules stored in the memory 702, and calling data stored in the memory 702, thereby monitoring the computer apparatus 700 as a whole.

In the embodiment of the present application, the processor 701 in the computer device 700 loads instructions corresponding to processes of one or more application programs into the memory 702, and the processor 701 executes the application program stored in the memory 702, so as to implement various functions as follows:

receiving an event creating request aiming at a target application from a request terminal through a first server, and acquiring an event template type of an event corresponding to the event creating request and configuration parameter information of the event; generating an event instance of the event according to the event template type and the configuration parameter information; generating an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type; and realizing the management of the events according to the event management examples of the event examples.

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

Optionally, as shown in fig. 12, the computer device 700 further includes: a touch display screen 703, a radio frequency circuit 704, an audio circuit 705, an input unit 706, and a power supply 707. The processor 701 is electrically connected to the touch display screen 703, the radio frequency circuit 704, the audio circuit 705, the input unit 706, and the power source 707. Those skilled in the art will appreciate that the computer device configuration illustrated in FIG. 12 does not constitute a limitation of the computer device, and may include more or fewer components than illustrated, or some components may be combined, or a different arrangement of components.

The touch display screen 703 may be used to display a graphical user interface and receive operation instructions generated by a user acting on the graphical user interface. The touch display screen 703 may include a display panel and a touch panel. Among other things, the display panel may be used to display information input by or provided to a user as well as various graphical user interfaces of the computer device, which may be made up of graphics, text, icons, video, and any combination thereof. Alternatively, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations of a user (for example, operations of the user on or near the touch panel by using a finger, a stylus pen, or any other suitable object or accessory) and generate corresponding operation instructions, and the operation instructions execute corresponding programs. The touch panel may cover the display panel, and when the touch panel detects a touch operation thereon or nearby, the touch panel transmits the touch operation to the processor 701 to determine the type of the touch event, and then the processor 701 provides a corresponding visual output on the display panel according to the type of the touch event. In the embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 703 to realize input and output functions. However, in some embodiments, the touch panel and the touch panel can be implemented as two separate components to perform the input and output functions. That is, the touch display screen 703 can also be used as a part of the input unit 706 to implement an input function.

In this embodiment, the touch display screen 703 is used for presenting a graphical user interface and receiving an operation instruction generated by a user acting on the graphical user interface.

The radio frequency circuit 704 may be used for transceiving radio frequency signals to establish wireless communication with a network device or other computer device through wireless communication, and for transceiving signals with the network device or other computer device.

Audio circuitry 705 may be used to provide an audio interface between a user and a computer device through speakers and microphones. The audio circuit 705 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 705 and converted into audio data, which is then processed by the output processor 701 and sent to, for example, another computer device via the rf circuit 704, or output to the memory 702 for further processing. The audio circuit 705 may also include an earbud jack to provide communication of a peripheral headset with the computer device.

The input unit 706 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

The power supply 707 is used to power the various components of the computer device 700. Optionally, the power source 707 may be logically connected to the processor 701 through a power management system, so as to implement functions of managing charging, discharging, power consumption, and the like through the power management system. The power supply 707 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

Although not shown in fig. 12, the computer device 700 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described in detail herein.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.

To this end, embodiments of the present application provide a computer-readable storage medium, in which a plurality of computer programs are stored, and the computer programs can be loaded by a processor to execute the steps in any one of the event management methods provided by the embodiments of the present application. For example, the computer program may perform the steps of:

receiving an event creation request aiming at a target application from a request terminal through a first server, and acquiring an event template type of an event corresponding to the event creation request and configuration parameter information of the event; generating an event instance of the event according to the event template type and the configuration parameter information; generating an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type; and realizing the management of the events according to the event management examples of the event examples.

Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

Since the computer program stored in the storage medium can execute the steps of any event management method provided in the embodiments of the present application, beneficial effects that can be achieved by any event management method provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.

The above detailed description is provided for an event management method, an event management apparatus, a storage medium, and a computer device according to embodiments of the present application, and a specific example is applied in the present application to explain the principles and embodiments of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. An event management method, comprising:

receiving an event creating request aiming at a target application from a request terminal through a first server, and acquiring an event template type of an event corresponding to the event creating request and configuration parameter information of the event;

2. The event management method according to claim 1, wherein the event management instance comprises a user object management instance, and the step of managing the event according to the event management instance of the event instance comprises:

receiving an event entry request for the event, the event entry request including identification information of an event entry user object;

calling a user object logic component in the user object management instance according to the identification information;

determining, by using the user object logic component, whether the event entry user object corresponding to the identification information satisfies a participation condition for participating in the event of the target application;

and if so, adding the event entry user object as a user object entity into an event queue of the event, and updating the event entry information of the event.

3. The event management method according to claim 1, wherein the event management instance comprises a group management instance, and the step of managing the event according to the event management instance of the event instance comprises:

when the match is detected to meet the match-opening condition, transmitting the match queue of the user object management instance to the grouping management instance;

invoking a grouping logic component of the grouping management instance;

and grouping the user object entities in the event queue by using the grouping logic component to determine a group information list, wherein the group information list comprises the grouping entities corresponding to the grouping management instances, and each grouping entity comprises the user object entities included in each group.

4. The event management method according to claim 1, wherein the event management instance comprises a group management instance and a course management instance, and the step of managing the event according to the event management instance of the event instance comprises:

transmitting the group information list in the grouping management example to the competition process management example;

calling a course logic component in the course management instance;

and processing the grouping entities in the group information list by using the course logic component to determine a course instance corresponding to the event, wherein the course instance comprises a course information list, the course information list comprises at least one competition arraying entity, and the competition arraying entity comprises competition time information and a competition user object entity.

5. The event management method according to claim 1, wherein the event management instance comprises a course management instance and a time management instance, and the step of implementing management of the event according to the event management instance of the event instance comprises:

extracting match time information in a course information list of the course management instance through the time management instance;

generating a stage list structure according to the competition time information, wherein the stage list structure comprises at least one time node of the competition determined according to the competition time information and event binding functions corresponding to the time nodes, and the time nodes are arranged according to a time sequence;

and transmitting the time node and the event binding function into a timer instance, and triggering the event binding function according to the timer instance.

6. The event management method according to claim 5, wherein the step of passing the time node and the event binding function into a timer instance and triggering the event binding function according to the timer instance comprises:

transmitting the time node and the event binding function into a timer instance to trigger countdown information from the time node according to the timer instance;

triggering the event binding function corresponding to the time node according to the countdown information;

the timer instance is updated.

7. The event management method according to claim 6, wherein the course instance of the course management instance comprises at least one sub-course, each sub-course comprises at least one competition battle entity, and when the time node is a time node corresponding to a start time of a sub-course of the course instance, the step of triggering the event binding function corresponding to the time node according to the countdown information comprises:

when the countdown information represents that the current time is a preset time point before the time node, triggering a first server to generate a competition room of the competition arraying entity of the sub-competition process so that a user object entity in the competition arraying entity can enter the competition room; and/or

And detecting whether the competition room meets corresponding competition starting conditions or not, if so, triggering to send an competition request of the target application to a second server, so that the second server executes competition between competition competing entities of the target application according to the competition request.

8. The event management method according to claim 6, wherein the course instance of the course management instance includes at least one sub-course, each sub-course includes at least one competition battle entity, and when the time node is a time node corresponding to an ending time of a sub-course of the course instance, the step of triggering the event binding function corresponding to the time node according to the countdown information includes:

triggering and calling a grouping logic component of the grouping management instance according to the countdown information;

obtaining a competition result between the competition array entities according to the grouping logic component;

and updating the competition asset data of the user object entity in the competition array entity according to the competition result.

9. The event management method according to claim 8, further comprising:

counting the competition asset data of the user object entity in all the competition arraying entities of the sub-competition process, and determining the competition arraying entity of the next sub-competition process of the competition process example according to a preset rule;

and filling corresponding fields in the competition arraying entity of the next sub-competition-course in the competition-course examples according to the determined competition arraying entity.

10. The event management method according to claim 8, wherein after obtaining the event information of the user object entity, the event management method further comprises:

and synchronizing the competition asset data of the user object entity to the request end and the second server through the time management instance.

11. An event management method according to any of claims 1-10, wherein the event management instance comprises a storage management instance, and the step of implementing management of the event according to the event management instance of the event instance comprises: and storing the data related to the events to a database through the storage management instance.

12. The event management method according to any of claims 1-10, wherein the step of generating an event management instance corresponding to the event instance according to the at least one event management component corresponding to the event template type comprises:

determining at least one event management component corresponding to the event template type, and calling an event management template class corresponding to the event management component;

creating a corresponding event management instance according to the event management template class;

and binding the event management instance with the event instance to obtain the event management instance corresponding to the event instance.

13. An event management device, comprising:

the second generation module is used for generating an event management instance corresponding to the event instance according to at least one event management component corresponding to the event template type;

14. A computer-readable storage medium, characterized in that it stores a computer program adapted to be loaded by a processor for performing the steps of the method according to any one of claims 1-12.

15. A computer arrangement, characterized in that the computer arrangement comprises a memory in which a computer program is stored and a processor which performs the steps in the event management method according to any of claims 1-12 by calling the computer program stored in the memory.