CN112988291A

CN112988291A - Page event management method and device, computer readable medium and electronic equipment

Info

Publication number: CN112988291A
Application number: CN201911301779.XA
Authority: CN
Inventors: 凌刚
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-12-17
Filing date: 2019-12-17
Publication date: 2021-06-18
Anticipated expiration: 2039-12-17
Also published as: CN112988291B

Abstract

The embodiment of the application provides a page event management method and device, a computer readable medium and electronic equipment. The matching method comprises the following steps: when a target page is to be displayed, determining a first event concerned by the target page; acquiring the page event attribute of the first event in the target page; acquiring a recording event attribute of the first event in an event record; and responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page. The technical scheme of the embodiment of the application can improve the flexibility of managing the page event, particularly the cross-page event.

Description

Page event management method and device, computer readable medium and electronic equipment

Technical Field

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

Background

In a page event management scenario, such as a management scenario of a cross-page event, management of an event is usually achieved through an agent mode or a notification center mode, and in the agent mode, a client and an agent manage the page event through a protocol. However, how to improve the flexibility of managing page events, especially cross-page events, is a technical problem to be solved urgently.

Disclosure of Invention

Embodiments of the present application provide a method and an apparatus for managing a page event, a computer-readable medium, and an electronic device, so that accuracy of managing a page event can be improved to at least a certain extent.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.

According to an aspect of an embodiment of the present application, there is provided a page event management method, including: when a target page is to be displayed, determining a first event concerned by the target page; acquiring the page event attribute of the first event in the target page; acquiring a recording event attribute of the first event in an event record; and responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.

According to an aspect of an embodiment of the present application, there is provided a page event management apparatus, including: the system comprises a determining unit, a display unit and a display unit, wherein the determining unit is used for determining a first event concerned by a target page when the target page is to be displayed; a first obtaining unit, configured to obtain a page event attribute of the first event in the target page; a second acquiring unit, configured to acquire a recording event attribute of the first event in an event record; and the response unit is used for responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.

In some embodiments of the present application, based on the foregoing solution, a trigger button for triggering a second event is included in the target page, and the apparatus further includes: the generating unit is used for responding to the second event triggered by the user through the trigger button after the target page is displayed, and generating a recording event attribute aiming at the second event; a saving unit, configured to save the recording event attribute of the second event in the event record.

In some embodiments of the present application, based on the foregoing scheme, the event record is recorded by an event management center.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a creation time of the target page, the recording event attribute includes a first response reference time of the first event, and the response unit is configured to: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; and responding to the first event concerned by the target page if the creation time of the target page is earlier than the first response reference time of the first event.

In some embodiments of the present application, based on the foregoing solution, the response unit is configured to: and after responding to the first event concerned by the target page, updating the first response reference time of the first event in the record event attribute to the creation time of the target page.

In some embodiments of the present application, based on the foregoing scheme, the determining unit is configured to: before determining a first event of interest of a target page, when the first event of interest does not exist in the target page, updating a first response reference time of the first event in the record event attribute to a creation time of the target page.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a second response reference time of the first event, the recording event attribute includes a trigger time of the first event, and the response unit is configured to: detecting whether a second response reference time of the first event is earlier than a trigger time of the first event; and responding to the first event concerned by the target page if the second response reference time of the first event is earlier than the trigger time of the first event.

In some embodiments of the present application, based on the foregoing solution, the response unit is configured to: and after responding to the first event concerned by the target page, updating the second response reference time of the first event in the page event attribute as the trigger time of the first event.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit is configured to: and updating the first state value to a second state value to obtain a new first state value.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit is configured to: detecting whether the first state value is consistent with the second state value; and if the first state value is inconsistent with the second state value, updating the first state value to the second state value to obtain a new first state value.

According to an aspect of an embodiment of the present application, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor implements the page event management method as described in the above embodiment.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the page event management method as described in the above embodiments.

In the technical solutions provided by some embodiments of the present application, when a target page is to be displayed, a response is made to a first event concerned by the target page by acquiring a page event attribute of the first event concerned in the target page and a recording event attribute in an event record, and according to the page event attribute and the recording event attribute of the first event. According to the method and the device, the record event attribute of the first event concerned by the target page is recorded in the event record, the record event attribute of the first event is acquired from the event record, and the page event attribute acquired in the target page is referred to, so that the corresponding response is made to the first event concerned by the target page, the management of the page event is simplified, and the flexibility of managing the page event, particularly the cross-page event, can be improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 illustrates an implementation environment diagram of a solution according to an embodiment of the present application;

FIG. 2 illustrates an application diagram of a page event management method according to an embodiment of the present application;

FIG. 3 shows a flow diagram of a page event management method according to one embodiment of the present application;

FIG. 4 illustrates a flowchart of a method after a target page is exposed according to one embodiment of the present application;

FIG. 5 illustrates a communication diagram of an event management center according to one embodiment of the present application;

FIG. 6 illustrates a flow diagram for an implementation of an event management center according to an embodiment of the present application;

FIG. 7 illustrates a diagram of implementation elements of an event management center according to one embodiment of the present application;

FIG. 8 illustrates a detailed flow diagram responsive to a first event of interest to a target page according to one embodiment of the present application;

FIG. 9 illustrates a detailed flow diagram responsive to a first event of interest to a target page according to one embodiment of the present application;

FIG. 10 illustrates a detailed flow diagram responsive to a first event of interest to a target page according to one embodiment of the present application;

FIG. 11 illustrates a business flow diagram for implementing page event management according to one embodiment of the present application;

FIG. 12 shows a block diagram of a page event management apparatus according to an embodiment of the present application;

FIG. 13 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

Fig. 1 shows an implementation environment diagram of a technical solution according to an embodiment of the present application.

As shown in fig. 1, an implementation environment of the technical solution of the embodiment of the present application may include a terminal device. For example, any one of the smart phone 101, the tablet computer 102, the touch display 103 and the portable computer 104 shown in fig. 1 is included, but other electronic devices with touch or non-touch display functions and the like are also possible.

In an embodiment of the present application, a user may implement the technical solution of the embodiment of the present application by using a smartphone with a touch or non-touch display function, such as the smartphone 101 shown in fig. 1. Specifically, the screen of the smartphone may display a page, and the page displayed on the screen has an event that may be displayed or may be triggered.

To make the present application more intuitive for those skilled in the art, a specific example will be described herein.

In a specific implementation of an embodiment, the technical solution of the present application may be implemented with reference to a page shown in fig. 2, for example, fig. 2 shows an application diagram of a page event management method according to an embodiment of the present application.

As shown in fig. 2, a change situation of event information in a display page after an operation instruction across pages is shown, specifically, if a user a performs some operations on a playing page, after returning to a personal page, the entire page needs to be refreshed to ensure that the information is shown updated in real time, and these operations are triggers of events. The simple application procedure is as follows:

user A can see the "like" number (like event) and "play" number (play event) of each video in his personal page like video list, and can also see the privacy status (privacy event) if this video is user A's own video

In an effect aspect of event information presentation in the event management process, after the user a clicks the 2 nd video in the private page 201 (at this time, the number of "praise" in the private page is 80), the private page 201 jumps to the play page 202 of the 2 nd video, and in the play process, the user performs the praise operation through the lower right corner of the play page 202.

Meanwhile, if the video is just the video published by the user a, the user a can also perform editing operations, including modifying the private or public state of the video and deleting the video (editing-related events are not shown in fig. 2).

After the user performs the operation of approval, the user clicks the return button on the upper left corner of the play page, at this time, the play page 202 returns to the private page 203 of the user, and at this time, the information of the private page needs to be wholly or partially refreshed to ensure that the display of the page event information is normal. Such as the "like" number (at this time, the "like" number in the private page is 81), the play number, the private or public state, the deletion state of the video, and the like.

The simplest scenario spanning two consecutive pages is described above, and in practical applications, we also often encounter an event management scenario with a complex link. For example, the user a may first enter the attention list of the private page, enter the private page of the user B in the attention list, then enter a play page of a certain video from the private page of the user B, perform a relevant operation (like or cancel like) on the play page, and then return to the private page of the user a itself, and if the video operated on the play page is just displayed in the video list that the user a likes itself, it is also necessary to refresh the entire page immediately at this time. To ensure that the event change information caused by self-operation can be effective in real time.

The implementation details of the technical solution of the embodiment of the present application are set forth below:

according to a first aspect of the present disclosure, a page event management method is provided.

Referring to fig. 3, a flow diagram of a page event management method according to an embodiment of the present application is shown, which may be performed by a device having a computing processing function, such as the smartphone 101 shown in fig. 1, or the tablet 102 shown in fig. 1. As shown in fig. 3, the page event management method at least includes steps 310 to 370:

step 310, when the target page is to be displayed, determining a first event concerned by the target page.

Step 330, acquiring the page event attribute of the first event in the target page.

And step 350, acquiring the record event attribute of the first event in the event record.

Step 370, responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event, so as to display the target page.

In an embodiment of the present application, after the page is presented, a page event management method as shown in fig. 4 may also be implemented.

Referring to FIG. 4, a flowchart of a method after presenting a target page is shown, according to one embodiment of the present application. Specifically, the method may include steps 380 to 390:

step 380, in response to the user triggering the second event through the trigger button, generating a recording event attribute for the second event.

Step 390, saving the recording event attribute of the second event in the event record.

In one embodiment of the present application, event logging as described above may be recorded by an event management center.

In order to make those skilled in the art understand the event management center disclosed in the present application, the following will describe the technical solution of the present application in detail around the event management center:

referring to fig. 5, a communication diagram of an event management center according to an embodiment of the present application is shown. As shown in fig. 5, the page event management method disclosed in the present application is implemented based on two parts, namely, a basic page display module 501 and an event management center 502.

Specifically, the basic page display module is mainly used for managing links of a page in the whole life cycle, including page creation, page display, page event response, page interaction and page closing. In the present application, the event management center may provide the capability of querying and recording the trigger event for the page. In addition, for the basic page presentation module, in order to ensure that the result of querying the trigger event is more accurate when the multi-level page repeatedly enters, the page presentation module is also required to have the capability of recording and refreshing the time point to the event management center.

In a specific implementation of an embodiment, the implementation of the page event management method disclosed in the present application by the basic page presentation module and the event management center may be implemented by a process as shown in fig. 6.

Referring to fig. 6, a flow diagram of an implementation of an event management center according to an embodiment of the present application is shown. Specifically, the method includes a process 601, a process 602, and a process 603:

the process 601 mainly implements the process of the page at the time of creation, and the main content is recording the creation time, and registering the types of events concerned by the page based on the business situation, such as "like" event, "delete" event, and so on.

The process 602 mainly implements a process of displaying a page, specifically, if there is an event of interest on the page, the page is queried in an event management center, a trigger record is queried, that is, an event response is performed, and then a record event attribute of the event in the event management center can be updated. The event record attribute of the event management center can also be updated if there is no event of interest or no trigger is queried.

The process 603 mainly implements a process in the user interaction process, and specifically, if the user triggers events (e.g., "approve" event, "delete" event, etc.), records the triggering events of the events in the event management center.

Each page has an implementation of a base class, for example, the base class of all pages in the IOS system is UI View Controller. In the present application, in all the process nodes shown in fig. 6, except for 3 process nodes of "setting an event type of interest", "response event", and "event trigger record", other process nodes may be implemented in the base class.

In a specific implementation of an embodiment, implementing the page event management method disclosed herein may be implemented by implementing elements as shown in fig. 7.

Referring to FIG. 7, a diagram of implementation elements of an event management center is shown, according to one embodiment of the present application. Specifically, the method includes a basic page controller 701, a sub-page controller 702, and an event management center 703:

the underlying page controller 701: the page Controller inherits the basis of the UI View Controller, each App usually has its own page Controller Base class, which can be expressed by the Base View Controller in the application, and it has 2 attributes, namely the concerned event type and the page creation time, and simultaneously has three method protocols including page creation completion, page display and response event.

The sub-page controller 702: specific business page controllers, such as the private page and the play page shown in fig. 2, that inherit from the Base View Controller are the representation of the specific content carried by the sub-page controllers. Since the sub-page Controller inherits the capability of the Base View Controller, only 3 process nodes of "set event type of attention", "response event", and "event trigger record" as shown in FIG. 6 need to be implemented

The event management center 703: the application can include 2 attributes, namely, the creation time point of the last display page, and an event information storage dictionary (which is required for internal logic implementation and does not need to be exposed to the outside), and can also include an external capability of triggering events and inquiring whether events are triggered.

The implementation steps as shown in fig. 3 will be explained in detail below:

referring to fig. 3, in step 310, when a target page is to be presented, a first event of interest to the target page is determined.

In an embodiment of the application, before determining a first event focused on by a target page, it may be detected whether the first event is focused on by the target page, and if the first event is detected to be focused on by the target page, a subsequent step is performed.

With continued reference to FIG. 3, in step 330, a page event attribute of the first event in the target page is obtained.

In an embodiment of the present application, the page event attribute of the first event in the target page may refer to a creation time of the target page. For example, in fig. 2, the private page 201 is created 11 minutes and 11 seconds at 11/2019, and the page event attribute of the "like" event that the private page 201 focuses on may be: "page creation time: 11/11.

In an embodiment of the present application, the page event attribute of the first event in the target page may also refer to a second response reference time of the first event. In particular, there may be a second response reference time for each event in the page. It should be noted that, when a page is created, if an event of interest exists in the page, the initial second response reference time corresponding to the event of interest in the page may be the creation time of the page, for example, in fig. 2, the private page 201 is created 11 minutes and 11 seconds at 11 th of 2019, and the page event attribute of the "like" event of interest to the private page 201 may be: "second response reference time: 11 months 11 days 11 minutes 11 seconds in 2019. It should also be noted that the second response reference time corresponding to each event may be changed in subsequent operations.

In an embodiment of the present application, the page event attribute of the first event in the target page may refer to a first state value of the first event. Specifically, for example, in fig. 2, the "80" praise number shown in the private page 201 is the first state value of the "praise" event.

With continued reference to fig. 3, in step 350, a recording event attribute of the first event in the event record is obtained.

In an embodiment of the present application, the recording event attribute of the first event in the event record may refer to a trigger time of the first event. For example, in fig. 2, if an "like" event in the private page 202 is triggered by a user click 13 minutes and 13 seconds at 13.13.13.13.13.13.13.13 months in 2019, the trigger time of the "like" event may be: "13 minutes and 13 seconds at 13 months and 13 days in 2019", therefore, the recording event attribute of the "like" event recorded in the event record may be: "time to trigger: 13 months 13 days 13 minutes 13 seconds 2019 ".

Furthermore, the triggering time of the first event may also be the creation time of the page shown when the first event is triggered, for example, in fig. 2, the private page 202 is created 12 minutes and 12 seconds at 12 months and 12 days in 2019, 12 months and 12 days, then after the "like" event is triggered in the private page 202, the creation time "12 minutes and 12 seconds at 12 months and 12 days in 2019, 12 months and 12 days" of the private page 202 may be used as the triggering time of the "like" event, and therefore, the recording event attribute of the "like" event recorded in the event record may be: "time to trigger: 12 months 12 days 12 minutes 12 seconds in 2019 ".

It should be noted that there may be a trigger time in the event log for each event in the page, and the trigger time of the event in the event log is not changed.

In an embodiment of the present application, the recording event attribute of the first event in the event record may also refer to a first response reference time of the first event. Specifically, each event may have a first response reference time in the event log. It should be noted that each time an event is triggered, its trigger time may be used as the initial first response reference time of the event. For example, in fig. 2, the trigger time of the "like" event in the private page 202 is "12 minutes and 12 seconds 12 months 12 days 2019", then the initial first response reference time of the "like" event in the event record may be: "first response reference time: 12 months 12 days 12 minutes 12 seconds in 2019 ". It should be noted that, in the subsequent operation, the first response reference time corresponding to each event may be changed in the event record.

In an embodiment of the present application, the recording event attribute of the first event in the event record may also refer to a second state value of the first event. Specifically, for example, in fig. 2, after the "like" event shown in the private page 202 is triggered, the like number "81" is the second state value of the "like" event in the event record.

With continued reference to fig. 3, in step 370, responding to the first event of interest of the target page according to the page event attribute and the record event attribute of the first event to display the target page.

In the present application, step 370 may be implemented by the following embodiments:

the first embodiment,

In this embodiment, the page event attribute includes creation time of the target page, the recording event attribute includes first response reference time of the first event, and responding to the first event focused by the target page according to the page event attribute and the recording event attribute of the first event can be implemented by the steps shown in fig. 8.

Referring to FIG. 8, a detailed flow diagram is shown illustrating a response to a first event of interest to a target page according to one embodiment of the present application. Specifically, the method may include steps 371 to 372:

step 371, detecting whether the creation time of the target page is earlier than a first response reference time of the first event.

Step 372, responding to the first event concerned by the target page if the creation time of the target page is earlier than the first response reference time of the first event.

For example, the creation time of the target page is "11 minutes 11 seconds at 11 days 11/11 months in 2019", the first response reference time of the first event is "12 minutes 12 seconds at 12 days 12/12 months at 12 months in 2019", and it can be known through detection that the creation time of the target page is earlier than the first response reference time of the first event, and at this time, a response needs to be made to the first event concerned by the target page.

In a specific implementation of the first embodiment, the page event attribute further includes a first state value of the first event, the record event attribute further includes a second state value of the first event, and the responding to the first event concerned by the target page may be updating the first state value to the second state value to obtain a new first state value.

For example, if the first event is an "like" event, the first state value of the "like" event is: and 80 times, wherein the second state value of the event of like is as follows: "81 times". Responding to a first event concerned by the target page, namely updating a first state value of the event of 'like' into: "81 times".

In a specific implementation of the first embodiment, after responding to the first event of interest of the target page, the first response reference time of the first event in the record event attribute may be further updated to the creation time of the target page.

For example, the first response reference time of the first event in the recorded event attributes is "12 minutes 12 seconds 12 days 12 months 12 days 12 hours 2019", the creation time of the target page is "11 minutes 11 seconds 11 days 11 months 11 hours 2019", and after the response is made to the first event of interest to the target page, the first response reference time of the first event in the recorded event attributes may be updated to "11 minutes 11 seconds 11 days 11 months 2019".

In a specific implementation of the first embodiment, before the determining the first event of interest of the target page in step 310, the method may further include: if it is detected that there is no concerned first event in the target page, the first response reference time of the first event in the record event attribute may be updated to the creation time of the target page.

The advantages of this embodiment are: the first event concerned by the target page is responded by detecting whether the creation time of the target page is earlier than the first response reference time of the first event recorded in the event record, so that the monitoring and responding to the page event can be clearly, simply and flexibly realized and completed.

Example II,

In this embodiment, the page event attribute includes a second response reference time of the first event, the recording event attribute includes a trigger time of the first event, and responding to the first event focused by the target page according to the page event attribute and the recording event attribute of the first event may be implemented by the steps shown in fig. 9.

Referring to FIG. 9, a detailed flow diagram responsive to a first event of interest to a target page is shown, according to one embodiment of the present application. Specifically, steps 373 to 374 may be included:

step 373, detecting whether the second response reference time of the first event is earlier than the trigger time of the first event.

In step 374, if the second response reference time of the first event is earlier than the trigger time of the first event, responding to the first event concerned by the target page.

In a specific implementation of the second embodiment, the page event attribute further includes a first state value of the first event, the record event attribute further includes a second state value of the first event, and the responding to the first event concerned by the target page may be updating the first state value to the second state value to obtain a new first state value.

In a specific implementation of the second embodiment, after responding to the first event of interest of the target page, the second response reference time of the first event in the page event attribute may be further updated to the trigger time of the first event.

In a specific implementation of the second embodiment, after responding to the first event of interest of the target page, the second response reference time of the first event in the page event attribute may also be updated to the response time when responding to the first event of interest of the target page.

Example III,

In this embodiment, the page event attribute includes a first state value of the first event, the recording event attribute includes a second state value of the first event, and responding to the first event focused by the target page according to the page event attribute and the recording event attribute of the first event may be implemented by the steps shown in fig. 10.

Referring to FIG. 10, a detailed flow diagram responsive to a first event of interest to a target page is shown, according to one embodiment of the present application. Specifically, the method may include steps 375 to 376:

step 375, detecting whether the first state value and the second state value are consistent.

In step 376, if the first state value is not consistent with the second state value, the first state value is updated to the second state value, so as to obtain a new first state value.

In order to make the present application more understandable to those skilled in the art, the present application will be described in a specific service scenario with reference to embodiment one:

referring to FIG. 11, a business flow diagram implementing page event management is shown, according to one embodiment of the present application.

In the business scenario, the user jumps from page 1 to page 2, from page 2 to page 3, and from page 3 to page 4 in sequence. Then returning the way. The event a1 concerned by the page 1, the event a2 concerned by the page 2, and no event concerned by the page 3 and the page 4 exist, but in the page 3, the event a1 can be triggered by corresponding operations, in the page 4, the event a2 can be triggered by corresponding operations, and when the page 2 and the page 1 are displayed again, responses need to be respectively carried out according to the events a2 and a1 concerned by the page 1. The specific implementation process comprises the following 23 steps:

step 1: when the page 1 is created and displayed, the creation time t1 of the page 1 is recorded, the event type a1 concerned by the page 1 is registered based on the business situation (both t1 and a1 are in the page event attribute of the page 1), meanwhile, the t1 is updated to the event management center, and the creation time of the last displayed page is recorded as t 1.

Step 2: in response to the user's interactive operation, page 2 is created and jumps from page 1 to page 2.

And step 3: similar to the step 1, when the page 2 is displayed, the creation time t2 is recorded, the concerned event type a2 is registered based on the business situation (both t2 and a2 are in the page event attribute of the page 2), meanwhile, the t2 is updated to the event management center, and the creation time of the last displayed page is recorded as t 2.

And 4, step 4: in response to the user's interaction, page 3 is created and jumps from page 2 to page 3.

And 5: similar to the step 1, when the page 3 is displayed, the creation time t3 of the page is recorded (because the page 3 has no concerned event, no a3, a1 or a2 exists), meanwhile, the t3 is updated to the event management center, and the creation time of the last displayed page is recorded as t 3.

Step 6: event a1 is triggered in response to a user interaction at page 3.

And 7: the trigger event record of the event a1 is recorded in the event management center and stored in a dictionary manner, the state value of the event a1 is a1, and the first response reference time of the event a1 is t3 (because the creation time of the event trigger page is t 3).

And 8: in response to the user's interaction, page 4 is created and jumps from page 3 to page 4.

And step 9: similar to the step 5, when the page 4 is displayed, the creation time t4 of the page is recorded (because the page 4 has no concerned event, no a4, a1 or a2 exists), meanwhile, the t4 is updated to the event management center, and the creation time of the last displayed page is recorded as t 4.

Step 10: in response to a user interaction at Page 4, event a2 is triggered

Step 11: the trigger event record of the event a2 is recorded in the event management center and stored in a dictionary manner, the state value of the event a2 is a2, and the first response reference time of the event a2 is t4 (because the creation time of the event trigger page is t 4).

Step 12: in response to the user's interaction, a jump back is made from page 4 to page 3.

Step 13: when the page 3 is redisplayed, since it does not concern itself about any event, the last presentation page creation time of the event management center is directly updated to t3, while the first response reference time of all events in the dictionary is updated to t 3.

Step 14: and jumping back from the page 3 to the page 2 in response to the user interaction.

Step 15: when the page 2 is redisplayed, because there is the event a2 concerned, it is necessary to detect whether the event management center has been triggered by a 2.

Step 16: since the first response reference time corresponding to the event a2 is t3 and the creation time t2 of the page 2 is earlier than the first response reference time t3 corresponding to the event a2 in the dictionary stored in the event management center, the trigger result of the event a2 is returned

And step 17: page 2 responds to event a2, which it is interested in, based on the trigger result of event a2 returned by the event management center.

Step 18: the last presentation page creation time of the update event management center is t2, while the first response reference time of all events in the dictionary is updated to t 2.

Step 19: and responding to the interaction operation of the user, and jumping back from the page 2 to the page 1.

Step 20: similar to step 15, when the page 1 is redisplayed, since there is an event a1 concerned, it is necessary to detect whether the event a1 has been triggered or not to the event management center.

Step 21: similarly to the step 16, since the first response reference time corresponding to the event a1 is t2 and the creation time t1 of the page 1 is earlier than the first response reference time t2 corresponding to the event a1 in the dictionary stored in the event management center, the trigger result of the event a1 is returned.

Step 22: similar to step 17, page 1 responds to event a1, which it is interested in, based on the trigger result of event a1 returned by the event management center.

Step 23: similar to step 18, the creation time of the last presentation page of the update event management center is t1, and the dictionary can be emptied because only 1 root page of page 1 remains in the whole page link.

In the technical solution of the foregoing embodiment of the present application, a page event attribute of a first event concerned in a target page in the target page and a record event attribute of the first event in an event record are obtained, and a response is made to the first event concerned in the target page according to the page event attribute and the record event attribute of the first event. According to the method and the device, the record event attribute of the first event concerned by the target page is recorded in the event record, the record event attribute of the first event is obtained from the event record, the page event attribute obtained from the target page is referred, and the corresponding response is made to the first event concerned by the target page, so that the management of the page event is simpler, and the flexibility of managing the page event, particularly the cross-page event, can be improved.

The following describes embodiments of an apparatus of the present application, which may be used to perform the page event management method in the foregoing embodiments of the present application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the page event management method described above in the present application.

FIG. 12 shows a block diagram of a page event management apparatus according to an embodiment of the present application.

Referring to fig. 12, a page event management apparatus 1200 according to an embodiment of the present application includes: a determination unit 1201, a first acquisition unit 1202, a second acquisition unit 1203, and a response unit 1204.

The determining unit 1201 is used for determining a first event concerned by a target page when the target page is to be displayed; a first obtaining unit 1202, configured to obtain a page event attribute of the first event in the target page; a second obtaining unit 1203, configured to obtain a recording event attribute of the first event in an event record; a responding unit 1204, configured to respond to the first event of interest of the target page according to the page event attribute and the record event attribute of the first event, so as to display the target page.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a creation time of the target page, the recording event attribute includes a first response reference time of the first event, and the response unit 1204 is configured to: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; and responding to the first event concerned by the target page if the creation time of the target page is earlier than the first response reference time of the first event.

In some embodiments of the present application, based on the foregoing solution, the response unit 1204 is configured to: and after responding to the first event concerned by the target page, updating the first response reference time of the first event in the record event attribute to the creation time of the target page.

In some embodiments of the present application, based on the foregoing scheme, the determining unit 1204 is configured to: before determining a first event of interest of a target page, when the first event of interest does not exist in the target page, updating a first response reference time of the first event in the record event attribute to a creation time of the target page.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a second response reference time of the first event, the recording event attribute includes a trigger time of the first event, and the response unit 1204 is configured to: detecting whether a second response reference time of the first event is earlier than a trigger time of the first event; and responding to the first event concerned by the target page if the second response reference time of the first event is earlier than the trigger time of the first event.

In some embodiments of the present application, based on the foregoing solution, the response unit 1204 is configured to: and after responding to the first event concerned by the target page, updating the second response reference time of the first event in the page event attribute as the trigger time of the first event.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit 1204 is configured to: and updating the first state value to a second state value to obtain a new first state value.

In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit 1204 is configured to: detecting whether the first state value is consistent with the second state value; and if the first state value is inconsistent with the second state value, updating the first state value to the second state value to obtain a new first state value.

It should be noted that the computer system 1300 of the electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 13, a computer system 1300 includes a Central Processing Unit (CPU)1301 that can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 1302 or a program loaded from a storage portion 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for system operation are also stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An Input/Output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program executes various functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 1301.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A page event management method is characterized by comprising the following steps:

when a target page is to be displayed, determining a first event concerned by the target page;

acquiring the page event attribute of the first event in the target page;

acquiring a recording event attribute of the first event in an event record;

and responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.

2. The method of claim 1, wherein the target page includes a trigger button for triggering a second event, and wherein after presenting the target page, the method further comprises:

generating a recording event attribute for the second event in response to the user triggering the second event through the trigger button;

and saving the recording event attribute of the second event in the event record.

3. The method of claim 1, wherein the event record is recorded by an event management center.

4. The method of claim 1, wherein the page event attribute comprises a creation time of the target page, wherein the recording event attribute comprises a first response reference time of the first event,

the responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event comprises the following steps:

detecting whether the creation time of the target page is earlier than a first response reference time of the first event;

and responding to the first event concerned by the target page if the creation time of the target page is earlier than the first response reference time of the first event.

5. The method of claim 4, wherein after responding to a first event of interest to the target page, the method further comprises:

and updating the first response reference time of the first event in the record event attribute to the creation time of the target page.

6. The method of claim 4, wherein prior to determining the first event of interest to the target page, the method further comprises:

and when the first event concerned does not exist in the target page, updating the first response reference time of the first event in the record event attribute as the creation time of the target page.

7. The method of claim 1, wherein the page event attribute comprises a second response reference time for the first event, wherein the recording event attribute comprises a trigger time for the first event,

detecting whether a second response reference time of the first event is earlier than a trigger time of the first event;

and responding to the first event concerned by the target page if the second response reference time of the first event is earlier than the trigger time of the first event.

8. The method of claim 7, wherein after responding to a first event of interest to the target page, the method further comprises:

and updating the second response reference time of the first event in the page event attribute to the trigger time of the first event.

9. The method of any of claims 1-8, wherein the page event attribute comprises a first state value of the first event, wherein the record event attribute comprises a second state value of the first event,

the responding to the first event of interest to the target page comprises:

and updating the first state value to a second state value to obtain a new first state value.

10. The method of claim 1, wherein the page event attribute comprises a first state value of the first event, wherein the record event attribute comprises a second state value of the first event,

detecting whether the first state value is consistent with the second state value;

and if the first state value is inconsistent with the second state value, updating the first state value to the second state value to obtain a new first state value.

11. A page event management apparatus, characterized in that the apparatus comprises:

the system comprises a determining unit, a display unit and a display unit, wherein the determining unit is used for determining a first event concerned by a target page when the target page is to be displayed;

a first obtaining unit, configured to obtain a page event attribute of the first event in the target page;

a second acquiring unit, configured to acquire a recording event attribute of the first event in an event record;

and the response unit is used for responding to the first event concerned by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.

12. A computer-readable medium, on which a computer program is stored, the computer program comprising executable instructions that, when executed by a processor, carry out the method of any one of claims 1 to 10.

13. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is arranged to execute the executable instructions to implement the method of any one of claims 1 to 10.