Travel reminder method and electronic device

Abstract

This application provides a method and electronic device for providing travel reminders. Using the method described in this application, after detecting that the electronic device has received a flight text message and detecting that there is no authorization relationship between the authorized object and a specific application account, a determination is made as to whether to perform the operation of displaying guidance information for the Nth time. If the operation of displaying guidance information for the Nth time is determined to be performed, the guidance information is displayed for the Nth time. When authorization is completed, the electronic device obtains the user's flight itinerary data from the server corresponding to the specific application and displays a travel reminder based on the user's flight itinerary data. This application can remind the user to authorize at the appropriate time, thereby providing the user with accurate and timely travel reminders based on the user's detailed travel information.

Description

[0001] This application is a divisional application. The name of the original application is Travel Reminder Method and Electronic Device, the application number of the original application is 202111595477.5, and the original application date is December 23, 2021. All the contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a method and electronic device for reminding people to travel. Background Art

[0003] With the rapid development of electronic technology, the penetration rate of mobile terminals such as smartphones is increasing. Furthermore, with the development of network technology, the functions of mobile terminals are becoming increasingly powerful. Users can complete many tasks through mobile terminals, such as booking air tickets and train tickets online. Usually, ticket purchasing websites will send text message reminders to users after they have booked their air tickets to prevent them from missing their trips. Summary of the Invention

[0004] The embodiments of the present application provide an optimized travel reminder method and electronic device.

[0005] In some scenarios, after a user orders a flight ticket, the ticket purchasing website will push a text message reminder to the user's mobile phone. However, there is a problem with the text message content being missing when using the text message reminder. For example, the text message only prompts the travel time or flight destination, while other information is missing, resulting in the user not being able to obtain more detailed information. Therefore, other reminder methods can be used to remind the user of their travel. However, using other reminder methods requires user authorization. After obtaining user authorization, the reminder can be sent from the server of a specific application (such as The application server (the Air Travel application is an application that integrates flight ticket information from major airlines) obtains the user's complete itinerary information. Some embodiments of the present application can remind the user to authorize when appropriate, and then provide the user with accurate and timely travel reminders based on the user's detailed travel information.

[0006] In a first aspect, an embodiment of the present application provides a travel reminder method, applied to an electronic device, the method comprising: detecting whether a flight text message has been received; if it is determined that a flight text message has been received, detecting whether there is any information missing in the flight text message and detecting whether there is an authorization relationship between an authorization object and a user account of a user in a specific application, the authorization object including the user account of the user in a server corresponding to the electronic device or an identifier of the electronic device, the specific application being used to obtain the user's flight itinerary data from servers corresponding to at least two airlines; when it is detected that there is information missing in the flight text message and no authorization relationship exists between the authorization object and the user account of the user in the specific application, determining whether to perform an operation of displaying guidance information for the Nth time, the guidance information being used to guide the user to perform an authorization operation so that the server corresponding to the specific application establishes an authorization relationship between the authorization object and the user account of the user in the specific application, where N is an integer greater than 0; if it is determined that the operation of displaying guidance information for the Nth time is performed, displaying the guidance information; after the authorization relationship is established, the electronic device obtains the user's flight itinerary data from the server corresponding to the specific application based on the authorization relationship and the authorization object, and displays a travel reminder on the electronic device based on the obtained user's flight itinerary data.

[0007] If there is no authorization relationship between the user's user account in a specific application and the authorized object (such as the identifier of an electronic device), the server corresponding to the electronic device cannot obtain the user's complete itinerary information from the Air Travel server, resulting in the electronic device being unable to provide the user with accurate flight itinerary reminders. In addition, although the servers of each airline or Air Travel will send a feedback SMS after the user orders a flight ticket, the feedback SMS has the problem of missing content (for example, the SMS content lacks departure time information), which cannot meet the needs of flight itinerary reminders. In this application, it is detected that the flight SMS content is default (default can also be understood as missing) and there is no authorization relationship between the authorized object and the user's user account in a specific application, and guidance information is displayed. Through the detection operation, it can be determined that the user has the need to travel by plane; when it is determined that the user has the need to travel by plane, the guidance information is displayed, and the user is reminded to perform the authorization operation at the appropriate time so that the electronic device's identifier is bound to the user's user account in the specific application, so that the electronic device can obtain the user's complete itinerary information in a timely manner, so that the electronic device can remind the user based on the complete user itinerary information to prevent the user from missing the flight itinerary. In addition, since the server of a specific application is used to obtain the user's itinerary information from the servers corresponding to at least two airlines, this application guides the user to perform authorization operations by displaying guidance information, so that after the authorization operation, the electronic device can obtain the user's itinerary data on different airlines, so that the accuracy of itinerary reminders to the user can be further improved subsequently.

[0008] According to a first aspect, detecting whether a flight text message contains missing information includes: obtaining pre-stored basic information of the flight text message, the basic information of the flight text message including the flight number, departure date, departure place, and destination; detecting whether any of the basic information of the flight text message is missing from the flight text message; and determining that the flight text message contains missing information if any of the basic information of the flight text message is missing from the flight text message. In this way, using the pre-set basic information of the flight text message, it is possible to quickly determine whether the flight text message contains missing information.

[0009] According to the first aspect, determining whether to execute the operation of displaying the guidance information for the Nth time includes: obtaining the difference between the moment when the guidance information is displayed for the N-1th time and the first moment, the first moment being the moment when the flight SMS default is detected and there is no authorization relationship between the authorization object and the user account of the user in the specific application; determining whether the time difference is greater than the N-1th preset interval time, the N-1th preset interval time is used to indicate the minimum interval time between the N-1th display of the guidance information and the Nth display of the guidance information; if it is determined that the difference is greater than or equal to the N-1th preset interval time, determining that the guidance information is displayed for the Nth time.

[0010] In this way, the time difference is compared with the N-1th preset interval length to determine whether the conditions for displaying the guidance information are met. When the obtained difference is greater than the N-1th preset interval length, the guidance information is displayed to avoid a short time interval between two adjacent displays of the guidance information, thereby reducing the disturbance of the display of the guidance information to the user.

[0011] According to the first aspect, before determining whether the difference is greater than the N-1th preset interval duration, the method further includes: obtaining a cumulative number of times the guidance information has been displayed; and determining the N-1th preset interval duration based on the cumulative number of times. In this way, the interval duration between two consecutive guidance information displays is related to the cumulative number of times the guidance information has been displayed, rather than using the same preset interval duration. This allows the determined N-1th preset interval duration to better meet user needs.

[0012] According to a first aspect, determining the N-1th preset interval duration based on the cumulative number of times includes: obtaining a first product value between the cumulative number of times and a preset fixed duration; and using the first product value as the N-1th preset interval duration. As the cumulative number of times increases, the N-1th preset interval duration increases. That is, as the cumulative number of times increases, the time interval between two consecutive displays of guidance information increases to avoid disturbing the user.

[0013] According to the first aspect, the method further includes: obtaining the time at which the guidance information was displayed for the Nth time; updating the stored time at which the guidance information was displayed for the Nth time as the time at which the guidance information was displayed; and incrementing the stored cumulative number by 1. Each time the guidance information is displayed, the time at which the guidance information was displayed and the cumulative number are stored so that a subsequent determination of whether to display the guidance information next time can be made quickly, thereby improving the determination speed.

[0014] According to a first aspect, the method further includes: after displaying the guidance information for the Nth time, in response to a user's ignore operation, setting the time at which the ignore operation was received as the time at which the guidance information was displayed for the N-1th time, wherein the ignore operation indicates that the guidance information was ignored. When the user ignores the guidance information, the stored time for displaying the guidance information is updated, increasing the interval between the next display of the guidance information, reducing the number of times the guidance information is displayed, and further reducing the number of times the guidance information is displayed, thereby avoiding disturbing the user. For example, if the stored time for displaying the guidance information is T1, and the user ignores the card 23 hours after display, and the preset interval is 24 hours, if the stored time for displaying the guidance information is not updated, then after one hour, if the flight SMS is detected to be missing again and no authorization relationship exists between the authorized object and the user's user account in the specific application, the guidance information will be displayed again, resulting in frequent display of the guidance information. Updating the stored time value to the time at which the ignore operation was received increases the interval between two consecutive display times of the guidance information, thereby avoiding the problem of frequent display of the guidance information.

[0015] According to the first aspect, before displaying the guidance information for the Nth time, the method further includes: determining whether the cumulative number of times reaches a preset threshold; and if it is determined that the cumulative number of times reaches the threshold, canceling the display of the guidance information for the Nth time. The guidance information is canceled when the cumulative number of times reaches the threshold. Repeatedly displaying the guidance information indicates that the user does not intend to authorize guidance. In this case, canceling the display of the guidance information does not disturb the user, making authorized guidance more in line with user needs.

[0016] According to the first aspect, the interval between two adjacent displays of the guidance information is a preset fixed time length, and the interval between two adjacent displays of the guidance information is the same, so that the guidance information is displayed regularly.

[0017] According to the first aspect, after using the first product value as the N-1th preset interval duration, the method further includes: detecting whether the N-1th preset interval duration exceeds a preset interval threshold; if it is detected that the N-1th preset interval duration exceeds the interval threshold, setting the N-1th preset interval duration as the interval threshold. After the preset interval duration exceeds the interval threshold, setting the N-1th preset interval duration as the interval threshold can avoid the problem of authorization reminders not being issued for a long time.

[0018] According to the first aspect, the method further includes: in response to the user's authorization operation, detecting whether the user's user account in the specific application is logged in; when it is detected that the user's user account in the specific application is logged in, jumping to an authorization page for the user to approve the authorization operation or cancel the authorization operation. After the user has authorized the operation, jumping to the authorization page facilitates the user to approve the authorization or cancel the authorization operation, thereby improving the flexibility of user operations.

[0019] According to the first aspect, before detecting whether a flight text message has been received, the method further includes: detecting that no authorization relationship exists between the authorization object and the user's user account in a specific application. Before detecting the flight text message, a check is performed once to determine if no authorization relationship exists between the authorization object and the user's user account in the specific application. This avoids the issue of performing a text message check when an authorization relationship exists, which could result in an invalid operation (i.e., detecting whether a flight text message has been received). Simultaneously detecting twice that no authorization relationship exists between the authorization object and the user's user account in the specific application can avoid detection errors and improve detection accuracy.

[0020] According to the first aspect, before determining whether to perform the operation of displaying the guidance information for the Nth time, the method further includes: obtaining a display mode for displaying the guidance information for the Nth time, where the display mode includes: a card and / or a notification. There are multiple ways to display guidance information, and one of these display modes may be used, providing flexibility. The guidance information may also be displayed simultaneously using both display modes, thereby increasing the likelihood that the user will see the guidance information and preventing the user from missing the guidance information.

[0021] According to the first aspect, before determining whether to perform an operation of displaying guidance information for the Nth time, the method further includes: detecting that the display mode of displaying the guidance information for the Nth time includes a notification mode. When, before detecting the Nth operation, detecting that the display mode of displaying the guidance information for the Nth time includes a notification mode, when the electronic device receives the notification, regardless of the application currently running on the electronic device, the notification is displayed, causing a disturbance to the application, and the display mode of the notification is a strong disturbance mode. Before the guidance of the notification display, determining whether to display the guidance information is performed to avoid frequent disturbances to the user.

[0022] In a second aspect, the present application provides an electronic device comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory. When the computer programs are executed by one or more processors, the electronic device executes the travel reminder method corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect.

[0023] The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0024] In a third aspect, the present application provides a computer-readable medium for storing a computer program. When the computer program runs on an electronic device, the electronic device executes the travel reminder method corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0026] Figure 1 is a schematic structural diagram of an electronic device;

[0027] Figure 2 is a schematic diagram illustrating a software structure of an electronic device;

[0028] Figure 3 This is a schematic diagram of the interaction between internal modules and other servers when an electronic device performs a travel reminder method provided by an embodiment of the present application;

[0029] Figure 4 is a schematic diagram showing an exemplary flight SMS message with default information;

[0030] Figure 5 is a schematic diagram showing an exemplary display of guidance information;

[0031] Figure 6 FIG. 1 is a schematic diagram showing exemplary displayed guide information and ignored guide information. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0033] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0034] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0035] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0036] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0037] Figure 1 This is a schematic diagram of the structure of an electronic device 100 shown in an embodiment of the present application. It should be understood that, Figure 1 The illustrated electronic device 100 is merely one example of an electronic device, and the electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. Figure 1 The various components shown in the drawings may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0038] The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0039] It is understandable that in other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently.

[0040] Figure 2 It is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.

[0041] In the embodiment of the present application, the electronic device 100 takes the Android system with a layered architecture as an example to exemplify the software structure of the electronic device 100.

[0042] The layered architecture of electronic device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other via software interfaces. In some embodiments, the Android system is divided into four layers: from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0043] like Figure 2 As shown, the application layer may include a series of application packages, including a context awareness module, a business logic processing module, a business presentation module, a gallery, WLAN, Bluetooth, music, games, short messaging, and other applications.

[0044] The context-aware module runs permanently or in a low-power mode and has the ability to perceive external facts or environments. When the card reminder service processing is enabled, the context-aware module monitors registered events (such as specific time, specific location, or specific event). If the user triggers one of these events, the context-aware module sends a notification to the business logic processing module. In addition, the context-aware module can also detect related events and obtain the status of events from other applications in the application layer, the application framework layer, or the kernel layer through the application program interface. For example, it can detect Bluetooth connections, network connections, monitor user text messages, and customize timers.

[0045] The business logic processing module is used to implement the display of various cards and notifications.

[0046] The service presentation module (e.g., YOYO Suggestion) controls the display or disappearance of cards. For example, the service presentation module can receive a command from the service logic processing module to display a reminder card and display the reminder card to the user. Conversely, if a command to disappear a card is received from the service logic processing module, the service presentation module removes the card.

[0047] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0048] like Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a resource manager, a notification manager, an activity manager, and the like.

[0049] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0050] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, Wi-Fi drivers, Bluetooth drivers, audio drivers, sensor drivers, etc.

[0051] It is understandable that Figure 2 The layers in the illustrated software structure and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, which is not limited in the present application.

[0052] In some embodiments, after a user has booked a flight, an airline travel website can send a text message to remind the user of their flight. However, the content of these text message reminders varies from airline to airline, with some missing content. For example, a text message may only include the flight departure time or the destination. Mobile phones are unable to provide travel reminders (such as check-in time, check-in time, and check-in location) via the default text message.

[0053] If there is an authorization relationship between the user's electronic device and the user's user account on the airline's server, the airline (hereinafter referred to as the "airline") can obtain the user's basic information and return the user's detailed itinerary information to the mobile phone, so that the electronic device can provide the user with itinerary reminders. When the flight SMS is missing, the airline's server cannot return the user's complete itinerary information based on the default basic information, resulting in the electronic device being unable to provide the user with accurate travel reminders. Therefore, the mobile phone needs to promptly remind the user to authorize the acquisition of complete itinerary information so that other methods can be used to provide the user with accurate travel reminders.

[0054] Some embodiments of the present application provide a method for travel reminders, so that an electronic device can obtain user authorization in a timely manner, thereby obtaining the user's complete travel information, and provide the user with accurate and timely travel reminders based on the complete travel information.

[0055] In the embodiments of the present application, the electronic device is described by taking a mobile phone as an example. In other embodiments, the electronic device may also be a tablet, a smart wearable device, a vehicle-mounted device, etc.

[0056] Figure 3 This is a schematic diagram illustrating the interaction between internal modules and other servers when a mobile phone executes the travel reminder method provided in an embodiment of the present application. The travel reminder method includes the following steps:

[0057] Step 301: The business logic processing module registers the flight SMS fence with the context awareness module.

[0058] For example, the business logic processing module may be a system application that may not be visible to the user. The business logic processing module may be started during phone initialization. After startup, the business logic processing module may send an instruction to the context awareness module to register the flight SMS fence. The context awareness module, in response to the registration instruction from the business logic processing module, registers the flight SMS fence.

[0059] Optionally, when the business logic processing module registers the flight SMS fence with the context awareness module, it can instruct the context awareness module to monitor whether the mobile phone receives the flight SMS.

[0060] In one example, before executing step 301, the business logic processing module can also detect whether there is an authorization relationship (also called a binding relationship) between the authorization object and the user's user account in a specific application (hereinafter referred to as a "specific application account"). Optionally, the authorization object can be the user account of the user on the server corresponding to the electronic device (hereinafter referred to as a "user service platform account"), or it can be the identifier of the user's electronic device. In this example, the server corresponding to the electronic device is also called the user service platform, and the user service platform can be a Honor server. The specific application account can be the user's account in the server of a specific application (hereinafter referred to as a specific server), and the specific application can be an application that integrates air ticket travel information of major airlines, for example, the "Air Travel" application. In this example, the authorization object takes the identifier of the electronic device as an example.

[0061] The business logic processing module can also detect whether an authorization relationship exists between the authorization object and a specific application account. Specifically, the business logic processing module can initiate a query request to the user service platform, requesting the relationship between the authorization object and the specific application account. In response to the query request, the user service platform queries whether an authorization relationship exists between the authorization object and the specific application account and returns the query result to the business logic processing module. Optionally, the query request can include identification information of the electronic device, such as "Device ID."

[0062] If the query result indicates that there is no authorization relationship between the authorization object and the specific application account, the business logic processing module executes step 301 and stores the query result. If the query result indicates that there is an authorization relationship between the authorization object and the specific application account, the business logic processing module ends the process.

[0063] Optionally, the mobile phone can call a specific function from the server of a specific application through the authorization relationship between the authorization object and the specific application account. For example, the mobile phone can obtain the user's complete itinerary information from the specific server (i.e., the server of the specific application).

[0064] Before instructing to register the flight SMS fence, the business logic processing module can first detect whether there is an authorization relationship between the authorization object and the specific application account. If there is an authorization relationship, the process is terminated to avoid erroneous authorization reminders to the user.

[0065] Step 302: The context awareness module detects that a flight SMS fence is triggered.

[0066] Exemplarily, the scenario awareness module can register a flight SMS fence based on the instructions of the business logic processing module. After the scenario awareness module registers the flight SMS fence, it can detect whether the received SMS contains flight-sensitive words. Flight-sensitive words include but are not limited to: flight number, mobile phone number, take-off time, landing time and other information. The scenario awareness module monitors each SMS. If the scenario awareness module recognizes that the SMS includes any of the information such as flight number, mobile phone number, take-off time, landing time, etc., it can be determined that the flight SMS fence is triggered. Optionally, the scenario awareness module can use a natural language understanding (NLU) model to identify the content of the flight SMS.

[0067] Exemplarily, a user can log in to a third-party application, such as a Ctrip application or an airline application, through the local mobile phone number (or a Honor account or other account password). After the user logs in successfully, he can purchase a ticket through a third-party application. When the third-party application detects that the ticket purchase is successful, it can send a ticketing feedback SMS to the user's registered mobile phone number (such as the local mobile phone number mentioned above). Exemplarily, the ticketing feedback SMS includes but is not limited to: flight number, passenger name, take-off time, landing time, departure place, destination and other information. Exemplarily, the mobile phone receives a ticketing feedback SMS sent by a third-party application through the operator server. The situational awareness module detects the SMS and recognizes that the SMS includes flight-sensitive words. Accordingly, the perception module determines that the flight SMS fence is triggered.

[0068] In another example, the context awareness module can also detect whether the SMS is a flight SMS by using the SMS sender information of the SMS. The SMS sender information may include the sender's name, the sender's phone number, etc. If the context awareness module detects the SMS sender information, it determines that the flight SMS fence is triggered. For example, Figure 4 The second text message begins with "XX Business Travel," which is the sender's information. The context-aware module recognizes the sender's information and determines that the text message is a flight message. Alternatively, the flight message can be identified by identifying the sender's number.

[0069] In another example, flight text messages can be identified based on the text message sender information and flight-sensitive words.

[0070] Step 303: The context awareness module instructs the business logic processing module that the flight SMS fence is triggered.

[0071] When the situation awareness module detects that the flight SMS fence is triggered, it reports the flight SMS fence triggering event to the business logic processing module.

[0072] Step 304: The business logic processing module detects that there is information missing in the flight SMS and there is no authorization relationship between the authorization object and the user account of the user in the specific application.

[0073] The business logic processing module receives the flight message parsed by the context awareness module. It checks the basic information of the flight message to see if any information is missing. The business logic processing module extracts keywords from the flight message. If no keywords match the basic information in the message, the message is considered missing. If all basic information is present, the message is considered complete and subsequent authorization guidance is not performed. Therefore, step 305 is not executed.

[0074] For example, the business logic processing module may pre-set basic information of a flight SMS message including flight number, departure date, departure location, and destination. If the business logic processing module detects that any of the basic information of the flight SMS message is missing, it is determined that the flight SMS message has information missing. Figure 4 This example shows the default situation of flight SMS. Figure 4 In the table, the first column shows the content of the SMS, and the second column lists the omitted items. For example, in the first refund SMS, the flight number is omitted. The second SMS omits the departure and destination. The third SMS omits the date, departure, and destination.

[0075] If the business logic processing module detects that the flight SMS message contains missing information, it can initiate another query request to the user service platform to inquire whether an authorization relationship exists between the authorization object and the specific application account. The user service platform responds to the query request, inquiring whether an authorization relationship exists between the authorization object and the specific application account, and obtains a query result. The user service platform returns the query result to the business logic processing module. If the query result indicates that an authorization relationship does not exist between the authorization object and the specific application account, subsequent authorization guidance operations can be performed (e.g., executing step 305).

[0076] If the query result indicates that there is a binding relationship (ie, an authorization relationship) between the authorization object and the specific application account, the business logic processing module ends the process.

[0077] Optionally, the business logic processing module may first detect whether there is an authorization relationship between the authorization object and the specific application account. When the business logic processing module detects that there is no authorization relationship between the authorization object and the specific application account, it then detects whether the flight SMS is default.

[0078] When the flight SMS is complete and an authorized relationship exists, the mobile phone can obtain the user's complete itinerary information from a specific server through the basic information in the flight SMS (such as basic information including: flight number, departure date, departure place and destination). However, when the flight SMS is missing, due to the missing basic information, the user's complete information cannot be obtained from the specific server, and the user cannot be reminded of travel based on the user's complete itinerary information.

[0079] In this example, when the flight SMS fence is triggered, if the flight SMS is detected as missing and no authorization relationship exists between the authorized object and the specific application account, a guidance message is displayed to avoid the problem of incorrectly displaying the guidance message and avoiding disturbing the user. At the same time, after the guidance message is displayed, it is convenient for the user to bind the electronic device's identity to the specific server account in a timely manner. This allows the electronic device to obtain the user's detailed itinerary information from the specific server (such as Air Travel's server) through the user service platform, thereby allowing the mobile phone to accurately remind the user of the itinerary.

[0080] In an example, after the business logic processing module detects that no authorization relationship exists between the authorization object and the specific application account, step 305 may be executed.

[0081] Step 305: The service logic processing module sends a display instruction to the context awareness module for instructing the service presentation module to display the guidance information.

[0082] Exemplarily, the business logic processing module sends a display instruction to the business presentation module, and the display instruction is used to instruct the business presentation module to display guidance information. The display instruction may carry guidance information, and the guidance information is used to instruct the user to perform authorization operations. For example, the guidance information includes a link to an authorization-related page, such as a link to the login page of a specific application server (such as "Air Travel"), or a link to a page authorized between an authorization object (such as the identifier of the electronic device where YOYO Suggest is located) and a specific application account.

[0083] Step 306: The service presentation module displays guidance information.

[0084] The service presentation module displays the guidance information, which is used to guide the user to perform the authorization operation. There are many ways of displaying, and the guidance information can be displayed through a card on the mobile phone, such as displaying the guidance information through a card on the negative screen, such as displaying the guidance information through a card on the main screen, or displaying the guidance information through a notification. The service presentation module can also prompt the guidance information through voice prompts or vibration prompts. The service presentation module can also display the guidance information in multiple display modes at the same time, for example, displaying the guidance information through a card on the negative screen of the screen, and displaying the guidance information in the form of a notification. The ways of displaying the guidance information are no longer listed one by one in this application.

[0085] Using multiple display methods can improve the reminder efficiency of the authorization reminder and increase the probability of users discovering the authorization reminder, thereby authorizing the user service platform to obtain user travel information in a timely manner.

[0086] Step 307: The service presentation module detects the user's authorization operation.

[0087] For example, the user performs an authorization operation according to the instructions of the guidance information so that the specific server completes the authorization between the authorization object and the specific application account. The user's authorization operation can be an operation indicating that the user agrees to the authorization, such as clicking a "Agree to Authorization" button.

[0088] For example, the guidance information is displayed in the form of a card. When the user clicks the reminder card, if it is detected that the specific application account is logged in, it will jump to the authorization page, such as Figure 5 In (4) of the page 408, the authorization page 408 may include a control for indicating that authorization is allowed (such as Figure 5 (8) in the control 409) and the control indicating the cancellation of authorization (such as Figure 5 (8) in the control 410), if the business presentation module receives an operation that allows authorization (such as clicking Figure 5 (8) of the control 409), then execute step 308.

[0089] In one example, if the user clicks the reminder card and detects that the specific application account is not logged in, the user is first redirected to the login page of the specific application account. The user then performs the login operation according to the instructions on the login page.

[0090] Step 308: The service presentation module sends authorization information to the specific application server.

[0091] The service presentation module can obtain the user's authorization information, which may include relevant information about the user service platform, such as the functional interface parameters of the user service platform and the package name of the application in the electronic device, such as the package name recommended by YOYO. It may also include relevant information about specific applications, such as the package name of the specific application, the APPID (Application ID) of the specific application, the user's OpenID on Air Travel, and information about the user account on the user service platform.

[0092] Step 309: The specific application server sends authorization completion information to the user service platform.

[0093] The specific application server verifies the authorization information, and the detailed authorization process is not described in detail in this application. The specific application server sends authorization completion information to the user service platform, which can be used to indicate that the authorization between the electronic device identifier and the specific application account is completed.

[0094] Step 310: The user service platform receives authorization completion information.

[0095] After receiving the authorization completion information, the user service platform stores the authorization relationship between the authorized object and the specific application account. Optionally, the user service platform can also store the PUSH subscription relationship between the electronic device and the user service platform. Through this PUSH subscription relationship, the user service platform can push push messages to electronic devices that have a PUSH subscription relationship with the user service platform. For example, if mobile phone A has a PUSH subscription relationship with the user service platform, the user service platform can push messages to mobile phone A via push.

[0096] Step 311: The user service platform pushes a push notification of successful authorization to the context awareness module of the mobile phone.

[0097] Therefore, the user service platform can send the authorization completion message to the mobile phone in the form of a push notification, and the context awareness module of the mobile phone receives the push notification.

[0098] Step 312: The context awareness module sends a message indicating successful authorization to the business logic processing module.

[0099] Step 313: The service logic processing module sends a termination instruction to the service presentation module for instructing to terminate the display of the guidance information.

[0100] After receiving the authorization completion information, the service logic processing module may send a termination instruction for closing the guidance information to the service presentation module. The termination instruction is used to instruct the service presentation module to remove the guidance information from the display screen.

[0101] In this example, timely instructing the service presentation module to terminate the guidance information can reduce disturbance to the user and improve the user experience.

[0102] Step 314: The service presentation module stops displaying the guidance information.

[0103] Exemplarily, the service presentation module terminates display of the guidance information. For example, if the guidance information is displayed in the form of a card, when the service presentation module terminates display of the guidance information, the service presentation module removes the card from the interface. If the guidance information is displayed in multiple modes simultaneously, when the service presentation module receives a termination instruction, it terminates the guidance information displayed in multiple modes. For example, a mobile phone interface contains both Notification A and Card A, Notification A displays the guidance information, and Card A displays the guidance information. When the service presentation module receives the termination instruction, it removes both Card A and Notification A.

[0104] After the authorization relationship is established, the electronic device obtains the user's flight itinerary data from the server corresponding to the specific application based on the authorization relationship and the authorization object, and displays a travel reminder on the electronic device based on the obtained user's flight itinerary data. For example, the authorization object can be the identifier of the mobile phone. The mobile phone can obtain the user's flight itinerary data (i.e., detailed flight itinerary data) from the server corresponding to Air Travel through the authorization relationship stored on the Honor platform. Since the Honor platform also stores the correspondence between the Honor account and the mobile phone identifier, the mobile phone can obtain the user's flight itinerary data from the Honor platform. The electronic device makes a travel reminder based on the user's flight itinerary data. For example, if the user's flight itinerary data indicates that it will take off from Capital Airport at 12:00 on September 20 and the destination is Shanghai, the mobile phone can pop up a card at 8:00 on September 20, which reminds the user that there is a flight trip at 12:00. For another example, when the user arrives at Capital Airport, the user's check-in information (such as check-in counter information, etc.) can be displayed on the mobile phone interface to remind the user to check in. Travel reminders for other scenarios are not listed one by one in this example.

[0105] If there is no authorization relationship between the user's account on a specific server (such as the user's account on Air Travel) and the authorized object (such as the identifier of an electronic device), the user service platform cannot obtain the user's complete itinerary information from Air Travel's server, resulting in the electronic device being unable to provide the user with accurate itinerary reminders. In addition, although the airline or Air Travel will send a feedback SMS after the user orders a flight ticket, the feedback SMS has the problem of missing content and cannot meet the needs of itinerary reminders. In this example, the flight SMS fence trigger is detected, and it can be determined that the user has the need to travel by plane; after it is determined that the user has the need to travel by plane, it is detected that the flight SMS is default and there is no authorization relationship between the authorized object and the specific application account, and a guidance message is displayed to remind the user to perform the authorization operation so that the electronic device's identifier is bound to the specific application account and the user's complete itinerary information is obtained in a timely manner, so that the subsequent electronic device can remind the user based on the complete user itinerary information to prevent the user from missing the flight itinerary.

[0106] In other embodiments, in order to reduce the number of times the guidance information is displayed, the steps in situation 2 may be executed after step 304 is executed, that is, the business logic processing module executes step 3041 (not in step 3042). Figure 3 shown in ).

[0107] Scenario 2:

[0108] Step 3041: The business logic processing module obtains the time when the guidance information was last displayed and the cumulative number of times the guidance information was displayed.

[0109] For example, the business logic processing module stores the time when the guidance information was last displayed and the cumulative number of times the guidance information was displayed. The time when the guidance information was last displayed can also be used to indicate the time when the user operates the guidance information.

[0110] Step 3042: The business logic processing module determines the time for displaying the guidance information this time based on the accumulated times.

[0111] For example, the business logic processing module can determine the preset interval between two adjacent displays of the guidance information based on the cumulative number of times. In this example, the preset interval can increase as the cumulative number of times increases to avoid disturbing the user.

[0112] For example, the preset interval duration can be equal to the cumulative number of times * L, such as L is equal to 24 hours. For example, the first preset interval duration = 1 * 24h, that is, the preset interval duration between the first display time and the second display time is 24 hours, and the second preset interval duration = 2 * 24h, that is, the preset interval duration between the second display time and the third display time is 48 hours. Optionally, the preset interval duration can also be pre-stored. For example, the first preset interval duration (i.e., the interval between the first display time and the second display time) can be set to 24 hours, the second preset interval duration (i.e., the interval between the second display time and the third display time) can be 72 hours, and the third preset interval duration (i.e., the interval between the third display time and the fourth display time) can be 168 hours.

[0113] After the preset interval is determined, the time interval between the last display of guidance information is checked to see if it exceeds the preset interval. If so, the guidance information is displayed when the flight SMS is detected to be default and no authorization relationship exists between the authorized object and the specific application account. For example, if the cumulative number of times is 1, the preset interval is determined to be 24 hours, the time when the guidance information was last displayed is T1, the time when the flight SMS is detected to be default and no authorization relationship exists between the authorized object and the specific application account is T2, and T2-T1 is greater than 24 hours, then the guidance information can be displayed at time T2 (i.e., the guidance information will be displayed at T2).

[0114] If the preset interval duration is not exceeded, whether to display the guidance information is determined based on the preset interval duration and the time when the guidance information was last displayed. For example, the cumulative number of times is 2, the preset interval duration is determined to be 48 hours, the time when the guidance information was last displayed is T1, the current detection time (that is, the time when it is detected that the flight SMS has default information and no authorization relationship exists between the authorization object and the specific application account) is T2, and T2-T1 is less than 48 hours. It can be determined that when the flight SMS is detected to be default and no authorization relationship exists between the authorization object and the specific application account this time, the guidance information will not be displayed. The next time the flight SMS is detected to be default and no authorization relationship exists between the authorization object and the specific application account (such as the detection time is T3), it is detected whether T3-T1 is greater than or equal to 48 hours. If it is determined that T3-T1 is greater than or equal to 48 hours, it is determined that the guidance information will be displayed the next time the flight SMS is detected to be default and no authorization relationship exists between the authorization object and the specific application account.

[0115] After determining to display the guidance information, the service logic processing module may send a display instruction to the service presentation module, ie, execute step 3051 .

[0116] Step 3051: The service logic processing module sends a display instruction to the service presentation module to instruct the service presentation module to display the guidance information.

[0117] Exemplarily, the display indication includes guidance information.

[0118] Step 3052: The business logic processing module updates the current display time and cumulative number of guidance information.

[0119] Exemplarily, the business logic processing module updates the stored time of displaying the guidance information to the time of the current display of the guidance information, and increments the cumulative number by 1. For example, if the stored time of the last display of the guidance information is recorded as Th=T1, the cumulative number N=1, and the time of the current display of the guidance information is determined to be T2, then Th is set to T2, i.e., Th=T2, and the cumulative number N=2.

[0120] It should be noted that step 3051 and step 3052 can be executed simultaneously.

[0121] Step 306: The service presentation module displays guidance information for instructing to bind the specific application account.

[0122] Step 307: The service presentation module detects the user's authorization operation.

[0123] Step 308: The service presentation module sends authorization information to the specific application server.

[0124] Step 309: The specific application server sends authorization completion information to the user service platform.

[0125] Step 310: The user service platform receives authorization completion information.

[0126] Step 311: The user service platform pushes a push notification of successful authorization to the context awareness module of the mobile phone.

[0127] Step 312: The context awareness module sends a message indicating successful authorization to the business logic processing module.

[0128] Step 313: The service logic processing module sends a termination instruction to the service presentation module for instructing to cancel the display of the guidance information.

[0129] In this example, steps 306 to 313 in case 2 are the same as Figure 3 Steps 306 to 313 are similar and will not be described again here.

[0130] In this example, by recording the last time the guidance information was displayed and the cumulative number of times the guidance information was displayed, the preset interval duration can be determined to determine whether to display the guidance information this time. This can avoid frequent display of the guidance information and causing disturbance to the user. The preset interval duration increases with the increase in the cumulative number of times, thereby reducing the number of times the guidance information is displayed and further reducing the disturbance to the user.

[0131] Case 3: The user ignores the guidance information.

[0132] In another example, after executing step 306 in case 2, steps 307' to 308' may be executed (not in Figure 3 shown in ).

[0133] Step 307': If the service presentation module receives an ignore operation from the user, the service presentation module may send the time of receiving the ignore operation to the service logic processing module. After executing step 307', execute step 308'.

[0134] For example, the ignore operation can be an operation such as swiping left on a card or clicking an ignore control. For example, if the guidance information is displayed in the form of a card, swiping left on the card will ignore the card. The service presentation module receives the ignore operation and reports the ignore operation event to the business logic processing module. The business logic processing module uses the time of receiving the ignore operation event as the time of receiving the ignore operation.

[0135] Step 308 ′: the business logic processing module updates the stored time of displaying the guidance information to the time of receiving the ignore operation.

[0136] For example, the time Th for displaying the guidance information stored in step 3052 is T2, the time for displaying the guidance information in step 306 is T2, and the time for receiving the ignore operation is T4, then the business logic processing module sets Th to T4.

[0137] After step 308 ′, the context awareness module continues to detect whether the flight SMS fence is triggered, and then returns to step 302 .

[0138] In this example, if the time for displaying the guidance information is T1, and the user ignores the card 23 hours after the display, the preset interval is 24 hours. If the stored time for displaying the guidance information is not updated, then after 1 hour, when the flight SMS is detected to be default again and there is no authorization relationship between the authorized object and the specific application account, the guidance information will be displayed again. The guidance information will be displayed frequently. To avoid this situation, this example updates the stored time for displaying the guidance information to the time when the ignore operation is received, thereby increasing the interval for displaying the guidance information next time and reducing the number of times the guidance information is displayed.

[0139] In other embodiments, after executing step 304, the business logic processing module obtains a display mode for displaying the guidance information. If the business logic processing module uses a push notification display mode, the business logic processing module executes step 3041; if the business logic processing module determines that a card display mode is used, step 305 is directly executed.

[0140] In some embodiments, if the business logic processing module determines to adopt the notification display method, the business logic processing module can set an interval time threshold, for example, the interval time threshold is set to 7*24h (hours). If the business logic processing module determines that the preset interval time is greater than or equal to 7*24h, the preset interval time is set to 7*24h. After the card is displayed at an interval of 7*24h, if the business logic processing module receives a flight SMS trigger event, it is detected that the flight SMS is default and that the "Air Travel" account is not bound to the authorized object (DeviceID of the mobile phone). The business logic processing module instructs the business presentation module to display the guidance information at an interval of 7*24 hours. Reduce the number of notifications and avoid the problem of not issuing authorization reminders for a long time.

[0141] In this example, since the card is usually on the negative one screen or the main screen, long-term display of the guidance information will not affect the user and can be displayed for a long time. Notifications are a form of strong interruption. In this example, the number of notifications is controlled to avoid disturbing the user.

[0142] Figure 5 This example illustrates the travel reminder method of the present application with reference to specific examples.

[0143] In this example, the specific application takes "Air Travel" as an example, and the user service platform (that is, the server corresponding to the electronic device) takes the Honor platform as an example. The business logic processing module initiates a query request to the Honor platform to inquire whether the authorization object is bound to the "Air Travel" account (that is, the user's user account on Air Travel). The Honor platform returns the query result, which indicates that the authorization object is not bound to the "Air Travel" account. The business logic processing module instructs the scenario perception module to register the flight SMS fence, and the scenario perception module monitors whether the mobile phone receives the flight SMS. When the scenario perception module recognizes the flight SMS A, it reports the event triggered by the flight SMS fence to the business logic processing module. The business logic module obtains the flight SMS reported by the scenario perception module. If it is detected that the content of the flight SMS defaults to any of the preset SMS basic information (such as flight number, departure date, departure place and destination), the business logic module determines that the flight SMS is default. The business logic processing module again detects that the authorization object is not bound to the "Air Travel" account, and instructs the business presentation module (such as YOYO suggestion) to display the guidance information, wherein the business logic processing module indicates that the guidance information can be displayed in the form of a notification. Figure 5 (1) in the figure shows that the notification icon 403 is displayed in the SMS interface 401, and the received flight SMS 402 defaults to the destination, landing time, etc. When the business logic processing module of the mobile phone determines to display the guidance information, the notification icon 403 is displayed on the SMS interface 401 (that is, the guidance information is displayed in the form of a notification). Figure 5 In (1), the user slides in the direction of the black arrow, and the phone responds to the user's sliding operation and displays the specific content of the notification on the display screen. Figure 5 As shown in (2), the interface 404 displays two notifications, and the notification 405 displays the content of the guidance information. The user clicks the notification 405 to jump to the authorization page (such as Figure 5 Interface 408 shown in (4)).

[0144] In another scenario, the user does not open the flight SMS message received, e.g. Figure 5 As shown in (3), the guidance information is displayed in the form of a card. The main screen of the mobile phone is located in interface 406. The service presentation module displays the guidance information in the form of a card. Interface 406 displays card 407, which contains guidance information. Card 407 displays a prompt message for guidance authorization and a control 4071 for guidance authorization. If the user clicks control 4071, it can jump to the authorization interface 408. Figure 5In (4), the interface 408 prompts the user to authorize. If the control 409 is triggered, the authorization information is sent to the server of Air Travel, and the server of Air Travel sends the authorization completion information to the Honor platform. After receiving the authorization completion information, the Honor platform returns the authorization success information to the context perception module of the mobile phone. The context perception module sends the authorization success information to the business logic processing module, and the business logic processing module instructs the business presentation module (such as YOYO suggestion) to stop displaying card 407. The business presentation module removes card 407 from the interface 406.

[0145] In this example, the authorization relationship between the identifier of the electronic device and the Air Travel account is taken as an example. Specifically, after the user performs the authorization operation, in this example, YOYO recommends reporting the authorization information to the Air Travel server. The authorization information is such as the user's OpenID. The Air Travel server verifies the authorization information and sends the authorization completion information to the Honor platform. After the Honor platform receives the authorization completion information, it records that the Air Travel account is bound to the user's OpenID. The Honor platform also records the correspondence between the user's OpenID and the identifier of the electronic device (such as DeviceID). When the Honor platform records that the Air Travel account is bound to the user's OpenID, the authorization relationship between the identifier of the stored electronic device and the Air Travel account is realized. It should be noted that after the authorization is completed, the electronic device can obtain the user's complete itinerary data from the Air Travel server through the Honor platform and the stored authorization relationship.

[0146] Figure 5 (5) in the figure shows the interface of the "Air Travel" application to check the user's Air Travel account authorization success. Figure 5 As shown in (5), interface 411 is the authorization management interface of the "Air Travel" application, and control 412 is in the open state, that is, the user authorizes YOYO suggestions in the user account of Air Travel.

[0147] Optionally, you can also log in to the Honor platform through the Honor account to achieve authorization with a specific server (i.e., the server of a specific application).

[0148] In another example, account binding may also be performed, where account binding refers to binding between a user's account on the Honor platform and an account on a specific server (i.e., a server for a specific application).

[0149] The following combination Figure 6 This section describes the scenario where a user ignores a card.

[0150] Please refer to Figure 6For example, in this example, the specific application takes "Air Travel" as an example, and the user service platform takes the Honor platform as an example. The business logic processing module initiates a query request to the Honor platform to inquire whether there is an authorization relationship between the identifier of the electronic device and the account of "Air Travel". The Honor platform returns the query result, which indicates that the identifier of the electronic device is not bound to the account of "Air Travel". The business logic processing module instructs the scenario perception module to register a flight SMS fence, and the scenario perception module monitors whether the mobile phone receives flight SMS. When the scenario perception module recognizes flight SMS A, it reports the event of flight SMS fence triggering to the business logic processing module. The business logic processing module extracts information from SMS A through the NLU model. When the extracted information lacks any of the preset basic information of the SMS (such as flight number, departure date, departure place and destination), the business logic module determines that the flight SMS is missing. The business logic processing module detects again that the identifier of the electronic device is not bound to the account of "Air Travel". The business logic processing module obtains the time of the last guidance information display and the cumulative number of guidance information displays. In this example, the identifier Th indicates the time of the last guidance information display, and the identifier N indicates the cumulative number of displays, where Th = null and N = 0. The time when the flight SMS message is detected to be missing and no authorization relationship exists between the electronic device identifier and the specific application account (i.e., the first detection time) is recorded as T1. The business logic processing module sends a display instruction to the business presentation module, which includes the guidance information and the display method (e.g., notification method). Simultaneously, Th = T1 and N = 1 are updated. Therefore, time T1 is the time of the first display. The business presentation module displays the guidance information as a notification. The user swipes left on the notification. A left swipe indicates that the user ignores the notification. The business presentation module receives the user's ignore operation (e.g., a left swipe) and reports the ignore operation event to the business logic processing module. The time when the business logic processing module receives the ignore operation event is t1, i.e., the time when the business logic processing module receives the ignore operation is t1. The business logic processing module sets Th to t1. When the situational awareness module continues to monitor the flight SMS fence, when it detects that the flight SMS fence is triggered again, continue as above Figure 2 In steps S303 to S304, the business logic processing module detects for the second time that the flight text message is default and there is no authorization relationship between the electronic device identifier and the specific application account. The second detection time is recorded as T2. The business logic module obtains Th=t1, N=1. The business logic processing module determines the first preset interval duration as 1*24 hours based on N. The second detection time (T2) is detected to be greater than or equal to 24 hours from the time t1. The business logic processing module instructs the business presentation module to perform a second display at time T2, and updates Th=T2, N=2. Figure 6 The intermediate interval A is greater than or equal to 24 hours.

[0151] If the user does not take any action on the notification displayed for the second time, the notification will still be displayed on the screen. The situational awareness module continues to monitor whether the flight SMS fence is triggered. If the flight SMS fence is triggered for the third time, the above steps will continue. Figure 2 Steps S303 to S304 in the process. The business logic processing module detects for the third time that the flight SMS is default and there is no authorization relationship between the authorization object and the specific application account. The third detection time is recorded as t2. The business logic processing module obtains Th=T2, N=2. The business logic processing module determines the second preset interval duration as 2*24 hours based on N. If the time (t2-T2) from the third detection time t2 (i.e., the time when the flight SMS is detected for the third time to have information default and there is no authorization relationship between the authorization object and the specific application account) to the time T2 is less than 2*24 hours, then it is determined that when the flight SMS is detected for the third time to have information default and there is no authorization relationship between the authorization object and the specific application account, the guidance information is not displayed. Figure 6 The middle interval B is less than 2*24 hours.

[0152] In this example, if the business logic processing module receives the fourth flight SMS fence trigger event reported by the context awareness module, it will continue as described above. Figure 2 After steps S302 to S304, the business logic processing module detects for the fourth time that the flight SMS message is missing and that there is no authorization relationship between the authorization object and the specific application account. The fourth detection time is recorded as T3. The business logic processing module obtains Th=T2, N=2. The business logic processing module determines the second preset interval duration as 2*24 hours based on N. If the time (T3-T2) between the fourth detection time T3 (i.e., the time when the fourth detection time T3 is detected to have information missing and that there is no authorization relationship between the authorization object and the specific application account) and the time T2 is greater than 2*24 hours, then it is determined that the fourth detection time T3 is detected to have information missing and that there is no authorization relationship between the authorization object and the specific application account, and the guidance information is displayed. Figure 6 The intermediate interval C is greater than or equal to 2*24 hours.

[0153] In this example, if the business logic processing module receives the event triggered by the SMS fence of the fifth flight from the context awareness module, it will continue as described above. Figure 2 The business logic processing module can detect whether the cumulative number of times reaches a preset number threshold. In this example, Figure 6 As shown, the number threshold is 3 times, and the cumulative number N=3, which is equal to the number threshold, then the business logic processing module instructs the business presentation module to cancel the displayed guidance information.

[0154] In this example, a threshold number is set, and the business logic processing module cancels the displayed guidance information to avoid excessive guidance information for users, thereby improving the user experience.

[0155] It is understandable that, in order to implement the above functions, the electronic device includes hardware and / or software modules that perform the corresponding functions. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0156] This embodiment also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-described method steps to implement the travel reminder method described in the above embodiment. Storage media include various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0157] This embodiment also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the travel reminder method in the above-mentioned embodiment.

[0158] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0159] Any content of each embodiment of this application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of this application.

[0160] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A travel reminder method, characterized in that: Applied to electronic equipment, the method includes: When it is detected that the electronic device has received a flight SMS, a trigger is provided to detect whether there is any missing information in the flight SMS and whether there is an authorization relationship between an authorization object and a user account of the user in a specific application, wherein the authorization object includes the user account of the user in a server corresponding to the electronic device or an identifier of the electronic device, and the specific application is used to obtain the user's flight information from servers corresponding to at least two airlines; When it is detected that information in the flight SMS message is missing and no authorization relationship exists between the authorization object and the user account of the user in the specific application, determining whether to perform an operation of displaying guidance information for the Nth time, the guidance information being used to guide the user to perform an authorization operation so that a server corresponding to the specific application can establish an authorization relationship between the authorization object and the user account of the user in the specific application, where N is an integer greater than 0; If it is determined to perform the operation of displaying the guidance information for the Nth time, displaying the guidance information; After the authorization relationship is established, the electronic device obtains the user's flight information from the server corresponding to the specific application according to the authorization relationship and the authorization object, and provides travel reminders to the user on the electronic device based on the obtained flight information of the user; and the electronic device stops displaying the guidance information.

2. The method according to claim 1, characterized in that The detecting whether the flight SMS contains any missing information includes: Obtaining pre-stored basic information of a flight message, wherein the basic information of the flight message includes: flight number, departure date, departure place, and destination; Detecting whether any of the basic information of the flight text message is missing from the information of the flight text message; If it is detected that any item of the basic information of the flight text message is missing in the information of the flight text message, it is determined that there is information missing in the flight text message.

3. The method according to claim 1, characterized in that The determining whether to perform the operation of displaying the guidance information for the Nth time includes: Obtaining a difference between a time when the guidance information is displayed for the N-1th time and a first time, where the first time is a time when the flight SMS message is detected to be missing and no authorization relationship exists between the authorization object and the user account of the user in the specific application; Determining whether the difference is greater than an N-1th preset interval duration, where the N-1th preset interval duration is used to indicate a minimum interval duration between displaying the guidance information for the N-1th time and displaying the guidance information for the Nth time; If it is determined that the difference is greater than or equal to the N-1th preset interval duration, it is determined that the guidance information is displayed for the Nth time.

4. The method according to claim 3, characterized in that Before determining whether the difference is greater than the N-1th preset interval duration, the method further includes: Obtaining the cumulative number of times the guidance information is displayed; The N-1th preset interval duration is determined according to the accumulated number of times.

5. The method according to claim 4, characterized in that The determining, based on the accumulated number of times, the N-1th preset interval duration includes: Obtaining a product of the accumulated number of times and a preset fixed time length as a first product value; The first product value is used as the N-1th preset interval duration.

6. The method according to claim 4 or 5, characterized in that The method further comprises: Obtaining the time when the guidance information is displayed for the Nth time; updating the stored time of displaying the guidance information for the N-1th time to the time of displaying the guidance information for the Nth time; The stored value of the accumulated number of times is increased by 1.

7. The method according to claim 6, characterized in that The method further comprises: After the guidance information is displayed for the Nth time, in response to an ignore operation of the user, the time when the ignore operation is received is used as the time when the guidance information is displayed for the N-1th time, wherein the ignore operation is used to instruct to ignore the guidance information.

8. The method according to claim 4 or 5, characterized in that Before displaying the guidance information for the Nth time, the method further includes: Determining whether the cumulative number of times reaches a preset number threshold; If it is determined that the accumulated number of times reaches the number threshold, the Nth display of the guidance information is canceled.

9. The method according to claim 1, characterized in that The interval between two consecutive displays of the guidance information is a preset fixed time length.

10. The method according to claim 5, characterized in that After taking the first product value as the N-1th preset interval duration, the method further includes: Detecting whether the N-1th preset interval duration exceeds a preset interval threshold; If it is detected that the N-1th preset interval duration exceeds the interval threshold, the N-1th preset interval duration is set as the interval threshold.

11. The method according to claim 1, wherein The method further comprises: In response to the user's authorization operation, detecting whether the user's user account in the specific application is in a logged-in state; When it is detected that the user is logged in to the user account of the specific application, the page is redirected to the authorization page for the user to agree to the authorization operation or cancel the authorization operation.

12. The method according to claim 1, characterized in that Before detecting whether a flight SMS message is received, the method further includes: It is detected that no authorization relationship exists between the authorization object and the user account of the user in the specific application.

13. An electronic device, characterized in that: include: one or more processors; Memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device executes the travel reminder method according to any one of claims 1 to 12.

Images