Activity calendar reminder method and electronic device

Abstract

The present application provides a method and electronic device for event calendar reminder, the method comprising: displaying a first page of a target activity of a first application on an electronic device; displaying a first pop-up window in response to a user's confirmation operation on a first control indicating whether to participate in the target activity; starting a calendar application and creating a calendar reminder item in response to a user's confirmation operation on a second control in the first pop-up window indicating whether to create a calendar reminder; the calendar reminder item includes a reminder time corresponding to the target activity and a deep link to the first page; each time the reminder time is reached, in response to a user input confirmation operation to participate in the target activity again, starting the first application on the electronic device and reloading the first page based on the deep link. The scheme automatically writes parameters such as the deep link and the reminder time when creating a calendar reminder item, so that when the reminder time arrives, it can automatically jump to the first page based on this deep link.

Description

[0001] This application is a divisional application of the Chinese patent application submitted to the State Intellectual Property Office on October 17, 2023, with application number 202311341787.3 and application name "Method and electronic device for event calendar reminder". Technical Field

[0002] The present application relates to the technical field of electronic devices, and in particular to a method and electronic device for reminding an activity calendar. Background Art

[0003] As the use of calendar reminders becomes more and more widespread, new demands have emerged. That is, users hope to be able to open the corresponding application directly through the reminder pop-up window after seeing the reminder pop-up window, eliminating the tediousness of first exiting the calendar application, then finding the corresponding application and opening it. For example, a user creates a contact reminder: "On a certain day of a certain month of a certain year, I need to call Xiao A with a saved number." When the reminder time comes, the user can directly click on the prompt in the calendar reminder pop-up window, and the phone application will be started in the background, and the dialing page can be loaded, and Xiao A can even be added to the contact column. However, the items of this calendar reminder still need to be manually created by the user after manually opening the calendar application. Moreover, in this example, in order to automatically jump to the dialing page and fill in the contact as Xiao A, a simple keyword (text) extraction and filling method is adopted, which is not applicable to calendar reminders in other complex situations.

[0004] For various games, shopping and other applications, there are many marketing activities to increase interactivity, such as continuous sign-in, daily tasks, timed collection of vegetables, timed collection of energy, etc. The interactive pages of such marketing activities are provided by the merchants of the marketing activities. In order to attract consumers, they often have complex designs and gorgeous pictures. This leads to the need to rely on manually opening the calendar application and creating calendar reminders through simple keyword extraction and filling, and the created calendar items cannot realize the function of jumping to the corresponding interactive page.

[0005] Therefore, how to better provide calendar reminders for marketing activities is a technical problem that needs to be solved urgently. Summary of the invention

[0006] The present application provides a method and electronic device for event calendar reminder, which can better provide calendar reminders for marketing activities.

[0007] In a first aspect, a method for activity calendar reminder is provided, the method comprising: displaying a first page of a target activity of a first application on an electronic device; displaying a first pop-up window in response to a user's confirmation operation on a first control indicating whether to participate in the target activity; starting a calendar application and creating a calendar reminder item in response to a user's confirmation operation on a second control in the first pop-up window indicating whether to create a calendar reminder; the calendar reminder item includes a reminder time corresponding to the target activity and a deep link to the first page; each time the reminder time arrives, starting the first application on the electronic device in response to a confirmation operation input by the user to participate in the target activity again, and loading the first page again based on the deep link.

[0008] In the technical solution of this application, a deep link corresponding to the interactive page of the target activity is added when creating a calendar reminder, so that when the reminder time arrives, the interactive page can be directly loaded again based on this deep link, which simplifies the operation steps and improves the user experience. Since the parameters for creating a calendar do not require manual input by the user, and it can also automatically jump back to the activity page, the whole process is more user-friendly.

[0009] In combination with the first aspect, in certain implementations of the first aspect, in response to the user's second operation on the second control in the first pop-up window, when the calendar application is started and a calendar reminder is created, it may include: before creating the calendar reminder, receiving the first file from the H5 front-end server through the bridge (JSbridge), and obtaining the reminder time and deep link from the first file; when creating the calendar reminder, writing the deep link and the reminder time into the calendar reminder. In this implementation, a file containing the parameters required to create a calendar reminder is received from the H5 front-end server through the bridge, and the parameters are parsed and written into the calendar reminder. This execution process does not require manual participation by the user and is executed in the background, and the process does not need to be presented to the user.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the above-mentioned step of receiving the first file from the H5 front-end server through the bridge before creating the calendar reminder, and obtaining the reminder time and deep link from the first file, may include: under the triggering of the second operation, sending a data request to the H5 front-end server, and forwarding the data request to the marketing center server of the first application through the H5 front-end server; the data request includes the reminder time and deep link; the reminder time includes the start date and end date of the target activity date, and the start time and end time of each day in the target activity date; the data request also includes at least one of the following: an activity identifier (ID) and an identifier of whether to participate in the target activity; receiving the first file from the H5 front-end server through JSbridge, the first file is sent to the H5 front-end server by the marketing center server according to the data request after receiving the data request; the first file includes the target data corresponding to the data request, the target data includes the reminder time and deep link, and the target data also includes the activity ID and / or an identifier of whether to participate in the target activity. In this implementation, a specific process of taking data from the server is given.

[0011] For security reasons, if a third-party application wants to read and write the internal space of an electronic device, it needs to be granted access rights. Therefore, for the first application, if it wants to read and write data to the calendar application (the electronic device's own application, that is, a non-third-party application), it also needs authorization from the calendar application. Therefore, when the first application creates a calendar reminder for the first time, it can obtain the read and write permissions of the calendar application before creating it. For subsequent creations, such as other activities of the first application, or the user unsubscribing from the target activity and then re-participating in the target activity, there is no need to apply for read and write permissions.

[0012] In conjunction with the first aspect, in certain implementations of the first aspect, in response to the user's second operation on the second control in the first pop-up window, starting the calendar application and creating a calendar reminder item may include: obtaining the read and write permissions of the calendar application; after obtaining the read and write permissions of the calendar application and receiving the first file, starting the calendar application and creating the calendar reminder item. This implementation is mainly aimed at when the first application needs to access the calendar application for the first time, it is necessary to first obtain the read and write permissions of the calendar application and then create it, while for non-first access, this step of obtaining read and write permissions does not need to be performed.

[0013] In one example, when obtaining the read and write permissions of a calendar application, the following may be included: displaying a second pop-up window on the screen of the electronic device, wherein the second pop-up window includes a confirmation authorization control for authorizing the read and write permissions of the calendar application; and obtaining the read and write permissions of the calendar application in response to a user clicking on the confirmation authorization control. This example provides an example of the authorization method, where the read and write permissions of the calendar application are granted to the first application only if the user confirms and agrees to the authorization operation, otherwise they are not granted.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the above-mentioned step of starting the first application on the electronic device and reloading the first page based on the deep link in response to the user input confirmation operation of participating in the target activity again each time the reminder time is reached may include: displaying a third pop-up window on the electronic device each time the reminder time is reached, the third pop-up window is used to remind the user whether to participate in the target activity again; in response to the user's click operation on the third pop-up window, starting the first application, and loading the first page based on the deep link for display, and the click operation on the third pop-up window is the confirmation operation of participating in the target activity again. In this implementation, the user only needs to click the pop-up window once to jump to the first page, and the operation steps are few.

[0015] In another implementation, the above-mentioned step of starting the first application on the electronic device and reloading the first page based on the deep link each time the reminder time is reached in response to the user input confirmation operation of participating in the target activity again, may include: displaying a fourth pop-up window on the electronic device each time the reminder time is reached, the fourth pop-up window is used to remind the user whether to participate in the target activity again; in response to the user's click operation on the fourth pop-up window, starting the calendar application and displaying the calendar reminder; in response to the user's click operation on the deep link in the calendar reminder, starting the first application and loading the first page for display, and the combination of the click operation on the fourth pop-up window and the click operation on the deep link is the confirmation operation of participating in the target activity again. In this implementation, the step of first presenting the calendar reminder to the user is added, and it requires two clicks to jump.

[0016] In one implementation, each time the reminder time is reached, in response to the user input confirmation operation of participating in the target activity again, the first application is started on the electronic device, and the first page is loaded again based on the deep link, which may include: detecting whether the first application is installed in the electronic device; when it is detected that the first application is installed, the first application is started, and the first page is jumped to based on the deep link; or, when it is detected that the first application is not installed, a fifth pop-up window is displayed, and the fifth pop-up window is used to indicate whether the user has installed the first application. In this implementation, a judgment on whether the first application is installed is added. This judgment can prevent the user from uninstalling the first application midway, resulting in a jump failure, and the user only sees the jump failure but does not know that the reason for the failure is that the application has been uninstalled.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to a third operation of the user on the first control, not displaying the first pop-up window, the third operation being used to indicate not participating in the target activity. This is a fallback solution, that is, you can still unsubscribe after you have subscribed, but it should be understood that if you do not subscribe from the beginning, there will be no third operation, because the system will default to the initial state of not participating in the target activity, so this implementation will only occur when you want to unsubscribe after subscribing.

[0018] In combination with the first aspect, in some implementations of the first aspect, the method further includes: in response to a fourth operation of the user on the second control, not starting the calendar application, the fourth operation being used to indicate not to create a calendar reminder. That is, after the first pop-up window is displayed, the second control (whether to create a calendar reminder) appears, at which time the user can choose whether to create it according to his or her own considerations, and if he or she chooses not to create it, there is no need to execute the subsequent process.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the second pop-up window further includes a cancel authorization control that does not allow authorization of the read and write permissions of the calendar application, and the above method further includes: in response to the user clicking the cancel authorization control, canceling the acquisition of the read and write permissions of the calendar application. In other words, if the user sees that the first application is still required to read and write the calendar application of the electronic device during this process, and is afraid of bringing security risks, and wants to terminate the creation, it can be executed based on the cancel operation.

[0020] In a second aspect, a device for executing an activity calendar reminder is provided, the device comprising a unit composed of software and / or hardware for executing any one of the methods of the first aspect.

[0021] In a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the electronic device is enabled to implement any one of the methods of the first aspect.

[0022] In a fourth aspect, a chip is provided, comprising a processor, wherein the processor is used to read and execute a computer program stored in a memory, and when the computer program is executed by the processor, the electronic device in which the chip is located can implement any one of the methods of the first aspect.

[0023] Optionally, the chip also includes a memory, and the memory is electrically connected to the processor.

[0024] Optionally, the chip may also include a communication interface.

[0025] According to a fifth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by an electronic device, any one of the methods according to the first aspect can be implemented.

[0026] In a sixth aspect, a computer program product is provided, which includes a computer program, and when the computer program is executed by an electronic device, it can implement any one of the methods of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is a schematic diagram of the data interaction process of the H5 section in the hybrid app.

[0028] Figure 2 It is a system interaction diagram of the activity calendar reminder method of an embodiment of the present application.

[0029] Figure 3 It is a schematic flow chart of a method for event calendar reminder according to an embodiment of the present application.

[0030] Figure 4 It is a schematic diagram of the execution process of a method for activity calendar reminder in an embodiment of the present application.

[0031] Figure 5 It is a schematic diagram of the execution process of a game app loading an H5 activity page.

[0032] Figure 6 It is a schematic flow chart of a method for event calendar reminder according to an embodiment of the present application.

[0033] Figure 7 It is a schematic diagram of an execution process of entering an activity page through a calendar reminder according to an embodiment of the present application.

[0034] Figure 8It is a schematic diagram of the execution process of an activity calendar reminder in an embodiment of the present application.

[0035] Fig. 9 This is a result diagram of a created calendar reminder according to an embodiment of the present application.

[0036] Fig.10 It is a schematic diagram of an activity calendar reminder device according to an embodiment of the present application.

[0037] Fig.11 It is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The scheme of the embodiment of the present application is introduced below with reference to the accompanying drawings.

[0039] Figure 1 This is a schematic diagram of the data interaction process of the H5 section in the hybrid app. Figure 1 As shown, a hybrid application (hybrid application, hybrid app) is running in electronic device A, and the page displayed is an interactive page of a marketing activity. Here, App-1 is running, and the marketing activity being displayed is an activity page for seven consecutive days of sign-in. Electronic device A can be a terminal device such as a mobile phone, tablet computer, laptop computer, etc. Server B is a fifth-generation hypertext markup language (abbreviated as H5) front-end server, that is, an H5 front-end server. Server C is a marketing center server.

[0040] When the hybrid app is running, the hybrid app can send requests to server B, such as a request to load H5, and receive requests for files such as web page (html) files, cascading style sheets (CSS) files, and scripting language (javascript, JS) files.

[0041] Server B will receive, forward, and store the above requests and files that can be requested, and can also receive, forward, and store bridge (JSbridge) files. For example, the request received from electronic device C can be forwarded to the marketing center server, and the file requested by electronic device C from the marketing center server can be forwarded to electronic device C.

[0042] Server C will maintain the data of all hybridapps. For H5, it will receive the POST request initiated by server B and return the basic data of the H5 activity. The returned data can be sent in JSON format.

[0043] For the solution of the embodiment of the present application, electronic device C will receive the file from server C from server B, and parse the deep link and other basic data of the H5 activity, such as the activity period, activity time period, etc., to write into the calendar application, thereby creating a calendar reminder in the calendar application that can automatically jump back to the H5 activity page. Figure 2 Provide a detailed introduction.

[0044] Figure 2 1 is a system interaction diagram of the method for event calendar reminder in the embodiment of the present application. Figure 2 As shown, after the game center app (an example of the first application below, it can also be other applications, such as shopping applications, reading applications, audiobook applications, etc.) on the electronic device A is running, the JSbridge.js file will be reserved on the activity page. This file will store activity-related parameters, including the interactive name or activity identifier (ID), whether the activity is involved (activity switch status), the start date and end date of the activity, the start time and end time of each day during the activity, and the deeplink of this page. When the game center app sends these files in HTML / CSS / JS format to the H5 front-end server to request H5 activity-related data, it can carry the above-mentioned request for data related to creating a calendar reminder (or understood as data required to create a calendar reminder). After receiving the data request sent by the game center app, the H5 front-end server will forward the data request to the marketing center server. After receiving the data request, the marketing center server returns the basic data of the H5 activity. The marketing center server sends a file in JSON format to the H5 front-end server, which carries the basic data of the H5 activity. The H5 front-end server can convert the basic data of the H5 activity into a file in HTML / CSS / JS format and then return it to the game center app.

[0045] When creating calendar events, the Game Center app obtains the read and write authorization of the Calendar app, and then writes the event name, start and end dates, daily event start and end times, deeplink, and other descriptions into the Calendar app. The Calendar app creates reminders based on the data written.

[0046] In the reminder stage, the calendar app displays a reminder pop-up window when it detects that the reminder time has arrived. When the user clicks the deeplink through the reminder pop-up window, the game center app can be launched and directly jump to the H5 activity page in the game center app.

[0047] It should be noted that the game center app and the calendar app are both apps in the same electronic device (electronic device A is used as an example here), so the data interaction between them is implemented within the device, not across devices.

[0048] Figure 3 1 is a schematic flow chart of a method for event calendar reminder in an embodiment of the present application. Figure 3 Each step is described below.

[0049] S301: Run a first application on an electronic device and display a first page of the first application, where the first page is an interactive page of a target activity.

[0050] In the embodiment of the present application, the first application is an application that supports H5 technology.

[0051] It should also be understood that hybrid apps are developed by combining the development technology of ordinary apps with H5 technology. To a certain extent, hybrid apps can be considered as apps that also integrate H5 applets, and H5 applets are the carriers of marketing activities (the target activities here).

[0052] In some implementations, the first application may be a hybrid app, and the first page may be an H5 page.

[0053] S302: In response to a first operation of a user on a first control in a first page, display a first pop-up window.

[0054] The first control is used to indicate whether to participate in the target activity, the first operation is used to indicate participation in the target activity, and the first pop-up window includes a second control for indicating whether to create a calendar reminder.

[0055] The first operation is to confirm participation in the target activity, that is, to subscribe to notification reminders. The third operation of the first control below is to not participate in the target activity, that is, not subscribe to notification reminders. In practice, two controls can also be provided, corresponding to participation and non-participation respectively, but in comparison, it is more common to use the floating ball to select and unselect, so it is more in line with user operation habits.

[0056] In one implementation, the method further includes: in response to a third operation of the user on the first control, not displaying the first pop-up window, the third operation being used to indicate not participating in the target activity. This is a fallback solution, that is, you can still unsubscribe after you have subscribed, but it should be understood that if you do not subscribe from the beginning, there will be no third operation, because the system will default to the initial state of not participating in the target activity, so this implementation will only occur when you want to unsubscribe after subscribing.

[0057] S303: In response to a second operation of the user on the second control in the first pop-up window, start a calendar application and create a calendar reminder.

[0058] The calendar reminder includes the reminder time corresponding to the target activity and a deep link (deeplink) to the first page; the second operation is used to indicate the creation of a calendar reminder.

[0059] The time in the reminder time is a natural time, which can be a moment or a time interval, for example, date + clock time.

[0060] It should be understood that in the embodiment of the present application, the calendar application is automatically started when triggered by the second operation, and the user does not need to manually start the calendar application. In the process of creating calendar reminders, no manual input from the user is required, and the parameters in the calendar reminders are directly obtained, for example, from the marketing center server through the H5 front-end server, and no manual input is required.

[0061] In one implementation, the above step S303 may include: before creating a calendar reminder, receiving a first file from an H5 front-end server through a bridge (JSbridge), and obtaining a reminder time and a deep link from the first file; when creating a calendar reminder, writing the deep link and the reminder time into the calendar reminder. In this implementation, a file containing parameters required to create a calendar reminder is received from an H5 front-end server through a bridge, and the parameters are parsed and written into the calendar reminder. This execution process does not involve manual user participation and is executed in the background, and the process does not need to be presented to the user.

[0062] In one implementation, the above-mentioned step of receiving the first file from the H5 front-end server through the bridge JSbridge before creating the calendar reminder, and obtaining the reminder time and deep link from the first file, may include: under the triggering of the second operation, sending a data request to the H5 front-end server, and forwarding the data request to the marketing center server of the first application through the H5 front-end server; the data request includes the reminder time and deep link; the reminder time includes the start date and end date of the target activity date, and the start time and end time of each day in the target activity date; the data request also includes at least one of the following: activity identification (ID) and whether to participate in the target activity; receiving the first file from the H5 front-end server through JSbridge, the first file is sent to the H5 front-end server by the marketing center server according to the data request after receiving the data request; the first file includes the target data corresponding to the data request, the target data includes the reminder time and deep link, and the target data also includes the activity ID and / or the identification of whether to participate in the target activity. In this implementation, the specific process of getting data from the server is given.

[0063] For security reasons, if a third-party application wants to read and write the internal space of an electronic device, it needs to be granted access rights. Therefore, for the first application, if it wants to read and write data to the calendar application (the electronic device's own application, that is, a non-third-party application), it also needs authorization from the calendar application. Therefore, when the first application creates a calendar reminder for the first time, it can obtain the read and write permissions of the calendar application before creating it. For subsequent creations, such as other activities of the first application, or the user unsubscribing from the target activity and then re-participating in the target activity, there is no need to apply for read and write permissions.

[0064] In one implementation, step S303 may include: obtaining the read and write permissions of the calendar application; after obtaining the read and write permissions of the calendar application and receiving the first file, starting the calendar application and creating a calendar reminder. This implementation is mainly for when the first application needs to access the calendar application for the first time, it is necessary to first obtain the read and write permissions of the calendar application and then create it, while for non-first access, it is not necessary to perform the step of obtaining the read and write permissions.

[0065] In one example, when obtaining the read and write permissions of a calendar application, the following may be included: displaying a second pop-up window on the screen of the electronic device, wherein the second pop-up window includes a confirmation authorization control for authorizing the read and write permissions of the calendar application; and obtaining the read and write permissions of the calendar application in response to a user clicking on the confirmation authorization control. This example provides an example of the authorization method, where the read and write permissions of the calendar application are granted to the first application only if the user confirms and agrees to the authorization operation, otherwise they are not granted.

[0066] In another example, the second pop-up window also includes a cancel authorization control that does not allow the authorization of the read and write permissions of the calendar application, and the above method also includes: in response to the user clicking the cancel authorization control, canceling the acquisition of the read and write permissions of the calendar application. In other words, assuming that the user sees that the first application is still required to read and write the calendar application of the electronic device during this process, and is afraid of security risks, and wants to terminate the creation, it can be executed based on the cancel operation. In other words, assuming that the user sees that the first application is still required to read and write the calendar application of the electronic device during this process, and is afraid of security risks, and wants to terminate the creation, it can be executed based on the cancel operation.

[0067] It should be noted that a control can reuse two states, on and off, corresponding to two functions respectively, such as the first control. This is because the first control is not selected, that is, the closed state can exist as a default state. However, when it comes to authorizing permissions, the user has a clear intention to allow or not allow. In order to prevent misoperation, it is generally set that the selection of each of the two controls corresponds to a selection. In the above example, the two controls of "Allow" and "Do not allow" are used to correspond to the two options of confirming authorization and canceling authorization respectively. However, it should be understood that in practice, the two controls of "Confirm" and "Cancel" can also be used to correspond to authorization and non-authorization respectively. It's just that the two controls of "Allow" and "Do not allow" are currently the most used on electronic devices, so this setting that is more in line with the user's historical cognition can be adopted.

[0068] In one implementation, the method further includes: in response to a fourth operation of the user on the second control, not starting the calendar application, the fourth operation being used to indicate not to create a calendar reminder. That is, after step S302 is executed, the second control (whether to create a calendar reminder) appears, at which time the user can choose whether to create it according to his or her own considerations, and if he or she chooses not to create it, there is no need to execute the subsequent process.

[0069] It should be understood that the second operation and the fourth operation of the second control correspond to creation and non-creation, respectively, that is, the switch state of the control corresponds to two options. In practice, two second controls can also be used to implement it, so the second operation and the fourth operation can both be click operations, when clicking the second control corresponding to creation, it is creation, and when clicking the second control corresponding to non-creation, it is non-creation.

[0070] In another implementation, the second operation is a click operation, the second operation on the second control is a click operation on the second control, the click operation on the second control is used to indicate the creation of a calendar reminder, and the above method further includes: in response to the user's click operation on the third control in the first pop-up window, not creating a calendar reminder. That is, the click operation on the third control is used to indicate not creating a calendar reminder.

[0071] In one example, the second control is "confirm" and the third control is "cancel". In another example, the second control is "create" and the third control is "do not create". Other cases are not listed one by one.

[0072] S304. Each time the reminder time is reached, in response to a confirmation operation input by the user to participate in the target activity again, the first application is started on the electronic device, and the first page is loaded again based on the deep link.

[0073] That is to say, each time the reminder time is reached, the user can be instructed whether to participate again. If the user performs operations related to re-participation, the user can automatically jump to the first page of the first application. If the user does not want to participate again, the jump will not be triggered.

[0074] In one implementation, the above step S304 may include: displaying a third pop-up window on the electronic device each time the reminder time is reached, the third pop-up window is used to remind the user whether to participate in the target activity again; in response to the user clicking the third pop-up window, starting the first application, and loading the first page based on the deep link for display, and the clicking operation on the third pop-up window is a confirmation operation to participate in the target activity again. In this implementation, the user only needs to click the pop-up window once to jump to the first page, and the operation steps are few.

[0075] In another implementation, the above step S304 may include: displaying a fourth pop-up window on the electronic device each time the reminder time is reached, the fourth pop-up window is used to remind the user whether to participate in the target activity again; in response to the user's click operation on the fourth pop-up window, starting the calendar application and displaying the calendar reminder; in response to the user's click operation on the deep link in the calendar reminder, starting the first application and loading the first page for display, and the combination of the click operation on the fourth pop-up window and the click operation on the deep link is the confirmation operation of participating in the target activity again. In this implementation, the step of presenting the calendar reminder to the user first is added, and it takes two clicks to jump.

[0076] In one implementation, the above step S304 may include: detecting whether the first application is installed in the electronic device; when it is detected that the first application is installed, starting the first application and jumping to the first page based on the deep link; or, when it is detected that the first application is not installed, displaying a fifth pop-up window, the fifth pop-up window is used to indicate whether the user has installed the first application. In this implementation, a judgment on whether the first application is installed is added, and this judgment can prevent the user from uninstalling the first application midway, resulting in a jump failure, and the user only sees the jump failure but does not know that the failure is caused by the application being uninstalled.

[0077] exist Figure 3 In the solution shown, a deep link corresponding to the interactive page of the target activity is added when creating a calendar reminder, so that when the reminder time arrives, the interactive page can be directly loaded again based on this deep link, which simplifies the operation steps and improves the user experience. This solution does not require users to manually enter the parameters for creating a calendar, and can also automatically jump back to the activity page, making the entire process more user-friendly.

[0078] It should be noted that in the embodiment of the present application, the first application is an application that supports H5 technology. Only in the H5 scenario is it possible to obtain a deep link. For applications that are not based on H5 technology and cannot obtain a deep link, it is impossible to use the method of the embodiment of the present application to create a calendar reminder that can automatically jump. It can be considered that H5 has given marketing activities a new carrier form.

[0079] Taking the Game Center app (an example of the first application) as an example, in the traditional solution, in order to prevent users from missing a certain marketing H5 activity of the Game Center app, users need to actively create a calendar reminder in the Calendar app, manually enter the time of the activity reminder and the content of the participation in the Calendar app, and when the calendar reminder time arrives, they also need to find the Game Center app, click to open it, then find the H5 activity page and then enter the target activity page.

[0080] However, by utilizing the solution of the embodiment of the present application, the user only needs to operate the control twice to create a calendar reminder, and when the reminder time comes, the user can directly jump to the H5 activity page based on the deep link, without having to start the game center app first, and then search and operate the game center app multiple times to find the activity page.

[0081] For traditional third-party applications, that is, third-party applications developed based on Android native, although it is possible to consider directly integrating the function of automatically creating calendar reminders in them, this function can only be implanted at the beginning of development, that is, it needs to be added synchronously with the development of the third-party application. Moreover, once the version of the third-party application is updated, the function also needs to be updated synchronously by the application manufacturer during the development process, which brings high R&D costs to the third-party application manufacturers and prolongs the time of version update. Most importantly, if there are many marketing activities, each marketing activity must be designed with an independent automatic calendar reminder function. Moreover, when the marketing activities increase or decrease, the third-party application cannot be updated synchronously and has to be re-released, which will increase the cost. Therefore, no manufacturer adopts this method, which also makes it impossible for third-party applications developed purely based on Android native to automatically jump to the target page. In the scheme of the embodiment of the present application, it is based on the emergence of hybridapp, and most marketing activities use H5 technology as a carrier to facilitate iterative updates. Based on this premise, how to realize the calendar reminder that automatically jumps to the target page is reconsidered, and finally it is thought that the calendar reminder can be created by taking the required data of deeplink from the server, realizing a better calendar reminder scheme. In addition, for the above possible hypothetical solution, that is, the solution of directly integrating the function of creating a calendar reminder for each marketing activity in the application, from the perspective of the user using the electronic device, the user cannot independently choose which activity in which application to create a calendar reminder, and can only passively choose to accept or refuse to create for individual third-party applications that have the function of automatically creating calendar reminders, and still cannot jump to the target page. At most, the target application can only be automatically started, which is difficult to meet user expectations. In contrast, the solution of the embodiment of the present application is based on H5 activities, which can automatically jump to the target page, and even if the version of the application is updated, the calendar reminder of this H5 activity is still valid, and it will not be unable to jump to the corresponding page because of the version update, which is more flexible. In addition, the solution of the present application is a solution that is universal for all H5 activities, and its universality is relatively higher.

[0082] Figure 4 It is a schematic diagram of the execution process of a method for activity calendar reminder in an embodiment of the present application. Figure 4 The continuous check-in activity in the game app is taken as an example, but it should be understood that in practice other marketing activities can be used as the target activities of this application, such as timed collection of vegetables, timed collection of energy, daily tasks, etc. The first application can also be other applications such as shopping, chatting, reading, etc., without limitation.

[0083] S401, H5 is loaded in the terminal, H5 creates a DOM node and mounts JSbridge to the DOM node.

[0084] Loading H5 on the end means loading it on an electronic device. Creating a node is also an operation on an electronic device. Creating a node is for the execution of subsequent steps and the use of JSbridge.

[0085] It should also be understood that before the user clicks the calendar reminder switch, there is also an operation to start and run the game app, and the user finds the H5 activity page of the marketing activity in the game app. The game app will request the HTML / CSS / JS files of the H5 activity page from the H5 front-end server, and the game app will render the H5 page. The page loading process is as follows Figure 5 shown.

[0086] Figure 5 It is a schematic diagram of the execution process of a game app loading an H5 activity page.

[0087] S501. The game app sends a request to the H5 front-end server to request the resource file of the H5 activity.

[0088] S502, initialize the browser (init webview).

[0089] S503, the JSbridge injection method of webview reads the field and provides it to H5 for calling.

[0090] Reading fields can be achieved using the readSchedule() function.

[0091] S504, HTML / CSS / JS page rendering.

[0092] S505, H5 requests the marketing center server for the basic data required for the activity.

[0093] The request here can be implemented by a getPOST request, and the basic data includes elements such as pictures and text.

[0094] S506, page loading is completed.

[0095] It should be understood that Figure 5 This is a schematic diagram of the loading process of the H5 activity page. The solution of this application does not change this execution process, but only adds requests for reminder time and deeplink, which are data required for creating a calendar, when requesting data, so as to achieve the purpose of creating a better calendar reminder. It is an easy-to-implement solution that will not affect other processes.

[0096] S402: The user clicks the calendar reminder switch.

[0097] Here, it means that the electronic device collects the user's operation through the sensor device, which may be that the user clicks the control corresponding to the calendar reminder switch on the touch screen of the electronic device, and then the electronic device collects the click operation on the control.

[0098] S403, H5 page pop-up window prompts "Do you want to enable the daily sign-in activity calendar notification reminder in the game center?"

[0099] It should be understood that the pop-up window here is drawn by H5 itself, not by the local system of the electronic device. The pop-up window here can be regarded as an example of the first pop-up window. The control corresponding to "Whether to turn on the game center daily sign-in activity calendar notification reminder" is an example of the first control.

[0100] When the reminder is given for the first time, a pop-up window will be displayed requesting the user to authorize access to the Calendar app. Allowing access here means allowing reading and writing to the Calendar app.

[0101] S404, H5 requests the marketing server for the activity reminder fields, activity ID, activity time, current activity switch status, and deeplink.

[0102] After the user clicks the confirmation control in the pop-up window of the H5 page, H5 will request the marketing service end (marketing server) for the data required to create a calendar reminder. The request is forwarded through the H5 front-end server.

[0103] It can be seen that here can be followed by Figure 5 The execution of the request of step S505 in the process shown is performed together, which is equivalent to requesting the data required for creating a calendar reminder when requesting the basic data. However, it should be understood that the two requests can also be sent separately, which will not affect the execution effect of the present application solution.

[0104] S405 and H5 use the JSsbridge bridging method to pass the fields of the activity reminder, activity ID, activity time, current activity switch status, and deeplink requested from the marketing server to the game app side.

[0105] After the data is requested, the readSchedule() method injected into Jssbridge will be called through H5, and the fields requested by S404 will be passed to readSchedule.

[0106] S406. The game app uses the received fields to read and write to the calendar app, and after the writing is successful, the switch status is called back to H5.

[0107] After obtaining the fields stored in readSchedule in step S405, the game app applies for read and write permissions from the calendar app.

[0108] Applying for read and write permissions can be expressed as:

[0109] <uses-permission android:name="android.permission.READ_CALENDAR" / >

[0110] <uses-permission android:name="android.permission.WRITE_CALENDAR" / >

[0111] After the user clicks the permission pop-up window for read and write authorization of the calendar app, they can obtain read and write permissions by clicking the confirmation control.

[0112] After that, the game app will use the newly added CalendarScheduleHelper schedule writing helper class to write the event field to the calendar app.

[0113] Afterwards, the game app calls back H5 through the readSchedule method to indicate that the calendar has been written successfully, and also calls back the switch status to H5.

[0114] S407. After receiving the switch status, H5 grays out the switch button and displays a toast prompt "Calendar reminder subscription successful".

[0115] The toast prompt will disappear after the preset time, which can let users know the message without occupying display resources for too long.

[0116] S408: The user clicks on the calendar schedule link to jump to the calendar reminder page of the H5 activity.

[0117] When the reminder time arrives, for example, a certain time period, such as 9:00-10:00 in the morning, the electronic device notification bar reminds the user to participate in the event. The notification bar here is an example of the fourth pop-up window. The user clicks the notification bar to enter the schedule page. In other words, clicking the calendar schedule link is an example of a confirmation operation to participate in the target activity again.

[0118] S409: The user clicks on the calendar schedule https link transfer link and jumps to the calendar transfer page of the H5 activity.

[0119] The https link transfer link is the above-mentioned deeplink link.

[0120] S410, H5 loads the H5 activity page according to the instruction of the activity transfer page.

[0121] Can be Figure 5 The process shown is loaded.

[0122] S411. Enter the H5 activity page on the terminal.

[0123] That is to display the H5 activity page on the electronic device.

[0124] Figure 6 It is a schematic flow chart of a method for event calendar reminder according to an embodiment of the present application. Figure 6 This can be considered as an example of steps S302 - S304 .

[0125] S601. The user clicks the calendar reminder switch on the H5 activity page of the first application.

[0126] The calendar reminder switch is an example of the first control, which indicates whether there is a need to create a calendar reminder.

[0127] S602, H5 pop-up window reminds the user whether to confirm that the calendar reminder notification needs to be turned on.

[0128] The confirmation here is after the user confirms to participate in the activity and knows that there is a reminder requirement, to confirm that the user really wants to create a calendar reminder. The pop-up window here is an example of the first pop-up window.

[0129] When the first pop-up window appears for the first time, you can also request authorization for the read and write permissions of the calendar app. In this way, when other H5 activities in this game app need to be reminded later and the first pop-up window appears again, there is no need to repeat the authorization.

[0130] S603. The user will be reminded by the notification bar of the calendar during the specified time period every day.

[0131] The notification bar here is an example of the second pop-up window.

[0132] S604: The user clicks the deep link in the calendar reminder to jump to the H5 activity page of the first application.

[0133] Figure 7 It is a schematic diagram of an execution process of entering an activity page through a calendar reminder according to an embodiment of the present application. Figure 7 This can be regarded as an example of step S304.

[0134] S701. The user clicks a deeplink in a calendar reminder.

[0135] S702: Jump to the calendar transfer page.

[0136] S703, in the calendar page, determine whether the app corresponding to deeplink has been installed on the electronic device. When the judgment result is yes, proceed to step S704; when the judgment result is no, proceed to step S705.

[0137] S704, jump to the H5 activity page of the corresponding app.

[0138] S705: Prompt the user to install the corresponding app in the calendar transfer page.

[0139] Figure 8 It is a schematic diagram of the execution process of an activity calendar reminder in an embodiment of the present application. Figure 8 It can be seen as Figure 3 An example of the method shown.

[0140] like Figure 8 As shown, interface 801 is a display of an H5 activity page (an example of the first page) of an app. Here, the sign-in activity is taken as an example. Interface 801 includes the display of the sign-in result and the control A (an example of the first control) indicating whether to subscribe to the activity "Sign-in reminder subscription notification". Assuming that the user clicks control A in interface 801, a pop-up window B (an example of the first pop-up window) will appear, indicating whether the user turns on the reminder in pop-up window B, as shown in interface 802. Assuming that the user clicks the "Cancel" control in interface 802, it means not to create a calendar reminder, end the process, and continue to display the state shown in interface 801. Assuming that the user clicks the "Confirm" control in interface 802, it means to create a calendar reminder and continue the process. If it is not the first time to subscribe to an activity on this app (including subscribing to other H5 activities), it will jump directly to interface 804, where the user is told that the subscription is successful in a light prompt. In the interface 804, the control A of "Sign-in Reminder Subscription Notification" is selected, and the calendar reminder item has been created, but it should be understood that this series of processes are automatically completed by the system background and no user operation is required.

[0141] Assuming that the "Confirm" control is clicked in interface 802, it means that a calendar reminder is to be created. Then the system detects that this is the first time to subscribe to an activity on this app, then it is necessary to obtain authorization for the read and write permissions of the calendar application in order to achieve the result of automatically creating calendar reminders. At this time, it will first jump to interface 803, which includes a pop-up window (an example of the second pop-up window) indicating whether the user allows access to the calendar app. Assuming that the user clicks "Allow" (an example of confirming the authorization control) in interface 803, the read and write permissions can be obtained, then the system background continues to execute the relevant steps of the application scheme, and then the prompt of successful creation shown in interface 804 is obtained. Assuming that the user clicks "Do not allow" (an example of unauthorized control) in interface 803, the read and write permissions can be obtained, then the process ends, the creation is canceled, and the prompt of canceling the creation shown in interface 805 is obtained. In interface 805, control A does not change its state.

[0142] It should be understood that in the solution of the embodiment of the present application, starting the calendar application and creating calendar reminders are all completed automatically in the background, and the user does not need to manually enter any parameters. Reminder time, reminders, deeplink, these are all data obtained directly from the server, and no manual user participation is required. If it is not the first subscription, the user only needs two clicks, that is, clicking on control A in interface 801 and clicking on the "Confirm" control in interface 802. After that, no manual input is required until the calendar reminder is created.

[0143] After creation, if the user wants to see the details, he can click the calendar application icon to start the calendar application and then view the creation results. However, if the user does not want to see the details, there is no need to verify.

[0144] After creation, when the reminder time comes every day, a calendar notification bar (an example of the third pop-up window or the fourth pop-up window) will be displayed, as shown in interface 806. Interface 806 includes a calendar notification bar to prompt the user whether to participate in this H5 activity again.

[0145] In one case, if the user clicks on the main content of the notification bar in interface 806, it means that the user needs to participate in the event, and can directly jump to the situation shown in interface 808, where the H5 event page of the app is directly displayed. In this case, the calendar notification bar is an example of the third pop-up window. Clicking the pop-up window can jump directly.

[0146] In another case, assuming that the user clicks on the main content part of the notification bar in interface 806, the page of the calendar reminder in the calendar application will be opened, that is, the transfer page of this H5 activity, as shown in interface 807. When the user clicks on the deeplink in interface 807, it will jump to the situation shown in interface 808. This method adds a calendar transfer page, that is, the interface shown in interface 807, and the user will jump only when he further clicks on the link in the transfer page.

[0147] The calendar notification bar in interface 806 may also include controls for selecting cancel reminders, etc., so that users can operate as desired without opening the application.

[0148] After creating the calendar reminder in interface 804, if the user wants to see the creation result, he can open the calendar application and see Fig. 9 The situation shown. Fig. 9 Schematic diagram of the result of creating a calendar reminder item in the embodiment of the present application. Fig. 9 As shown, the calendar items are already included in interface 810. If the user clicks on the calendar item in interface 810, the situation shown in interface 811 can be seen. Interface 811 includes parameters such as the activity name, time interval, reminder date, and deeplink, and these parameters are requested by the electronic device from the server, and do not require manual input by the user, simplifying tedious operations. However, it should be understood that interface 810 and interface 811 do not need to be displayed. It is the user's own choice whether to view them after the creation is completed. The process of executing interface 810 and interface 811 does not need to be executed during the creation process.

[0149] The above mainly introduces the method of the embodiment of the present application in conjunction with the accompanying drawings. It should be understood that although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence, these steps are not necessarily performed in sequence in the order shown in the figure. Unless clearly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the various embodiments described above may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a part of the steps or stages in other steps. The device of the embodiment of the present application is introduced below in conjunction with the accompanying drawings.

[0150] Fig.10 Schematic diagram of an activity calendar reminder device according to an embodiment of the present application. Fig.10As shown, the device 2000 includes a processing unit 2001 and a creating unit 2002. The device 2000 may be integrated in an electronic device such as a mobile phone, a tablet computer, or a notebook computer.

[0151] The device 2000 can be used to execute any of the above methods for event calendar reminder. For example, the processing unit 2001 can be used to execute steps S301, S302 and S304, and the creation unit 2002 can be used to execute step S303. For another example, the device 2000 can also be used to execute Figures 5 to 7 The device 2000 can also be used to perform Figure 3 The steps performed by the electronic device A in the embodiment of the present invention, that is, the device 2000 may be integrated in Figure 3 The device 2000 can also be used to perform Figure 4 The device 2000 can also be used to perform the steps performed by H5, game app and calendar app, as well as receive user operations and respond. Figure 8 and Fig. 9 The process shown.

[0152] In one implementation, the apparatus 2000 may further include a storage unit for storing relevant data. The storage unit may be integrated in any one of the above units, or may be a unit independent of all the above units.

[0153] Fig.11 Schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. Fig.11 As shown, the electronic device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, an earphone interface 970D, a sensor module 980, a button 990, a motor 991, an indicator 992, a camera 993, a display screen 994, and a subscriber identification module (SIM) card interface 995, etc. Among them, the sensor module 980 may include a pressure sensor 980A, a gyroscope sensor 980B, an air pressure sensor 980C, a magnetic sensor 980D, an acceleration sensor 980E, a distance sensor 980F, a proximity light sensor 980G, a fingerprint sensor 980H, a temperature sensor 980J, a touch sensor 980K, an ambient light sensor 980L, a bone conduction sensor 980M, etc.

[0154] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 900. In other embodiments of the present application, the electronic device 900 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0155] For example, Fig.11 The processor 910 shown may include one or more processing units, for example, the processor 910 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0156] The controller may be the nerve center and command center of the electronic device 900. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0157] The processor 910 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 910 is a cache memory. The memory may store instructions or data that the processor 910 has just used or cyclically used. If the processor 910 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 910, and thus improves the efficiency of the system.

[0158] In some embodiments, the MIPI interface can be used to connect the processor 910 with peripheral devices such as the display screen 994 and the camera 993. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. The processor 910 and the display screen 994 communicate through the DSI interface to realize the display function of the electronic device 900.

[0159] In some embodiments, the GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. The GPIO interface can be used to connect the processor 910 with the camera 993, the display screen 994, the wireless communication module 960, the audio module 970, the sensor module 980, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0160] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 900. In other embodiments of the present application, the electronic device 900 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0161] The electronic device 900 implements the display function through a GPU, a display screen 994, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 994 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 910 may include one or more GPUs, which execute program instructions to generate or change display information.

[0162] The display screen 994 is used to display images, videos, etc. The display screen 994 includes a display panel. In some embodiments, the electronic device 900 may include 1 or N display screens 994, where N is a positive integer greater than 1.

[0163] The internal memory 921 can be used to store computer executable program codes, which include instructions. The processor 910 executes various functional applications and data processing of the electronic device 900 by running the instructions stored in the internal memory 921. The internal memory 921 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 900 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 921 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0164] The pressure sensor 980A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 980A can be set on the display screen 994. There are many types of pressure sensors 980A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 980A, the capacitance between the electrodes changes. The electronic device 900 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 994, the electronic device 900 detects the touch operation intensity according to the pressure sensor 980A. The electronic device 900 can also calculate the touch position according to the detection signal of the pressure sensor 980A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0165] The touch sensor 980K is also called a "touch panel". The touch sensor 980K can be set on the display screen 994, and the touch sensor 980K and the display screen 994 form a touch screen, also called a "touch screen". The touch sensor 980K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 994. In other embodiments, the touch sensor 980K can also be set on the surface of the electronic device 900, which is different from the position of the display screen 994.

[0166] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0167] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0168] The embodiment of the present application also provides an electronic device, which includes: one or more processors, a memory, and a computer program stored in the memory and executable on the one or more processors, wherein the one or more processors execute the computer program so that the electronic device can implement the steps in any of the above methods. The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by the electronic device, the steps in each of the above method embodiments can be implemented.

[0169] The computer-readable medium may include at least: any entity or device capable of carrying computer program codes to a camera / electronic device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk, or an optical disk. In some jurisdictions, according to legislation and patent practice, a computer-readable medium cannot be an electric carrier signal or a telecommunication signal.

[0170] The present application embodiment provides a computer program product, which includes a computer program, and when the computer program is executed by an electronic device, the steps in the above-mentioned various method embodiments can be implemented. The computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form.

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

[0172] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0173] In the embodiments provided in the present application, it should be understood that the disclosed devices / equipment and methods can be implemented in other ways. For example, the device / equipment embodiments described above are merely schematic, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0174] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0175] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0176] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0177] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0178] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0179] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for event calendar reminder, characterized in that: include: Running a first application on the electronic device and displaying a first page of the first application, where the first page is an interactive page of a target activity; The first application is a hybrid app, and the first page is an H5 page; In response to a first operation of a user on a first control in the first page, a first pop-up window is displayed; the first control is used to indicate whether to participate in a target activity, the first operation is used to indicate participation in the target activity, and the first pop-up window includes a second control for indicating whether to create a calendar reminder; In response to the user's second operation on the second control, a data request is sent to the H5 front-end server, and the data request is forwarded to the marketing center server of the first application through the H5 front-end server; the data request is used to request a reminder time and a deep link deeplink; the reminder time includes the start date and end date of the target activity date, and the start time and end time of each day in the target activity date; the data request is also used to request at least one of the following: an activity identification ID and an identification of whether to participate in the target activity; Receiving a first file from the H5 front-end server through JSbridge, wherein the first file is sent by the marketing center server to the H5 front-end server according to the data request after receiving the data request; the first file includes target data corresponding to the data request, the target data includes the reminder time and the deep link, and the target data also includes an activity ID and / or an identifier for participating in the target activity; In response to the second operation, starting a calendar application and creating a calendar reminder; In a case where the operation of starting the calendar application in response to the second operation is an operation of the first application accessing the calendar application for the first time, acquiring read and write permissions for the calendar application; And, after obtaining the read and write permissions of the calendar application and receiving the first file, starting the calendar application and creating the calendar reminder; When creating the calendar reminder, writing the deep link and the reminder time into the calendar reminder; Each time the reminder time is reached, in response to a confirmation operation input by the user to participate in the target activity again, the first application is started on the electronic device, and the first page is loaded again based on the deep link.

2. The method according to claim 1, characterized in that The obtaining of the read and write permissions of the calendar application includes: Displaying a second pop-up window on the screen of the electronic device, wherein the second pop-up window includes a confirmation authorization control for authorizing the read and write permissions of the calendar application; In response to the user clicking the confirmation authorization control, the read and write permissions of the calendar application are obtained.

3. The method according to claim 1, characterized in that The method of starting the first application on the electronic device and reloading the first page based on the deep link in response to a confirmation operation input by the user to participate in the target activity again each time the reminder time is reached includes: Each time the reminder time is reached, a third pop-up window is displayed on the electronic device, and the third pop-up window is used to remind the user whether to participate in the target activity again; In response to a user clicking operation on the third pop-up window, the first application is started, and the first page is loaded and displayed based on the deep link. The clicking operation on the third pop-up window is a confirmation operation for participating in the target activity again.

4. The method according to any one of claims 1 to 3, characterized in that The method of starting the first application on the electronic device and reloading the first page based on the deep link in response to a confirmation operation input by the user to participate in the target activity again each time the reminder time is reached includes: Each time the reminder time is reached, a fourth pop-up window is displayed on the electronic device, and the fourth pop-up window is used to remind the user whether to participate in the target activity again; In response to a user clicking operation on the fourth pop-up window, starting the calendar application and displaying the calendar reminder; In response to the user clicking on the deep link in the calendar reminder, the first application is started and the first page is loaded for display. The combination of the clicking operation on the fourth pop-up window and the clicking operation on the deep link is the confirmation operation of participating in the target activity again.

5. The method according to any one of claims 1 to 3, characterized in that The method of starting the first application on the electronic device and reloading the first page based on the deep link in response to a confirmation operation input by the user to participate in the target activity again each time the reminder time is reached includes: Detecting whether the first application is installed in the electronic device; When it is detected that the first application has been installed, the first application is started, and the first page is redirected based on the deep link; or, When it is detected that the first application is not installed, a fifth pop-up window is displayed, and the fifth pop-up window is used to instruct the user whether to install the first application.

6. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In response to a third operation of the user on the first control, the first pop-up window is not displayed, and the third operation is used to indicate non-participation in the target activity.

7. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In response to a fourth operation of the user on the second control, the calendar application is not started, and the fourth operation is used to indicate that a calendar reminder is not created.

8. The method according to claim 2, characterized in that: The second pop-up window also includes a deauthorization control that does not allow authorization of the read and write permissions of the calendar application, and the method further includes: In response to a user clicking operation on the deauthorization control, the acquisition of the read and write permissions of the calendar application is canceled.

9. An electronic device comprising a memory, one or more processors, and a computer program stored in the memory and executable on the processors, characterized in that: When the one or more processors execute the computer program, the electronic device implements the method according to any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by an electronic device, the method according to any one of claims 1 to 8 is implemented.

Images