Event management methods, devices, computer-readable storage media and computer equipment

Abstract

This application discloses a method, apparatus, computer-readable storage medium, and computer device for managing competitions. The method includes: receiving a competition creation request for a target application from a requesting client via a first server, and obtaining the competition template type and configuration parameter information of the competition corresponding to the competition creation request; generating a competition instance based on the competition template type and configuration parameter information; generating a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type; and managing the competition based on the competition management instance of the competition instance. This application embodiment enables competition customization, improves the user's competition experience, and enhances the efficiency and applicability of competition management.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a competition management method, apparatus, computer-readable storage medium, and computer equipment. Background Technology

[0002] The rapid development of communication technology has greatly improved users' lives, allowing them to install and use various applications on their devices, such as games.

[0003] In some applications, various online tournaments can also be held. Currently, most online tournaments in applications are small-scale, with large-scale tournaments being less common. Therefore, in current designs, the management of online tournaments is usually coupled with the management of the application itself. When the tournaments provided by the application are small-scale, there are usually no obvious problems. However, when the tournaments provided by the application are large-scale, coupling the management of the tournaments with the management of the application itself will reduce the efficiency of tournament management and the tournament experience.

[0004] Furthermore, the online tournaments in the target application are basically provided by the game itself, and all the processes, details, and other information of the tournament are fixed, which users cannot make any changes to, thus reducing the user's tournament experience. Summary of the Invention

[0005] This application provides a method, apparatus, computer-readable storage medium, and computer equipment for event management, which can enable event creation, improve the user's event experience, and enhance the efficiency and applicability of event management.

[0006] This application provides a method for managing competitions, including:

[0007] The first server receives a competition creation request for the target application from the requesting end, and obtains the competition template type and configuration parameter information of the competition corresponding to the competition creation request.

[0008] A tournament instance is generated based on the tournament template type and the configuration parameter information;

[0009] Generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type;

[0010] The event is managed based on the event management instance of the event instance.

[0011] This application also provides a competition management device, including:

[0012] The acquisition module is used to receive a competition creation request for a target application from the requesting end through the first server, and to acquire the competition template type and configuration parameter information of the competition corresponding to the competition creation request.

[0013] The first generation module is used to generate a competition instance of the competition based on the competition template type and the configuration parameter information;

[0014] The second generation module is used to generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type.

[0015] The management module is used to manage the event based on the event management instance of the event instance.

[0016] This application also provides a computer-readable storage medium storing a computer program adapted for loading by a processor to perform the steps in the event management method as described in any of the above embodiments.

[0017] This application also provides a computer device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the steps in the event management method described in any of the above embodiments by calling the computer program stored in the memory.

[0018] The event management method, apparatus, computer-readable storage medium, and computer device provided in this application embodiment receive an event creation request for a target application from a requesting end via a first server. Based on the event creation request, the application obtains the event template type and configuration parameter information corresponding to the event in the target application. That is, this application embodiment can set the event configuration parameter information and obtain the event template type corresponding to the event. Event instances are generated based on the configuration parameter information and event template type to create events, achieving event customization / configurability and improving the user's event experience. Furthermore, this application embodiment creates event management instances for at least one event management component of the event instance, integrating event management into the event management component. Event management is achieved through the event management instance corresponding to the event management component, improving the efficiency and applicability of event management. In addition, by centralizing event management on the first server, event management is independent of the target application, further improving the efficiency of event management. Attached Figure Description

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

[0020] Figure 1 This is a schematic diagram illustrating an application scenario of the event management method provided in this application embodiment.

[0021] Figure 2 This is a flowchart illustrating the event management method provided in an embodiment of this application.

[0022] Figure 3 This is a schematic diagram of the event management components included in the event example provided in this application embodiment.

[0023] Figure 4 A schematic diagram of a competition example provided in the embodiments of this application.

[0024] Figure 5 This is a schematic diagram of a sub-process of the event management method provided in the embodiments of this application.

[0025] Figure 6 This is a schematic diagram of a sub-process of the event management method provided in the embodiments of this application.

[0026] Figure 7 This is a schematic diagram of another sub-process of the event management method provided in the embodiments of this application.

[0027] Figure 8 This is another flowchart illustrating the event management method provided in the embodiments of this application.

[0028] Figure 9 A schematic diagram of the timeline provided for an embodiment of this application.

[0029] Figure 10 Another flowchart of the event management method provided in this application embodiment.

[0030] Figure 11 A schematic diagram of the structure of the event management device provided in the embodiments of this application.

[0031] Figure 12 A schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] This application provides a method, apparatus, computer-readable storage medium, and computer device for event management. Specifically, the event management method of this application can be executed by a computer device, which can be a server device, such as a first server. The first server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0034] The target application in this application can be a learning application, a work application, a game application, or other applications that provide competition functions; there is no specific limitation. For ease of understanding, this application will use a game application as an example for illustration.

[0035] like Figure 1 The diagram shown illustrates an application scenario of a competition management method provided in this application. The competition management system includes a first server, a second server, and a third server. The second and third servers are identical to the first server and can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or various cloud servers, etc.

[0036] The first server can be a tournament server, the second server can be a game server corresponding to a game application, and the third server can be a server corresponding to multiple game information service application platforms. The tournament server communicates with both the game server and the third server. Game clients access the game server via the network, and information service application clients (third clients) access the third server via the network. Here, "third client" does not refer to a single client but rather a collective term for a class of clients. In some cases, game clients can directly connect to the tournament server via TCP. The tournament management method in this embodiment is applied to the tournament server, while the actual execution of the tournament takes place on the game server, thus decoupling tournament management from game management and improving the efficiency of game management.

[0037] It is important to note that Figure 1 This is merely a schematic diagram of an application scenario; the embodiments in this application are based on... Figure 1 The application scenario shown is used as an example for illustration. The event management method in this application embodiment can also be applied to application scenarios that include event servers and game servers. In this case, the event server corresponds to the event client, and the event client connects to the event server through the network. The game server corresponds to the game client, and the game client connects to the game server through the network.

[0038] The following will provide a detailed description of a competition management method, apparatus, computer-readable storage medium, and computer device provided in the embodiments of this application. It should be noted that the sequence numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0039] Figure 2 This is a flowchart illustrating the event management method provided in this application embodiment. The event management method is applied to a first server and specifically includes the following steps.

[0040] 101. Receive the event creation request for the target application from the requesting end through the first server, and obtain the event template type and event configuration parameter information corresponding to the event creation request.

[0041] In this context, the requesting client is relative to the first server. When the first server is the tournament server, the requesting client can be a third server or a tournament client. The target application's tournament is an online tournament, where participants can engage in remote battles via network connection.

[0042] For example, a request to host / create an event can be initiated on a third-party client. This request will call the parameter configuration interface, where you can set / select / input the event template type, such as a Masters Cup format, a ball game league format, a card game format, etc. You can also set / select / input configuration parameter information on this interface. This configuration parameter information includes the competition mode (group stage, knockout stage, etc.), participation conditions, number of participants, number of participants in each group, waiting time for each round of the competition, match time, knockout stage match time, number of knockout stage matches, and final victory conditions.

[0043] The configuration parameters expose options for customizing tournaments in different games. If no corresponding option is set / selected / inputted in the parameter settings interface, the default configuration parameters are used. Alternatively, other methods can be used to obtain the corresponding tournament template type and configuration parameters, such as writing the tournament template type and configuration parameters to a file, loading the file through a third-party client, and reading the corresponding tournament template type and configuration parameters. This allows for the customization of the tournament template type and configuration parameters, providing a foundation for tournament customization.

[0044] After setting / selecting / entering the event template type and configuration parameters, the corresponding control is triggered to generate an event creation request for the target application. This request includes the event template type and configuration parameters for the event. The third server receives the event creation request but does not perform any business processing; it directly forwards the request to the event server. The event server then receives the event creation request from the third server and retrieves the corresponding event template type and configuration parameters from the request.

[0045] The event creation request also includes first identification information of the event creation user object, such as the username and / or number of the event creation user object. After receiving the event creation request for the target application from the third server, the event server obtains the event creation user object information corresponding to the first identification information from the second server of the target application through the first service interface. The event creation user object information includes information related to the creation conditions, such as the level and / or privileges of the event creation user object. The event server determines whether the event creation user object meets the creation conditions for creating an event of the target application based on the event creation user object information. The event creation conditions can be set in advance. If the creation conditions for creating an event of the target application are met, the following step 102 is executed; if not, a prompt is given.

[0046] 102. Generate a tournament instance based on the tournament template type and configuration parameter information.

[0047] Each event template type is designed as an event template class. Different event template types have corresponding event template classes pre-designed in the event server. The corresponding event template class is called based on the event template type, and the corresponding fields in the event template class are populated according to the configuration parameters. Finally, the corresponding event instance is generated based on the event template class with the populated fields.

[0048] After generating a competition instance, record the competition instance's competition status as "registration status" and store it.

[0049] 103. Generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type.

[0050] The event template class corresponding to an event template type generally includes at least one event management component, such as a user object management component, group management component, schedule management component, time management component, and storage management component. A brief introduction to these event management components is provided below. The event management components included in the event instance are as follows: Figure 3 As shown.

[0051] User object management component: includes user object entity (MatchUser) and user object logic component, which includes a series of methods / functions.

[0052] Group management component: includes group entity (MatchGroup) and group logic component, which includes a series of methods / functions.

[0053] The schedule management component includes the schedule entity (MatchSchedule) and the schedule logic component, which includes a series of methods / functions.

[0054] Time management component: mainly records the current event status, group stage / knockout stage and round information (which can correspond to the sub-schedules in the following text), timeline information, timer component, and event binding functions for each round of the game, such as settlement logic, score statistics, ranking statistics, etc.

[0055] Storage management component: responsible for storing event data in the database.

[0056] These event management components are essentially event management template classes. Specifically, at least one event management component corresponding to a given event template type can be identified, and the event management template class corresponding to that component can be called. A corresponding event management instance is then generated based on the event management template class, and the generated event management instance is bound to the event instance to obtain the event management instance corresponding to the event instance.

[0057] For example, the User Object Management component corresponds to the User Object Management class, calls the User Object Management class, and generates a User Object Management instance (UserMgr) based on the User Object Management class; the Group Management component corresponds to the Group Management class and generates a Group Management instance (GroupMgr) based on the Group Management class; the Schedule Management component corresponds to the Schedule Management class and generates a Schedule Management instance (ScheduleMgr) based on the Schedule Management class; the Time Management component corresponds to the Time Management class and generates a Time Management instance (TimeLineMgr) based on the Time Management class. The Time Management component can also be called the Process Management component, and it generates a Process Management instance; the Storage Management component corresponds to the Storage Management class and generates a Storage Management instance (PersistMgr) based on the Storage Management class.

[0058] These event management instances are dynamically generated from event instances. For example, when generating an event instance, the required user object management instance, time management instance, and storage management instance can be automatically generated. Subsequently, group management instances and schedule management instances are generated as needed. This is because if the event creator does not meet the creation requirements, or if the event does not reach the required number of participants, it will be disbanded. In this case, there is no need to generate group management instances and schedule management instances, thus reducing the storage space occupied by group management instances and event management instances. Alternatively, all necessary event management instances can be automatically generated when generating the event instance.

[0059] The relationship between event instances and event management instances can be described as follows: Figure 4 As shown, a competition instance may include a user object management instance, a group management instance, a schedule management instance, a time management instance, a storage management instance, and configuration parameter information. Alternatively, it can be understood as generating a competition instance based on the user object management instance, group management instance, schedule management instance, time management instance, storage management instance, and configuration parameter information. Or, it can be understood as the competition template class (class) including the corresponding competition management template class (class), such as the user object management class, group management class, schedule management class, time management class, and storage management class.

[0060] The user object management instance records the event creator (the event creation user object), current registration information, etc. The time management component records the event creation time, current event status, event validity period, and other information, which will be described later. The storage management instance stores event-related data in the database, including data that needs to be stored and updated in each event management instance.

[0061] 104. Implement event management based on the event management instance of the event instance.

[0062] During the event management process, the event request of the target application is sent to the second server so that the second server can execute the event of the target application according to the event request and obtain the execution result of the event of the target application executed by the second server.

[0063] The following section will describe how the event management instance manages the event, based on some of the main processes executed by the event instance.

[0064] After creating a tournament instance, the client of the consulting service application, i.e., the third client, can query the list of created tournaments at the tournament entry point. Specifically, the third client generates a tournament query request to request the list of created tournaments and sends this request to the third server. Since the third server does not currently have tournament information, it forwards the request to the tournament server via an HTTP interface. The tournament server receives the tournament query request from the requesting party, including the third server, and queries the list of created tournaments based on the request. It then returns the list to the requesting party via a second service interface. If the list is returned to the third server, it is returned to the third client for presentation / display. Similarly, the game client can also obtain the corresponding tournaments from the game server. In some embodiments, the third server can periodically retrieve the corresponding tournament list from the tournament server, and correspondingly, the game server periodically retrieves the corresponding tournaments from the tournament server. Alternatively, in one embodiment, after a tournament is successfully created on the tournament server, it is pushed to the third server or the game server.

[0065] In one embodiment, such as Figure 5 As shown, step 104 above includes the following steps.

[0066] 201, Receive a competition registration request for the competition, which includes the second identification information of the competition registration user object.

[0067] After the event list is displayed in the third client, users can click / select an event in the list to register for the event. If the registration control for that event is triggered on the third client, an event registration request is generated and sent to the third server. This event registration request includes the second identification information of the event registration user object. The third server forwards the event registration request to the event server. The event server receives the event registration request for the event from the requesting party, such as the third server, and obtains the second identification information of the event registration user object from the event registration request. This second identification information may be the nickname and / or ID of the event registration user object, etc.

[0068] 202. Invoke the user object logic component in the user object management instance based on the second identifier information.

[0069] The second identifier information is used to invoke the user object logic component in the user object management instance, and the second identifier information is passed as a parameter to the corresponding method / function in the user object logic component.

[0070] 203. Use the user object logic component to determine whether the event registration user object corresponding to the second identifier information meets the participation conditions of the target application's event.

[0071] Using the user object logic component, the system accesses a second server, such as a game server, through a first service interface. It then retrieves the event registration user object information corresponding to the second identifier information from the game server, such as the event registration user object's level. The event server determines whether the event registration user object meets the participation conditions of the target application's event based on the event registration user object information. These participation conditions can be set in advance. For example, for a certain event template type, these participation conditions can be fixed or modified, such as by modifying them in the configuration parameter information.

[0072] If the user registering for the event meets the participation requirements of the target application's event, proceed to step 204; otherwise, proceed to step 205.

[0073] 204. Add the event registration user object as a user object entity to the event queue and update the event registration information.

[0074] The event instance's user object management instance adds registered user objects as user object entities to the event queue and updates the current registration information in real time, such as the current number of registrants. Each user object entity contains the same information, such as nickname, level, and user icon.

[0075] In this context, user objects in the event queue can be added or deleted. For example, when canceling an event registration, the corresponding user object in the event queue will be deleted, and the current registration information will be updated in real time.

[0076] 205, a prompt will be given.

[0077] If a user registering for an event does not meet the participation requirements for the event of the target application, a corresponding prompt will be displayed to the user.

[0078] In one embodiment, such as Figure 6 As shown, step 104 above also includes the following steps.

[0079] 301. Check whether the event meets the conditions for starting.

[0080] The registration process for the event will continue until the registration period ends or the number of registrants reaches the preset limit. When the registration period ends, it is checked whether the number of registrants has reached the preset limit for starting the event. If so, the event is determined to meet the conditions for starting; otherwise, it is determined not to meet the conditions. If the registration period has not ended and the number of registrants has already reached the preset limit, the event is determined to meet the conditions for starting. Note that the conditions for starting an event can also be other conditions, and the specific conditions vary from event to event.

[0081] If the conditions for starting the competition are met, proceed to step 302; otherwise, proceed to step 306.

[0082] 302, Modify the event status to "Grouping" using the time management instance.

[0083] 303, Passes the event queue of the user object management instance to the group management instance.

[0084] If a group management instance is not generated when the event instance is created, the group management component will be instantiated to obtain a group management instance when the event meets the start conditions. The event queue of the user object management instance is passed to the group management instance.

[0085] 304 indicates an invocation of the grouping logic component of the grouping management instance. This involves calling the corresponding grouping method / function within the grouping logic component, passing the event queue as a parameter to the corresponding grouping method / function.

[0086] 305. Use the grouping logic component to group the user object entities in the event queue to determine the group information list. The group information list includes the group entity corresponding to the group management instance, and each group entity includes the user object entities included in each group.

[0087] Using the grouping methods / functions in the grouping logic component, a group information list (GroupList) is calculated through corresponding grouping logic and rules. Each element in the group information list (GroupList) is a group entity (MatchGroup), which includes the group ID, the list of user object entities corresponding to the current group (MatchUser list), etc.

[0088] 306. Using time management examples, the event can be disbanded based on its validity period.

[0089] This embodiment implements the grouping process.

[0090] In one embodiment, such as Figure 7 As shown, step 104 above also includes the following steps.

[0091] 401, The event status has been changed to "Event schedule calculation in progress" using the time management component.

[0092] 402, Pass the group information list from the group management instance to the schedule management instance.

[0093] If a schedule management instance is not generated when the event instance is generated, the schedule management component is instantiated first to obtain the schedule management instance. The group information list from the group management instance is then passed to the schedule management instance.

[0094] 403, Invoking the schedule logic component in the schedule management instance.

[0095] If the corresponding schedule calculation method / function in the schedule logic component is called, the group information list is passed as a parameter to the corresponding schedule calculation method / function.

[0096] 404. The schedule logic component is used to process the grouping entities in the group information list to determine the schedule instance corresponding to the event. The schedule instance includes a schedule information list, which includes at least one match-up entity. The match-up entity includes match time information and the match's user object entity.

[0097] Using the schedule calculation methods / functions in the schedule logic component, a schedule instance corresponding to the event is generated through the corresponding schedule logic and rules. This schedule instance includes a schedule information list, which includes at least one match pairing entity. Each match pairing entity includes information about each match, such as the match ID, the user object entities of both sides, the score information of both sides, and the match time information.

[0098] In general, a large tournament schedule instance can be divided into group stage, knockout stage, and finals. The group stage includes multiple match-up entities, the knockout stage also includes multiple match-up entities, and some finals even include multiple match-up entities. When generating a tournament schedule instance, the user object entities of both sides in each match-up entity in the first round of the group stage are determined. However, since the tournament has not yet started, the user object entities of both sides in the subsequent rounds of the group stage, the knockout stage, and the finals are not yet determined. Taking the Masters Cup as an example, the tournament schedule information can be divided into group stage, knockout stage, and finals. Group stage information includes: grouping information (which user object entities are grouped together), player information for each match including the user object entities of both sides, match time information, and match number (BO3, BO5), etc. Knockout stage information includes: match-up information for each knockout stage match (user object entities are unknown, but the match number is determined, such as which match's ranked players are known), match time information, and match number, etc. The finals are the same as the knockout stage.

[0099] In some cases, a tournament can be divided into group stages, knockout stages, semi-finals, and finals. These stages can include multiple rounds, and even the finals can consist of multiple rounds. For example, the group stage might have 3 rounds, the knockout stage 2 rounds, and so on. Each round involves multiple matchups, and each round can be considered a sub-segment. Therefore, the group stage could have 3 sub-segments, the knockout stage 2 sub-segments, and so on. Sub-segments will be discussed further below.

[0100] After obtaining the group information list, the third-party client and / or game client can view the group information corresponding to the group information list. Correspondingly, after generating a schedule instance, the third-party client and / or game client can view the schedule information corresponding to the schedule instance. Taking viewing schedule information as an example, specifically, the third-party client sends a schedule viewing request to the third-party server, the third-party server forwards the schedule viewing request to the event server, and after receiving the schedule viewing request, the event server returns the schedule information to the third-party server so that the third-party client can view the corresponding schedule information. A TCP connection can be established between the game client and the event server, and the game client can directly obtain the corresponding schedule information from the event server. If no TCP connection is established between the game client and the event server, it needs to be relayed through the game server, and the specific relay is the same as the relay through the third server.

[0101] In some embodiments, after the event server receives the group information or schedule information, it may proactively push it to the game server and the third server, or the game server and the third server may periodically obtain the corresponding group information and schedule information from the event server.

[0102] After generating the tournament schedule instance, the event status is modified using a time management instance to indicate "awaiting the start of the next round." For example, if the next round is the group stage, the status will be "awaiting the start of the group stage." When the group stage begins, the event status is changed to "in the group stage," and so on. The event status will be updated for each subsequent round to ensure clients are promptly informed of the event's status. The event status will not be described in detail below.

[0103] In one embodiment, such as Figure 8 As shown, step 104 above also includes the following steps.

[0104] 501. Extract match time information from the match schedule information list of the match schedule management instance using the time management instance.

[0105] Since the schedule information list includes at least one match-up entity, and each match-up entity includes match time information, the match time information in each match-up entity of the schedule management instance is extracted using the time management instance.

[0106] 502. Generate a stage list structure based on the match time information. The stage list structure includes at least one time node for the event determined based on the match time information and the event binding function corresponding to the time node. The time nodes are arranged in chronological order.

[0107] Based on the match schedule information, at least one time point related to the event is determined. This time point could include: the start and end times of all group stage rounds, the start and end times of all knockout stage rounds, the start and end times of all final rounds, and so on. It's important to note that the specific time points for each event can be determined based on the specific event. Each time point and / or the process of reaching that time point has a corresponding event binding function. Designating the corresponding event binding function as the event binding function for a time point means that the corresponding event binding function will be executed when and / or during the process of reaching a certain time point.

[0108] Time nodes and their corresponding event binding functions can be stored in key-value pairs, where the key corresponds to the time node and the value corresponds to the event binding function of the time node.

[0109] Each round of matches (each round of matches) is treated as a sub-schedule, and the times corresponding to these time points are arranged chronologically to form a timeline. Correspondingly, this timeline can be represented as follows: Figure 9 As shown. The competition includes sub-segment 1, sub-segment 2, ..., sub-segment N and the final. At the end of each sub-segment, an event binding function is executed. This event binding function implements the sub-segment settlement logic, updates the next round's matchups, and pushes the results.

[0110] For example, the sub-segment settlement logic includes updating the ranking and points of user object entities; in the event entity, only the user object entity in the first sub-segment is real, while the user object entities in other sub-segments, such as those in the knockout stage, are just representations of user object entities and are not real. The ranking of each user object entity in the final knockout stage needs to be used to populate the next round's match-up entity; the match results and the match asset data of user object entities are pushed to the third-party server and / or the game server to achieve the push results, etc.

[0111] 503, Passes the time node and event binding function to the timer instance, and triggers the event binding function based on the timer instance.

[0112] A timer instance is generated based on the timer class corresponding to the timer component. For each time node in the timeline, the time node and its corresponding event binding function are passed to the timer instance in chronological order, and the corresponding event binding function is triggered based on the timer instance. Alternatively, the time from the start of the next event can be determined based on the time corresponding to the time node, and the time from the start of the next event and its corresponding event binding function are passed to the timer.

[0113] In one embodiment, such as Figure 10 As shown, step 503 above includes the following steps.

[0114] 5031 passes the time node and its corresponding event binding function to the timer instance to trigger the countdown information until the time node is reached, based on the timer instance.

[0115] The time node and its corresponding event binding function are passed as parameters to the timer instance. For example, if the current event status is "waiting for the start of the first round of the group stage," the start time of the first round of the group stage is obtained as the time node. The event binding function corresponding to the arrival and / or process of the arrival of the start time of the first round of the group stage is determined, and the corresponding event binding function is passed as the event binding function for the time node. The start time of the first round of the group stage and the corresponding event binding function are input together into the timer instance, and the countdown information for the time node is triggered according to the timer instance. Other time nodes are processed in the same way.

[0116] 5032, triggers the event binding function corresponding to the time node based on the countdown information.

[0117] When the time node corresponds to the start time of a sub-segment of the tournament instance, step 5032 includes: when the countdown information indicates that the current time is a preset time point before the time node, triggering the first server to generate a match room for the match-up entities of the sub-segment so that the user object entities in the match-up entities can enter the match room; and / or detecting whether the match room meets the corresponding match start conditions. If it does, triggering the sending of a tournament request for the target application to the second server so that the second server can execute the match between the match-up entities of the target application according to the tournament request.

[0118] For example, when the sub-stage is the first round of the group stage, the time management instance will start a countdown for the first round of the group stage based on its start time. When the countdown indicates that the current time is 15 minutes before the start time of the first round of the group stage, the event server will generate a match room for the corresponding user object entities to enter. The event server will check whether the match room meets the corresponding match start conditions. For example, the match start conditions could be that both user object entities in the match room have entered the match room and the countdown indicates that the current time has reached the start time of the first round of the group stage, or other conditions. If the conditions are met, an event request will be sent to the target application to notify the game server to start the match on the corresponding game server. The match between user object entities takes place on the game server, which is a set of servers that includes the match server. The match takes place on the corresponding match server.

[0119] Each match room has a unique room identifier, such as a room ID. User entities within the corresponding match pairings can see and enter this match room. User entities can view and enter the match room in the game client to prepare for the game. The system checks if the match room meets the corresponding match start conditions. If it does, the event server sends a match request to the game server, where the corresponding match is executed. If a player fails to enter a match room and / or prepare for the match within the specified time frame, it is considered to have forfeited the match, resulting in a loss with the default score.

[0120] 5033, Update timer instance.

[0121] When the countdown information indicates that the current time has reached the start time of the sub-segment of the schedule instance, update the timer instance and start the countdown for the maximum duration of the match-up entities in the sub-segment. For example, start a 20-minute countdown to prepare for settlement statistics.

[0122] When the time node corresponds to the end time of a sub-segment of the schedule instance, that is, when the maximum duration of the match-up entity in the sub-segment, such as the first round of the group stage, is reached, the steps described above for triggering the event binding function corresponding to the time node based on the countdown information include: triggering the call to the group logic component of the group management instance based on the countdown information; obtaining the match results between the match-up entities based on the group logic component; and updating the match asset data of the user object entity in the match-up entity based on the match results.

[0123] For example, if the maximum duration of a match is 20 minutes, then when the match has lasted 20 minutes, all matches in the sub-schedule have been completed, and the countdown information is 0, the grouping logic component of the group management instance is called, such as the group stage settlement function. Based on the grouping logic component, the match results between the opposing entities are obtained, such as which side won the match and the score. This match result can be obtained from the match server, or the match server can send the match result to the event server after the match is completed. The event server obtains the match result and updates the match asset data of each user object entity in the opposing entity according to the match result, such as updating the points and ranking of each user object entity in the opposing entity.

[0124] In one embodiment, when the time node is the time node corresponding to the end time of a sub-segment of the schedule instance, the step of triggering the event binding function corresponding to the time node based on the countdown information further includes: statistically analyzing the match asset data of the user object entity in all match-up entities of the sub-segment, and determining the match-up entity of the next sub-segment of the schedule instance according to preset rules; and filling the corresponding fields of the match-up entity of the next sub-segment in the schedule instance according to the determined match-up entity. In this process, before the end of the current round of the competition (i.e., the sub-segment), the user object entities in the match-up entities of the next round (i.e., the next sub-segment) cannot be determined. Therefore, when the sub-segment ends, the match asset data between each user object entity in the sub-segment is statistically analyzed, and then the user object entities in the match-up entities of the next sub-segment are determined according to preset rules. For example, the first and second place winners of each group stage are obtained, their order is shuffled, and then the actual user object entities in the match-up entities of the next sub-segment are determined according to preset rules. The user object entity field in the match-up entities of the next sub-segment is then populated based on the determined user object entities to determine the actual user object entities in each match-up entity of the next round.

[0125] In one embodiment, when the time node corresponds to the end time of a sub-segment of the tournament instance, the step of triggering the event binding function corresponding to the time node based on the countdown information further includes: synchronizing the match asset data of the user object entity to the requesting end, such as a third server, and the second server, such as a game server, through a time management instance. This facilitates the third client and the game client in obtaining the match asset data of each user object entity in the corresponding sub-segment from the third server and the game server.

[0126] After completing the above operations, the countdown will continue to be updated based on the start time of the next round of the competition, i.e., the next sub-segment.

[0127] In the above embodiment, throughout the entire event, event-related data is stored in the database through a storage management instance.

[0128] As described above, the tournament server executes all tournament-related business, including: tournament creation, tournament participation, tournament schedule generation, tournament grouping, tournament flow, tournament storage, tournament result updates, and tournament result push (to third-party servers, game servers, or game clients directly connected to the tournament server). On the third-party server, tournament-related services mainly include: forwarding tournament creation requests, forwarding tournament registration requests, viewing tournament information through the tournament server's service interface, and forwarding the tournament server's push results to third-party clients. Push results include the match asset data and match results of user objects within the tournament server. On the game server, tournament-related services mainly include: providing user object information such as tournament registration user object information, verifying whether user objects have permission to create and participate in tournaments, viewing tournament information through the tournament server's service interface, and players participating in the actual match process and sending match results to the tournament server.

[0129] All logic related to the event is implemented within the event server, which also handles the storage of event-related data. The original game servers and third-party servers only interact with the event server through service / communication interfaces. The event server provides service interfaces for game clients and third-party clients to query various event information. The actual match process, since each game is relatively independent, is handled by the game server (e.g., the event server). If a game application wants to use the event server's services, it only needs to implement the service / communication interface with the event server. The third-party server merely acts as a forwarding entry point, primarily for applying for events and querying event information, allowing user entities to access event information outside the game.

[0130] Therefore, any competitive game, as long as it connects to the tournament server (implementing the service interface / communication interface), can use all the services provided by the tournament server without needing to develop its own server from scratch. The tournament server itself can support multiple games, improving its applicability.

[0131] Furthermore, in this embodiment of the application, a competition management instance is created for at least one competition management component of the competition instance, and the competition management is integrated into the competition management component. The competition management is realized through the competition management instance corresponding to the competition management component, thereby improving the efficiency and applicability of competition management. In addition, the competition management is centralized on the first server, and the competition management is unrelated to the target application, further improving the efficiency of competition management.

[0132] All of the above technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here.

[0133] To facilitate better implementation of the event management method of this application embodiment, this application embodiment also provides an event management device. Please refer to 11. Figure 11 This is a schematic diagram of the structure of a competition management device provided in an embodiment of this application. The competition management device is integrated into a first server. The competition management device 600 may include an acquisition module 601, a first generation module 602, a second generation module 603, and a management module 604.

[0134] The acquisition module 601 is used to receive a competition creation request for a target application from the requesting end through the first server, and to acquire the competition template type and configuration parameter information of the competition corresponding to the competition creation request.

[0135] In one embodiment, the acquisition module 601 is further configured to, after receiving a competition creation request for the target application from the requesting end, obtain competition creation user object information corresponding to the first identification information from the second server of the corresponding target application through the first service interface, and the competition server determines whether the competition creation user object meets the creation conditions for creating a competition of the target application based on the competition creation user object information. If it does not meet the conditions, a prompt is issued.

[0136] The first generation module 602 is used to generate a competition instance of the competition based on the competition template type and the configuration parameter information.

[0137] In one embodiment, the first generation module 602 is specifically used to call the corresponding event template class according to the event template type, fill the corresponding fields in the event template class according to the configuration parameter information, and generate the corresponding event instance according to the event template class with the corresponding fields filled.

[0138] The second generation module 603 is used to generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type.

[0139] In one embodiment, the second generation module 603 is specifically used to determine at least one event management component corresponding to the event template type, call the 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 with the event instance to obtain the event management instance corresponding to the event instance.

[0140] The event management instances include user object management instances, group management instances, event schedule management instances, time management instances, and storage management instances.

[0141] The management module 604 is used to manage the event based on the event management instance of the event instance.

[0142] In one embodiment, the management module 604 includes a query management unit. This query unit receives event query requests from a requesting end, including a third server, and queries a list of events with created events based on the query request. The query unit then returns the event list to the requesting end via a second service interface. The query unit is also used to query various information from the event server, as described above.

[0143] In one embodiment, the management module 604 includes a user object management unit. The user object management unit is configured to receive a registration request for the event, the registration request including identification information of the registration user object; invoke a user object logic component in the user object management instance based on the identification information; use the user object logic component to determine whether the registration user object corresponding to the identification information meets the participation conditions for the event of the target application; if it does, add the registration user object as a user object entity to the event queue and update the event registration information.

[0144] In one embodiment, the management module 604 includes a group management unit. The group management unit is configured to, when detecting that the event meets the start conditions, pass the event queue of the user object management instance to the group management instance; invoke the grouping logic component of the group management instance; and use the grouping logic component to group the user object entities in the event queue to determine a group information list, wherein the group information list includes the group entities corresponding to the group management instance, and each group entity includes the user object entities included in that group.

[0145] In one embodiment, the management module 604 includes a schedule management unit. The schedule management unit is configured to: pass a list of group information from the group management instance to the schedule management instance; invoke a schedule logic component in the schedule management instance; and use the schedule logic component to process the group entities in the group information list to determine the schedule instance corresponding to the event. The schedule instance includes a schedule information list, which includes at least one match-up entity, and the match-up entity includes match time information and a user object entity for the match.

[0146] In one embodiment, the management module 604 includes a time management unit or a process management unit. The time management unit or process management unit is configured to: extract match time information from the match information list of the match management instance using the time management instance; generate a stage list structure based on the match time information, the stage list structure including at least one time node of the event determined based on the match time information and an event binding function corresponding to the time node, the time nodes being arranged in chronological order; pass the time node and the event binding function to a timer instance, and trigger the event binding function based on the timer instance.

[0147] In one embodiment, when the time management unit or process management unit executes the step of passing the time node and the event binding function to a timer instance and triggering the event binding function according to the timer instance, it specifically performs the following: passing the time node and the event binding function to the timer instance to trigger countdown information of the time node according to the timer instance; triggering the event binding function corresponding to the time node according to the countdown information; and updating the timer instance.

[0148] In one embodiment, the tournament instance includes at least one sub-tournament, and each sub-tournament includes at least one match-up entity. When the time node is the time node corresponding to the start time of the sub-tournament of the tournament instance, when the time management unit or process management unit executes the step of triggering the event binding function corresponding to the time node based on the countdown information, it specifically performs the following: when the countdown information indicates that the current time is a preset time point before the time node, it triggers the first server to generate a match room for the match-up entity of the sub-tournament so that the user object entity in the match-up entity can enter the match room; and / or detects whether the match room meets the corresponding match start condition. If so, it triggers the sending of the event request of the target application to the second server so that the second server executes the match between the match-up entities of the target application according to the event request.

[0149] In one embodiment, when the time node is the time node corresponding to the end time of a sub-segment of the schedule instance, the time management unit, when executing the step of triggering the event binding function corresponding to the time node based on the countdown information, specifically performs the following: triggering and calling the group logic component of the group management instance based on the countdown information; obtaining the match results between the match-up entities based on the group logic component; and updating the match asset data of the user object entity in the match-up entity based on the match results.

[0150] When the time node corresponds to the end time of a sub-segment of the schedule instance, the time management unit also performs statistics on the match asset data of user object entities in all match pairing entities of the sub-segment, and determines the match pairing entity of the next sub-segment of the schedule instance according to preset rules; and fills the corresponding fields of the match pairing entity of the next sub-segment in the schedule instance according to the determined match pairing entity.

[0151] When the time node corresponds to the end time of a sub-segment of the schedule instance, the time management unit also synchronizes the match asset data of the user object entity to the requesting end and the second server through the time management instance.

[0152] In one embodiment, the management module 604 includes a storage management unit. The storage management unit is used to store the event-related data to a database through the storage management instance.

[0153] All the above-described technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here. The beneficial effects achieved by the corresponding embodiments can be found in the beneficial effects described above.

[0154] Accordingly, embodiments of this application also provide a computer device, which can be a first server. For example... Figure 12 As shown, Figure 12 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. The computer device 700 includes a processor 701 with one or more processing cores, a memory 702 with one or more computer-readable storage media, and a computer program stored on the memory 702 and executable on the processor. The processor 701 and the memory 702 are electrically connected. Those skilled in the art will understand that the computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0155] The processor 701 is the control center of the computer device 700. It connects various parts of the computer device 700 through various interfaces and lines. By running or loading software programs (computer programs) and / or modules stored in the memory 702, and calling data stored in the memory 702, it performs various functions of the computer device 700 and processes data, thereby monitoring the computer device 700 as a whole.

[0156] In this embodiment, the processor 701 in the computer device 700 loads the instructions corresponding to the processes of one or more applications into the memory 702 according to the following steps, and the processor 701 runs the applications stored in the memory 702 to achieve various functions:

[0157] The system receives a tournament creation request for a target application from a requesting client via a first server, and obtains the tournament template type and configuration parameter information of the tournament corresponding to the tournament creation request; generates a tournament instance of the tournament based on the tournament template type and the configuration parameter information; generates a tournament management instance corresponding to the tournament instance based on at least one tournament management component corresponding to the tournament template type; and manages the tournament based on the tournament management instance of the tournament instance.

[0158] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0159] Optional, such as Figure 12 As shown, the computer device 700 also includes: a touch screen display 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 screen display 703, the radio frequency circuit 704, the audio circuit 705, the input unit 706, and the power supply 707. Those skilled in the art will understand that... Figure 12 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0160] The touch display screen 703 can be used to display a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. The touch display screen 703 may include a display panel and a touch panel. The display panel can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the computer device. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. Optionally, the display panel can be configured using a liquid crystal display (LCD), an organic light-emitting diode (OLED), or other similar devices. The touch panel can be used to collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel), generate corresponding operation commands, and execute the corresponding program. The touch panel may cover the display panel. When the touch panel detects a touch operation on or near it, it transmits the data to the processor 701 to determine the type of touch event. Subsequently, the processor 701 provides corresponding visual output on the display panel based on the type of touch event. In this embodiment, the touch panel and display panel can be integrated into the touch display screen 703 to achieve input and output functions. However, in some embodiments, the touch panel and the touch display screen 703 can be implemented as two independent components to achieve input and output functions. That is, the touch display screen 703 can also be used as part of the input unit 706 to achieve input functions.

[0161] In this embodiment, the touch display screen 703 is used to present a graphical user interface and receive operation commands generated by the user interacting with the graphical user interface.

[0162] The radio frequency circuit 704 can be used to transmit and receive radio frequency signals to establish wireless communication with network devices or other computer devices, and to transmit and receive signals with network devices or other computer devices.

[0163] Audio circuitry 705 can be used to provide an audio interface between a user and a computer device via a speaker and a microphone. Audio circuitry 705 converts received audio data into electrical signals, transmits them to the speaker, and the speaker converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by audio circuitry 705, converted back into audio data, and then processed by processor 701 before being transmitted via radio frequency circuitry 704 to, for example, another computer device, or output to memory 702 for further processing. Audio circuitry 705 may also include an earphone jack to facilitate communication between peripheral headphones and the computer device.

[0164] The input unit 706 can be used to receive input numbers, characters, or user characteristic information (such as fingerprints, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

[0165] Power supply 707 is used to supply power to various components of computer device 700. Optionally, power supply 707 can be logically connected to processor 701 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Power supply 707 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0166] although Figure 12 As not shown in the diagram, the computer device 700 may also include a camera, sensors, a wireless fidelity module, a Bluetooth module, etc., which will not be described in detail here.

[0167] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0168] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0169] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of computer programs that can be loaded by a processor to execute the steps in any of the event management methods provided in embodiments of this application. For example, the computer program can execute the following steps:

[0170] The system receives a tournament creation request for a target application from a requesting client via a first server, and obtains the tournament template type and configuration parameter information of the tournament corresponding to the tournament creation request; generates a tournament instance of the tournament based on the tournament template type and the configuration parameter information; generates a tournament management instance corresponding to the tournament instance based on at least one tournament management component corresponding to the tournament template type; and manages the tournament based on the tournament management instance of the tournament instance.

[0171] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0172] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0173] Since the computer program stored in the storage medium can execute the steps in any of the event management methods provided in the embodiments of this application, the beneficial effects that any of the event management methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0174] The above provides a detailed description of a competition management method, apparatus, storage medium, and computer device provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for managing competitions, characterized in that, include: The first server receives a competition creation request for the target application from the requesting end, and obtains the competition template type and configuration parameter information of the competition corresponding to the competition creation request. A tournament instance is generated based on the tournament template type and the configuration parameter information; Generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type; The event is managed based on the event management instance of the event instance; wherein, The event management instance includes a schedule management instance and a time management instance. The step of managing the event based on the event management instance of the event instance includes: The time management instance extracts the match time information from the match schedule information list of the match schedule management instance; A stage list structure is generated based on the match time information. The stage list structure includes at least one time node of the event determined based on the match time information and an event binding function corresponding to the time node. The time nodes are arranged in chronological order. The time node and the event binding function are passed to the timer instance to trigger a countdown to the time node based on the timer instance; The event binding function corresponding to the time node is triggered based on the countdown information; Update the timer instance.

2. The event management method according to claim 1, characterized in that, The event management instance includes a user object management instance, and the step of managing the event based on the event management instance of the event instance includes: Receive a registration request for the event, the registration request including the identification information of the user object registering for the event; The user object logic component in the user object management instance is invoked based on the identification information; The user object logic component is used to determine whether the event registration user object corresponding to the identification information meets the participation conditions for the event of the target application; If the conditions are met, the registered user object is added as a user object entity to the event queue, and the event registration information is updated.

3. The event management method according to claim 1, characterized in that, The event management instance includes a group management instance, and the step of managing the event based on the event management instance of the event instance includes: When the event is detected to meet the start conditions, the event queue of the user object management instance is passed to the group management instance; Invoke the group logic component of the group management instance; The user object entities in the event queue are grouped using the grouping logic component to determine a group information list. The group information list includes the grouping entities corresponding to the grouping management instance, and each grouping entity includes the user object entities included in each group.

4. The event management method according to claim 1, characterized in that, The event management instance includes a group management instance and a schedule management instance. The step of managing the event based on the event management instance of the event instance includes: Pass the group information list from the group management instance to the schedule management instance; Invoke the schedule logic component in the schedule management instance; The schedule logic component is used to process the grouping entities in the group information list to determine the schedule instance corresponding to the event. The schedule instance includes a schedule information list, which includes at least one match-up entity. The match-up entity includes match time information and the match's user object entity.

5. The event management method according to claim 1, characterized in that, The schedule management instance includes at least one sub-schedule, and each sub-schedule includes at least one match-up entity. When the time node corresponds to the start time of the sub-schedule of the schedule instance, the step of triggering the event binding function corresponding to the time node based on the countdown information includes: When the countdown information indicates that the current time is a preset time point before the time node, the first server is triggered to generate a match room for the match-up entity of the sub-segment so that the user object entity in the match-up entity can enter the match room; and / or If the match room meets the corresponding match start conditions, a match request for the target application is sent to the second server, so that the second server executes the match between the match-up entities of the target application according to the match request.

6. The event management method according to claim 1, characterized in that, The schedule management instance includes at least one sub-schedule, and each sub-schedule includes at least one match-up entity. When the time node corresponds to the end time of the sub-schedule of the schedule instance, and the event management instance includes a group management instance, the step of triggering the event binding function corresponding to the time node based on the countdown information includes: The countdown information triggers the invocation of the group logic component of the group management instance; The match results between the opposing entities are obtained according to the grouping logic component. Update the match asset data of the user object entity in the match-up entity based on the match results.

7. The event management method according to claim 6, characterized in that, Also includes: The match asset data of user object entities in all match pairs of the sub-schedule are statistically analyzed, and the match pairs of the next sub-schedule of the schedule instance are determined according to preset rules. Fill in the corresponding fields in the match-up entity of the next sub-schedule in the schedule instance based on the determined match-up entity.

8. The event management method according to claim 6, characterized in that, After obtaining the competition information of the user object entity, the competition management method further includes: The time management instance synchronizes the match asset data of the user object entity to the requesting client and the second server.

9. The event management method according to any one of claims 1-8, characterized in that, The event management instance includes a storage management instance. The step of managing the event based on the event management instance of the event instance includes: storing the event-related data into a database through the storage management instance.

10. The event management method according to any one of claims 1-8, characterized in that, The step of generating a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type includes: Identify at least one event management component corresponding to the event template type, and call the event management template class corresponding to the event management component; Create a corresponding event management instance based on the event management template class; Bind the event management instance to the event instance to obtain the event management instance corresponding to the event instance.

11. A competition management device, characterized in that, include: The acquisition module is used to receive a competition creation request for a target application from the requesting end through the first server, and to acquire the competition template type and configuration parameter information of the competition corresponding to the competition creation request. The first generation module is used to generate a competition instance of the competition based on the competition template type and the configuration parameter information; The second generation module is used to generate a competition management instance corresponding to the competition instance based on at least one competition management component corresponding to the competition template type. The management module is used to manage the event based on the event management instance of the event instance, wherein the event management instance includes a schedule management instance and a time management instance; wherein, The management module includes a time management unit or a process management unit. The time management unit or the process management unit is used to extract match time information from the match information list of the match management instance through the time management instance; generate a stage list structure based on the match time information, the stage list structure including at least one time node of the event determined based on the match time information and an event binding function corresponding to the time node; pass the time node and the event binding function to a timer instance to trigger a countdown to the time node based on the timer instance; and trigger the event binding function corresponding to the time node based on the countdown information. Update the timer instance.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted for loading by a processor to perform the steps of the event management method as described in any one of claims 1-10.

13. A computer device, characterized in that, The computer device includes a memory and a processor. The memory stores a computer program, and the processor executes the steps of the event management method as described in any one of claims 1-10 by calling the computer program stored in the memory.

Images