CN115016713B

CN115016713B - Travel event subscription method and electronic equipment

Info

Publication number: CN115016713B
Application number: CN202111452190.7A
Authority: CN
Inventors: 田舒; 陈志辉; 李若愚
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2023-11-24
Anticipated expiration: 2041-11-30
Also published as: CN115016713A

Abstract

The application provides a travel event subscription method and electronic equipment, wherein the method comprises the following steps: and the electronic equipment responds to the received triggering operation of the first application, and runs the first service of the first application. The electronic device may determine whether the first service is a taxi taking service based on the identification of the first service. When the first service is a taxi taking service, the electronic device may subscribe to an event of a specified type occurring in a first window to which the service belongs, and determine that a user uses the first service to take a taxi when detecting that the event of the specified type occurring in the first window includes a first target event. The electronic equipment can record that the service corresponding to the driving behavior is the first service of the first application, and recommend the first service of the first application when the user needs to drive, so that a more accurate driving application recommendation mode meeting the user needs is provided, and the user experience is effectively improved.

Description

Travel event subscription method and electronic equipment

Technical Field

The application relates to the field of terminal equipment, in particular to a travel event subscription method and electronic equipment.

Background

With the development of the field of terminal equipment, the variety of applications in the terminal is more and more, and the application scene is more and more extensive. Some travel application software, such as third party application software, such as taxi taking software, can provide taxi taking services for users. In some scenarios, the cell phone may provide a quick launch application portal such that a user may quickly launch a taxi service through the portal. However, the taxi taking software associated with the quick start application portal of the mobile phone is usually fixed, the recommendation mode is single, and the user experience is poor.

Disclosure of Invention

The application provides an optimized travel event subscription method and electronic equipment.

In some embodiments provided by the application, the electronic device can detect the driving event of the application, so that the appropriate driving software can be recommended according to the use condition of the user to meet the user requirement.

For example, in some scenarios, the electronic device may make a travel reminder for a flight of the user, such as popping up a travel reminder card. In order to improve the use experience of the user, a taxi taking software interface can be provided in the travel reminding card, so that the user jumps to corresponding taxi taking software by clicking taxi taking options in the card. For example, the electronic device may associate the taxi taking option with any application having a taxi taking function in the mobile phone, so that after clicking the taxi taking option, the user may jump to the interface of the taxi taking service of the associated application. For example, when the electronic device selects the associated taxi taking software, the electronic device may also refer to the use condition of the application with the taxi taking function in the mobile phone by the user to determine the associated application. Different people have different behavior habits, so that different end users have differences in driving and traveling. When the user wants to drive, the user can provide personalized recommendation service for the user according to the drive software which is frequently or last used by the user. However, many APP's are not limited to a single service function, and for traffic and competitiveness, one APP often has multiple functions, and driving may be only one of the sub-functions. Therefore, there is no way to determine what APP the user actually uses to drive by counting the APP package names used by the user. Some embodiments of the application provide a method for sensing the use condition of the taxi taking software of a user, and comprehensively determining the real use condition of the taxi taking software of the user through APP package names and page detection of taxi taking operation of the user after opening a designated APP.

In a first aspect, an embodiment of the present application provides a method for subscribing to a travel event. The method comprises the following steps: and the electronic equipment responds to the received triggering operation of the first application, and runs the first application, wherein the interface of the running first application is displayed as the interface of the first service. The electronic device obtains an identification of a first service, wherein the identification of the first service comprises an identification of a first application and an Activity identification of the first service. The electronic device determines that the first service is a taxi taking service based on the identification of the first service. The electronic device subscribes to a specified type of event that occurs in a first window to which the first service belongs. When a first target event occurs in a first window to which the first service belongs, the electronic device may determine that the user uses the first service of the first application to perform a taxi taking event, and store the taxi taking event performed by the user using the first service of the first application as a record in the taxi taking record. The first target event is an event of a specified type subscribed to by the electronic equipment. And the electronic equipment recommends the user to use the first service of the first application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user by using the first service of the first application meets the preset condition according to the driving record. In this way, the electronic device may determine whether the running service is a service having a taxi taking function based on the identification of the service of the running application. If the service is a service with a taxi taking function, the specified event which occurs in the window to which the service belongs can be further detected, so that whether the user takes a taxi by using the taxi taking function of the service or not is determined based on the detected specified event, accurate detection of taxi taking behavior is achieved, and under the condition that the user is determined to actually take a taxi by using the running service, the electronic device can generate a taxi taking record so as to indicate that the service used by the user for taking a taxi for the first time is the first service of the first application. Correspondingly, when the taxi taking software needs to be recommended, the electronic equipment can recommend taxi taking software meeting preset conditions from taxi taking software which is used by a user for taking a taxi according to the stored taxi taking record. Therefore, on the premise of improving the accuracy of the taxi taking behavior detection, the accuracy of software recommendation can be improved, the recommended software can be more fit with the requirements of users, and the use experience of the users is improved.

According to a first aspect, determining, according to the taxi taking record, that the record of the taxi taking event performed by the user using the first service of the first application satisfies the preset condition includes: the electronic device determines that the frequency of recording of the driving event by the user using the first service of the first application is highest in the driving records by determining that the driving event by the user using the first service of the first application is performed a plurality of times. Therefore, when the taxi taking software is recommended, the electronic equipment can determine the taxi taking software to be recommended based on the taxi taking frequency of the application used by the user, so that the accuracy of the taxi taking software propulsion is improved.

According to the first aspect, or any implementation manner of the first aspect, determining, according to the taxi taking record, that the record of the taxi taking event performed by the user using the first service of the first application meets the preset condition includes: the electronic device determines, according to the taxi taking record, that the record of the taxi taking event performed by the user using the first service of the first application is the latest record in the taxi taking record. Therefore, when the electronic equipment recommends the taxi taking software, the software for taking the taxi last time can be recommended to the user, and the accuracy of the taxi taking software is improved.

According to a first aspect, or any implementation manner of the first aspect, when a user needs to take a taxi, recommending that the user take a taxi using a first service of a first application, including: displaying a travel reminding card on a display screen of the electronic equipment, wherein the travel reminding card comprises travel reminding information and a taxi taking option; the travel reminding information comprises at least one of the following: road condition information, destination information and whole course time-consuming information; and the electronic equipment responds to the received operation of clicking the taxi taking option to display a display interface of the first service. Therefore, the electronic equipment can carry out travel reminding on travel modes such as flights and the like, and the corresponding travel reminding card is displayed. For convenience to the user, a taxi-taking option may be included in the travel reminder card to provide a quick portal associated with the taxi-taking software. The taxi taking software associated with the taxi taking options is taxi taking software which is recommended based on taxi taking records and used by a user.

According to a first aspect, or any implementation manner of the first aspect, the subscribing to the event of the specified type occurring in the first window to which the first service belongs includes: and acquiring the event of the appointed type, which occurs in the first window, through the barrier-free service of the electronic equipment. For example, the barrier-free service may periodically feed back a specified type of event that occurs in a first window to which the electronic device subscribes. For example, the barrier-free service may feed back corresponding event information whenever a specified type of event occurs in the first window. For example, the barrier-free service may also feed back a specified type of event that occurs in the first window at a set minimum interval.

According to the first aspect, or any implementation manner of the first aspect above, the specified type includes at least one of: click event, window state change event. In this way, the electronic device detects whether a characteristic event corresponding to the driving event occurs or not through the click event and/or the window state change event of the first window to which the subscription service belongs, and further determines whether the running service drives or not based on the detection result.

According to a first aspect, or any implementation manner of the first aspect, the first window includes a first driving control and a second control, and the first target event is a click first driving control event; when a first target event occurs in a first window to which a first service belongs, determining that a user uses the first service in a first application to perform a taxi taking event comprises: and the electronic equipment receives the operation of clicking the second control. The electronic equipment acquires a second control clicking event which occurs in the first window through barrier-free service; the click second control event is a click event. The electronic device determines that the click second control event occurring in the first window is not the first target event. And the electronic equipment receives the operation of clicking the first taxi taking control and executes the taxi taking operation. And the electronic equipment acquires a first driving control clicking event which occurs in the first window through barrier-free service. The electronic device detects that a first driving control clicking event occurring in a first window is a first target event, and determines that a user uses a first service in a first application to perform a driving event. For example, the electronic device may preset a feature event corresponding to the first service, that is, the first target event. For example, the feature event corresponding to the first service may be the user clicking on the first drive control. Correspondingly, when the electronic device acquires that the clicking event occurs in the first window through the barrier-free service, whether the clicking event occurring in the first window is a characteristic event corresponding to the first service, namely, clicking the first driving control event can be further judged. If not, continuing to subscribe to the click event generated by the first window until the click event generated by the first window is detected to comprise the event of clicking the first taxi control, and determining that the user uses the first service of the first application to taxi. Therefore, by detecting the specific event, the accuracy of detecting the taxi taking event can be improved, so that the taxi taking software which is used by a user when the taxi taking software is recommended, namely the taxi taking event actually occurs, can be ensured, and the recommendation accuracy of the taxi taking software is further improved.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: the electronic equipment responds to the received triggering operation of the second application, and the second application is operated; the electronic equipment responds to the received triggering operation of the second service of the second application, and operates the second service; the electronic equipment acquires an identifier of a second service, wherein the identifier of the second service comprises an identifier of a second application and an Activity identifier of the second service; the electronic equipment determines that the second service is a taxi taking service based on the identification of the second service; the electronic equipment subscribes to the appointed type of event which occurs in the second window of the second service; when a second target event occurs in a second window to which the second service belongs, the electronic equipment determines that the user uses the second service of the second application to perform a taxi taking event, and the taxi taking event which is performed by the user using the second service of the second application is used as a record and stored in a taxi taking record, wherein the second target event is an event of a specified type; and the electronic equipment recommends the user to use the second service of the second application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user using the second service of the second application meets the preset condition according to the driving record. Therefore, the electronic equipment can change different recommendation software based on the use condition of the taxi taking software, so that the recommended software can be updated at any time according to the user requirements in different stages or different scenes during recommendation, and the requirements of the user are met.

According to the first aspect, or any implementation manner of the first aspect, the second window includes a second driving control, and when a second target event occurs in the second window to which the second service belongs, determining that the user uses the second service of the second application to perform the driving event includes: receiving an operation of clicking a second taxi taking control, executing a taxi taking operation, and displaying first prompt information by a second window; the first prompt message is used for prompting that the vehicle is being driven; acquiring a first prompt information event which occurs in a second window and is displayed through barrier-free service, wherein the first prompt information event is a window state change event; and detecting that the first prompt information event displayed in the second window is a second target event, and determining that the user uses the second service of the second application to perform the taxi taking event. In this way, the electronic device can detect whether the application has a driving event based on different feature events corresponding to different applications, namely, target events.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: responding to the received triggering operation of the third application, and running the third application; displaying an interface of a third service in an interface of a third application; acquiring an identifier of a third service, wherein the identifier of the third service comprises an identifier of a third application and an Activity identifier of the third service; determining a third service non-taxi taking service based on the identification of the third service; running a fourth service of the third application in response to the received operation of the third application; acquiring an identifier of a fourth service, wherein the identifier of the fourth service comprises an identifier of a third application and an Activity identifier of the fourth service; determining that the fourth service is a taxi taking service based on the identification of the fourth service; subscribing to an event of a specified type occurring in a fourth window to which a fourth service belongs; when a fourth window to which a fourth service belongs has a fourth target event, determining that a user uses a fourth service of a third application to perform a taxi taking event, and storing the taxi taking event which is performed by the user using the fourth service of the third application as a record in a taxi taking record, wherein the fourth target event is an event of a specified type; and recommending the user to use the fourth service of the third application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user using the fourth service of the third application meets the preset condition according to the driving record. For example, in some scenarios, the interface opened by the taxi taking software during running is the interface corresponding to the taxi taking service. In other scenarios, the interface displayed during the running of the application is not the interface corresponding to the taxi taking service, and in the using process, the user may trigger the taxi taking service of the application. The electronic device can detect whether the running service is a taxi taking application or not based on the identification of each service, so that the specified type of event is subscribed again under the condition that the taxi taking application is determined to be running, and the system power consumption is reduced.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: responding to the received triggering operation of the fifth application, and running the fifth application; the interface of the fifth application displays the interface of the fifth service; acquiring an identifier of a fifth service, wherein the identifier of the fifth service comprises an identifier of a fifth application and an Activity identifier of the fifth service; determining that the fifth service is a taxi taking service based on the identification of the fifth service; subscribing to an event of a specified type occurring in a fifth window to which a fifth service belongs; and within the preset duration, the fifth target event is not included in the events of the appointed type, which occur in the fifth window, and the fact that the user does not use the fifth service to drive the car is determined, wherein the fifth target event is the event of the appointed type. In this way, the electronic device sets the preset duration to limit the upper limit of the subscription duration, so that when the preset duration is reached, the subscription of the event of the designated type is stopped, the system power consumption is reduced, the interaction among modules is reduced, and the system resources are saved.

According to the first aspect, or any implementation manner of the first aspect, the preset duration is 3 minutes.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: the subscription to the specified type of event occurring in the fifth window to which the fifth service belongs is stopped.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: the subscription to the specified type of event occurring in the first window to which the first service belongs is stopped. The electronic device can stop subscribing to the event of the designated type after detecting the driving event, so as to reduce the system power consumption, reduce the interaction among modules and save the system resources.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: after the first application is closed, responding to the received triggering operation of the first application, and running the first application; the interface of the first application displays the interface of the first service; acquiring an identifier of a first service; determining that the first service is a taxi taking service based on the identification of the first service; subscribing to an event of a specified type occurring in a sixth window to which the first service belongs; responding to the received triggering operation of the sixth service of the first application, and running the sixth service; stopping subscribing to the event of the appointed type which occurs in the first window to which the first service belongs; acquiring an identifier of a sixth service, wherein the identifier of the sixth service comprises an identifier of a first application and an Activity identifier of the sixth service; based on the identification of the sixth service, it is determined that the sixth service is a non-taxi taking service. For example, the electronic device may determine whether the service is a taxi taking service based on the identification of the service. If the driving service of the application is switched to other services in the driving service running process, the electronic equipment can determine that the switched service is not the driving service based on the identification of the switched service. The electronic device may cease subscribing to a previous service to reduce system power consumption, and, in the event that it is determined that the switched service is not a taxi service, no subscription to the service is required.

According to a first aspect, or any implementation of the first aspect above, the first application is a taxi taking application.

According to a first aspect, or any implementation of the first aspect above, the first application is a food application.

In a second aspect, the present application provides an electronic device. The electronic device includes: one or more processors, memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the steps of: responding to the received triggering operation of the first application, and running the first application; displaying an interface of a first service in an interface of a first application; acquiring an identifier of a first service, wherein the identifier of the first service comprises an identifier of a first application and an Activity identifier of the first service; determining that the first service is a taxi taking service based on the identification of the first service; subscribing to an event of a specified type occurring in a first window to which a first service belongs; when a first window to which a first service belongs has a first target event, determining that a user uses the first service of a first application to perform a taxi taking event, and storing the taxi taking event, which is performed by the user using the first service of the first application, as a record in a taxi taking record, wherein the first target event is an event of a specified type; and recommending the user to use the first service of the first application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user by using the first service of the first application is determined to meet the preset condition according to the driving record.

According to a first aspect, the computer program, when executed by one or more processors, causes the electronic device to perform the steps of: determining that the record of the taxi taking event performed by the user by using the first service of the first application meets the preset condition according to the taxi taking record comprises: the method comprises the steps of determining that the frequency of recording of the driving event by the user using the first service of the first application is highest in the driving records by determining that the driving event by the user using the first service of the first application is performed a plurality of times.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: determining that the record of the taxi taking event performed by the user by using the first service of the first application meets the preset condition according to the taxi taking record comprises: and determining that the record of the driving event performed by the user by using the first service of the first application is the latest record in the driving records according to the driving records.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: displaying a travel reminding card on a display screen of the electronic equipment, wherein the travel reminding card comprises travel reminding information and a taxi taking option; the travel reminding information comprises at least one of the following: road condition information, destination information and whole course time-consuming information; and responding to the received operation of clicking the taxi taking option, and displaying a display interface of the first service.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: and acquiring the event of the appointed type, which occurs in the first window, through the barrier-free service of the electronic equipment.

According to a second aspect, or any implementation of the second aspect above, the specified type includes at least one of: click event, window state change event.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: receiving an operation of clicking the second control; acquiring a second control clicking event which occurs in the first window through barrier-free service; clicking the second control event is a clicking event; judging that the event of clicking the second control, which occurs in the first window, is not a first target event; receiving an operation of clicking a first taxi taking control, and executing a taxi taking operation; acquiring a first taxi-clicking control event which occurs in a first window through barrier-free service; and detecting that the first driving control clicking event occurs in the first window as a first target event, and determining that the user uses a first service in the first application to perform the driving event.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: responding to the received triggering operation of the second application, and running the second application; responding to the received triggering operation of the second service of the second application, and running the second service; acquiring an identifier of a second service, wherein the identifier of the second service comprises an identifier of a second application and an Activity identifier of the second service; determining that the second service is a taxi taking service based on the identification of the second service; subscribing to a specified type of event occurring in a second window of a second service; when a second target event occurs in a second window to which the second service belongs, determining that the user uses the second service of the second application to perform a taxi taking event, and storing the taxi taking event which is performed by the user using the second service of the second application as a record in a taxi taking record, wherein the second target event is an event of a specified type; and recommending the user to use the second service of the second application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user using the second service of the second application meets the preset condition according to the driving record.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: receiving an operation of clicking a second taxi taking control, executing a taxi taking operation, and displaying first prompt information by a second window; the first prompt message is used for prompting that the vehicle is being driven; acquiring a first prompt information event which occurs in a second window and is displayed through barrier-free service, wherein the first prompt information event is a window state change event; and detecting that the first prompt information event displayed in the second window is a second target event, and determining that the user uses the second service of the second application to perform the taxi taking event.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: responding to the received triggering operation of the third application, and running the third application; displaying an interface of a third service in an interface of a third application; acquiring an identifier of a third service, wherein the identifier of the third service comprises an identifier of a third application and an Activity identifier of the third service; determining a third service non-taxi taking service based on the identification of the third service; running a fourth service of the third application in response to the received operation of the third application; acquiring an identifier of a fourth service, wherein the identifier of the fourth service comprises an identifier of a third application and an Activity identifier of the fourth service; determining that the fourth service is a taxi taking service based on the identification of the fourth service; subscribing to an event of a specified type occurring in a fourth window to which a fourth service belongs; when a fourth window to which a fourth service belongs has a fourth target event, determining that a user uses a fourth service of a third application to perform a taxi taking event, and storing the taxi taking event which is performed by the user using the fourth service of the third application as a record in a taxi taking record, wherein the fourth target event is an event of a specified type; and recommending the user to use the fourth service of the third application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user using the fourth service of the third application meets the preset condition according to the driving record.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: responding to the received triggering operation of the fifth application, and running the fifth application; the interface of the fifth application displays the interface of the fifth service; acquiring an identifier of a fifth service, wherein the identifier of the fifth service comprises an identifier of a fifth application and an Activity identifier of the fifth service; determining that the fifth service is a taxi taking service based on the identification of the fifth service; subscribing to an event of a specified type occurring in a fifth window to which a fifth service belongs; and within the preset duration, the fifth target event is not included in the events of the appointed type, which occur in the fifth window, and the fact that the user does not use the fifth service to drive the car is determined, wherein the fifth target event is the event of the appointed type.

According to a second aspect, or any implementation manner of the second aspect, the preset duration is 3 minutes.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: the subscription to the specified type of event occurring in the fifth window to which the fifth service belongs is stopped.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: the subscription to the specified type of event occurring in the first window to which the first service belongs is stopped.

According to a second aspect, or any implementation of the second aspect above, the computer program, when executed by the one or more processors, causes the electronic device to perform the steps of: after the first application is closed, responding to the received triggering operation of the first application, and running the first application; the interface of the first application displays the interface of the first service; acquiring an identifier of a first service; determining that the first service is a taxi taking service based on the identification of the first service; subscribing to an event of a specified type occurring in a sixth window to which the first service belongs; responding to the received triggering operation of the sixth service of the first application, and running the sixth service; stopping subscribing to the event of the appointed type which occurs in the first window to which the first service belongs; acquiring an identifier of a sixth service, wherein the identifier of the sixth service comprises an identifier of a first application and an Activity identifier of the sixth service; based on the identification of the sixth service, it is determined that the sixth service is a non-taxi taking service.

According to a second aspect, or any implementation of the second aspect above, the first application is a taxi taking application.

According to a second aspect, or any implementation of the second aspect above, the first application is a food application.

Any implementation manner of the second aspect and the second aspect corresponds to any implementation manner of the first aspect and the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation manner of the second aspect may be referred to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which are not described herein.

In a third aspect, embodiments of the present application provide a computer readable medium storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect.

Any implementation manner of the third aspect and any implementation manner of the third aspect corresponds to any implementation manner of the first aspect and any implementation manner of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation manner of the third aspect may be referred to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which are not described herein.

In a fourth aspect, embodiments of the present application provide a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect.

Any implementation manner of the fourth aspect and any implementation manner of the fourth aspect corresponds to any implementation manner of the first aspect and any implementation manner of the first aspect, respectively. Technical effects corresponding to any implementation manner of the fourth aspect may be referred to the technical effects corresponding to any implementation manner of the first aspect, and are not described herein.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processing circuit and a transceiver pin. Wherein the transceiver pin and the processing circuit communicate with each other via an internal connection path, the processing circuit performing the method of the first aspect or any one of the possible implementation manners of the first aspect to control the receiving pin to receive signals and to control the transmitting pin to transmit signals.

Drawings

Fig. 1 is a schematic diagram of a hardware structure of an electronic device exemplarily shown;

FIG. 2 is a schematic diagram of a software architecture of an exemplary electronic device;

fig. 3 is a flow chart of an exemplary travel event subscription method

FIG. 4 is a schematic diagram of an exemplary user interface;

FIG. 5 is a schematic diagram of an exemplary user interface;

FIG. 6 is a schematic diagram of an exemplary user interface;

FIG. 7 is a schematic diagram of an exemplary user interface;

fig. 8 is a schematic diagram of an exemplary user interface.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Fig. 1 shows a schematic configuration of an electronic device 100. It should be understood that the electronic device 100 shown in fig. 1 is only one example of an electronic device, and that 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. The various components shown in fig. 1 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.

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

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the application, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

Fig. 2 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present application.

The layered architecture of the electronic device 100 divides the software into several layers, each with a distinct role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is respectively an application program layer, an application program framework layer and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications such as smart travel services, taxi taking applications, food applications, perception modules, and the like.

Illustratively, the perception module operates resident or in a low power form, having the ability to perceive an external fact or environment, providing that ability to other modules in the form of a "fence". Such as "time-varying" time-fences, geo-location-aware "geo-location fences," etc. When the card reminding service is in an on state, the sensing module monitors the capacity (or matters such as specific time, specific place or specific event) registered by the service logic processing module, and if a user triggers one of the capacity, the sensing module sends a notification to the service logic processing module. In addition, the sensing module may also detect related events and acquire status of events from other application or application framework layers or system layers or kernel layers of the application layer through an API (application programming interface ), such as detecting bluetooth connection, network connection, monitoring user sms, customizing timers, etc.

By way of example, the smart travel service may include a business logic processing module and a business presentation module. The business logic processing module is used for core business calculation, subscribing different fences to the sensing module, sensing scene change according to fence events, combining user interaction information provided by the business presentation module, calling a rule or algorithm model defined by the business scene, and deciding which service information and presentation modes (cards, notices, earphone broadcasting and the like) are pushed to the user. And sending the service information to a service presentation module for presentation to the user. The business presentation module is used for user interface interaction and result display. The service presentation module can receive the display and disappearance instruction and corresponding data of the card, the notification, the earphone broadcasting and the like sent by the service logic processing module, and display or disappearance of the card, the notification and the broadcasting is carried out. And the service logic processing module is used for transmitting the user interaction information (such as user clicking, sliding card and the like) to the service logic processing module for making a next service decision. It may be understood that, in the embodiment of the present application, the display-related steps performed by the smart trip service are performed by the service presentation module, and the other steps are performed by the service logic processing module.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 2, the application framework layer may include a window manager, barrier-free services, and the like.

Illustratively, the window manager is configured to manage a window program, and may obtain an identifier of a running application and an Activity (Activity) identifier of a service of the running application.

The barrier-free service (Accessibility Service) is used for text-to-speech, haptic feedback, gesture navigation, track ball and directional navigation, and can provide barrier-free functions for applications, so that the applications are more barrier-free. One of the most important functions of the barrier-free service configuration parameters is to allow a developer to specify the type of barrier-free event that the barrier-free service can handle. Successful specification of this information enables collaboration among barrier-free services and allows developers to flexibly handle specific event types for specific applications. Event filtering may contain the following rules: package name and event type. The package name is an application package name specifying a barrier-free event for which barrier-free service processing is desired. If this parameter is omitted, the barrier-free service will be considered as a barrier-free event servicing any application. The event type is used to specify the type of barrier-free event that the developer wants the barrier-free service to handle. For example, types may include, but are not limited to: click events, window content changes, window state changes, scroll event operations, etc.

The kernel layer comprises: display drive, wi-Fi drive, bluetooth drive, audio drive, sensor drive, etc.

It will be appreciated that the layers and components contained in the layers in the software structure shown in fig. 2 do not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer layers than shown and may include more or fewer components per layer, as the application is not limited.

The travel event subscribing method in the embodiment of the present application is described in detail below with reference to a flowchart of the travel event subscribing method exemplarily shown in fig. 3. Referring to fig. 3, the method specifically includes:

s301, the intelligent travel service indication sensing module registers a travel fence.

In the embodiment of the present application, the subscription driving event is taken as an example for explanation, that is, the technical solution of the present application can accurately monitor whether the driving event occurs. The intelligent travel service can acquire whether each application installed in the mobile phone has a taxi taking function or not, and can also understand whether the taxi taking service is included or not.

For example, after the taxi taking application is installed in the mobile phone, the smart trip service can acquire the taxi taking application with the taxi taking function from the cloud or the description information of the taxi taking application. For another example, after the food application is installed in the mobile phone, the smart trip service may obtain that the food application has a taxi taking function (or taxi taking service) from the cloud or the description information of the food application. It should be noted that for a food application, the application includes a plurality of sub-services, including, for example, but not limited to: food search service, food ranking service, and taxi taking service. It is understood that the taxi taking service is one of the sub-services of the food application.

The intelligent travel service sends indication information to the sensing module, wherein the indication information can comprise application program identifiers of applications which are installed in the mobile phone and comprise the driving service, so that the sensing module is instructed to register a travel fence based on the application program identifiers indicated by the intelligent travel service, and the intelligent travel service can also be understood as being used for indicating the sensing module to monitor the appointed application program so as to monitor whether a driving event occurs.

In one possible implementation, the application indicated by the smart trip may be all applications installed in the cell phone that include the taxi taking service.

In another possible implementation, the application indicated by the smart trip may be an application in which the installed part of the cell phone contains a taxi taking service. For example, the mobile phone includes an application a, an application B and an application C, where the application a to the application C all include a taxi taking service, and the smart trip service has a protocol with owners of the application a and the application B, so that the application a and the application B can be recommended, and the application C does not allow the smart trip service to be recommended. Correspondingly, the intelligent travel service only subscribes to the taxi taking event of the application A and the application B so as to detect whether the taxi taking event exists in the application A and the application B, and does not subscribe to the taxi taking event of the application C. The indication information sent by the intelligent travel service to the perception module comprises the application program identification of the application A and the application program identification of the application B, but does not comprise the application program identification of the application C.

S302, a sensing module registers a travel fence.

Illustratively, the awareness module registers the travel fence based on the obtained application identification in response to the indication of the smart travel service.

In an embodiment of the present application, the travel fence may include a plurality of sub-fences, where the sub-fences may include, but are not limited to: application fencing, feature set fencing, and timing fencing.

The following describes the concept and registration of each fence (the triggering of each fence will be described in the following embodiments):

the application fence is used for monitoring the foreground application by the sensing module to detect whether the currently running foreground application is a designated application (namely, an application containing a taxi taking service), and further detect whether the designated application runs the taxi taking service after determining that the application is the designated application.

The sensing module may obtain, from the cloud, application identifiers of all applications including the driving service and Activity identifiers of the corresponding driving service after receiving the indication of the smart travel service.

Alternatively, the identification of the application may be the package name of the application. For example, the package name of the XX taxi taking application is XX taxi taking. The package name of the application is set by the application developer, and the application is not limited.

Optionally, the Activity identifier is used for indicating an identifier corresponding to the sub-function runtime in the application. An Activity identity may be understood as an Activity identity of each service (or function) run-time of an application. For example, using a chat application as an example, the mobile phone starts the chat application in response to a received user operation, the chat application starts and is displayed in the foreground, and a window Manager (possibly an Activity Manager) may obtain an application identifier of the chat application, for example, a "chat application". The chat application may initiate a taxi taking applet in response to a received user operation. The window manager can obtain the identification corresponding to the currently running activity (i.e. the taxi taking applet) of the chat application.

The sensing module may query an Activity identifier of the taxi taking service corresponding to the application identifier based on the application identifier indicated by the smart travel service, and register the application fence based on the application identifier and the Activity identifier of the taxi taking service, so as to monitor whether the taxi taking service in the application subscribed by the smart travel service is running.

In one possible implementation manner, after receiving the indication of the smart travel service, the sensing module may obtain, from the cloud, an Activity identifier of a taxi taking service corresponding to an application program indicated by the smart travel service

The feature set fence is used for monitoring the currently running taxi service by the sensing module to monitor whether the feature event indicated in the feature set occurs or not. And the sensing module determines whether a driving event occurs according to the monitoring result.

The sensing module may obtain a characteristic event of a driving event of each driving service from the cloud, which may be understood that when the driving service generates the characteristic event, the driving behavior may be considered to exist, that is, the driving event occurs.

Optionally, the sensing module may also obtain a feature event corresponding to the driving service of the application indicated by the smart trip service from the cloud.

In one possible implementation, the perception module may register feature set fences based on all feature events acquired from the cloud. In another possible implementation, the sensing module may register the feature set fence based on feature information of the taxi taking service corresponding to the application indicated by the smart trip service. In yet another possible implementation, the awareness module registers the feature set fence based also on feature events of the taxi taking service corresponding to the application triggering the application fence. The application is not limited.

Alternatively, the feature events may include, but are not limited to: click events and page status feature events, etc. For example, the click event may be used to indicate that the click event is monitored while the taxi taking service is running to monitor whether a corresponding click event exists. Taking the "XX taxi taking" application as an example, the characteristic event corresponding to the taxi taking service of the XX taxi taking application is clicking the "immediately called" option. Correspondingly, after the sensing module detects that the taxi taking service in the XX taxi taking application operates, the sensing module further detects that the 'immediately calling' option is triggered, and the feature set fence trigger can be determined.

For example, the page status feature event may be used to indicate that a page status transition at the time of operation of the taxi service is monitored to monitor whether a corresponding page status change exists. For example, in a food application (e.gApplication) is taken as an example, and the characteristic event corresponding to the taxi taking service of the food application (such as the taxi taking service in the 'beauty group' application) is that 'in order sending' content appears in the page. Correspondingly, after the perception module detects that the taxi taking service in the food application operates, the information of 'in order sending' in the page is further detected, and then the feature set fence trigger can be determined. Specific examples will be described in detail below.

It should be noted that the feature events of the driving service corresponding to different applications may be the same or different, and the present application is not limited thereto. For example, the cloud may maintain feature events corresponding to the taxi taking services of each application. The cloud can periodically push feature events corresponding to the driving service of each application to each terminal (including mobile phones, tablet devices and the like). The sensing module may also periodically request, from the cloud, a feature set corresponding to a taxi taking service of each application installed in the mobile phone. For example, the sensing module may send request information to the cloud, where the request information may include an application program identifier of the application indicated by the smart trip service in S301 and a version number of the application. It should be noted that, the version numbers of the applications may be different, and the corresponding feature information may also be different. The cloud responds to the request of the sensing module, and feeds back characteristic events of the taxi taking service corresponding to the appointed version of the appointed application to the mobile phone to which the sensing module belongs. The perception module may re-register the feature set fence based on the acquired feature events.

The intelligent trip service may also include timing fence information, where the timing fence information may include a timing duration, for example, 3 minutes, and may be set according to actual needs, and the application is not limited thereto, and the timing fence information is used to instruct the sensing module to register the timing fence based on the time indicated by the timing fence information. The specific triggering means will be described in detail in the following examples.

Illustratively, the sensing module registers the travel fence in response to the received indication information sent by the smart travel service, including: application fencing, feature set fencing, and timing fencing. It should be noted that in the embodiment of the present application, there is a sequence in executing the application fence, the feature set fence, and the timing fence. For example, after the application fence is triggered, the awareness module determines the application and the taxi service that triggered the application fence, and the awareness module registers the feature set fence and the timing fence to determine whether a taxi taking event occurred. Meanwhile, the sensing module monitors the time to monitor whether the time exceeds the time limit of the timing fence.

S303, the window manager detects application activity.

S304, the window manager sends the application identifier and the Activity identifier to the perception module.

Illustratively, as described above, the window manager may obtain an application identifier corresponding to the running application and an Activity identifier (e.g., may be an Activity class name) corresponding to the service that the application runs. The manner in which the window manager obtains the application identifier and the Activity identifier may refer to the related description in the prior art embodiment, and the present application is not repeated.

Optionally, the window manager may periodically send, to the awareness module, an application identifier of each application running in the period and an Activity identifier of each service.

Optionally, the window manager may also send the identifier of the running application and the Activity identifier to the awareness module in case of an Activity update. For example, when the taxi taking application is running, the window manager acquires the application program identifier of the taxi taking application and the Activity identifier of the currently running service, and the window manager sends the application program identifier and the Activity identifier of the taxi taking application to the perception module. For another example, a food product application runs and, in response to a received user operation, a food product search service interface is displayed. The window manager acquires an application program identifier of the food application and an Activity identifier of the food search service currently running. The window manager sends the application program identifier of the food application and the Activity identifier of the food search service to the perception module. And displaying a taxi taking service interface when the food application responds to the received user operation. The window manager acquires the application program identifier of the food application and the Activity identifier of the currently running taxi taking service. The window manager sends the application program identifier of the food application and the Activity identifier of the taxi taking service of the food application to the perception module.

It should be noted that, the Activity identifier of the "taxi taking service" in the embodiment of the present application may be the same or different for different applications. Under the condition that the Activity identifications of the taxi taking services of different applications are the same, the window manager can enable the perception module to distinguish the taxi taking services corresponding to the different applications based on the application identifications and the Activity identifications by sending the application identifications and the Activity identifications.

S305, detecting application fence triggering by the sensing module.

Illustratively, as described above, the awareness module registers the application fence based on the application identification and the Activity identification. The perception module identifies the application identifier and the Activity identifier sent by the window manager to determine whether the application identifier and the Activity identifier hit the application identifier and the Activity identifier in the application fence.

Illustratively, the sensing module initiates the timing fence after determining the application fence trigger, i.e., begins to count, optionally for 3 minutes.

S306, the perception module requests the applied event information from the barrier-free service.

Illustratively, the awareness module sends request information to the barrier-free service, where the request information includes, but is not limited to, an application identifier (e.g., an application package name) and an event type, for indicating that the barrier-free service feeds back to the awareness module a specified event that includes an application occurrence indicated by the application identifier.

Exemplary, as described above, types of events for barrier-free service monitoring include, but are not limited to: click events, window content changes, window state changes, scroll events, etc. In the embodiment of the application, the sensing module sends a registration request to the barrier-free service, wherein the registration request comprises event type information, and the event type information can include but is not limited to: window state change event type and click event type to instruct the barrier-free service to feed back window state change event and click event of the specified application to the perception module.

It should be noted that, in the embodiment of the present application, only the click event and the window state change event are described as examples. In other embodiments, the feature event may be of other types, for example, may be a window state change event, and accordingly, the awareness module may register the window state change type with the barrier-free service.

S307, the barrier-free service sends the event information of the application to the perception module.

For example, the barrier-free service may snoop the specified application (i.e., the application indicated by the application identification) based on the request of the awareness module to identify whether the specified event occurred. For example: click events, popups in windows, display state changes in windows, etc.

Illustratively, in an embodiment of the present application, the awareness module may indicate a minimum feedback interval to the barrier-free service, which may be 300ms, for example. That is, the barrier-free service may feedback the specified event of the application to the sensing module based on the indication of the sensing module, with a minimum interval of 300ms between feedback intervals. For example, if the barrier-free service continuously detects multiple click events within 300ms, the barrier-free service may only feed back the last click event within 300ms to the perception module to reduce the inter-module interaction power consumption.

For example, the barrier-free service detects the specified event of the application every time, and the interval between the barrier-free service and the specified time sent last time is greater than or equal to 300ms, and the barrier-free service sends event information to the sensing module, wherein the event information comprises the specified event occurring this time and the corresponding description information thereof.

In one possible implementation, the sensing module may indicate a feedback period to the barrier-free service such that the barrier-free service may periodically feedback to the sensing module specified events occurring within the period. For example, the barrier-free service periodically transmits event information specifying an application to the barrier-free service transmission perception module according to the instruction. The event information includes description information of a specified event occurring in the present period. Optionally, the descriptive information specifying the event includes, but is not limited to: event type (e.g., click event, page pop, etc.), event content, time of occurrence, etc.

In another possible implementation manner, the barrier-free service may feed back event information of the application to the perception module after detecting that the application has a specified event, where the event information includes description information of the specified event.

Optionally, if the event information fed back by the barrier-free service includes a plurality of click events, or the number of times of feeding back by the barrier-free service is more, for example, the feedback is more than 300ms, the processing period may be set by the sensing module when the sensing module processes the event information, for example, the processing period is 300ms, and the sensing module processes the event sent by the barrier-free service every 300 ms. For example, if the barrier-free service transmits 3 times of event information within 300ms, the sensing module processes the content in the received 3 rd time of event information only at the 300ms trigger time, and ignores the event information received in the first two times, so that the processing power consumption of the sensing module is reduced.

It should be noted that, as described above, the barrier-free service may actually monitor a plurality of event types, and after the sensing module indicates to the barrier-free service to monitor a specified event, the event information fed back by the barrier-free service to the sensing module only includes the specified event. For example, if the user clicks on the "determine call" option in the taxi service interface, the unobstructed service may detect a window state change. If the barrier-free service detects that the user slides the taxi taking service interface, the operation is not an event subscribed by the perception module, and the event information of the application sent to the perception module by the barrier-free service comprises clicking a 'determine taxi-calling' option, but does not comprise a sliding event.

It should be noted that, events acquired by the barrier-free service are all feedback-fed to the barrier-free service. For example, the barrier-free service may obtain all click events that occur with the taxi taking application through an interface with the taxi taking application. It should be further noted that, since events acquired by the barrier-free service are all feedback from the application, events acquired by the barrier-free service depend on the configuration of the application. For example, the taxi taking service of the food application includes an "immediate taxi taking" option, and the user can click on the "immediate taxi taking" option to call a taxi, and the taxi taking service responds to the received user operation to take a dispatch, and displays "in order sending" in an interface. When the food application feeds back to the barrier-free service, a click "get on car immediately" event may not be fed back to the barrier-free service due to the application configuration. Accordingly, if the perception module subscribes to the click event of the food application from the barrier-free service, and the barrier-free service does not acquire the click event of the click "immediately get on the car" option fed back by the food application, the perception module cannot detect the get on event of the get on service of the food application through the occurred click event. The perception module may register a window state change event with the barrier-free service, which may obtain the window display "in order send" content from the food application and send the event to the perception module. Correspondingly, the sensing module can generate a window state change event based on the taxi taking service of the food application, and the window state change content is 'in order sending', so that the taxi taking event of the taxi taking service of the food application is determined. That is, in the embodiment of the present application, based on different application configurations, a driving event occurs as well, and the driving service of the food application optionally needs to monitor whether the driving event occurs by changing the window state event. The taxi taking service of the taxi taking application can determine whether a taxi taking event occurs or not by clicking the event. The cloud can acquire characteristic events corresponding to the driving events of the driving services of the applications, for example, the characteristic events corresponding to the driving events of the driving services of the food applications are window state changes, and the content is in order sending. The characteristic event corresponding to the taxi taking service of the taxi taking application is a clicking event, and the content is as follows: click on the "determine call express" option.

S308, the sensing module detects feature set fence triggering.

Illustratively, the awareness module identifies information in event information for applications sent by the barrier-free service to detect whether a feature event indicated by the feature set fence is included.

In one example, if the sensing module detects that the event information of the application includes the feature event indicated in the feature set fence, the sensing module may determine that the feature set fence triggers, and perform S309.

In another example, if the sensing module detects that the application interface does not include the feature event indicated in the feature set fence, the sensing module continues to wait for the interface of the application fed back next time by the barrier-free service, and repeats the identifying step. Illustratively, as described above, the sensing module has initiated the timing fence, i.e., begins timing. And when the 3-minute timing is finished, if the sensing module still does not detect that the event information of the application comprises the characteristic event, ending the flow, and sending stopping feedback information to the barrier-free service by the sensing module, wherein the stopping feedback information comprises an application program identifier and is used for indicating the barrier-free service to stop feeding back the event information of the application.

In yet another example, if the sensing module is in the process of executing any step, the user closes the driving service and switches to other interfaces, including a desktop, a screen locking interface, a screen extinguishing interface, other application interfaces, other service interfaces of the current application, and the like. The window manager may detect an Activity switch, i.e., an Activity switch of the current taxi taking service to other activities. The window manager may indicate to the awareness module the Activity of the currently running service. The awareness module may determine that an Activity switch exists in response to an indication by the window manager. The sensing module finishes the current flow, and sends stopping feedback information to the barrier-free service, wherein the stopping feedback information comprises an application program identifier and is used for indicating the barrier-free service to stop feeding back event information of the application. The sensing module may re-execute the steps above for the new Activity to detect whether the new Activity is the Activity corresponding to the taxi taking service, and the specific description may refer to the above, which is not repeated herein.

S309, the perception module instructs the barrier-free service to stop feeding back the event information of the application.

Illustratively, the awareness module sends stopping feedback information to the barrier-free service, the stopping feedback information including an application identity for instructing the barrier-free service to stop feeding back event information for the application. The barrier-free service stops feeding back event information of the designated application to the perception module in response to the indication of the perception module. Illustratively, the sensing module releases the timing fence, i.e., stops timing.

It should be noted that the interaction between the perception module and the barrier-free service described in the embodiments of the present application is only a schematic example. In other embodiments, the awareness module may send a list of applications to the barrier-free service, where the list may include information such as an identification of applications (e.g., application package names) and event types to which the awareness module needs to subscribe, to indicate specified events that occur for applications in the barrier-free service feedback list. In the embodiment of the present application, the driving event corresponding to the driving service of the subscription application of the perception module is taken as an example for illustration only, in other embodiments, the perception module may subscribe to the designated event of other applications, and correspondingly, the perception module may send the application list to the barrier-free service for multiple times under the condition of meeting the requirement. Each time the perception module sends a list, the list comprises applications (such as taxi taking applications) to which taxi taking services currently need to be subscribed. Alternatively, when the sensing module stops feeding back event information of the driving application when the barrier-free service is required, the sensing module may remove the identification of the driving application in the list transmitted to the barrier-free service next time, that is, the application list transmitted next time does not include the identification of the driving application. The barrier-free service is based on the received application list and does not feed back event information of the taxi taking application to the perception module.

S310, the perception module indicates the application to execute the taxi taking operation to the intelligent travel service.

For example, after the sensing module detects the feature set fence trigger, it may determine that a driving event occurs in the driving service of the currently running application. The perception module sends indication information to the intelligent travel service, wherein the indication information can comprise application program identifiers so as to indicate that the application has a taxi taking event.

The smart travel service may determine that the application indicated by the application identification has a taxi taking event based on the indication of the awareness module. The smart trip service may save a taxi taking record of the application. Optionally, when the intelligent trip service needs to recommend the taxi taking service, detecting an application corresponding to the latest taxi taking record in the saved taxi taking records, and pushing the application by the intelligent trip service. Optionally, the smart trip service may also periodically perform statistics to obtain the application with the largest occurrence of the driving event in the mobile phone (which may also be understood as the application with the highest occurrence frequency of the driving event), so as to push the application to the user when the pushing is required.

It should be noted that, in the embodiment of the present application, before executing S302, the smart travel service registers a travel fence with the sensing module, where the travel fence includes a plurality of sub-fences. In other embodiments, the smart travel service may also register when the awareness module is required to monitor the designated fence. For example, the smart travel service may register an application fence with the awareness module. After the application fence triggers, the sensing module may indicate the application fence triggers to the smart travel service. The smart travel service sends feature set fence information and timing fence information to the sensing module in response to the indication of the sensing module for indicating the sensing module to register the feature set fence and the timing fence. The perception module registers the feature set fence and the timing fence in response to an indication of the smart travel service.

In one possible implementation, the cloud end stores all the identifications of the applications including the taxi taking service and the corresponding Activity identifications of the taxi taking service. The smart trip service may send request information to the cloud based on the application currently installed in the mobile phone, where the request information may include an identifier of the installed application. The cloud end can inquire the received application identification to determine an application set containing the taxi taking service, wherein the application set is included in the application installed in the mobile phone, and the cloud end feeds the identification of the application containing the taxi taking service back to the smart trip service. Correspondingly, the intelligent travel service can acquire the Activity identifier of the taxi taking service corresponding to the application containing the taxi taking service in the application installed on the mobile phone. For example, the indication information sent by the smart trip service to the sensing module may include application identification information including an application of the taxi taking service and a corresponding Activity identification of the taxi taking service, and the sensing module may register an application fence based on the received application identification and the Activity identification of the taxi taking service. Optionally, the smart trip service may acquire a feature event corresponding to the driving service from the cloud, and send the feature event to the sensing module. The perception module may register a feature set fence based on the feature events sent by the perception module. In other words, in the embodiment of the present application, the perception module may acquire the activity identifier and the feature event from the cloud, and in other embodiments, the information may be acquired by the smart trip service and indicated to the perception module, which is not limited by the present application.

The flow in fig. 3 is described in detail below in connection with specific embodiments. Referring to fig. 4 (1), an exemplary mobile phone display interface 401 includes one or more controls, including but not limited to: battery controls, network controls, application icon controls, and the like. Optionally, the application icon controls include, but are not limited to: a clock application icon control, a drive application icon control 402, a food application icon control 408, and the like. In this embodiment, the taxi taking application and the food application each include a taxi taking service. After the mobile phone is provided with the taxi taking application and the food application, the intelligent travel service can acquire the taxi taking application and the food application including the taxi taking service. The smart travel service may acquire an application identification of a driving application (hereinafter, simply referred to as a "driving application identification") and an application identification of a food application (hereinafter, simply referred to as a "food application identification").

The intelligent travel service sends indication information to the sensing module, wherein the indication information comprises a taxi taking application identifier and a food application identifier, so that the sensing module is instructed to register a travel fence based on the taxi taking application identifier and the food application identifier.

For example, as described above, the sensing module may obtain, from the cloud, all application program identifiers including applications of the taxi taking service and actigraphy identifiers of taxi taking services of the taxi taking application, including an Activity identifier of taxi taking services of the taxi taking application (hereinafter, abbreviated as "taxi taking application-taxi taking service actigraphy"), and an Activity identifier of taxi taking services of the food application (hereinafter, abbreviated as "food application-taxi taking service Activity"). The sensing module also obtains feature events corresponding to the taxi taking services of the applications from the cloud.

The perception module may register an application fence based on the indication of the smart travel service, based on the taxi taking application identification and the food application identification, to monitor whether the taxi taking service of the taxi taking application is running, and whether the taxi taking service of the food application is running.

The perception module is used for responding to the indication of the intelligent travel service and registering an application fence based on the taxi taking application identifier and the food application identifier.

With continued reference to fig. 4 (1), an exemplary user may click on the drive application icon control 402. And the mobile phone responds to the received user operation to run the taxi taking application. As shown in fig. 4 (2), the cellular phone displays a taxi taking application interface 403. The taxi taking application interface 403 includes, but is not limited to: a route display area 404, a vehicle type options box 405, and a "determine call express" option 406. In the embodiment of the present application, the selected vehicle type is exemplified by "express car" type, and the corresponding taxi taking confirmation option is the "determine call express car" option. In other embodiments, if the user selected vehicle type is a "taxi" type, the corresponding taxi-taking confirmation option may be displayed as a "confirm call taxi" option. For another example, if the user selects the vehicle type to be "taxi" and "express" types, the corresponding taxi taking confirmation option may be displayed as a "determine simultaneous call" option. The application is not limited.

Illustratively, as depicted in S303, the taxi taking service is initiated simultaneously with the initiation of the taxi taking application. The window manager can acquire an application identifier of a currently running taxi taking application, namely a taxi taking application identifier, and an Activity identifier of a taxi taking service of the taxi taking application, namely a taxi taking application-taxi taking service Activity identifier. Illustratively, the window manager sends indication information to the sensing module, where the indication information includes: a taxi application identifier and a taxi application-taxi service actvisual identifier.

Illustratively, the sensing module obtains the driving application identifier and the driving application-driving service actvisual identifier in response to the indication information sent by the window manager. The perception module matches the taxi taking application identifier and the taxi taking application-taxi taking service Activity identifier with the application identifier and the Activity identifier in the application fence, and determines that the matching is successful. That is, the application fence includes a taxi taking application identifier and a taxi taking application-taxi taking service actvisual identifier.

The perception module determines an application fence trigger. The sensing module registers a feature set fence based on the feature information acquired from the cloud, and the feature fence comprises feature information corresponding to all driving services acquired from the cloud. In this embodiment, the sensing module may obtain, from the cloud, feature information corresponding to a driving service of a current version of an application indicated by the smart trip service.

For example, the sensing module obtains feature information corresponding to the driving service of the driving application from the cloud end, where the feature information includes: clicking the option of 'determining to call express', clicking the option of 'determining to call simultaneously', clicking the option of 'determining to call taxi', clicking the option of 'determining to call special car', clicking the option of 'determining to call carpooling', clicking the option of 'reserving to get on the car' and the like. And the sensing module acquires feature information corresponding to the taxi taking service of the food application from the cloud, wherein the feature information comprises: "in order delivery".

As described above, the sensing module may determine that the currently running driving service is a driving service of the driving application, and correspondingly, the sensing module may register the feature set fence based on feature information corresponding to the driving service of the driving application, so as to monitor whether the driving service of the driving application has a driving event.

Illustratively, the awareness module sends a registration request to the barrier-free service, the registration request including an application identifier of the taxi taking application. The sensing module detects that characteristic events corresponding to the taxi taking service of the taxi taking application all belong to clicking event types, and correspondingly, the registration request can also comprise clicking event types so as to request the barrier-free service to feed back clicking events of the taxi taking application to the sensing module.

Illustratively, the sensing module registers a timing fence for a 3 minute period.

Referring to fig. 4 (2), the user clicks the "determine call to taxi" option, for example. The barrier-free service may detect clicking on the "determine call to taxi" option. The barrier-free service sends event information of the taxi taking application to the sensing module, wherein the event information comprises clicking events and description information of the clicking events of the taxi taking application, and the event information is shown in table 1:

TABLE 1

Text content: [ taxi taking]
	Event type: click event

Referring to table 1, exemplary event information includes event type information, i.e. click event type, and content of the event, for example: the clicking content [ taxi taking ] is used for indicating that the text corresponding to the clicking operation is taxi taking, that is, the user clicks the taxi taking option. For example, other description information may be further included in the event information, for example, a location of a "get on car" option, a size of an option, etc., which is not limited by the present application.

It should be noted that, in the embodiment of the present application, the content in the event information is only better illustrated in a list manner, and in other embodiments, the content fed back by the barrier-free service to the perception module may be in any form, which is not limited by the present application.

And the sensing module responds to the received event information of the taxi taking application and acquires a clicking event of the taxi taking application. The perception module matches the obtained click event with the feature information in the feature set fence, and determines that the click calling express option event is successfully matched. The sensing module can determine the triggering of the feature set fence, namely the occurrence of a driving event of the driving application. The sensing module releases the timing fence.

The sensing module sends a stopping feedback request to the barrier-free service, wherein the request comprises driving application identification information so as to indicate the barrier-free service to stop feeding back event information of the driving application.

Referring to fig. 4 (3), the taxi taking application performs a taxi taking operation in response to the received operation of clicking on the "call taxi" option, for example, the taxi taking application transmits order information, and the taxi taking application displays the order-in information 407 in the interface 403 to prompt the user that a taxi is being dispatched.

Illustratively, the awareness module indicates to the smart travel service that the taxi taking application is experiencing a taxi taking event. The intelligent travel service can store a taxi taking record in the memory, and an application indicating that the taxi taking event occurs last time in the taxi taking record is a taxi taking application.

Alternatively, the smart travel service may provide a travel reminder service. The intelligent travel service can execute travel reminding on flights of the user so as to remind the user to travel in time. As shown in fig. 5 (1), the smart travel service may pop up the travel reminder card 502 in the display interface 501, for example. Travel reminder card 502 includes travel reminder information (e.g., road conditions, destination, time consuming whole journey, etc.) and drive options 5021. The user may click on the get-to option 5021. And the intelligent travel service responds to the received user operation, acquires the taxi taking record stored in the memory, and determines that the user uses the taxi taking application in the mobile phone for the last time. The smart travel service may invoke the taxi taking application to jump to the taxi taking application. Illustratively, as shown in fig. 5 (2), the handset jumps from the current interface 501 to the taxi taking application interface 503. The taxi-application interface 503 includes a route display area 504 and other controls. Illustratively, the origin in the route display area 504 may be the user's current location and the destination may be the destination indicated in the travel reminder card (e.g., a T3 terminal).

In one possible implementation, referring to (2) of fig. 5, the user may query the current road condition information through the taxi taking application, that is, the user does not click on the "determine call express" option while using the taxi taking application. As described above, the sensing module registers the timing fence, and within 3 minutes, the sensing module does not detect the feature set fence trigger, and the sensing module can request barrier-free service to stop feeding back the interface of the driving application, thereby reducing the power consumption of frequent interaction between modules.

Referring to fig. 6 (1), an exemplary mobile phone display 601 includes one or more controls, including but not limited to: battery controls, network controls, application icon controls, and the like. Optionally, the application icon controls include, but are not limited to: a clock application icon control, a taxi taking application icon control 602, a food application icon control 603, and the like.

As described above, the intelligent travel service indication sensing module registers the travel fence, and the specific implementation can refer to the related content above, which is not described herein.

With continued reference to fig. 6 (1), the user may click on the food application icon control 603, for example. And the mobile phone responds to the received user operation to run the food application. As shown in fig. 6 (2), the handset displays a food application interface 604 and enters a food recommendation service. The food product application interface 604 includes, but is not limited to: food recommendation information (including store name, rating, business information), geographic location information 605, drive options 6051, and the like.

The window manager obtains the application identifier of the currently running food application, namely the food application identifier and the Activity identifier of the currently running service, namely the food recommended service Activity identifier. The window manager sends the food application identifier and the food recommendation service Activity identifier to the perception module. The sensing module detects that the application fence does not comprise the food application identifier and the food recommendation service Activity identifier based on the food application identifier and the food recommendation service Activity identifier.

With continued reference to fig. 6 (2), the user clicks on the enter option 6051, for example. As shown in fig. 6 (3), the food service application displays a taxi taking service interface 606 in response to the received user operation. The taxi service interface 606 includes, but is not limited to: a route display area 607, a vehicle type options box 608, and an "instant call" option 609.

For example, the window manager may obtain an application identifier of the currently running food service, i.e., a food service identifier, and an Activity identifier of a taxi taking service of the food service, i.e., a food application-taxi taking service Activity identifier. Illustratively, the window manager sends indication information to the sensing module, where the indication information includes: a food application identifier and a food application-taxi service actvisual identifier.

Illustratively, the sensing module obtains the food application identifier and the food application-taxi taking service actvisual identifier in response to the indication information sent by the window manager. The perception module matches the food application identifier and the food application-taxi taking service actvisual identifier with the application identifier and the Activity identifier in the application fence, and determines that the matching is successful. That is, the application fence includes a food application identifier and a food application-taxi service actvisual identifier.

As described above, the sensing module may determine that the currently running taxi taking service is a taxi taking service of the food application, and correspondingly, the sensing module may register the feature set fence based on feature information corresponding to the taxi taking service of the food application, so as to monitor whether the taxi taking service of the food application has a taxi taking event.

Illustratively, the awareness module sends a registration request to the barrier-free service, the registration request including an application identifier of the food application. The sensing module detects that characteristic events corresponding to the taxi taking service of the food application all belong to window state change types, and correspondingly, the registration request can also comprise the window state change types so as to request the barrier-free service to feed back the window state change events of the food application to the sensing module.

Referring to fig. 6 (3), the user clicks the "get immediate" option, for example. As shown in fig. 6 (4), the taxi taking service of the food application displays an "in order send" prompt 610 in the taxi taking service interface 606 in response to the received user operation. The barrier-free service may obtain a change in the window status of the taxi service interface 606, i.e., obtain that the current window is an "in order send" hint.

Exemplary, when the barrier-free service detects that the window state change event occurs in the food application, the barrier-free service sends event information of the food application to the sensing module, wherein the event information comprises the window state change event occurring in the food application, and the event information is shown in table 2:

TABLE 2

Text content in order delivery
	Event type: window state change type

Referring to table 2, window state changes for the food applications include: "in order delivery". That is, the barrier-free service detects that a window state change event occurs in the current window of the food application (i.e., the window to which the driving service belongs), and the content of the window state change event is "in order sending". It should be noted that, the event information may also include other information corresponding to the window change event, for example, information for describing the window change event, including "in order sending" font color, font size, and the like, which is not limited by the present application.

The sensing module responds to the received event information of the food application and acquires a window state change event of the food application. The sensing module matches the acquired window state change event with the feature information in the feature set fence, and detects successful matching of the event in order sending. The sensing module can determine the triggering of the feature set fence, namely the occurrence of a driving event of the food application. The sensing module releases the timing fence.

For example, the sensing module sends a feedback stopping request to the barrier-free service, where the request includes a food application identifier to indicate the barrier-free service to stop feeding back event information of the food application.

Illustratively, the perception module indicates to the smart travel service that the food application is experiencing a drive-in event. The smart trip service may save the taxi taking record in memory, the application in the taxi taking record indicating the latest occurrence of the taxi taking event being a food application.

Optionally, when the smart travel service needs to provide a travel reminder, the smart travel service displays a travel reminder card, and the detailed description can refer to the above, and will not be repeated here. After clicking the taxi taking option in the taxi reminding card, the intelligent taxi taking service determines taxi taking software (such as taxi taking software used last time) meeting preset recommendation conditions as a food application based on the current taxi taking record. The smart travel service can call the food application, the display interface of the mobile phone can jump to the food application and directly enter the taxi taking service interface of the food application.

In the solution in the above embodiment, the sensing module may identify whether the application is getting a car based on a click event or a window state change event. In some embodiments, for some applications, the perception module may identify whether the application is getting on in conjunction with a click event and a window state change event. Referring now to FIG. 7 (1), a user clicks on the map application icon control 702 in the display interface 701. Referring to fig. 7 (2), the mobile phone displays a map application interface 703 in response to a received user operation. Included in the map application interface are a plurality of service options including, for example, a drive service option, a public transportation service option, a taxi service option 704, a ride service option, a walk service option, and more.

In the embodiment of the application, the feature events corresponding to the map application comprise click events and window state change events. For example, feature events include, but are not limited to: clicking on "get on option" and displaying "loading". And if other characteristic events occur between the two events, such as clicking on a "driving option", clicking on a "public transportation" option, etc., the detection of the driving event of the subscription map application is canceled. Referring still to fig. 7 (2), the window manager obtains an application identifier of the currently running map application, that is, a map application identifier, and an Activity identifier of the currently running service, that is, a main service Activity identifier of the map application.

It should be noted that, in the embodiment of the present application, the taxi taking service and other services of the application may have the same Activity. In a mapping application, the Activiti of services such as a main service, a driving service, a public transportation service, and a taxi taking service may be the same. Either service running may trigger the application fence.

Illustratively, the window manager sends the identity of the main service of the map application (i.e., the identity of the map application and the Activity identity of the main service) to the awareness module. The sensing module detects that the application fence comprises the identification based on the main service identification of the map application, and determines the triggering of the application fence.

The sensing module registers a feature set fence based on the feature information acquired from the cloud, and the feature fence comprises feature information corresponding to all driving services acquired from the cloud. In this embodiment, the sensing module subscribes to a feature fence, where the feature fence includes feature information corresponding to the map application, including but not limited to: clicking on "drive option" and displaying "loading" and, if other characteristic events occur between the two events, such as clicking on "drive option", clicking on "public transportation" option, etc., unsubscribing from the drive event detection of the map application. It will be appreciated that if the perception module detects that the user clicks on the "get on option", it further detects whether "loading" is displayed. If "loading" is displayed, a feature set fence trigger may be determined. If the user is detected to click the driving option after the user is detected to click the driving option, the process is ended, and the residual fence is released.

For example, referring to fig. 7 (2), after the main service is running, the sensing module determines the application fence trigger. The perception module sends a registration request to the barrier-free service, wherein the registration request comprises an application identifier of the map application. The sensing module detects that the characteristic event corresponding to the driving service of the map application comprises a click event type and a window state change type, and correspondingly, the registration request can also comprise the click event type and the window state change type so as to request the barrier-free service to feed back the click event and the window state change event of the map application to the sensing module.

Referring to fig. 7 (2), an exemplary user clicks the "drive" option. As shown in fig. 7 (3), the map application displays a driving service interface 705 in response to the received user operation. The driving service interface 705 includes a map display area, a "start navigation" option 706.

For example, the barrier-free service detects a user clicking on the "drive" option, and the barrier-free service sends event information of the map application to the perception module. The event information includes clicking on "driving" option event and other description information, and details not described herein are referred to above and will not be described herein.

For example, the sensing module determines that the event of clicking the "driving" option occurs in response to the received event information, and the sensing module ends the detection flow.

Referring to fig. 8 (1), the user clicks the map application icon control 802 in the display interface 801. Referring to (2) of fig. 8, the mobile phone displays a map application interface 803 in response to the received user operation. Illustratively, the window manager sends the identity of the main service of the map application (i.e., the identity of the map application and the Activity identity of the main service) to the awareness module. The sensing module detects that the application fence comprises the identification based on the main service identification of the map application, and determines the triggering of the application fence. The perception module registers click event types and window state change events of the map application with the barrier-free service. Specific details may be found in the description of fig. 7, which is not repeated here.

Referring to fig. 8 (2), an exemplary user clicks the enter option 804. As shown in fig. 8 (3), the map application displays a taxi taking service interface 805 in response to the received user operation. The taxi service interface 805 includes a map display area, a taxi type option box 806, a determine call taxi option 807, and the like.

The barrier-free service detects operation of the user clicking the get-on option 804 and sends event information to the perception module. The event information comprises clicking the "taxi taking option" event and description information thereof. The perception module may determine that the user clicks on the "get on option" based on the event information and further detect whether "loading" information is present. It should be noted that in the map application, the taxi taking service is similar to the food application described above, and does not feed back the operation of clicking the "determine call taxi" option by the user. Accordingly, the perception module may determine whether a taxi taking event has occurred based on the displayed "loading" information. However, as shown in fig. 7 (3), in the driving service, if the user clicks the "start navigation" option, the driving service also appears to be "loading" information. Therefore, the sensing module needs to combine the click event and the window state change event to determine whether the map application has a driving event, so that erroneous judgment is avoided.

Still referring to fig. 8 (4), by way of example, the user clicks on the "determine call to fast" option 807 and the taxi service displays "loading" information in response to a received user operation. The barrier-free service detects a window state change event and sends event information of the map application to the sensing module. The event information includes the display of "loading" and other descriptive information. The sensing module acquires the event which happens at the time based on the received event information, namely, displaying 'loading'. The sensing module matches the event with the feature event indicated in the feature set fence, and determines that the matching is successful, namely determines that the feature set fence is triggered.

For another example, if the user clicks the driving option 804, after the mobile phone displays the driving service interface 805 as shown in fig. 8 (3), the user exits the driving service interface and clicks the driving option in the main service interface 803. The barrier-free service detects a click event and sends event information of the map application to the sensing module. The event information comprises clicking on a driving option event and descriptive information thereof. The sensing module receives the event information and determines that the driving option event occurs after the driving option event is clicked, and the sensing module ends the detection flow. That is, after clicking the driving option, the user clicks the driving option, and even if the "loading" information appears in the driving service interface, the sensing module will not continue to detect the driving service interface, so as to prevent erroneous judgment. In other embodiments, the sensing module responds to the received event information to determine that the event of clicking the "driving option" occurs after the event of clicking the "driving option" occurs, and the sensing module can continue to time, if the sensing module detects that the event of clicking the "driving option" and displaying "loading" occurs before the timer is finished, and the event of clicking the "driving option" does not occur between the two events, the feature set fence trigger can be determined.

It may be understood that in the embodiment of the present application, the feature set fence may include valid feature information and invalid feature information, and after an event trigger in the valid feature information, for example, a trigger such as clicking a "get-on option" event, the sensing module may continue to monitor or determine that the feature set fence triggers. And when the event in the invalid characteristic information is triggered, the sensing module ends the detection flow.

In the embodiment of the present application, feature sets corresponding to different applications are the same or different, and the present application is not illustrated one by one.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the application, are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A travel event subscription method, characterized in that it is applied to an electronic device, the method comprising:

responding to the received triggering operation of the first application, and running the first application; displaying an interface of a first service in the interface of the first application;

acquiring an identifier of the first service, wherein the identifier of the first service comprises an identifier of the first application and an Activity identifier of the first service;

Determining that the first service is a taxi taking service based on the identification of the first service;

subscribing to a first taxi-clicking control event which occurs in a first window to which the first service belongs;

when the first service clicking event occurs in a first window to which the first service belongs, determining that the first service of the first application is used for driving the vehicle, and storing the driving event of the first service of the first application used by the user as a record in a driving record;

after subscribing to a first taxi-taking control event which occurs in a first window to which the first service belongs, if the first taxi-taking control event does not occur in the first window to which the first service belongs within a preset duration, determining that a user does not use the first service of the first application to perform the taxi-taking event, and stopping subscribing to the first taxi-taking control event which occurs in the first window to which the first service belongs;

after subscribing a first taxi-clicking control event which occurs in a first window to which the first service belongs, responding to a received triggering operation of a sixth service of the first application, running the sixth service, and stopping subscribing the first taxi-clicking control event which occurs in the first window to which the first service belongs;

Responding to the received triggering operation of the second application, and running a second service of the second application; wherein, the configuration of the first application and the second application is different, and the type of the taxi taking event which is subscribed to the window to which the taxi taking service belongs is related to the configuration of the application to which the taxi taking service belongs;

acquiring an identifier of the second service, wherein the identifier of the second service comprises an identifier of the second application and an Activity identifier of the second service;

determining that the second service is a taxi taking service based on the identification of the second service;

subscribing a window state change event which occurs in a second window to which the second service belongs, wherein prompt information corresponding to the window state change event is used for prompting that a taxi is being driven;

when the window state change event occurs in a second window to which the second service belongs, determining that a user uses the second service of the second application to perform a taxi taking event, and storing the taxi taking event, which is performed by the user using the second service of the second application, in a taxi taking record as a record;

after subscribing a window state change event which occurs in a second window to which the second service belongs, if the window state change event does not occur in the second window to which the second service belongs within a preset duration, determining that a user does not use the second service of the second application to perform a taxi taking event, and stopping subscribing the window state change event which occurs in the second window to which the second service belongs;

After subscribing a window state change event which occurs in a second window to which the second service belongs, responding to a received trigger operation of a seventh service of the second application, running the seventh service, and stopping subscribing the window state change event which occurs in the second window to which the second service belongs;

when the fact that the record of the taxi taking event carried out by the user by using the first service of the first application meets the preset condition is determined according to the taxi taking record, recommending the user to take a taxi by using the first service of the first application when the user needs to take a taxi, and displaying an interface of the first service in the first application in response to the operation of recommending options;

or recommending the user to use the second service of the second application to drive under the condition that the record of the driving event carried out by the user by using the second service of the second application meets the preset condition according to the driving record, and displaying an interface of the second service in the second application in response to the operation of the recommended option when the user needs to drive.

2. The method of claim 1, wherein determining from the taxi taking record that the record of the taxi taking event by the user using the first service of the first application satisfies a preset condition comprises:

And determining that the frequency of the record of the driving event by the user using the first service of the first application is highest in the driving records by determining that the driving event by the user using the first service of the first application is performed a plurality of times.

3. The method of claim 1, wherein determining from the taxi taking record that the record of the taxi taking event by the user using the first service of the first application satisfies a preset condition comprises:

and determining that the record of the driving event carried out by the user by using the first service of the first application is the latest record in the driving records according to the driving records.

4. A method according to any one of claims 1-3, wherein recommending that the user use the first service of the first application to drive when the user needs to drive, and displaying an interface of the first service in the first application in response to the operation of the recommended option, comprises:

displaying a travel reminding card on a display screen of the electronic equipment, wherein the travel reminding card comprises travel reminding information and a taxi taking option; the travel reminding information comprises at least one of the following: road condition information, destination information and whole course time-consuming information;

And responding to the received operation of clicking the taxi taking option, and displaying a display interface of the first service.

5. The method of claim 1, wherein subscribing to a click first drive control event that occurs in a first window to which the first service belongs comprises:

acquiring a first taxi-clicking control event which occurs in the first window through barrier-free service of the electronic equipment;

the event of changing window state of the second window to which the second service belongs is subscribed, which comprises

And acquiring a window state change event of a second window to which the second service belongs through the barrier-free service.

6. The method of claim 1, wherein the first window further comprises a second control; the method further comprises the steps of:

receiving an operation of clicking the second control;

acquiring the event of clicking the second control, which occurs in the first window, through barrier-free service; the event of clicking the second control is a clicking event;

and judging that the event of clicking the second control, which occurs in the first window, is not a characteristic event related to the driving operation based on the driving service.

7. The method of claim 1, wherein the second window includes a second drive control, and wherein the determining that a drive event was performed by a user using the second service of the second application when the window state change event occurred in the second window to which the second service belongs comprises:

Receiving the operation of clicking the second taxi taking control, executing the taxi taking operation, and displaying first prompt information by the second window; the first prompt message is used for prompting that the vehicle is being driven;

acquiring the first prompt information event displayed by the second window through barrier-free service of the electronic equipment, wherein the first prompt information event displayed is the window state change event;

and detecting the window state change event of the second window, and determining that a user uses the second service of the second application to perform a taxi taking event.

8. The method according to claim 1, wherein the method further comprises:

responding to the received triggering operation of a third application, and running the third application; displaying an interface of a third service in the interface of the third application;

acquiring an identifier of the third service, wherein the identifier of the third service comprises an identifier of the third application and an Activity identifier of the third service;

determining, based on the identification of the third service, that the third service is not a taxi taking service;

running a fourth service of the third application in response to the received operation of the third application;

Acquiring an identifier of the fourth service, wherein the identifier of the fourth service comprises an identifier of the third application and an Activity identifier of the fourth service;

determining that the fourth service is a taxi taking service based on the identification of the fourth service;

subscribing to an event of a specified type occurring in a fourth window to which the fourth service belongs;

when a target event occurs in a fourth window to which the fourth service belongs, determining that a user uses the fourth service of the third application to perform a taxi taking event, and storing the taxi taking event, which is performed by the user using the fourth service of the third application, as a record in a taxi taking record, wherein the target event is a taxi taking control clicking event or a window state change event;

and recommending the user to use the fourth service of the third application to drive when the user needs to drive under the condition that the record of the driving event carried out by the user using the fourth service of the third application meets the preset condition according to the driving record.

9. The method of claim 1, wherein the predetermined period of time is 3 minutes.

10. The method according to claim 1, wherein the method further comprises:

After the first application is closed, responding to the received triggering operation of the first application, and running the first application; the interface of the first application displays the interface of the first service;

acquiring an identifier of the first service;

and subscribing the operation event of clicking the first driving control, which occurs in the first window to which the first service belongs.

11. The method of claim 1, wherein the first application is a taxi taking application and the second application is a food application.

12. An electronic device, comprising:

one or more processors, memory;

and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the method of any of claims 1-11.