CN115016713A

CN115016713A - Travel event subscription method and electronic equipment

Info

Publication number: CN115016713A
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: 2022-09-06
Anticipated expiration: 2041-11-30
Also published as: CN115016713B

Abstract

The application provides a travel event subscription method and electronic equipment, wherein the method comprises the following steps: the electronic equipment responds to the received trigger operation of the first application and executes 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 equipment can subscribe the event of the specified type in the first window to which the service belongs, and when the event of the specified type in the first window is detected to include a first target event, the electronic equipment determines that the user takes a taxi by using the first service. The electronic equipment can record the service corresponding to the taxi taking action as the first service of the first application, and recommends the first service of the first application when the user needs to take the taxi, so that a taxi taking application recommendation mode which is more accurate and meets the user requirements is provided, and the user use experience is effectively improved.

Description

Travel event subscription method and electronic equipment

Technical Field

The present application relates to the field of terminal devices, and in particular, to a travel event subscription method and an electronic device.

Background

With the development of the field of terminal equipment, the application types in the terminal are more and more, and the application scenes are more and more extensive. The system comprises some travel application software, such as third-party application software such as taxi taking software, and can provide taxi taking service for users. In some scenarios, the handset may provide a quick-start application portal so that the user may quickly start the taxi service through the portal. However, taxi taking software associated with the quick start application entrance 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 taxi taking event of the application, so that the appropriate taxi taking 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 perform a travel reminder for the flight of the user, such as popping up a travel reminder card. In order to improve the user experience, a taxi taking software interface can be provided in the trip reminding card, so that the user can skip to corresponding taxi taking software by clicking a taxi taking option 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 the user may jump to a taxi taking service interface of the associated application after clicking the taxi taking option. For example, when the electronic device selects the associated taxi taking software, the electronic device may also refer to the use 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 terminal users have differences in taxi taking and traveling. When a user wants to take a taxi, the user can provide personalized recommendation service for the user according to taxi taking software frequently or last used by the user. However, many APPs are no longer limited to a single service function, and for traffic and competitiveness, one APP often has multiple functions, and a taxi taking function may be only one of the sub-functions. Therefore, it is impossible to determine what APP the user actually uses to take the car by simply counting the APP package names used by the user. Some embodiments of the application provide a method for sensing the use condition of taxi taking software of a user, and the taxi taking software condition actually used by the user is comprehensively determined through APP package name and page detection of taxi taking operation of the user after a specified APP is opened.

In a first aspect, an embodiment of the present application provides a travel event subscription method. The method comprises the following steps: the electronic equipment responds to the received trigger operation of the first application, and the first application is executed, wherein an interface of the first service is displayed in the interface of the executed first application. The electronic equipment acquires an identifier of the first service, wherein the identifier of the first service comprises an identifier of the first application and an Activity identity 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 occurring in a first window to which the first service belongs. When a first target event occurs in a first window to which a first service belongs, the electronic equipment can determine that a user uses the first service of a first application to take a taxi, and the taxi taking event of the user using the first service of the first application is stored in a taxi taking record as a record. The first target event is a specific type of event subscribed by the electronic equipment. The electronic equipment recommends the user to use the first service of the first application to take a taxi when the user needs to take the taxi under the condition that the record of the taxi taking event of the user by using the first service of the first application meets the preset condition according to the taxi taking record. In this way, the electronic device may determine whether the running service is a taxi-taking enabled service based on the identity of the service of the running application. If the service is the service with the taxi taking function, the specified event occurring in the window to which the service belongs can be further detected, whether the user takes a taxi by using the taxi taking function of the service is determined based on the detected specified event, so that accurate detection of taxi taking behaviors is achieved, and under the condition that the user is determined to actually take a taxi by using the running service, the electronic equipment can generate a taxi taking record to indicate the service used by the user in taxi taking at this time as the first service of the first application. Correspondingly, when 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 records. Therefore, on the premise of improving the accuracy of taxi taking behavior detection, the accuracy of software recommendation can be improved, the recommended software can better meet the requirements of users, and the user experience is improved.

According to a first aspect, determining that a record of a taxi-taking event performed by a user using a first service of a first application satisfies a preset condition according to a taxi-taking record comprises: the electronic equipment determines that the frequency of recording that the user uses the first service of the first application to carry out taxi taking events is the highest in taxi taking records by determining that the user uses the first service of the first application to carry out taxi taking events for multiple times. Therefore, when the electronic equipment recommends taxi taking software, taxi taking frequency can be determined based on the application used by the user, taxi taking software needing to be recommended is determined, and accuracy of propulsion of taxi taking software is improved.

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

According to the first aspect, or any implementation manner of the first aspect, when a user needs to take a taxi, recommending the user to take the taxi using a first service of a first application, includes: displaying a travel reminding card on a display screen of the electronic equipment, wherein the travel reminding card comprises travel reminding information and taxi taking options; the travel reminding information comprises at least one of the following: road condition information, destination information and whole-course time consumption information; the electronic equipment responds to the received operation of clicking the taxi taking option and displays a display interface of the first service. Therefore, the electronic equipment can remind the travel modes such as flights of going out and display corresponding travel reminding cards. For convenience of use by the user, the trip reminder card may include a taxi taking option to provide a quick entry associated with 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 the user once.

According to the first aspect, or any implementation manner of the first aspect above, subscribing to an event of a specified type occurring in a first window to which a first service belongs includes: and acquiring the events of the specified type occurring in the first window through the barrier-free service of the electronic equipment. For example, the barrier-free service may periodically feed back events of a specified type that occurred in a first window to which the electronic device is subscribed. For example, the barrier-free service may feed back corresponding event information every time an event of a specified type is detected in the first window. For example, the barrier-free service may also feed back the events of the specified type that occurred in the first window at a set minimum interval.

According to a first aspect, or any implementation of the first aspect above, the specified type comprises at least one of: click events, window state change events. In this way, the electronic device detects whether a characteristic event corresponding to the taxi taking event occurs or not by a click event and/or a window state change event occurring in the first window to which the subscription service belongs, and then judges whether the running service takes a taxi or not based on the detection result.

According to the first aspect, or any one implementation manner of the first aspect, the first window includes a first typing control and a second control, and the first target event is a first typing control event; when a first target event occurs in a first window to which a first service belongs, determining that a user makes a taxi taking event by using the first service in a first application comprises the following steps: and the electronic equipment receives the operation of clicking the second control. The electronic equipment acquires a second control clicking event occurring in the first window through barrier-free service; and clicking the second control event is a clicking event. The electronic equipment judges that the second control clicking 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. The electronic equipment acquires a first vehicle-hitting control piece event which occurs in the first window through barrier-free service. The electronic equipment detects that a first taxi taking control event which is clicked and occurs in the first window is a first target event, and determines that a taxi taking event is carried out by a user by using a first service in the first application. For example, the electronic device may preset a feature event corresponding to the first service, that is, the first target event. For example, the characteristic event corresponding to the first service may be that the user clicks the first typing control. Correspondingly, when the electronic equipment acquires that the first window has a click event through the barrier-free service, whether the click event occurring in the first window is a characteristic event corresponding to the first service or not can be further judged, namely, the first vehicle-driving control event is clicked. If not, continuing to subscribe the click event generated by the first window until the click event generated by the first window is detected to include the click first car driving control event, and determining that the user uses the first service of the first application to drive the car. Therefore, the accuracy of detecting the taxi taking event can be improved by detecting the specific event, so that the taxi taking software of the taxi taking event can be ensured to be used by a user once when the taxi taking software is recommended, namely the taxi taking software of the taxi taking event is really generated, and the recommendation accuracy of the taxi taking software is further improved.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: the electronic equipment responds to the received trigger operation of the second application and runs the second application; the electronic equipment responds to the received trigger operation of the second service of the second application and runs 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 identifier of the second service; the electronic equipment subscribes to a specified type of event which occurs in a second service second window; when a second target event occurs in a second window to which a second service belongs, the electronic equipment determines that a user uses the second service of a second application to perform a taxi taking event, and stores the taxi taking event 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 under the condition that the electronic equipment determines that the record of the taxi taking event of the user by using the second service of the second application meets the preset condition according to the taxi taking record, recommending the user to use the second service of the second application to take the taxi when the user needs to take the taxi. Therefore, the electronic equipment can replace different recommended software based on the service condition of taxi taking software, so that the recommended software can be updated at any time according to user requirements in different stages or different scenes during recommendation, and the user requirements are better met.

According to the first aspect, or any implementation manner of the first aspect, the determining that the user uses the second service of the second application to perform the taxi taking event when the second target event occurs in the second window to which the second service belongs includes: receiving an operation of clicking a second taxi taking control, executing taxi taking operation, and displaying first prompt information on a second window; the first prompt message is used for prompting that the car is being driven; acquiring a first prompt information display event occurring in a second window through barrier-free service, and displaying the first prompt information event as a window state change event; and when the first prompt information display event occurring in the second window is detected to be a second target event, determining that the user makes a taxi taking event by using a second service of the second application. In this way, the electronic device may detect whether a taxi taking event has occurred in the application based on different feature events, i.e., target events, corresponding to different applications.

According to the first aspect, or any implementation manner of the first aspect above, the method further includes: responding to the received trigger operation of the 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 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 is not a taxi taking service based on the identifier of the third service; in response to the received operation on the third application, executing a fourth service 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 the fourth service as a taxi taking service based on the identifier of the fourth service; subscribing the event of the specified type which occurs in a fourth window to which the fourth service belongs; when a fourth target event occurs in a fourth window to which the fourth service belongs, determining that the user uses the fourth service of the third application to take a taxi, and storing the taxi taking event of 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 under the condition that the record that the user uses the fourth service of the third application to take the taxi meets the preset condition according to the taxi taking record, recommending the user to use the fourth service of the third application to take the taxi when the user needs to take the taxi. In some scenarios, the interface opened by the taxi-taking software during running is an 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 equipment can detect whether the running service is the taxi taking application or not based on the identification of each service, and then subscribe the event of the specified type under the condition that the taxi taking application is determined to run, so that the power consumption of the system is reduced.

According to the first aspect, or any implementation manner of the first aspect above, the method further includes: in response to the received trigger operation on the fifth application, running the fifth application; the interface of the fifth application displays an interface of a 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 the fifth service as a taxi-taking service based on the identifier of the fifth service; subscribing the event of the specified type which occurs in a fifth window to which the fifth service belongs; and within the preset time length, determining that the user does not use a fifth service to take the taxi, wherein the fifth target event is the event of the specified type. Therefore, the electronic equipment limits the upper limit of the subscription duration by setting the preset duration, and stops subscribing the events of the specified type when the preset duration is reached, so as to reduce the system power consumption, reduce the interaction among modules and save the system resources.

According to a first aspect, or any implementation manner of the first aspect above, the preset time period is 3 minutes.

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

According to the first aspect, or any implementation manner of the first aspect above, the method further includes: stopping subscribing to the event of the specified type occurring in the first window to which the first service belongs. For example, after detecting a taxi taking event, the electronic device may stop subscribing to the event of the specified type, so as to reduce system power consumption, reduce interaction between modules, and save system resources.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: after the first application is closed, responding to the received trigger 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 identifier of the first service; subscribing the events of the specified type which occur in a sixth window to which the first service belongs; executing a sixth service of the first application in response to the received trigger operation on the sixth service; stopping subscribing the events of the specified type which occur 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 the first application and an Activity identifier of the sixth service; and determining that the sixth service is the non-taxi taking service based on the identification of the sixth service. For example, the electronic device may determine whether the service is a taxi service based on the identification of the service. If the taxi taking service is switched to other services in the running process of the taxi taking service, the electronic equipment can determine that the switched service is not the taxi taking service based on the identifier of the switched service. The electronic device may stop subscription to a previous service to reduce system power consumption, and may not need to subscribe to a switched service if it is determined that the service is not a taxi service.

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

According to a first aspect or any one of the above implementations of the first aspect, 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, and when executed by the one or more processors, cause the electronic device to perform the steps of: responding to the received trigger 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 identifier of the first service; subscribing the events of a specified type which occur in a first window to which the first service belongs; when a first target event occurs in a first window to which a first service belongs, determining that a user uses the first service of a first application to perform a taxi taking event, and storing the taxi taking event of 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 under the condition that the record that the user uses the first service of the first application to take the taxi meets the preset condition according to the taxi taking record, recommending the user to use the first service of the first application to take the taxi when the user needs to take the taxi.

According to a first aspect, the computer program, when executed by one or more processors, causes an 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 following steps: by determining that the user made the taxi taking event using the first service of the first application a plurality of times, it is determined that the frequency of the user making the record of the taxi taking event using the first service of the first application is the highest in the taxi taking 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: 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 following steps: and determining that the record of the taxi taking event of the user by using the first service of the first application is the latest record in the taxi taking records according to the taxi taking 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 trip reminding card on a display screen of the electronic equipment, wherein the trip reminding card comprises trip reminding information and taxi taking options; the travel reminding information comprises at least one of the following: road condition information, destination information and whole-course time consumption 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 events of the specified type occurring in the first window through the barrier-free service of the electronic equipment.

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

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 control; acquiring a second control clicking event occurring in the first window through barrier-free service; clicking the second control event to be a clicking event; judging that a second control clicking event occurring in the first window is not a first target event; receiving an operation of clicking a first taxi taking control, and executing taxi taking operation; acquiring a first vehicle-hitting control piece event which occurs in a first window through barrier-free service; and determining that the user uses the first service in the first application to carry out the taxi taking event when the first taxi taking control event clicked in the first window is detected as a first target 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 trigger operation of the second application, and running the second application; responding to the received trigger 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 the second service as a taxi-taking service based on the identifier 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 a second service belongs, determining that a user uses the second service of a second application to take a taxi, and storing the taxi-taking event of 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 under the condition that the record that the user uses the second service of the second application to take the taxi meets the preset condition according to the taxi taking record, recommending the user to use the second service of the second application to take the taxi when the user needs to take the taxi.

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 taxi taking operation, and displaying first prompt information on a second window; the first prompt message is used for prompting that the car is being driven; acquiring a first prompt information display event occurring in a second window through barrier-free service, and displaying the first prompt information event as a window state change event; and detecting that the first prompt information event displayed on the second window is a second target event, and determining that the user makes a taxi taking event by using a second service of the second application.

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 trigger operation of the 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 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 identifier of the third service; in response to the received operation on the third application, executing a fourth service 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 the fourth service as a taxi taking service based on the identifier of the fourth service; subscribing the event of the specified type which occurs in a fourth window to which the fourth service belongs; when a fourth target event occurs in a fourth window to which the fourth service belongs, determining that the user uses the fourth service of the third application to take a taxi, and storing the taxi taking event of 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 under the condition that the record that the user uses the fourth service of the third application to take the taxi meets the preset condition according to the taxi taking record, recommending the user to use the fourth service of the third application to take the taxi when the user needs to take the taxi.

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: in response to the received trigger operation on the fifth application, running the fifth application; the interface of the fifth application displays an interface of a 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 the fifth service as a taxi taking service based on the identifier of the fifth service; subscribing the event of the specified type which occurs in a fifth window to which the fifth service belongs; and within the preset time length, determining that the user does not use a fifth service to take a taxi if the fifth target event is not included in the specified type of events occurring in the fifth window, wherein the fifth target event is the specified type of event.

According to a second aspect, or any implementation manner of the second aspect, the preset time period 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: stopping subscribing to the event of the specified type occurring in the fifth window to which the fifth service belongs.

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: stopping subscribing to the event of the specified type occurring in the first window to which the first service belongs.

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 trigger 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 identifier of the first service; subscribing the event of the specified type which occurs in a sixth window to which the first service belongs; executing a sixth service of the first application in response to the received trigger operation on the sixth service; stopping subscribing the events of the specified type which occur 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 the first application and an Activity identifier of the sixth service; and determining that the sixth service is the non-taxi taking service based on the identification of the sixth service.

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

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

Any one implementation manner of the second aspect and the second aspect corresponds to any one implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one implementation manner of the second aspect and the second aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not repeated here.

In a third aspect, the present application provides a computer-readable medium for storing a computer program including instructions for executing the method of the first aspect or any possible implementation manner of the first aspect.

Any one implementation manner of the third aspect corresponds to any one implementation manner of the first aspect. For technical effects corresponding to any one implementation manner of the third aspect and the third aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not repeated here.

In a fourth aspect, an embodiment of the present application provides a computer program, where the computer program includes instructions for executing the method in the first aspect or any possible implementation manner of the first aspect.

Any one implementation manner of the fourth aspect and the fourth aspect corresponds to any one implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one implementation manner of the fourth aspect and the fourth aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not described here again.

In a fifth aspect, an embodiment of the present application provides a chip, which includes a processing circuit and a transceiver pin. Wherein the transceiver pin and the processing circuit are in communication with each other via an internal connection path, and the processing circuit is configured to perform the method of the first aspect or any one of the possible implementations of the first aspect to control the receiving pin to receive signals and to control the sending pin to send signals.

Drawings

Fig. 1 is a schematic diagram of a hardware configuration of an exemplary electronic device;

fig. 2 is a schematic diagram of a software structure of an exemplary electronic device;

FIG. 3 is a flowchart of an exemplary travel event subscription method

FIG. 4 is an exemplary illustrative user interface diagram;

FIG. 5 is an exemplary illustrative user interface diagram;

FIG. 6 is an exemplary user interface diagram;

FIG. 7 is an exemplary illustrative user interface diagram;

FIG. 8 is an exemplary user interface diagram.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 shows a schematic structural diagram 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: the mobile terminal includes a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. Wherein the sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 2 is a block diagram of a software structure 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 layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into an application layer, an application 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 a smart travel service, a taxi taking application, a gourmet application, and a perception module.

Illustratively, the perceiving module, which runs resident or in a low power form, has the ability to perceive external facts or circumstances, and provides this ability to other modules in the form of a "fence". Such as "time fences" to sense temporal changes, "geo-location fences" to sense geo-location, and the like. When the card reminding service is in an open state, the sensing module monitors the registered capability (or events, such as specific time, specific place, or specific event) of the service logic processing module, and if a user triggers one of the registered capability (or events), the sensing module sends a notification to the service logic processing module. In addition, the sensing module may also detect related events and obtain the state of the events from other application programs or application framework layers or system layers or kernel layers of the application program layer through an Application Programming Interface (API), such as detecting bluetooth connection, network connection, monitoring user short messages, customizing timers, and the like.

Illustratively, the intelligent travel service may include a business logic processing module and a business presentation module. The service logic processing module is used for core service calculation, subscribing different fences to the sensing module, sensing scene changes according to fence events, calling rules or algorithm models defined by service scenes in combination with user interaction information provided by the service presentation module, and deciding which service information to push to a user and display modes (cards, notifications, earphone broadcasting and the like). And sending the service information to a service presentation module to be displayed to the user. And the service presentation module is used for user interface interaction and result display. The service presentation module can receive the display and disappearance indication and corresponding data of the cards, the notifications, the earphone broadcasts and the like sent by the service logic processing module, and display or disappearance of the cards, the notifications and the broadcasts is carried out. And the system is used for transmitting user interaction information (such as user click, card sliding and the like) to the service logic processing module to make the next service decision. It should be understood that, in the embodiment of the present application, the display-related steps performed by the smart travel service are performed by the business presentation module, and other steps are performed by the business logic processing module.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program 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 used for managing the window program, and can acquire the identification of the running application and the Activity identification of the service of the running application.

The Accessibility Service (Accessibility Service) is used for text-to-speech, tactile feedback, gesture navigation, trackball and directional navigation, and can provide an Accessibility function for an application, so that the application is more accessible. One of the most important functions of the barrier-free service configuration parameters is to allow the developer to specify the types of barrier-free events that the barrier-free service can handle. Successfully specifying this information enables collaboration between barrier-free services and allows developers the flexibility to handle specific event types for specific applications. Event filtering may include the following rules: package name and event type. The package name is an application package name that specifies an unobstructed event that the unobstructed service is intended to handle. If the parameter is omitted, the barrier-free service will be treated as a barrier-free event that services any application. The event type is used to specify the type of barrier-free event that the developer wants barrier-free service processing. For example, types may include, but are not limited to: click events, window content changes, window state changes, scroll event operations, and the like.

The inner core layer includes: display driver, Wi-Fi driver, Bluetooth driver, audio driver, sensor driver, etc.

It is to be understood that the layers in the software structure shown in fig. 2 and the components included in each layer do not constitute a specific limitation of the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer layers than those shown, and may include more or fewer components in each layer, which is not limiting in the present application.

The following describes in detail a travel event subscription method in the embodiment of the present application with reference to a flow chart of the travel event subscription method exemplarily shown in fig. 3. Referring to fig. 3, the method specifically includes:

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

For example, in the embodiment of the application, a subscription taxi taking event is taken as an example for explanation, that is, the technical scheme in the application can accurately monitor whether a taxi taking 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 understand whether taxi taking service is included or not.

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

The intelligent travel service sends indication information to the sensing module, wherein the indication information can include an application program identifier installed in a mobile phone and containing the application of the taxi taking service, so that the sensing module is indicated to register the travel fence based on the application program identifier indicated by the intelligent travel service, and the indication sensing module can also be understood to monitor a specified application program to monitor whether a taxi taking event occurs or not.

In one possible implementation manner, the application program indicated by the smart trip may be all applications including taxi taking services installed in the mobile phone.

In another possible implementation manner, the application program indicated by the intelligent trip may include an application of taxi taking service for the installed part of the mobile phone. For example, the mobile phone includes an application a, an application B, and an application C, and the applications a to C all include a taxi-taking service, and the smart travel service has an agreement with owners of the applications a and B, and can recommend the application a and the application B, while the application C does not allow the smart travel service to be recommended. Correspondingly, the intelligent travel service only subscribes the taxi taking events of the application A and the application B to detect whether the taxi taking events exist in the application A and the application B, but does not subscribe the taxi taking events of the application C. The indication information sent by the smart 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, the sensing module registers a travel fence.

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

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

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

for example, the application fence is used for the sensing module to monitor the foreground application, so as to detect whether the currently running foreground application is a designated application (i.e., an application containing a taxi taking service), and after determining that the currently running foreground application is the designated application, further detect whether the designated application runs the taxi taking service.

For example, after receiving the indication of the smart travel service, the awareness module may obtain, from the cloud, application identifiers of all applications including the taxi-taking service and Activity identifiers of the corresponding taxi-taking service.

Alternatively, the identification of the application may be the package name of the application. For example, the name of the application package 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 to indicate an identifier corresponding to the sub-function runtime in the application. The Activity identifier can be understood as an Activity identifier when each service (or function) of the application runs. For example, taking a chat application as an example, the mobile phone starts the chat application in response to the received user operation, the chat application starts and is displayed in the foreground, and the window Manager (which may also be an Activity Manager) may obtain an application program identifier of the chat application, such as "chat application". The chat application may initiate a taxi cab applet in response to the received user operation. The window manager can obtain the identifier corresponding to the currently running activity (i.e., the car-playing applet) of the chat application.

For example, 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 to monitor whether the taxi taking service in the application subscribed by the smart travel service is running.

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

Illustratively, the feature set fence is used for the perception module to monitor the currently running taxi taking service to monitor whether a feature event indicated in the feature set occurs. And the sensing module determines whether a taxi taking event occurs according to the monitoring result.

For example, the sensing module may obtain a characteristic event of a taxi taking event of each taxi taking service from the cloud, and it may be understood that when the characteristic event occurs in the taxi taking service, a taxi taking behavior may be considered to exist, that is, a taxi taking event occurs.

Optionally, the sensing module may also obtain, from the cloud, a feature event corresponding to the taxi taking service applied by the smart travel service.

In one possible implementation, the perception module may register the feature set fence based on all feature events obtained from the cloud. In another possible implementation manner, 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 travel service. In yet another possible implementation manner, the sensing module also registers the feature set fence based on a feature event of the taxi taking service corresponding to the application triggering the application fence. The present application is not limited.

Alternatively, the characteristic 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 during the taxi service runtime to monitor whether a corresponding click event exists. For example, 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 "immediate taxi taking" option. Correspondingly, when the sensing module detects that the taxi taking service in the XX taxi taking application runs, the sensing module further detects that the 'call for taxi immediately' 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 the taxi taking service is monitored to monitor whether a corresponding page status change exists. For example, in a gourmet application (e.g., in a food service application)

Applications) for example, food applicationsThe characteristic event corresponding to the car service (such as the car taking service in the Mei Tuo application) is that the content of 'order sending' appears in the page. Correspondingly, when the sensing module detects that the taxi taking service in the gourmet application runs, the sensing module further detects that the information of order sending is in the page, and the triggering of the feature set fence can be determined. Specific examples will be described in detail below.

It should be noted that the characteristic events of the taxi taking 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 characteristic events corresponding to taxi taking services of each application. The cloud end can periodically push characteristic events corresponding to taxi taking services of all applications to all terminals (including mobile phones, flat panels and other devices). For example, the sensing module may also periodically request the cloud for a feature set corresponding to the taxi taking service of each application installed in the mobile phone. For example, the awareness module may send request information to the cloud, where the request information may include an application identifier of the application indicated in S301 by the smart travel service, and a version number of the application. It should be noted that, the application version numbers are different, and the corresponding feature information may also be different. The cloud end responds to the request of the perception module and feeds back the characteristic event of the taxi taking service corresponding to the specified version of the specified application to the mobile phone to which the perception module belongs. The perception module may re-register the feature set fence based on the obtained feature events.

Illustratively, the indication information sent by the smart travel service to the sensing module may further include timing fence information, where the timing fence information may include a timing duration, for example, 3 minutes, and may be set according to an actual requirement, and the timing fence information is used to indicate the sensing module to register the timing fence based on a time indicated by the timing fence information. The specific triggering mode 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, and includes: application fences, feature set fences, and timing fences. It should be noted that, in the embodiment of the present application, there is a precedence order in the execution of the application fence, the feature set fence, and the timing fence. For example, after the application fence is triggered, the sensing module determines the application and taxi taking service that triggered the application fence, and the sensing module registers the feature set fence and the timing fence to determine whether a taxi taking event occurs. Meanwhile, the sensing module monitors time to monitor whether the time exceeds the time length limited by the timing fence or not.

S303, the window manager detects application activity.

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

For example, as described above, the window manager may obtain an application identifier corresponding to the running application and an Activity identifier (which may be, for example, 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 is not described in detail herein.

Optionally, the window manager may periodically send the application identifiers of the applications running in the period and the Activity identifiers of the services to the awareness module.

Optionally, the window manager may also send the identity of the running application and the Activity identity to the awareness module in case of an Activity update. For example, when the taxi taking application runs, 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 gourmet application runs and, in response to a received user operation, displays a gourmet search service interface. The window manager acquires an application program identifier of the food application and an Activity identifier of the currently running food search service. And the window manager sends the application program identifier of the gourmet application and the Activity identifier of the gourmet search service to the perception module. And when the gourmet application responds to the received user operation, displaying a taxi taking service interface. The window manager acquires an application program identifier of the gourmet application and an Activity identifier of the taxi-taking service currently running. And the window manager sends the application program identifier of the gourmet application and the Activity identifier of the taxi taking service of the gourmet application to the sensing module.

It should be noted that, for different applications, the Activity identifiers of the "taxi taking service" described in the embodiment of the present application may be the same or different. 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 different applications based on the application identifications and the Activity identifications by sending the application identifications and the Activity identifications.

S305, the sensing module detects an application fence trigger.

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 identifiers and the Activity identifiers sent by the window manager to determine whether the application identifiers and the Activity identifiers hit the application identifiers and the Activity identifiers in the application fence or not.

For example, after determining that the application fence is triggered, the sensing module starts a timing fence, that is, starts timing, and the timing duration is optionally 3 minutes.

S306, the sensing module requests the event information of the application 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., application package name) and an event type, and is used to instruct the barrier-free service to feed back to the awareness module a specified event that includes the application occurrence indicated by the application identifier.

Exemplary, as described above, the types of events for barrier-free service monitoring include, but are not limited to: click events, window content changes, window state changes, scrolling events, and the like. In this embodiment of the present application, the sensing module sends a registration request to the barrier-free service, where the registration request includes event type information, and the event type information may include, but is not limited to: the window state change event type and the click event type to instruct the barrier-free service to feed back the window state change event and the click event of the specified application to the perceiving module.

It should be noted that, in the embodiment of the present application, only a click event and a window state change event are taken as examples for description. In other embodiments, the feature events may be of other types, for example, may be of window state change events, 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 sensing module.

For example, the barrier-free service may listen to a specific application (i.e., the application indicated by the application identification) based on a request from the awareness module to identify whether a specific event has occurred. For example: click events, pop-ups in windows, display state changes in windows, etc.

For example, in the embodiment of the present application, the sensing module may indicate a minimum feedback interval to the barrier-free service, for example, may be 300 ms. That is, the barrier-free service may feed back the specified event of the application to the perceiving module with a minimum interval of 300ms between two feedback intervals based on the indication of the perceiving module. 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 sensing module, so as to reduce the inter-module interaction power consumption.

Illustratively, each time the barrier-free service detects a specific event of an application and an interval between the specific event and the last sent specific time is greater than or equal to 300ms, the barrier-free service sends event information to the awareness module, where the event information includes the specific event that occurs this time and its corresponding description information.

In one possible implementation, the awareness module may indicate a feedback period to the barrier-free service, such that the barrier-free service may periodically feedback to the awareness module a specified event occurring within the period. Illustratively, the barrier-free service periodically sends event information specifying the application to the barrier-free service transmission awareness module as instructed. The event information includes description information of a specific event occurring in the present period. Optionally, the description information of the specified 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 the event information of the application to the awareness module after detecting that the application has a specific event, where the event information includes description information of the specific event.

Optionally, if the event information fed back by the barrier-free service includes multiple click events, or the number of times of the barrier-free service feedback is large, for example, the feedback is performed multiple times within 300ms, when the sensing module performs processing, a processing period may be set, 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 sends the event information 3 times within 300ms, the sensing module only processes the content in the received event information 3 times at the trigger time of 300ms, and ignores the event information received two times before, thereby reducing the processing power consumption of the sensing module.

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

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

S308, the sensing module detects feature set fence triggering.

Illustratively, the awareness module identifies information in the event information of the application 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 is triggered, and execute 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 that is fed back next time without being blocked, and repeatedly performs the above-mentioned identification step. Illustratively, as described above, the sensing module has started the timing fence, i.e., the timing is started. 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, the process is finished, the sensing module sends stop feedback information to the barrier-free service, and the stop 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 another example, if the sensing module closes the taxi taking 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 during the execution of any one of the above steps. The window manager may detect an Activity switch, i.e., an Activity switch of the current taxi-taking service to another Activity. The window manager may indicate to the awareness module the Activity of the currently running service. The awareness module, responsive to an indication by the window manager, may determine that an Activity switch exists. The sensing module finishes the current flow, the sensing module sends stop feedback information to the barrier-free service, and the stop 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. Moreover, the sensing module may re-execute the above steps on the new Activity to detect whether the new Activity is an Activity corresponding to the taxi taking service, and the specific description may refer to the above, which is not described herein again.

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

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

It should be noted that the interaction between the sensing module and the barrier-free service described in the embodiment of the present application is only an illustrative example. In other embodiments, the awareness module may send a list of applications to the barrier-free service, which may include information such as an identification of the application (e.g., application package name) and the type of event that the awareness module needs to subscribe to, to indicate the specified event that occurred for the application in the barrier-free service feedback list. For example, in the embodiment of the application, only the taxi taking event corresponding to the taxi taking service for which the sensing module subscribes the application is taken as an example for description, in other embodiments, the sensing module may subscribe to a specified event of other applications, and accordingly, the sensing module sends a multiple application list to the barrier-free service when the requirement is met. The list sent by the perception module each time includes applications (for example, taxi taking applications) to which taxi taking services which need to be subscribed currently belong. Optionally, when the sensing module needs the barrier-free service to stop feeding back the event information of the taxi-taking application, the sensing module may remove the identifier of the taxi-taking application in the list sent to the barrier-free service next time, that is, the identifier of the taxi-taking application is not included in the application list sent next time. The barrier-free service does not feed back the event information of the taxi taking application to the sensing module any more based on the received application list.

And S310, the perception module instructs an application to execute taxi taking operation to the intelligent travel service.

For example, after detecting the feature set fence trigger, the perception module may determine that a taxi-taking event occurs in a taxi-taking service of the currently running application. The sensing module sends indication information to the smart travel service, and the indication information can include application program identification to indicate that the application has a taxi taking event.

The intelligent travel service can determine that the application indicated by the application program identification has a taxi taking event based on the indication of the perception module. The wisdom trip service can save the record of taking a car of this application. Optionally, the smart travel service may detect an application corresponding to the latest taxi taking record in the stored taxi taking records when the taxi taking service needs to be recommended, and the smart travel service may push the application. Optionally, the smart travel service may also periodically perform statistics to obtain an application with the most taxi taking events in the mobile phone (which may also be understood as the application with the highest frequency of taxi taking events), so as to push the application to the user when pushing is needed.

It should be noted that, in the embodiment of the present application, before performing 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 sensing module is needed to monitor the designated fence. For example, the smart travel service may register an application fence with the awareness module. After the application fence is triggered, the perception module can indicate the application fence to trigger to the smart travel service. The intelligent travel service responds to the indication of the perception module, and sends feature set fence information and timing fence information to the perception module, and the feature set fence information and the timing fence information are used for indicating the perception 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 a smart travel service.

In a possible implementation manner, the cloud stores all identifiers including the application of the taxi taking service and the Activity identifier of the corresponding taxi taking service. The smart travel service can send request information to the cloud terminal based on the currently installed applications in the mobile phone, and the request information can include the identification of the installed applications. The cloud can inquire the received application identification to determine an application set containing the taxi taking service in the installed application of the mobile phone, and the cloud feeds the identification of the application containing the taxi taking service back to the intelligent travel service. Correspondingly, the intelligent travel service can obtain the Activity identification of the taxi taking service corresponding to the application of the taxi taking service in the installed application of the mobile phone. For example, the indication information sent by the smart travel service to the awareness module may include application identification information of an application including the taxi-taking service and an Activity identification of a corresponding taxi-taking service, and the awareness module may register the application fence based on the received application program identification and the Activity identification of the taxi-taking service. Optionally, the smart travel service may acquire a feature event corresponding to the taxi taking service from the cloud, and send the feature event to the perception module. The perception module may register the feature set fence based on the feature events sent by the perception module. That is to say, in the embodiment of the present application, the example that the awareness module can obtain the activity identity and the characteristic event from the cloud is taken as an example for description, and in other embodiments, the information may be obtained by the smart travel service and indicated to the awareness module, which is not limited in the present application.

The flow in fig. 3 will be described in detail with reference to specific examples. Referring to fig. 4 (1), for example, the display interface 401 of the mobile phone 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 402, a gourmet application icon control 403, and the like. In this embodiment, for example, the taxi taking application and the gourmet application both include taxi taking services. After the taxi taking application and the food application are installed on the mobile phone, the intelligent travel service can acquire the taxi taking application and the food application including the taxi taking service. The smart travel service may obtain an application identifier of the taxi taking application (hereinafter, simply referred to as "taxi taking application identifier") and an application identifier of the gourmet application (hereinafter, simply referred to as "gourmet application identifier").

The intelligent travel service sends indication information to the perception module, the indication information comprises a taxi taking application identifier and a food application identifier, and therefore the perception module is indicated to register the travel fence based on the taxi taking application identifier and the food application identifier.

For example, as described above, the awareness module may obtain, from the cloud, all application identifiers including the taxi taking application and the actvision identifier of the taxi taking application, where the Activity identifier of the taxi taking application is included (hereinafter, referred to as "taxi taking application-taxi taking service actvision identifier"), and the Activity identifier of the taxi taking service of the gourmet application (hereinafter, referred to as "gourmet application-taxi taking service Activity identifier"). Illustratively, the sensing module further acquires a characteristic event corresponding to the taxi taking service of each application from the cloud.

The perception module can register the application fence based on the taxi taking application identifier and the gourmet application identifier based on the indication of the smart travel service so as to monitor whether the taxi taking service of the taxi taking application runs and whether the taxi taking service of the gourmet application runs.

The perception module responds to the indication of the smart travel service and registers the application fence based on the taxi taking application identification and the food application identification.

Continuing with reference to fig. 4 (1), the user can, for example, click on the taxi taking application icon control 402. The mobile phone responds to the received user operation and runs the taxi taking application. As shown in (2) of fig. 4, the mobile phone displays a taxi taking application interface 403. Taxi taking application interface 403 includes, but is not limited to: a route display area 404, a vehicle type option box 405, and a "determine call express" option 406. It should be noted that, in the embodiment of the present application, the selected vehicle type is an "express" type, and correspondingly, the corresponding taxi taking confirmation option is an "call express determination" option. In other embodiments, if the vehicle type selected by the user is a "taxi" type, the taxi taking confirmation option may be displayed as a "confirm call taxi" option, accordingly. As another example, if the user selects the vehicle type as a "taxi" type and a "express" type, the taxi-taking confirmation option may be displayed as a "confirm simultaneous call" option, accordingly. The present application is not limited.

Illustratively, after the taxi taking application is started, the taxi taking service is started at the same time, as described in S303. The window manager can obtain an application identifier of the current running taxi taking application, namely the taxi taking application identifier, and an Activity identifier of a taxi taking service of the taxi taking application, namely the taxi taking application-taxi taking service ActViewity identifier. Illustratively, the window manager sends indication information to the perception module, where the indication information includes: the taxi taking application comprises a taxi taking application identifier and a taxi taking application-taxi taking service ActVisive identifier.

Illustratively, the sensing module responds to the indication information sent by the window manager to acquire the taxi taking application identifier and the taxi taking application-taxi taking service ActVITY identifier. The sensing module matches the taxi taking application identification and the taxi taking application-taxi taking service ActViewity identification with the application identification and the Activity identification in the application fence, and determines that matching is successful. Namely, the application fence comprises a taxi taking application identifier and a taxi taking application-taxi taking service ActViewiy identifier.

The awareness module determines an application fence trigger. The sensing module registers a feature set fence based on feature information acquired from the cloud, and correspondingly, the feature fence comprises feature information corresponding to all taxi taking services acquired from the cloud. In this embodiment, the sensing module may acquire, from the cloud, the feature information corresponding to the taxi taking service of the current version of the application indicated by the smart travel service.

For example, the obtaining, by the sensing module, the feature information corresponding to the taxi taking service of the taxi taking application from the cloud includes: clicking the option of 'determining to call express trains', clicking the option of 'determining to call simultaneously', clicking the option of 'determining to call taxis', clicking the option of 'determining to call special trains', clicking the option of 'determining to call shared trains', clicking the option of 'reserving to take trains', and the like. And the sensing module acquires the characteristic information corresponding to the taxi service of the gourmet application from the cloud, and the characteristic information comprises the following steps: "order in progress".

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

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

Illustratively, the perception module registers a timed fence for a 3 minute period.

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

TABLE 1

Text content: [ getting-off vehicle]
	Event type: click events

Referring to table 1, for example, the event information includes event type information, i.e. a click event type, and the content of the event, for example: the click content [ get the car ] is used for indicating that the text corresponding to the click operation is 'get the car', that is, the user clicks the 'get the car' option. For example, the event information may further include other description information, such as a location of a "taxi taking" option, a size of the option, and the like, which is not limited in the present application.

It should be noted that, in the embodiment of the present application, only the content in the event information is described in a list manner to better describe, in other embodiments, the content that the barrier-free service feeds back to the awareness module may be in any form, and the present application is not limited thereto.

The sensing module responds to the received event information of the taxi taking application and acquires a click event of the taxi taking application. And the sensing module matches the acquired click event with the feature information in the feature set fence and determines that the click-to-call express option event is successfully matched. The perception module can determine that the feature set fence is triggered, namely, the taxi taking event of the taxi taking application can be determined. The perception module releases the timing fence.

Illustratively, the sensing module sends a stop feedback request to the barrier-free service, where the request includes taxi-taking application identification information to indicate that the barrier-free service stops feeding back event information of the taxi-taking application.

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

Illustratively, the awareness module indicates to the smart travel service that the taxi taking application is about a taxi taking event. The intelligent travel service can save the taxi taking record in the memory, and the application indicating the latest taxi taking event in the taxi taking record is taxi taking application.

Optionally, the smart travel service may provide a travel reminder service. The smart travel service may perform travel reminders for the user's flight to remind the user to travel in time. As shown in (1) of fig. 5, for example, the smart travel service may pop up a travel reminder card 502 in a display interface 501. Travel reminder cards 502 include travel reminder information (e.g., road conditions, destination, time consumed all the way, etc.) and departure options 5021. The user may click the taxi taking option 5021. The intelligent travel service responds to the received user operation, obtains the taxi taking record stored in the memory, and determines that the taxi taking application in the mobile phone is used by the user in the last taxi taking. Wisdom trip service can call the application of taking a car to it uses to jump to take a car. Illustratively, as shown in fig. 5 (2), the cell phone jumps from the current interface 501 to the taxi-taking application interface 503. The taxi taking 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., the T3 terminal).

In one possible implementation manner, please refer to (2) of fig. 5, the user may query the current traffic information through the taxi taking application, that is, the user does not click the "determine to call for express" option when 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 may request the barrier-free service to stop feeding back the interface of the taxi-taking application, thereby reducing power consumption for frequent interaction between the modules.

Referring to fig. 6 (1), the display interface 601 of the mobile phone illustratively includes one or more controls, including but not limited to: battery controls, web 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 gourmet application icon control 603, and the like.

As described above, the smart travel service indication sensing module registers the travel fence, and the specific implementation can refer to the above related contents, which are not described herein again.

Continuing with reference to fig. 6 (1), the user can, for example, click on the gourmet app icon control 603. The mobile phone responds to the received user operation and runs the food application. As shown in (2) of fig. 6, the cell phone displays the food application interface 604 and enters the food recommendation service. The gourmet application interface 604 includes, but is not limited to: food recommendation information (including store name, rating, business information), geographic location information 605, taxi taking options 6051, and the like.

The window manager obtains an application identifier of a currently running food application, namely a food application identifier, and an Activity identifier of a currently running service, namely a food recommendation service Activity identifier. And 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.

Continuing with reference to fig. 6 (2), the user illustratively clicks on the vehicle option 6051. As shown in (3) of fig. 6, the gourmet application displays a taxi-taking service interface 606 in response to the received user operation. Taxi service interface 606 includes, but is not limited to: a route display area 607, a vehicle type option box 608, and an "call for immediate" option 609.

Illustratively, the window manager may obtain an application identifier of a currently running gourmet application, that is, a gourmet application identifier, and an Activity identifier of a taxi-taking service of the gourmet application, that is, a gourmet application-taxi-taking service ActViewity identifier. Illustratively, the window manager sends indication information to the perception module, where the indication information includes: the system comprises a food application identifier and a food application-taxi service ActVisive identifier.

Illustratively, the perception module acquires the gourmet application identifier and the gourmet application-taxi taking service Actvity identifier in response to the indication information sent by the window manager. The perception module matches the food application identification and the food application-taxi taking service ActViewity identification with the application identification and the Activity identification in the application fence, and determines that matching is successful. Namely, the application fence includes a gourmet application identifier and a gourmet application-taxi taking service ActViewity identifier.

For example, the obtaining, by the sensing module, the feature information corresponding to the taxi taking service of the taxi taking application from the cloud includes: clicking the option of ' determining to call for express train ', clicking the option of ' determining to call for simultaneous ' simultaneously ', clicking the option of ' determining to call for taxi ', clicking the option of ' determining to call for special train ', clicking the option of ' determining to call for shared train ', clicking the option of ' reserving to take train ', and the like. And the sensing module acquires the characteristic information corresponding to the taxi service of the gourmet application from the cloud, and the characteristic information comprises the following steps: "in order transmission".

As described above, the sensing module may determine that the taxi taking service currently running is the taxi taking service of the gourmet application, and accordingly, the sensing module may register the feature set fence based on feature information corresponding to the taxi taking service of the gourmet application to monitor whether a taxi taking event occurs in the taxi taking service of the gourmet application.

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

Referring to fig. 6 (3), illustratively, the user clicks on the "call car immediately" option. As shown in (4) of fig. 6, the taxi-taking service of the gourmet application displays a "order is being sent" prompt message 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 state of the window of the taxi-taking service interface 606, that is, obtain a prompt that the current window is "order sending in progress".

Illustratively, the barrier-free service detects that a window state change event occurs in the gourmet application, and the barrier-free service sends event information of the gourmet application to the sensing module, where the event information includes the window state change event occurring in the gourmet application, and the event information is shown in table 2:

TABLE 2

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

Referring to table 2, the window state change of the gourmet application includes: "in order transmission". That is, the barrier-free service detects that a window state change event occurs in the current window of the gourmet application (i.e., the window to which the taxi taking service belongs), and the content of the window state change event is "order sending in progress". It should be noted that the event information may also include other information corresponding to the window change event, for example, the information includes a font color and a font size of "sending an order" for describing the window change event, which is not limited in this 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. And the sensing module matches the acquired window state change event with the feature information in the feature set fence and detects that the event matching of 'order sending in progress' is successful. The perception module can determine that the feature set fence triggers, namely, determine that the food application takes a taxi taking event. The sensing module releases the timing fence.

Illustratively, the sensing module sends a feedback stopping request to the barrier-free service, where the request includes a gourmet application identifier to indicate that the barrier-free service stops feeding back event information of the gourmet application.

Illustratively, the perception module indicates to the smart travel service that a food application has taken a taxi-taking event. The intelligent travel service can save the taxi taking record in the memory, and the application indicating the latest taxi taking event in the taxi taking record is a food application.

Optionally, when wisdom trip service need provide the trip and remind, wisdom trip service shows the trip and reminds the card, and the specific description can refer to the above, and it is no longer repeated here. After the user clicks the taxi taking option in the trip reminding card, the smart trip service determines taxi taking software (such as taxi taking software used for the last time) meeting the preset recommendation condition as food application based on the current taxi taking record. The smart travel service can call the gourmet application, and the display interface of the mobile phone can jump to the gourmet application and directly enter the taxi taking service interface of the gourmet application.

In the above embodiments, the awareness module may identify whether the application takes a taxi based on a click event or a window state change event. In some embodiments, for some applications, the awareness module may identify whether the application is taking a taxi in conjunction with the click event and the window state change event. Referring to fig. 7 (1), a user clicks a map application icon control 702 in a display interface 701. Referring to fig. 7 (2), the mobile phone displays a map application interface 703 in response to the 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 drive service option 704, a ride service option, a walk service option, and more.

In the embodiment of the application, the characteristic events corresponding to the map application comprise a click event and a window state change event. For example, characteristic events include, but are not limited to: click on the "get the car option" and display "loading". And, if other characteristic events occur between the two events, such as clicking on the "drive option", clicking on the "public transportation" option, etc., then the taxi taking event detection subscribed to the map application is cancelled. By way of specific example, still referring to fig. 7 (2), after the map application runs, 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 may have the same Activity. For example, in a mapping application, activitis for services such as a main service, a driving service, a public transportation service, and a driving service may be the same. Either service running can trigger the application fence.

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

The sensing module registers a feature set fence based on feature information acquired from a cloud, and correspondingly, the feature fence comprises feature information corresponding to all taxi taking 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, and the feature information includes, but is not limited to: clicking on the "get-right option" and displaying "loading", and canceling the detection of a get-right event subscribed to the mapping application if other characteristic events occur between the two events, such as clicking on the "drive option", clicking on the "public transportation" option, etc. It will be appreciated that if the perception module detects that the user has clicked on the "get-around option", it further detects whether "loading" is being displayed. If the display is "loading," then a feature set fence trigger can be determined. If the user clicks the driving option after the user clicks the driving option, the process is ended, and the residual fence is removed.

For example, referring to (2) of fig. 7, after the main service runs, the sensing module determines an application fence trigger. The sensing 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 events corresponding to the taxi taking service of the map application comprise 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), illustratively, the user clicks on the "drive" option. As shown in (3) of fig. 7, the map application displays a driving service interface 705 in response to the received user operation. Driving service interface 705 includes a map display area, a "start navigation" option 706.

Illustratively, the barrier-free service detects a user's operation of clicking on the "drive" option, and the barrier-free service sends event information of the map application to the awareness module. The event information includes the click "drive" option event and other description information, and details which are not described can be referred to above, and are not described herein again.

Illustratively, the sensing module determines that an event of clicking the "driving" option occurs in response to the received event information, and the sensing module ends the detection process.

Referring to fig. 8 (1), the user clicks on the map application icon control 802 in the display interface 801. Referring to fig. 8 (2), the mobile phone displays a map application interface 803 in response to the received user operation. Illustratively, the window manager sends an identification of the primary service of the map application (i.e., an identification of the map application and an Activity identification of the primary service) to the awareness module. The sensing module detects that the application fence comprises the identifier based on the main service identifier of the map application, and determines that the application fence is triggered. The awareness module registers a click event type and a window state change event of the map application with the barrier-free service. The specific details can be referred to the description in fig. 7, and are not described herein.

Referring to fig. 8 (2), the user illustratively clicks on the hit car option 804. As shown in (3) of fig. 8, the map application displays a taxi taking service interface 805 in response to the received user operation. The taxi taking service interface 805 includes a map display area, a taxi taking type option box 806, a call for express option 807, and the like.

The barrier-free service detects the operation of the user clicking the taxi taking option 804 and sends event information to the sensing module. The event information comprises a click 'taxi taking option' event and description information thereof. The perception module may determine that the user clicked the "get a car 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 gourmet application described above, and it does not feed back the operation of the user clicking the "determine to call for express" option. Accordingly, the awareness module may determine whether a taxi taking event has occurred based on the displayed "loading" information. However, as shown in (3) of fig. 7, in the driving service, if the user clicks the "start navigation" option, the driving service also appears with the "loading" information. Therefore, the sensing module can determine whether the taxi taking event occurs in the map application by combining the click event and the window state change event, so that misjudgment is avoided.

Still referring to (4) of fig. 8, illustratively, the user clicks on the "determine call express" option 807 and the taxi taking service displays "loading" information in response to the received user action. And 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 display "loading" and other description information. The sensing module acquires the event which occurs at this time based on the received event information, namely displaying that the loading is in progress. The sensing module matches the event with the feature events 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 taxi taking option 804, after the mobile phone displays the taxi taking service interface 805 shown in (3) of fig. 8, the user exits the taxi taking service interface and clicks the driving option in the main service interface 803. And when the barrier-free service detects a click event, sending event information of the map application to the sensing module. The event information comprises a click 'driving option' event and description information thereof. And the sensing module receives the event information, determines that a driving option event still occurs after the event of clicking the driving option, and ends the detection process. That is to say, after the user clicks the taxi taking option, the user clicks the taxi taking option again, and even if the 'loading' information appears in the taxi service interface, the sensing module cannot continuously detect the information so as to prevent misjudgment. In other embodiments, the perception module determines that a click on drive option event occurs after a click on drive option event occurs in response to the received event information, the perception module may continue to count, and the feature set fence trigger may be determined if the perception module detects that a click on drive option and a display of load before the timer ends and no click on drive option between the two events occurs.

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

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

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

The terms "first" and "second," and the like, in the description and in the claims of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order of the objects. For example, the first target object and the second target object, etc. are specific sequences for distinguishing different target objects, rather than describing target objects.

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

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

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A travel event subscription method is applied to an electronic device, and comprises the following steps:

executing a first application in response to a received trigger operation on 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 identifier of the first service;

subscribing to a specified type of event occurring 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, determining that a user uses the first service of the first application to perform a taxi taking event, and storing the taxi taking event of the user using the first service of the first application as a record in a taxi taking record, wherein the first target event is the event of the specified type;

and under the condition that the record of the taxi taking event of the first service of the first application used by the user is determined to meet the preset condition according to the taxi taking record, recommending the first service of the first application to be used by the user for taxi taking when the user needs to take the taxi.

2. The method of claim 1, wherein the determining from 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 a preset condition comprises:

determining that the frequency of recording of taxi-taking events by the user using the first service of the first application is the highest among taxi-taking records by determining that the user has performed taxi-taking events using the first service of the first application 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 performed by the user using the first service of the first application satisfies a preset condition comprises:

and determining that the record of the taxi taking event of the first service of the first application by the user is the latest record in the taxi taking records according to the taxi taking records.

4. The method according to any one of claims 1-3, wherein recommending that a user take a taxi using the first service of the first application when the user needs to take a taxi comprises:

displaying a trip reminding card on a display screen of the electronic equipment, wherein the trip reminding card comprises trip reminding information and taxi taking options; the travel reminding information comprises at least one of the following: road condition information, destination information and whole-course time consumption 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 the event of the specified type occurring within the first window to which the first service belongs comprises:

and acquiring the event of the specified type occurring in the first window through barrier-free service of the electronic equipment.

6. The method of claim 1, wherein the specified type comprises at least one of:

click events, window state change events.

7. The method of claim 6, wherein the first window includes a first typing control and a second control, and wherein the first target event is clicking the first typing control event; when a first target event occurs in a first window to which the first service belongs, determining that a user makes a taxi-taking event by using the first service in the first application includes:

receiving an operation of clicking the second control;

acquiring the second control clicking event generated by the first window through the barrier-free service; the second control clicking event is a clicking event;

determining that clicking the second control event that occurs in the first window is not the first target event;

receiving the operation of clicking the first taxi taking control, and executing taxi taking operation;

acquiring the first vehicle-driving control event clicked by the first window through the barrier-free service;

and determining that the user takes a taxi using the first service in the first application when the first taxi taking control event clicked in the first window is detected as the first target event.

8. The method of claim 6, further comprising:

responding to the received trigger operation of the second application, and running the second application;

executing a second service of the second application in response to the received trigger operation of the second service;

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 identifier of the second service;

subscribing to a specified type of event occurring on the second window for the second service;

when a second target 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 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 the event of the specified type;

and under the condition that the record of the taxi taking event of the user by using the second service of the second application meets the preset condition according to the taxi taking record, recommending the user to use the second service of the second application for taking a taxi when the user needs to take a taxi.

9. The method of claim 8, wherein the second window comprises a second taxi taking control, and wherein determining that the user has performed a taxi taking event using the second service of the second application when the second target event occurs in the second window to which the second service belongs comprises:

receiving an operation of clicking the second taxi taking control, executing a taxi taking operation, and displaying first prompt information on the second window; the first prompt message is used for prompting that the car is being driven;

acquiring the first prompt information event which is generated in the second window and is displayed through the barrier-free service, wherein the first prompt information event is displayed as a window state change event;

and detecting that the event of displaying the first prompt message occurring in the second window is the second target event, and determining that the user makes a taxi taking event by using the second service of the second application.

10. The method of claim 1, further comprising:

executing a third application in response to a received trigger operation on the third application; displaying an interface of a third service in the interface of the third application;

acquiring an identifier of the third service, where the identifier of the third service includes an identifier of the third application and an Activity identifier of the third service;

determining that the third service is a non-taxi taking service based on the identification of the third service;

in response to the received operation on the third application, executing a fourth service 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 identifier of the fourth service;

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

when a fourth 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 take a taxi, and storing the taxi taking event of the user using the fourth service of the third application as a record in a taxi taking record, wherein the fourth target event is the event of the specified type;

and under the condition that the record of the taxi taking event of the user by using the fourth service of the third application meets the preset condition according to the taxi taking record, recommending the user to use the fourth service of the third application to take the taxi when the user needs to take the taxi.

11. The method of claim 1, further comprising:

executing a fifth application in response to a received trigger operation on the fifth application; the interface of the fifth application displays an interface of a fifth service;

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

determining that the fifth service is a taxi taking service based on the identifier of the fifth service;

subscribing the event of a specified type which occurs in a fifth window to which the fifth service belongs;

and within a preset time length, determining that a user does not use the fifth service to take a taxi, wherein the event of the specified type does not include a fifth target event in the event of the specified type occurring in the fifth window, and the fifth target event is the event of the specified type.

12. The method of claim 11, wherein the preset duration is 3 minutes.

13. The method of claim 12, further comprising:

stopping subscribing to the event of the specified type occurring in the fifth window to which the fifth service belongs.

14. The method of claim 1, further comprising:

stopping subscribing to the event of the specified type occurring in the first window to which the first service belongs.

15. The method of claim 1, further comprising:

after the first application is closed, responding to the received trigger 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;

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

subscribing the events of the specified type which occur in a sixth window to which the first service belongs;

executing a sixth service of the first application in response to the received trigger operation on the sixth service;

stopping subscribing the events of the specified type which occur in the first window to which the first service belongs;

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

and determining that the sixth service is a non-taxi taking service based on the identifier of the sixth service.

16. The method of claim 1, wherein the first application is a taxi application or a gourmet application.

17. 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 and when executed by the one or more processors, cause the electronic device to perform the method of any of claims 1-16.