Method, device, server and system for reporting quick application card business data

Abstract

The present application provides a method, device, server and system for reporting business data of a quick application card, and relates to the field of communication technology. When the electronic device meets the first preset condition, the electronic device obtains the card resource data of the quick application card from the server side and completes the card creation, and caches the card resource data. The card resource data currently requested and the currently created card both carry a first tracking identifier. When the electronic device detects the occurrence of a card event (such as a card being displayed, a card being clicked, or a card pulling up an application, etc.), the card resource data can be quickly obtained from the electronic device side according to the first tracking identifier, and then the relevant business data of the card event is determined according to the event information and card resource data of the currently created card, thereby enabling the electronic device to report the card business data of various events to the server in a timely and accurate manner.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method for reporting quick application card business data, an electronic device, a server, a communication system and a storage medium. Background Art

[0002] In order to facilitate users to check information, electronic devices use the card recommendation function to present the information that users may need to view in the form of cards on the desktop or negative one screen of the electronic device. In this way, users can quickly obtain location information by viewing quick application cards on the desktop and negative one screen, and refer to the recommended services to decide to enter the corresponding page to view details.

[0003] When a user views or uses a quick app card, the electronic device will sense events such as the card being displayed to the user, the card being clicked by the user, and / or the card launching the application. The electronic device can report the card business data related to these events to the server side, so that the server side can analyze the user behavior habits based on the card collection data and optimize the card functions based on the user behavior habits.

[0004] The current problem is that when certain events occur in the quick application card, the electronic device side cannot report the card business data related to such events to the server side. Summary of the invention

[0005] The present application provides a method for reporting business data of a quick application card, an electronic device, a server, a communication system and a storage medium, which can effectively report relevant business data of various events to service providers and equipment manufacturers in the commercial operation of quick application cards and return monitoring links of corresponding events, thereby solving the problem that the electronic device side cannot report card business data related to certain card events to the server side.

[0006] In a first aspect, the present application provides a method for reporting quick application card business data, which is applied to an electronic device, and the method includes: when the electronic device meets a first preset condition, obtaining card resource data from a server, the card resource data including a first tracking identifier; creating a first quick application card according to the card resource data, the first quick application card carrying the first tracking identifier; in response to a first operation of a user, determining that a first event occurs in the first quick application card; in response to the first event occurring in the first quick application card, obtaining card resource data corresponding to the first quick application card according to the first tracking identifier carried by the first quick application card; determining card business data of the first quick application card according to the card resource data and event information of the first event; and sending the card business data to the server.

[0007] Through the reporting method of quick application card business data provided by the embodiment of the present application, when the electronic device meets the first preset condition, the electronic device obtains the card resource data of the quick application card from the server side and completes the card creation, and caches the card resource data. The card resource data currently requested and the currently created card both carry the first tracking identifier. When the electronic device detects the occurrence of a card event (such as a card being displayed, a card being clicked, or a card pulling up an application, etc.), the card resource data can be quickly obtained from the electronic device side according to the first tracking identifier, and then the relevant business data of the card event is determined according to the event information and card resource data of the currently created card, thereby enabling the electronic device to report the card business data of various events to the server in a timely and accurate manner.

[0008] The electronic device includes an operation management application, at least one media application and a quick application engine application; the media application can be a desktop application or a negative one screen application.

[0009] The technical improvements of the embodiments of the present application include: adding an operation management application based on the original software module of the electronic device, and the operation management application is responsible for transmitting the operation information of the quick application card (i.e., card resource data) to each media application of the electronic device for each media application to complete the card creation, and the operation management application stores the card resource data; then, when the media application detects a card exposure event, it passes the card exposure event to the operation management application; and when the quick application engine application detects various events such as a card click event or a card pull-up application event, it passes the detected event to the operation management application. Then, the operation management application can determine the card-related data that needs to be reported and returned based on the event information and the card resource data, and complete the card collection data reporting and monitoring link return.

[0010] The technical improvements of the embodiment of the present application also include: the cloud side generates a tracking identifier, splices the tracking identifier into the URL parameter of the quick application card, and sends the URL parameter containing the tracking identifier to the electronic device side. In each link of the card event processing process, the operation management application of the electronic device can read the complete quick application card information (i.e., card resource data) through the tracking identifier, and determine the card collection data to be reported and the monitoring link to be transmitted back based on the quick application card information and event information.

[0011] In some possible implementations, when the electronic device meets the first preset condition, the media application notifies the operation management application to obtain the card resource data; the operation management application obtains the card resource data from the server. The operation management application stores the card resource data with the first tracking identifier as an index; the operation management application sends the card resource data to the media application; the media application calls the quick application engine application to create a first quick application card based on the card resource data.

[0012] In some possible implementations, the media application determines that a card exposure event occurs in the first quick app card in response to the user's first operation; and sends the event information of the card exposure event and the first tracking identifier to the operation management application. In some possible implementations, the quick app engine application determines that a card click event occurs in the first quick app card in response to the user's first operation, and sends the event information of the card click event and the first tracking identifier to the operation management application. In some possible implementations, the quick app engine application determines that a card pull-up application event occurs in the first quick app card in response to the user's first operation, and sends the event information of the card pull-up application event and the first tracking identifier to the operation management application. Among them, the operation management application can obtain the card resource data corresponding to the first tracking identifier according to the first tracking identifier. The operation management application can determine the card business data of the first quick app card based on the card resource data and the event information of the first event.

[0013] Through the above method, the media application can sense the card exposure event and notify the operation management application of the card exposure event, which analyzes the event based on the card resource data and reports the relevant business data of the event to the server side. In addition, the quick application engine application can sense the card click event and the card pull-up application event, and notify the event to the operation management application, which analyzes the event based on the card resource data and reports the relevant business data of the event to the server side. In this way, the electronic device side reports the relevant business data of various card events to the server.

[0014] When a quick app card event occurs, the media application can pass the card URL parameter to the quick app engine application without going through an additional interface channel. The quick app engine application can parse the tracking identifier in the URL and pass the tracking identifier to the operation management application. The operation management application can obtain the quick app card resource data locally based on the tracking identifier, or obtain the complete quick app card resource data from the operation cloud based on the tracking identifier.

[0015] This application uses the operation management application to centrally manage the quick application card information, and the media applications do not need to make any changes. If there are changes in the subsequent reporting of card collection data or monitoring link protocols, only the operation management application needs to be modified accordingly, and the media application and quick application engine application do not need to be modified. In addition, if the quick application card is subsequently placed in a new media application, the media application does not need to make any access and automatically has the data collection or marking function for card exposure events, card hot zone click events, and card-initiated application events.

[0016] Compared with the media application side reporting card collection data and the quick application engine application reporting card collection data, both the media application and the quick application engine application need to request the quick application card resource data from the cloud side first. In this application, the media application only needs to obtain the quick application card resource data through the operation management application, and the quick application engine application does not need to request the cloud service, but the operation management application can obtain the quick application card resource data locally based on the tracking identifier of the quick application card.

[0017] The existing technology cannot realize the reporting of card hot zone click events and card application launch events, but the present application solves this problem. The quick application engine application notifies the operation management application of the tracking identifier and event. The operation management application can obtain the quick application card resource data locally according to the tracking identifier, and then determine the card business data related to the event according to the quick application card resource data, event information and device anonymous identity, and then upload the card business data to the server side, thereby completing the reporting of card collection data and the return of the monitoring link.

[0018] Among them, the card business data includes event monitoring links and / or card collection information.

[0019] The event monitoring link is a link that is sent back to the server when the occurrence of the first event is detected. The event monitoring link includes the event name, event type and / or event occurrence time of the first event.

[0020] Exemplarily, the monitoring link may include a monitoring link for a card exposure event, a monitoring link for a card hot zone click event, and a monitoring link for a card application pull-up event.

[0021] The card collection information is user behavior data collected for the first event according to a preset rule. The card collection data may include business information and event information.

[0022] Exemplarily, the business information may include an open anonymous identification (OAID), an identity document (ID), a card ID and / or a card request ID, etc. In some embodiments, the business information may also include scenario information.

[0023] Exemplarily, the event information may include the event type and the event occurrence time (referred to as event time). In some embodiments, the event information may also include the event name and / or event content.

[0024] In some possible implementations, after obtaining the card resource data and the first tracking identifier from the server, the method further includes: storing the card resource data on the electronic device side using the first tracking identifier as an index. In this case, obtaining the card resource data corresponding to the first quick app card according to the first tracking identifier carried by the first quick app card includes: obtaining the card resource data corresponding to the first tracking identifier from the electronic device side according to the first tracking identifier.

[0025] The first tracking identifier may be set in the card URL of the card resource data.

[0026] In this way, the card resource data is stored locally in the electronic device. When a card event occurs, it is helpful for the electronic device to obtain the card resource data locally in a timely manner to determine the card business data that needs to be reported, thereby enabling the electronic device to report card business data related to various events to the server.

[0027] In some possible implementations, the first preset condition includes the electronic device displaying a first interface, where the first interface is an interface configured to display a quick application card.

[0028] In this case, when the electronic device meets the first preset condition, obtaining the card resource data and the first tracking identifier from the server includes: in response to the user's second operation, the electronic device displays a first interface, and the first interface is an interface configured to display the quick application card; in response to the electronic device displaying the first interface, sending a first request message to the server, and the first request message is used to request the creation of a quick application card; receiving a first response message sent by the server according to the first request message, and the first response message includes the card resource data.

[0029] Among them, the first interface can be a desktop interface or a negative one screen interface.

[0030] In this way, when the user triggers the display screen to switch to the desktop interface or the negative one screen interface and other interfaces for displaying quick application cards, it will trigger the electronic device to automatically request the server to create a quick application card, obtain the card resource data carrying the tracking identifier from the server, and create the quick application card using the card resource data carrying the tracking identifier. This is conducive to reporting event information according to the tracking identifier when a card event occurs, and is conducive to helping the electronic device report various event-related card business data to the server.

[0031] In some possible implementations, the first preset condition also includes that current user scenario information of the electronic device satisfies preset scenario information.

[0032] In this case, in response to the electronic device displaying the first interface, sending a first request message to the server includes: in response to the electronic device displaying the first interface, determining whether the current user scenario information of the electronic device satisfies the preset scenario information; when it is determined that the user scenario information satisfies the preset scenario information, sending the first request message to the server, the first request message including the user scenario information, and the card resource data is data determined based on the user scenario information.

[0033] Exemplarily, the preset scenario information may be an electronic fence such as a subway or an airport. When the electronic device enters an electronic fence such as a subway or an airport, the electronic device may determine that the user scenario information satisfies the preset scenario information.

[0034] In this way, when the user triggers the display screen to switch to the desktop interface or the negative one screen interface for displaying quick app cards, it first determines whether the current user scene is a preset scene. If the current user scene is a preset scene, it triggers the electronic device to request the server to create a quick app card, which can more accurately recommend quick app cards to users.

[0035] In some possible implementations, the first request message includes a request identifier, which is used to request the creation of a first quick app card, and the first tracking identifier is an identifier generated by the server according to the request identifier. Wherein, when the request identifier is different, the tracking identifier obtained from the server is different. In this way, by adding a tracking identifier to the created card, the card resource data can be quickly obtained based on the tracking identifier, which is convenient for analyzing card events, obtaining card business data, and realizing timely reporting of the card business data to the server.

[0036] In some possible implementations, the first request message further includes a booth identifier, where the booth identifier is used to indicate a display position and a display size of the quick app card requested to be created, and the card resource data is data determined based on the booth identifier.

[0037] Exemplarily, the first interface is a desktop interface, and the booth logo is used to indicate that the location of the created card is located in the recommendation column in the desktop interface, and the display size is 2*4.

[0038] Through the above method, the server side can create a quick application card that meets the electronic device's request based on the booth logo.

[0039] In some possible implementations, creating the first quick app card according to the card resource data includes: displaying the first quick app card on the first interface.

[0040] In some possible implementations, the method further includes: if the accumulated storage time of the card resource data on the electronic device side is greater than a preset storage time, deleting the card resource data stored on the electronic device side. After the preset storage time, the card resource data stored on the electronic device side is deleted to release more memory space. The preset storage time can be set by the electronic device side or by the server side. Exemplarily, the preset storage time can be 7 days.

[0041] In some possible implementations, in response to a first operation of the user, determining that a first event occurs in the first quick app card includes: in response to a first operation on a screen of the electronic device, switching the first interface to a foreground display, the first operation being a trigger to unlock the screen or slide the screen; in response to the first interface being switched to a foreground display, determining that a card exposure event occurs in the first quick app card. The card exposure event belongs to the first event.

[0042] In some possible implementations, determining that a first event occurs in a first quick app card in response to a first operation of a user includes: determining that a card click event occurs in the first quick app card in response to a first operation on the first quick app card; the first operation is a click operation on a preset area of ​​the first quick app card; wherein the card click event (or referred to as a card hot zone click event) belongs to the first event.

[0043] In some possible implementations, determining that a first event occurs in a first quick app card in response to a first operation of a user includes: in response to a first operation on the first quick app card, starting a first app and displaying a page of the first app, and determining that a card-pull-up-app event occurs in the first quick app card; wherein the first operation is selecting a first control in the first quick app card, and the first control is a control associated with the first app; and the card-pull-up-app event belongs to the first event.

[0044] Among them, the first control can be a control in a preset area of ​​the first quick application card.

[0045] Through the above method, the electronic device can sense various card events such as card exposure events, card click events and / or card application launch events, and then the electronic device can report relevant business data of various card events to the server.

[0046] In some possible implementations, before determining the card service data of the first quick app card according to the card resource data and the first event, the method further includes: obtaining an anonymous identity of the electronic device. Accordingly, determining the card service data of the first quick app card according to the card resource data and the first event includes: determining the card service data of the electronic device regarding the first quick app card according to the card resource data, the first event, and the anonymous identity of the electronic device.

[0047] Through the anonymous identity of the electronic device, the server can determine that the received card service data of the first quick application card is reported by the electronic device, which facilitates the server side to perform card service data statistics.

[0048] Compare the improvement plan of this application with the related technology: In the related technology, on the one hand, the media application can provide card resource data (or called card operation information), but cannot perceive the card hot zone click event, nor can it perceive the card application launch event, etc.; on the other hand, the quick application engine can perceive the card hot zone click event, and can also perceive the card application launch event, etc., but without card resource data, it is impossible to complete the card collection data reporting and monitoring link feedback. Compared with the related technology, this application adds an operation management application, which can be responsible for quick application card requests, local management of quick application card data, and reception and analysis of quick application card events, complete the reporting of card collection data and the return of monitoring links, and solve the problem of being unable to report relevant business data when quick application cards are clicked, launched, and other events occur, so that in the commercial operation of quick application cards, relevant business data of various events can be effectively reported to service providers and equipment manufacturers, and the monitoring links of corresponding events can be returned.

[0049] In a second aspect, the present application provides a method for reporting quick application card business data, which is applied to a server, and the method includes: receiving a first request message sent by an electronic device, the first request message is used to request the creation of a first quick application card; according to the first request message, generating a first tracking identifier and setting the first tracking identifier in a card URL parameter, and determining card resource data for creating the first quick application card, the card resource data including a card URL parameter; sending a first response message to the electronic device, the first response message including the card resource data; receiving the card business data of the first quick application card sent by the electronic device.

[0050] In some possible implementations, the first request message includes a request identifier, and the request identifier is used to request the creation of a quick app card. In this case, generating a first tracking identifier according to the first request message includes: generating the first tracking identifier according to the request identifier.

[0051] In some possible implementations, when the request identifiers are different, the tracking identifiers generated by the server are different.

[0052] In some possible implementations, the first request message further includes user scenario information. In this case, determining the card resource data includes: determining the card resource data according to the user scenario information.

[0053] In some possible implementations, the first request message further includes a booth identifier, which is used to indicate the display position and display size of the requested quick app card. In this case, determining the card resource data according to the user scenario information includes: determining the card resource data according to the user scenario information and the booth identifier.

[0054] In some possible implementations, the method further includes: determining a preset storage time, and setting the preset storage time in the card resource data. The preset storage time is defined as: when the storage time of the card resource data on the electronic device side is greater than the preset storage time, the card resource data will be deleted.

[0055] Exemplarily, the preset storage period may be 7 days.

[0056] In a third aspect, the present application provides a device for reporting quick application card service data, the device comprising a unit for executing the method in the first aspect. The device may correspond to executing the method described in the first aspect. For the relevant description of the unit in the device, please refer to the description of the first aspect, which will not be repeated here for the sake of brevity.

[0057] The method described in the first aspect above can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a processing module or unit, a display module or unit, etc.

[0058] In a fourth aspect, the present application provides an electronic device, comprising a processor, a computer program or instructions stored in the processor and a memory, wherein the processor is configured to execute the computer program or instructions so that the method in the first aspect is executed.

[0059] In a fifth aspect, the present application provides a computer-readable storage medium on which a computer program (also referred to as instructions or codes) for implementing the method in the first aspect is stored. For example, when the computer program is executed by a computer, the computer can execute the method in the first aspect.

[0060] In a sixth aspect, the present application provides a chip, including a processor. The processor is used to read and execute a computer program stored in a memory to perform the method in the first aspect and any possible implementation thereof. Optionally, the chip also includes a memory, and the memory is connected to the processor via a circuit or wire.

[0061] In a seventh aspect, the present application provides a chip system, including a processor. The processor is used to read and execute a computer program stored in a memory to perform the method in the first aspect and any possible implementation thereof. Optionally, the chip system also includes a memory, and the memory is connected to the processor via a circuit or wire.

[0062] In an eighth aspect, the present application provides a computer program product, comprising a computer program (also referred to as instructions or codes), wherein when the computer program is executed by an electronic device, the electronic device implements the method in the first aspect.

[0063] It can be understood that the beneficial effects of the second to eighth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 A schematic diagram of an interface for displaying a quick application card on a desktop or a negative screen of an electronic device provided in an embodiment of the present application;

[0065] Figure 2 A user scenario diagram of the quick application card involved in the embodiment of the present application;

[0066] Figure 3 A schematic diagram of a quick application card provided in an embodiment of the present application;

[0067] Figure 4 A schematic diagram showing an electronic device reporting card service data to a cloud server;

[0068] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0069] Figure 6 A schematic diagram of a software architecture of an electronic device provided in an embodiment of the present application;

[0070] Figure 7 A schematic diagram of the system architecture provided for an embodiment of the present application;

[0071] Figure 8 Schematic diagram of the process of reporting the quick application card service data provided in the embodiment of the present application Figure 1 ;

[0072] Fig. 9 Module interaction sequence diagram of the method for reporting quick application card service data provided in the embodiment of the present application Figure 1 ;

[0073] Fig.10 Schematic diagram of the process of reporting the quick application card service data provided in the embodiment of the present application Figure 2 ;

[0074] Fig.11 Module interaction sequence diagram of the method for reporting quick application card service data provided in the embodiment of the present application Figure 2 ;

[0075] Fig.12 Schematic diagram of the process of reporting the quick application card service data provided in the embodiment of the present application Figure 3 ;

[0076] Fig.13 Module interaction sequence diagram of the method for reporting quick application card service data provided in the embodiment of the present application Figure 3 ;

[0077] Fig.14 Schematic diagram of the process of reporting the quick application card service data provided in the embodiment of the present application Figure 4 ;

[0078] Fig.15 Module interaction sequence diagram of the method for reporting quick application card service data provided in the embodiment of the present application Figure 4 ;

[0079] Fig.16 Module interaction sequence diagram of the method for reporting quick application card service data provided in the embodiment of the present application Figure 5 ;

[0080] Fig.17 A schematic diagram of the card creation process in the method for reporting quick application card business data provided in an embodiment of the present application;

[0081] Fig.18 A schematic diagram of adding services through YOYO suggestion in the method for reporting quick application card business data provided in an embodiment of the present application;

[0082] Fig.19 A schematic diagram of an interface in which a user views a quick application card on the negative one screen in the method for reporting quick application card business data provided in an embodiment of the present application;

[0083] Fig. 20 A schematic diagram of an interface for a user viewing a quick app card on a desktop in a method for reporting quick app card service data provided in an embodiment of the present application;

[0084] Fig.21 and Fig. 22 A schematic diagram of an interface for adding a quick app card in the method for reporting quick app card business data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the embodiments of the present application are further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0086] In order to provide users with convenient information access, electronic devices use a card recommendation function to present information that users may need to view in the form of cards on the desktop or negative one screen of the electronic device. In this way, users do not need to subconsciously remind themselves to enter certain software applications to view the required information in specific situations.

[0087] Currently, in response to the user's operation of adding a card, the electronic device can add a quick application card on the desktop and / or the negative one screen. These quick application cards are small components in the form of cards, which can be implemented based on JavaScript or other programs, and support the display of recommended services corresponding to user scenarios in the form of cards, such as taxi flights, flight services, scenic spot services, and other services for various use scenarios. In this way, users can quickly obtain location information by viewing quick application cards on interfaces such as the desktop and the negative one screen, and refer to the recommended services to decide to enter the corresponding page to view details.

[0088] For example, Figure 1 As shown in (a) and (b) in the figure, the electronic device presents the flight information in the form of a quick application card. The user does not need to check the text message or enter the relevant application for subscribing to the air ticket to view the flight information. The user can directly view the quick application card on the desktop or the negative one screen.

[0089] In some scenarios, reference Figure 2 As shown in (a) in the figure, in response to a user operation, the electronic device switches the foreground display interface to the desktop or the negative one screen. In this case, the electronic device can present the quick app card through the desktop or the negative one screen, and the quick app card is visible to the user, that is, the quick app card is exposed to the user. This scenario can be called a card exposure event, in other words, an exposure event occurs to the quick app card.

[0090] In other scenarios, reference Figure 2 As shown in (b), in response to the user's click operation on the quick app card, the electronic device may refresh the quick app card or switch from the main page displaying the quick app card to the sub-page displaying the quick app card. This scenario may be referred to as a card click event, in other words, a click event occurs on the quick app card.

[0091] It should be noted that the main page of a quick app card can include multiple areas with different functions. Figure 3As shown, the main page of the quick app card may include a title area, a service display area, and one or more function areas (or hot areas), which are provided with function icons. When a user clicks a function icon in a hot area of ​​a quick app card, the electronic device may switch from the main page displaying the quick app card to displaying a sub-page corresponding to the function icon or execute the function corresponding to the function icon. This scenario may be referred to as a card hot area click event, which is a special case of a card click event.

[0092] In other scenarios, reference Figure 2 As shown in (c), the quick app card is associated with the functions of one or more applications. In other words, the quick app card is provided with the startup entry control of one or more applications. Exemplarily, taking the one or more applications as the first application as an example, the electronic device displays a quick app card on the desktop or the negative one screen, and the quick app card presents the startup entry control of the first application. When the user clicks the startup entry control of the first application, from the underlying logic, the quick app card will automatically pull up the first application, so that the first application starts; from the user interface, the electronic device can switch from the main page displaying the quick app card to the preset page displaying the first application, etc. This scenario can be called a card pull-up application event. In other words, a pull-up application event occurs in the quick app card.

[0093] refer to Figure 2 As shown, when a user uses an electronic device, card exposure events, card click events and / or card application pull-up events will occur multiple times on the electronic device side. The electronic device side can report the card collection data related to these events to the server side to provide data support for operations. For example, the server side can analyze user behavior habits based on the card collection data and optimize the card functions based on the user behavior habits.

[0094] It should be noted that the card collection data reported by the electronic device to the server side usually includes business information and event information. This reporting action of the electronic device is called "card collection data reporting" or "dot reporting". In addition, if the server side configures the monitoring link of the corresponding event on the electronic device side, then the electronic device also needs to replace the value of the monitoring link and then execute the monitoring link reporting. Correspondingly, the server side can count information such as the user's usage frequency or time of the monitored event through the monitoring link reported by the electronic device. This reporting action of the electronic device is called "monitoring link feedback" or "monitoring feedback".

[0095] For example, Figure 4 The schematic diagram of the electronic device reporting the card collection data to the server side is shown. Figure 4As shown, the electronic device side includes media applications and quick application engine applications, where the media application can be a desktop or negative one screen application, and the quick application engine application can be referred to as the quick application engine. The server side includes multiple servers with different functions. For example, the server side includes an operation cloud server, a big data collection cloud server, a business promotion cloud server, and a third-party cloud server, which are referred to as the operation cloud, big data collection cloud, business promotion cloud, and third-party cloud in the figure.

[0096] Among them, the operation cloud is used to manage card operation information, which is also called card resource data. The big data collection cloud is used to manage the business information and event information of quick application cards. The third-party cloud is used to provide third-party applications to the electronic device side. The business promotion cloud is used to deliver advertising services to the electronic device side according to the business needs of third-party applications, so the business promotion cloud is also called the advertising cloud.

[0097] It should be noted that Shangtui Cloud and Third-Party Cloud will send monitoring links to electronic devices. When the electronic device detects a card exposure event, a card hot area click event, or a card application launch event, the electronic device can send back monitoring links to Shangtui Cloud and Third-Party Cloud respectively, carrying event information in the monitoring links.

[0098] The current problem is that when a certain type of event occurs in the quick application card, the electronic device side is unable to complete reporting the card collection data related to the event to the server side and is unable to return the event monitoring link.

[0099] Let's first look at the media application on the electronic device side. The media application can sense the exposure event of the quick application card, and then the media application can obtain the card resource data from the operation cloud, and determine the card collection data to be reported to the server side based on the card operation information and the card exposure event. For example, the media application reports the card collection data to the big data collection cloud, and returns the monitoring link of the card exposure event to the business promotion cloud and the third-party cloud. The monitoring link carries the relevant data of the card exposure event.

[0100] It should be noted that media applications can sense the exposure events of quick application cards, but due to functional limitations, they cannot accurately sense the click events of the card hot area, nor can they accurately sense the card launch event.

[0101] Let's look at the quick application engine application on the electronic device side. The quick application engine application can sense the card hot zone click event and the card pull-up application event. However, since the quick application engine application is responsible for card loading and rendering, it does not have complete card resource data. Therefore, the quick application engine application cannot determine the card collection data that needs to be reported to the server side, and therefore cannot report the card collection data to the server side. For example, the quick application engine application cannot report card collection data to the big data collection cloud, nor can it return the monitoring link of the card hot zone click event and the card pull-up application event to the business promotion cloud and the third-party cloud.

[0102] It can be seen that when a card hot zone click event and / or a card application pull-up event occurs on the electronic device side, the electronic device side cannot complete reporting the card collection data related to the event to the server side, nor can it return the event monitoring link.

[0103] Based on this, the embodiments of the present application provide a method and electronic device for reporting business data of a quick application card, which can solve the problem that relevant business data cannot be reported when events such as clicking and launching an application occur on a quick application card, thereby being able to effectively report relevant business data of various events to service providers and equipment manufacturers in the commercial operation of the quick application card and return monitoring links for corresponding events.

[0104] In order to better understand the embodiments of the present application, the embodiments of the present application are briefly described below:

[0105] The technical improvements of the embodiments of the present application include: adding an operation management application based on the original software module of the electronic device, and the operation management application is responsible for transmitting the operation information of the quick application card to each media application for each media application to complete the card creation, and the operation management application stores the card resource data; then, when the media application detects a card exposure event, it passes the card exposure event to the operation management application; when the quick application engine application detects various events such as a card click event or a card pull-up application event, it passes the detected event to the operation management application. Then, the operation management application can determine the card-related data that needs to be reported and returned based on the event information and the card resource data, and complete the card collection data reporting and monitoring link return.

[0106] In an embodiment of the present application, the card service data includes card collection data and / or event monitoring links.

[0107] Among them, the card collection data may include business information and event information.

[0108] Exemplarily, the business information may include device OAID, card booth ID, card ID and / or card request ID, etc. Among them, device OAID is an anonymous device identifier provided by the advertising industry to achieve accurate advertising and user tracking. OAID is bound to a specific device and remains unchanged during the life cycle of the device. In some embodiments, business information may also include scenario information.

[0109] Exemplarily, the event information may include the event type and the event occurrence time (referred to as event time). In some embodiments, the event information may also include the event name and / or event content.

[0110] It should be noted that the above examples exemplify the related events that may occur in the quick application card. It should be noted that other related events of the quick application card may also be involved in the actual implementation, and the embodiments of the present application do not limit this. The following examples are used to illustrate the card exposure event, the card hot area click event, and the card pull-up application event.

[0111] In an embodiment of the present application, the monitoring link may include a monitoring link for a card exposure event, a monitoring link for a card hot zone click event, and a monitoring link for a card application pull-up event.

[0112] The technical improvements of the embodiment of the present application also include: the cloud side generates a tracking identifier, splices the tracking identifier into the URL parameter of the quick application card, and sends the URL parameter containing the tracking identifier to the electronic device side. In each link of the card event processing process, the operation management application of the electronic device can read the complete quick application card information through the tracking identifier, and determine the card collection data to be reported and the monitoring link to be transmitted back based on the quick application card information and event information.

[0113] This application uses the operation management application to centrally manage the card resource data of the quick application card, and the media applications do not need to make any changes. If there are changes in the subsequent reporting of card collection data or monitoring link protocols, only the operation management application needs to be modified accordingly, and the media application and quick application engine application do not need to be modified. In addition, if the quick application card is subsequently placed in a new media application, the media application does not need to make any access, and automatically has the data collection or marking function for card exposure events, card hot zone click events, and card-initiated application events.

[0114] Compared with the media application side reporting card collection data and the quick application engine application reporting card collection data, both the media application and the quick application engine application need to request the quick application card resource data from the cloud side first. In this application, the media application only needs to obtain the quick application card resource data through the operation management application, and the quick application engine application does not need to request the cloud service, but the operation management application can obtain the quick application card resource data locally based on the tracking identifier of the quick application card.

[0115] The existing technology cannot realize the reporting of card hot zone click events and card application launch events, but the present application solves this problem. The quick application engine application notifies the operation management application of the tracking identifier and event. The operation management application can obtain the quick application card resource data locally according to the tracking identifier, and then determine the card business data related to the event according to the quick application card resource data, event information and device OAID, and then upload the card business data to the server side, thereby completing the reporting of card collection data and the return of the monitoring link.

[0116] Hereinafter, the electronic device to which the method for reporting quick application card service data provided in the embodiment of the present application is applied will be described with reference to the accompanying drawings.

[0117] Exemplarily, the electronic device in the embodiments of the present application may be a mobile phone, a tablet computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), a wearable device (such as a smart watch, a smart bracelet), and other devices with voice communication functions. The embodiments of the present application do not impose any special restrictions on the specific form of the electronic device.

[0118] Figure 5 The following is a schematic diagram showing the structure of an electronic device provided by an embodiment of the present application. Figure 5 The electronic device shown may be a mobile phone. Figure 5 As shown, the mobile phone may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver (i.e., an earpiece) 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, and a subscriber identification module (SIM) card interface 195, etc.

[0119] Exemplarily, the sensor module may include sensors such as 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, and a bone conduction sensor.

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

[0121] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0122] The processor 110 is used to: when the electronic device meets a first preset condition, obtain card resource data from the server, the card resource data including a first tracking identifier; create a first quick application card according to the card resource data, the first quick application card carrying the first tracking identifier; in response to a first operation of the user, determine that a first event occurs in the first quick application card; in response to the first event occurring in the first quick application card, obtain card resource data corresponding to the first quick application card according to the first tracking identifier carried by the first quick application card; determine card service data of the first quick application card according to the card resource data and the first event; and send the card service data to the server.

[0123] The controller can be the nerve center and command center of the mobile phone. The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of fetching and executing instructions.

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

[0125] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

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

[0127] The wireless communication function of the mobile phone can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0128] The mobile phone can realize the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or change display information. The display screen 194 is used to display images, videos, etc.

[0129] In an embodiment of the present application, the quick application card can be set on different interfaces of the display screen, which can be preset by the system or customized by the user. For example, the quick application card can be displayed on the desktop of the display screen, on the negative first screen of the display screen, in the quick service center of the display screen, or in the lock screen interface. For a folding screen electronic device with a small screen, the quick application card can be displayed on the small screen.

[0130] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone. The internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions. The processor 110 executes various functional applications and data processing of the mobile phone by running the instructions stored in the internal memory 121. For example, in an embodiment of the present application, the processor 110 can execute instructions stored in the internal memory 121, and the internal memory 121 may include a program storage area and a data storage area.

[0131] The above is a specific description of the embodiment of the present application using the electronic device 100 as an example. It should be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. The electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in the figure 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.

[0132] In addition, an operating system is running on the above hardware. The operating system of the operating system layer can be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system or Windows operating system, etc. Applications can be installed and run on the operating system.

[0133] The operating system of the electronic device 100 may adopt 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 the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

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

[0135] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer (applications), application framework layer (application framework), Android runtime (AndroidRuntime) and system library, and kernel layer (kernel).

[0136] The application layer may include a series of application packages. For example, the application layer may include desktop APP, negative one screen APP, quick service center APP and other applications, which may be collectively referred to as media applications.

[0137] In the embodiment of the present application, the application layer may also include a quick application engine application and an operation management application, wherein the operation management application is an application program added to the present application.

[0138] In the embodiment of the present application, the application layer may also include a context awareness module, a business logic processing module, a business presentation module, etc. The context awareness module, the business logic processing module, and the business presentation module may be independent APPs, or may be integrated in different APPs, or may be integrated in the same APP, which is not limited in the present application.

[0139] Among them, the context awareness module, which runs permanently or in a low-power form, has the ability to perceive external facts or environments. The context awareness module can detect related events and obtain the status of events from other applications in the application layer or the application framework layer or the system layer or the kernel layer through the application programming interface (API), such as detecting Bluetooth connections, network connections, monitoring user text messages, custom timers, etc. In an embodiment of the present application, the main function of the context awareness module is to monitor whether there are quick application card events. The context awareness module can also obtain the real-time geographic location information of the electronic device. The context awareness module can notify the business logic processing module of the monitored quick application card events and real-time geographic location information.

[0140] The business logic processing module (such as the computing engine) has the business logic processing capability, and can perform data processing or logic judgment based on the preset logic algorithm, the quick application card events monitored by the context awareness module, and the real-time geographic location information to determine the user's scene and the preset associated services corresponding to the user's scene. Then, based on the preset associated services corresponding to the user's scene and the user behavior data, determine which services are recommended to the user to be displayed on the quick application card. The specific judgment process will be described in detail below.

[0141] The business presentation module (such as YOYO Suggestion) can display quick application cards on the screen of the electronic device according to the instructions of the business logic processing module. The quick application cards can include service options related to the scene the user is in. The recommended services realized by the quick application cards have more intuitive information display, more comprehensive service recommendations, and more significant relevance.

[0142] The application framework layer provides API and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. Figure 6 As shown, the application framework layer may include a window manager, a notification manager, a view system, a resource manager, etc., and the embodiments of the present application do not impose any restrictions on this.

[0143] The notification manager enables applications to display notification information in the status bar, and can be used to convey notification-type messages. The window manager is used to manage window programs, such as window programs suggested by YOYO. The resource manager provides various resources for applications, such as localized strings, icons, pictures, etc. The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build applications. The display interface can be composed of one or more views. For example, in an embodiment of the present application, the view system can be used to display quick application cards on the desktop.

[0144] Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for scheduling and management of the Android system. The core library consists of two parts: one is the function that the Java language needs to call, and the other is the core library of Android. The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection. The system library can include multiple functional modules. For example: surface manager, media library, 3D graphics processing library (for example: openGL ES), 2D graphics engine (for example: SGL), etc. The surface manager is used to manage the display subsystem and provide the fusion of 2D layers and 3D layers for multiple applications.

[0145] The kernel layer is the layer between hardware and software. Its role is to pass the application layer's requests to the hardware and act as a low-level driver to address various devices and components in the system. For example, the kernel layer can include display drivers and sensor drivers.

[0146] For the convenience of explanation, the figure also shows a hardware layer that interacts with the above software structure. For example, the hardware layer may include a display screen.

[0147] It should be noted that although the embodiment of the present application is based on Android ® The system is used as an example, but the basic principle is also applicable to iOS-based ® or Windows ®Electronic devices with other operating systems.

[0148] Figure 7 Schematic diagram of system architecture involved in various exemplary embodiments of the present application is shown. Figure 7 As shown, the system architecture includes an electronic device side and a server side.

[0149] Among them, the electronic device side includes media applications, quick application engine applications and operation management applications.

[0150] The operation management application can be responsible for quick application card requests, local management of quick application card data, and reception, analysis, and reporting of quick application card events. Among them, the operation management application includes a transceiver module, an event management module, a data management module, and an OAID SDK. The transceiver module can be responsible for data transmission and reception. The event management module can be responsible for receiving event information and analyzing event information. The data management module can be responsible for managing quick application card resources that carry tracking identifiers. The OAID SDK can be responsible for calling the device identifier and forwarding the device identifier to the event management module, and the event management module can be based on the device identifier.

[0151] Media applications (such as desktop or negative one screen) can provide booths to present quick application cards and report card exposure events to the operation management application.

[0152] The quick application engine application can be responsible for loading the resources of the quick application card and reporting the card click event and the card application launch event to the operation management application.

[0153] Among them, the server side includes operation cloud, big data collection cloud, advertising cloud and third-party cloud.

[0154] The operation cloud can be responsible for generating a tracking identifier for the quick application card based on the quick application card request on the electronic device side, and then concatenating the tracking identifier of the quick application card with the URL parameters of the quick application card, and then sending the URL parameters containing the identifier to the operation management application, which will forward it to the electronic device.

[0155] The big data collection cloud can receive and process the card collection data reported by the electronic device side and complete the production of operation reports.

[0156] Advertising cloud / third-party cloud can be responsible for receiving the returned monitoring link and counting relevant data.

[0157] The method provided in the embodiment of the present application makes technical improvements on the electronic device side. The present application provides an independent background application service, called an operation management application, which can centrally manage the relevant data of the quick application card. Exemplarily, the operation management application can complete the following tasks:

[0158] (1) The operation management application forwards the quick application card request issued by the media application (such as the desktop or negative one screen) to the operation cloud side.

[0159] (2) The operation management application forwards the quick application card resource data sent by the operation cloud to the media application and stores it locally in the operation management application.

[0160] (3) The operation management application collects quick application card events.

[0161] (4) The operation management application integrates data based on the quick application card resource data and quick application card events, and then completes the card collection data reporting and monitoring link feedback based on the results of the data integration.

[0162] In the embodiment of the present application, the quick app card event can be a card exposure event, a card click event, and a card application launch event. In actual implementation, the quick app card event can also be any other possible event, which is not limited in the embodiment of the present application.

[0163] Accordingly, the method provided in the embodiment of the present application also makes corresponding technical improvements on the operation cloud side. The operation cloud can complete the following tasks:

[0164] (a) Based on the quick application card request from the electronic device side, the operation cloud generates a unique identifier for each quick application card requested. The identifier can be characters or numbers generated according to preset rules, or randomly generated characters or numbers, which is not limited in the embodiments of the present application.

[0165] For ease of explanation, this application refers to the identifier generated by the operation cloud as a tracking identifier.

[0166] It should be noted that the tracking identifier generated by the operation cloud side is different for each request of a certain electronic device. In addition, the tracking identifier generated by the operation cloud side for the card request is different from the unique identifier of the quick application card.

[0167] (b) The operations cloud sets the tracking ID into the card’s uniform resource locator (URL) parameter.

[0168] (c) The operation cloud sends the card resource data containing the URL to the operation management application.

[0169] When a quick app card event occurs, the media application can pass the card information to the quick app engine application without going through an additional interface channel. The quick app engine application can parse the tracking identifier in the URL and pass the tracking identifier to the operation management application. The operation management application can obtain the quick app card resource data locally based on the tracking identifier, or obtain the complete quick app card resource data from the operation cloud based on the tracking identifier.

[0170] Here, the improvement scheme of this application is compared with the related technology. In the related technology, on the one hand, the media application can provide card resource data (or called card operation information), but it cannot perceive the card hot zone click event, nor can it perceive the card application launch event, etc.; on the other hand, the quick application engine can perceive the card hot zone click event, and can also perceive the card application launch event, etc., but without card resource data, it is impossible to complete the card collection data reporting and monitoring link feedback. Compared with the related technology, the present application adds an operation management application, which can be responsible for quick application card requests, local management of quick application card data, and reception and analysis of quick application card events, complete the reporting of card collection data and the return of monitoring links, and solve the problem that relevant business data cannot be reported when quick application cards are clicked, applications are launched, and other events occur, so that in the commercial operation of quick application cards, relevant business data of various events can be effectively reported to service providers and equipment manufacturers, and monitoring links for corresponding events can be returned.

[0171] The execution subject of the method for reporting the quick application card business data provided in the embodiment of the present application can be the above-mentioned electronic device, or it can be a functional module and / or functional entity in the electronic device that can implement the method for reporting the quick application card business data, and the present application scheme can be implemented by hardware and / or software, which can be determined according to actual use requirements, and the embodiment of the present application is not limited. Below, taking an electronic device as an example, the method for reporting the quick application card business data provided in the embodiment of the present application is exemplarily described in combination with the accompanying drawings.

[0172] The following will be combined with the accompanying drawings to illustrate the embodiments of the present application through the following multiple exemplary embodiments. The methods in the following embodiments can be implemented in an electronic device with the above hardware structure and software architecture. The hardware structure diagram of the electronic device can be as follows: Figure 5 As shown, the software structure diagram of the electronic device can be as follows Figure 6 For the sake of convenience, the embodiments of the present application are all based on electronic devices as shown in FIG. Figure 5 Take the mobile phone shown as an example.

[0173] The following describes a method for reporting quick application card service data provided by an embodiment of the present application in conjunction with a specific embodiment.

[0174] First embodiment: Card creation process

[0175] Figure 8 This is a schematic diagram of the card creation process in the method for reporting the quick application card business data provided in the first embodiment of the present application. Figure 8 As shown, the card creation process includes the following steps A1 to A8. The following is an example of creating a quick application card in the YOYO suggestion bar on the desktop.

[0176] Step A1: The desktop application sends a card creation request to the operation management application to request the card resource data of the card to be created on the electronic device side. The card creation request carries a request ID and a card booth ID.

[0177] The request ID is used to indicate the tag when requesting to create a card, and the card booth ID is used to indicate information such as the card display position and display size.

[0178] Step A2: The operation management application receives the card creation request sent by the desktop application through the transceiver module, and then sends the card creation request to the operation cloud through the transceiver module.

[0179] Step A3: In response to the card creation request, the operation cloud generates a first tracking identifier and adds the first tracking identifier to the card URL, and then sends the card resource data including the card URL. The operation management application receives the card resource data including the card URL through the transceiver module.

[0180] The first tracking identifier is a tracking identifier generated by the operation cloud for the quick application card created for the request. In the embodiment of the present application, the operation cloud generates a tracking identifier for each request. The tracking identifiers generated by two different requests are different.

[0181] Steps A4-1 and A4-2: The operation management application sends the card resource data including the card URL to the desktop application, and stores the card resource data carrying the first tracking identifier in the data management module, that is, locally.

[0182] Steps A5 and A6: The desktop application receives the card resource data including the card URL, triggering the creation of the quick application card. Then, the desktop application sends the card URL to the quick application engine application, and the card URL carries the first tracking identifier.

[0183] In steps A7 and A8, the quick application engine application downloads the rpk package from the quick application engine cloud according to the card URL, and creates a view based on the rpk package to obtain a quick application card. The quick application engine application notifies the desktop application that the quick application card has been successfully created, and the desktop application can display the quick application card.

[0184] The card URL is the address of the quick app card created by the desktop application request. The rpk package may include the name, icon and address of the quick app card created by the desktop application request.

[0185] After the quick app card is successfully created, the quick app card can be displayed in the YOYO suggestion bar on the desktop. The quick app card carries a tracking identifier. When the electronic device senses the occurrence of a quick app card event, the electronic device can transmit event information based on the tracking identifier and quickly obtain card resource data based on the tracking identifier, and then analyze the event information based on the card resource data to obtain card collection data and event monitoring links, and then the electronic device reports the card collection data and event monitoring links to the server side.

[0186] Above through Figure 8 A schematic diagram of the card creation process in the method for reporting the quick application card business data provided in the embodiment of the present application is illustrated below. Fig. 9 This is a sequence diagram showing how to create a quick app card on the desktop. Fig. 9 As shown, the card creation process includes the following steps S201-S212.

[0187] S201. The desktop application monitors a screen-on-unlock event.

[0188] In the embodiment of the present application, the operation management application registers with the desktop application to monitor the screen unlock event. When the user triggers the electronic device to unlock the screen, the desktop application can monitor the screen unlock event, notify the operation management application of the screen unlock event and request card resource data.

[0189] In some embodiments, when a user triggers the screen to unlock an electronic device, the desktop application, after listening to the screen unlock event, determines whether the current scene of the electronic device meets the preset card creation conditions; when the desktop application determines that the current scene of the electronic device meets the preset card creation conditions, the desktop application requests card resource data for creating the card from the operation management application.

[0190] For example, a user can trigger the electronic device to light up the screen and unlock it by means of fingerprint unlocking or face unlocking.

[0191] S202: The desktop application sends a request to the operation management application. The request carries a first request ID and a first booth ID, and is used to request card resource data corresponding to the first booth ID.

[0192] S203: The operation management application forwards the request to the operation cloud.

[0193] S204: The operation cloud generates a first tracking identifier in response to the request, and adds the first tracking identifier to the card URL.

[0194] S205. The operation cloud generates card resource data carrying the card URL.

[0195] S206. The operation cloud sends the card resource data carrying the card URL to the operation management application. The card URL carries the first tracking identifier.

[0196] S207: The operation management application stores the card resource data carrying the first tracking identifier.

[0197] S208. The operation management application returns card resource data including the card URL to the desktop application.

[0198] This application does not limit the execution order of S207 and S208.

[0199] S209: The desktop application sends a card URL to the quick application engine application, where the card URL carries a first tracking identifier.

[0200] S210: The quick application engine application downloads the rpk package according to the card URL, and creates a quick application card according to the rpk package.

[0201] S211. The quick application engine application feeds back to the desktop application that the creation of the quick application card is complete. The quick application card carries a first tracking identifier.

[0202] S212: When the electronic device displays a desktop, the desktop application displays a quick application card in a preset area of ​​the desktop, and the quick application card carries a first tracking identifier. The quick application card also carries a card identifier.

[0203] Second embodiment: Reporting process of card exposure event

[0204] Fig.10 1 is a schematic diagram of the reporting process of the card exposure event in the reporting method of the quick application card business data provided in the second embodiment of the present application. Here, the quick application card on the desktop is displayed and exposed to the user as an example for exemplary description. Fig.10 As shown, the reporting process of the card exposure event includes the following steps.

[0205] In steps B1 and B2, the desktop application monitors the occurrence of a card exposure event and sends a message to the operation management application through the operation SDK. The message includes the first tracking identifier, the event type and event time of the card exposure event.

[0206] In steps B3 and B4, the event management module of the operation management application receives the first tracking identifier, the event type and event time of the card exposure event, queries the card resource data in the data management module based on the first tracking identifier, and obtains the device OAID from the OAID SDK. Then, the event management module determines the card business data of this card exposure event based on the card resource data, the card exposure event and the device OAID. The card business data includes the monitoring link and card collection data of the card exposure event.

[0207] Steps B5-1 to B5-3: The event management module reports the card collection data to the big data collection cloud, and returns the monitoring link of the card exposure event to the business promotion cloud and the third-party cloud respectively.

[0208] Above through Fig.10 A schematic diagram of a card exposure event reporting process in a method for reporting quick application card service data provided in an embodiment of the present application is illustrated. Fig.11 This section describes the timing diagram of reporting exposure events after an exposure event occurs on a quick app card created on the desktop.

[0209] According to the above Fig. 9 As can be seen from the process shown, the operation management application stores card resource data carrying the first tracking identifier, and when the electronic device displays the desktop, the desktop application displays the quick application card in a preset area of ​​the desktop, that is, the card is exposed to the customer, and the card carries the first tracking identifier.

[0210] Reference Fig.11 As shown, in Fig. 9 After step S212, the method for reporting quick app card service data further includes the following steps.

[0211] S301 and S302, the desktop application monitors the occurrence of a card exposure event, and then sends the card exposure event and a first tracking identifier to the operation management application.

[0212] S303 and S304, the operation management application obtains the card resource data according to the first tracking identifier and obtains the device OAID, and then determines the monitoring data and card collection data of the card exposure event according to the card resource data, the card exposure event and the device OAID.

[0213] It should be noted that the operation management application can obtain the card resource data from the local data storage module according to the first tracking identifier. If the acquisition fails, the operation management application can obtain the card resource data from the operation cloud according to the first tracking identifier.

[0214] S305. The operation management application reports the card collection data to the big data collection cloud. The card collection data includes business information and event information.

[0215] Exemplarily, the business information may include device OAID, card booth ID, card ID, card request ID, and / or scenario information related to the card exposure event.

[0216] Exemplarily, the event information may include an event type and an event time related to the card exposure event. In some embodiments, the event information may also include an event name and / or event content.

[0217] S306. The operation management application transmits a monitoring link to the business promotion cloud and the third-party cloud, where the monitoring link includes monitoring data of the card exposure event.

[0218] S307: The operation management application determines whether the reporting and feedback are successful.

[0219] S308: When it is determined that the reporting and feedback have failed, the operation management application executes a failure retry mechanism to re-report and feedback.

[0220] S309: When it is determined that the reporting and feedback are successful, the operation management application returns a message indicating that the event reporting is successful to the desktop application.

[0221] Third embodiment: Reporting process of card click event

[0222] Fig.12 1 is a schematic diagram of the reporting process of a card click event in the reporting method of the quick application card business data provided in the third embodiment of the present application. Here, the quick application card on the desktop is used as an example for exemplary description. Fig.12 As shown, the reporting process of the card click event includes the following steps.

[0223] Step C1: The desktop application monitors a card click event and sends the card click event and the card URL to the quick application engine application.

[0224] In some embodiments, the card click event refers to a card hotspot click event.

[0225] Steps C2 and C3: The quick application engine application analyzes the card click event to determine the event type and event time. The quick application engine application sends a message to the operation management application, the message including the first tracking identifier, the event type and event time of the card click event.

[0226] In steps C4 and C5, the event management module of the operation management application receives the first tracking identifier, the event type and event time of the card click event, and queries the card resource data in the data management module based on the first tracking identifier, and obtains the device OAID from the OAID SDK. Then the event management module determines the card business data of this card click event based on the card resource data, the card click event and the device OAID. The card business data includes the monitoring link and card collection data of the card click event.

[0227] Steps C6-1 to C6-3: The event management module reports the card collection data to the big data collection cloud, and returns the monitoring link of the card click event to the business promotion cloud and the third-party cloud respectively.

[0228] Above through Fig.12 A schematic diagram of a card click event reporting process in a method for reporting quick application card service data provided in an embodiment of the present application is illustrated below. Fig.13 This section describes the timing diagram of reporting exposure events after an exposure event occurs on a quick app card created on the desktop.

[0229] According to the above Fig. 9 As can be seen from the process shown, the operation management application stores card resource data carrying the first tracking identifier, and when the electronic device displays the desktop, the desktop application displays the quick application card in a preset area of ​​the desktop (such as the YOYO suggestion bar), that is, the card is exposed to the customer, and the card carries the first tracking identifier.

[0230] Reference Fig.13 As shown, in Fig. 9 After step S212, the method for reporting quick app card service data further includes the following steps.

[0231] S401 and S402, the desktop application monitors the occurrence of a card click event, and then sends the card click event and the first tracking identifier to the quick application engine application.

[0232] When a user clicks a hot area of ​​a quick app card, the desktop application monitors the occurrence of a card hot area click event.

[0233] S403 and S404, the quick application engine application determines the event information of the card click event, such as the event type, event time and event content, and the quick application engine application parses the card URL and determines whether the card URL contains a tracking identifier.

[0234] S405: When the card URL includes the first tracking identifier, the quick application engine application sends a message to the operation management application, where the message includes the first tracking identifier and event information.

[0235] Exemplarily, the business information may include a device OAID, a card booth ID, a card ID, a card request ID, and / or scenario information related to the card click event.

[0236] Exemplarily, the event information may include an event type and an event time related to the card click event. In some embodiments, the event information may also include an event name and / or event content.

[0237] S406 and S407, the operation management application obtains the card resource data according to the first tracking identifier, and obtains the device OAID, and then determines the monitoring data of the card click event and the card collection data according to the card resource data, event information and device OAID.

[0238] S408. The operation management application reports the card collection data to the big data collection cloud, where the card collection data includes business information and event information.

[0239] S409. The operation management application transmits a monitoring link back to the business promotion cloud and the third-party cloud. The monitoring link includes monitoring data of the card click event.

[0240] S410. The operation management application determines whether the reporting and feedback are successful.

[0241] S411. When it is determined that the reporting and feedback have failed, the operation management application executes a failure retry mechanism to re-report and feedback.

[0242] S412: When it is determined that the reporting and feedback are successful, the operation management application returns a message indicating that the event reporting is successful to the desktop application.

[0243] Fourth embodiment: Reporting process of card pull-up application event

[0244] Fig.14 This is a schematic diagram of the reporting process of the card launching application event in the reporting method of the quick application card business data provided in the third embodiment of the present application. Here, the quick application card on the desktop is used as an example for exemplary description. Fig.14 As shown, the reporting process of the card pull-up application event includes the following steps.

[0245] Step D1: The desktop application monitors the occurrence of a card application launch event, and sends the card application launch event and the card URL to the quick application engine application.

[0246] Steps D2 and D3: The quick application engine application analyzes the card application launch event to determine the event type and event time. The quick application engine application sends a message to the operation management application, the message including the first tracking identifier, the event type and event time of the card application launch event.

[0247] In steps D4 and D5, the event management module of the operation management application receives the first tracking identifier, the event type and event time of the card-pull-up application event, and queries the card resource data in the data management module based on the first tracking identifier, and obtains the device OAID from the OAID SDK. Then the event management module determines the card business data of this card-pull-up application event based on the card resource data, the card-pull-up application event and the device OAID. The card business data includes the monitoring link and card collection data of the card-pull-up application event.

[0248] Steps D6-1 to D6-3, the event management module reports the card collection data to the big data collection cloud, and returns the monitoring link of the card-launched application event to the business promotion cloud and the third-party cloud respectively.

[0249] Above through Fig.14 A schematic diagram of the card pull-up application event reporting process in the method for reporting the quick application card service data provided in the embodiment of the present application is illustrated below. Fig.15 This section describes the timing diagram of reporting exposure events after an exposure event occurs on a quick app card created on the desktop.

[0250] According to the above Fig. 9 As can be seen from the process shown, the operation management application stores card resource data carrying the first tracking identifier, and when the electronic device displays the desktop, the desktop application displays the quick application card in a preset area of ​​the desktop (such as the YOYO suggestion bar), that is, the card is exposed to the customer, and the card carries the first tracking identifier.

[0251] Reference Fig.15 As shown, in Fig. 9 After step S212, the method for reporting quick app card service data further includes the following steps.

[0252] S501 and S502, the desktop application monitors the occurrence of a card-pull-up application event, and then sends the card-pull-up application event and a first tracking identifier to the quick application engine application.

[0253] When the user clicks on the function control of the quick application card, the desktop application monitors that the application corresponding to the function control is triggered to start. Here, the card pull-up application event refers to the scenario where the quick application card triggers the application corresponding to the function control to start.

[0254] S503 and S504, the quick application engine application determines the event information of the card launching application event, such as event type, event time and event content, and the quick application engine application parses the card URL and determines whether the card URL contains a tracking identifier.

[0255] S505: When the card URL includes the first tracking identifier, the quick application engine application sends a message to the operation management application, where the message includes the first tracking identifier and event information.

[0256] Exemplarily, the business information may include a device OAID, a card booth ID, a card ID, a card request ID, and / or scenario information related to the card pull-up application event.

[0257] Exemplarily, the event information may include an event type and an event time related to the card pull-up application event. In some embodiments, the event information may also include an event name and / or event content related to the card pull-up application event.

[0258] S506 and S507, the operation management application obtains the card resource data according to the first tracking identifier, and obtains the device OAID, and then determines the monitoring data of the card launch application event and the card collection data according to the card resource data, event information and device OAID.

[0259] S508. The operation management application reports the card collection data to the big data collection cloud, where the card collection data includes business information and event information.

[0260] S509. The operation management application transmits a monitoring link to the business promotion cloud and the third-party cloud. The monitoring link includes monitoring data of the card-pulling application event.

[0261] S510: The operation management application determines whether the reporting and feedback are successful.

[0262] S511. When it is determined that the reporting and feedback have failed, the operation management application executes a failure retry mechanism to re-report and feedback.

[0263] S512: When it is determined that the reporting and feedback are successful, the operation management application returns a message indicating that the event reporting is successful to the desktop application.

[0264] The above embodiment takes the scenario of the quick application card on the desktop as an example to illustrate the card business data reporting process of the card exposure event, card click event and card application launch event. In actual implementation, the method provided in the embodiment of the present application can also be applied to the quick application card of the negative one screen interface or the quick application card in other interfaces.

[0265] Below through Fig. 9 This is a sequence diagram for creating a quick app card on the negative one screen. Fig. 9 As shown, the process of creating a card in the negative one screen interface includes the following steps.

[0266] S601: The desktop application detects that the negative one screen interface is switched to the foreground.

[0267] In the embodiment of the present application, the operation management application can register with the negative one screen application to monitor "the negative one screen is switched to the foreground". When the user triggers the electronic device to switch the display screen interface to the negative one screen interface, the negative one screen application can monitor that the negative one screen interface is switched to the foreground and request the card resource data from the operation management application.

[0268] In some embodiments, when a user triggers an electronic device to switch the display screen interface to the negative one screen, the desktop application, after listening to the event that the negative one screen is switched to the foreground, determines whether the current scene of the electronic device meets the preset card creation conditions; when the desktop application determines that the current scene of the electronic device meets the preset card creation conditions, the desktop application requests the operation management application for card resource data for creating a negative one screen card.

[0269] For example, the user may slide a finger along a preset direction on the desktop of the electronic device to trigger the display of the negative one screen interface.

[0270] S602: The negative one screen application sends a request to the operation management application. The request carries a second request ID and a second booth ID, and is used to request card resource data corresponding to the second booth ID.

[0271] The second request ID is used to indicate the current request of the negative one screen application, and the second booth ID is used to indicate the card display position information requested by the negative one screen application. It should be noted that the second request ID is different from the first request ID, and the second booth ID may be different from the first booth ID.

[0272] S603: The operation management application forwards the request to the operation cloud.

[0273] S604: The operation cloud generates a second tracking identifier in response to the request, and adds the second tracking identifier to the card URL.

[0274] It should be noted that the second tracking identifier is different from the first tracking identifier.

[0275] S605. The operation cloud generates card resource data carrying the card URL.

[0276] S606: The operation cloud sends the card resource data carrying the card URL to the operation management application, where the card URL carries the first tracking identifier.

[0277] S607: The operation management application stores the card resource data carrying the first tracking identifier.

[0278] S608. The operation management application returns card resource data including the card URL to the negative one screen application.

[0279] This application does not limit the execution order of S607 and S608.

[0280] S609: The negative one screen application sends a card URL to the quick application engine application, where the card URL carries a first tracking identifier.

[0281] S610: The quick application engine application downloads the rpk package according to the card URL, and creates a quick application card according to the rpk package.

[0282] S611. The quick application engine application feeds back to the negative one screen application that the quick application card creation is complete, and the quick application card carries the first tracking identifier.

[0283] S612: When the electronic device displays the negative one screen, the negative one screen application displays a quick application card in a preset area (YOYO suggestion bar) of the negative one screen interface, and the quick application card carries a first tracking identifier.

[0284] It should be noted that for the scenario of quick application cards in the negative one screen interface, the card business data reporting process of card exposure events, card click events and card application launch events is similar to the card business data reporting process of card exposure events, card click events and card application launch events in the scenario of quick application cards on the desktop in the above embodiment, and will not be repeated in the embodiments of this application.

[0285] In some possible implementations, if the accumulated storage time of the card resource data on the electronic device side is greater than the preset storage time, the electronic device may delete the stored card resource data. After the preset storage time, the card resource data stored on the electronic device side is deleted to free up more memory space. The preset storage time may be set by the electronic device side or by the server side. Exemplarily, the preset storage time may be 7 days.

[0286] Fig.17 The schematic diagram of the process of creating and rendering a quick application card by the quick application engine application and the host process provided in the embodiment of the present application is shown. Fig.17 As shown, on the cloud server side, the developer service platform uploads the quick app card data to the cloud server through the quick app card interface.

[0287] On the electronic device side, the quick application engine application loads the engine code into the host process to complete the card initialization.

[0288] Among them, the quick application engine application is a quick application (RPK) execution environment pre-installed in electronic devices. It has complete quick application capabilities and can be used to verify the actual performance of RPK on electronic devices.

[0289] The host process refers to a series of processes of the host, such as UI thread, creation of quick app cards, node conversion, and drawing and rendering. The host can be the quick service center, negative one screen, desktop, lock screen, or YOYO suggestion.

[0290] In the process of creating a quick application card, the electronic device starts the JS thread, which triggers the quick application engine application to download the quick application RPK package from the cloud server and send the quick application RPK package to the JS thread to complete resource loading and use the V8 engine to build a DOM model. After the node conversion, it is drawn and rendered to obtain a quick application card.

[0291] Among them, the V8 engine is a JavaScript engine implementation.

[0292] In an embodiment of the present application, the quick application engine application provides a card API, and all hosts can share the JS quick application card.

[0293] In an embodiment of the present application, when the host displays a JS quick application card, the card component can be dynamically loaded into the host process as needed.

[0294] In some embodiments, the user's scene can be determined in combination with reservation orders and location-based services, and preset associated services corresponding to the user's scene can be obtained, and associated services can be recommended to the user based on the user's behavior habits.

[0295] The reservation order information may come from a text message and / or an email received by the electronic device, etc. The electronic device may parse the received text message and / or email to obtain the reservation order information.

[0296] For example, reservation order information may be scenic spot ticket reservation information, air ticket reservation information, train ticket reservation information, conference reservation information, hotel reservation information, and movie ticket purchase information.

[0297] The electronic device may recommend associated services by displaying quick application cards, which may include a real-time location map corresponding to the scene where the user is located and options for preset associated services.

[0298] Exemplarily, the above-mentioned preset associated services may be the following services:

[0299] (1) Travel services: scenic spots, tickets, toilets, and food;

[0300] (2) Flight services: flight orders, boarding passes, food and drinks;

[0301] (3) Calendar services: meeting schedule, taxi, online meeting, and phone calls;

[0302] (4) Travel services: hotel reservations, taxis, and reporting lost luggage;

[0303] (5) Local life services: movie tickets, ticket collection, parking, drinks.

[0304] Quick application cards have the following beneficial effects: information display is more intuitive, service recommendations are more comprehensive, and relevance is more significant.

[0305] In the application embodiments, the display forms of quick application cards include but are not limited to: (1) displaying cards on the interface of the quick service center; (2) displaying cards on the negative one screen; (3) displaying cards on the desktop; (4) displaying cards on the foldable screen; and (5) displaying cards on the lock screen interface.

[0306] Through this application solution, it is possible to combine reservation order information, user behavior data, and location-based services LBS to explicitly recommend related services required by "scenario-based intentions". In other words, this application can provide users with targeted related services for different scenarios such as travel, flights, schedules, travel, and local life.

[0307] The above exemplifies various application scenarios of quick app cards and various display forms of quick app cards. The following is a more intuitive explanation of various application scenarios of quick app cards and various display forms of quick app cards through the user interface of an electronic device in conjunction with the accompanying drawings.

[0308] Fig.18 The following is a schematic diagram of the interface for setting up quick application cards based on YOYO suggestions. By setting up YOYO suggestions, the electronic device can present corresponding quick application cards in the display bar of YOYO suggestions according to the scene and usage habits, and provide various services.

[0309] like Fig.18 As shown in (a) of FIG. 1 , the electronic device displays a desktop 71, and a setting application icon 72 is displayed on the desktop 71. When the user clicks the setting application icon 72, as shown in FIG. Fig.18 As shown in (b) of FIG. 1 , the electronic device switches from displaying the desktop 71 to displaying the setting interface 73 in response to the user operation, and the setting interface 73 displays a smart assistant option 74. When the user clicks the smart assistant option 74, as shown in FIG. Fig.18 As shown in (c) of FIG. 1 , the electronic device switches from displaying the setting interface 73 to displaying the smart assistant setting interface 75 in response to the user operation. The smart assistant setting interface 75 displays the YOYO suggestion option 76. When the user clicks the YOYO suggestion option 76, as shown in FIG. Fig.18As shown in (d), the electronic device switches from displaying the smart assistant interface 75 to displaying the YOYO suggestion setting interface 77 in response to the user operation. The services that YOYO suggestions can provide are displayed in the YOYO suggestion setting interface 77. The electronic device can recommend the APP or service that the user currently needs through YOYO suggestions based on the scene and usage habits. The service setting bar 78 displays the services that YOYO suggestions can provide, such as travel services, flight services, schedule services, travel services, local life services, etc. Each service option corresponds to a switch control 79. The user can trigger the electronic device to turn on or off the service by clicking the switch control of a service according to actual usage needs.

[0310] In some embodiments, the travel service, flight service, schedule service, travel service, and local life service are all enabled by default in YOYO suggestions. When each service is enabled, the electronic device can recommend the currently needed APP or service to the user through YOYO suggestions according to the scenario and usage habits. For example, the electronic device can display the quick application card of the travel service category, the quick application card of the flight service category, the quick application card of the schedule service category, the quick application card of the travel service category, or the quick application card of the local life service category in the YOYO suggestion bar.

[0311] The following takes YOYO suggestion as an example to illustrate the method for reporting the business data of the quick application card provided by the embodiment of the present application. Among them, the quick application card is displayed with YOYO suggestion as the host.

[0312] Fig.19 A schematic diagram of the user interaction interface of the quick application card of the negative one screen interface is shown. Fig.19 As shown in (a) in the figure, when the electronic device displays the desktop, if the user wants to view the quick application cards recommended by the electronic device based on the user's order and the current application scenario, the user can slide his finger along the direction indicated by the arrow on one side of the screen to trigger the electronic device to display the negative one screen. Fig.19 As shown in (b), the electronic device switches from displaying the desktop to displaying the negative one screen in response to the user operation, and the YOYO suggestion bar is displayed in the negative one screen interface.

[0313] In some embodiments, the YOYO suggestion bar on the negative first screen may display a quick app card of the flight service category. In other embodiments, the YOYO suggestion bar on the negative first screen may display quick app cards of other categories except the flight service category. The quick app cards displayed in the YOYO suggestion bar on the negative first screen are quick app cards recommended in real time by the electronic device based on the user's order and the current application scenario.

[0314] Exemplarily, in the present application scheme, the quick application card can not only display travel order information (such as an introduction to a scenic spot), but also display a map of the travel location, ticket information, toilet-related information, and nearby food information. The quick application card can also provide a navigation or taxi service entrance from the current location to the scenic spot, and the electronic device can dynamically update and display the map in the quick application card according to the real-time positioning information of the electronic device.

[0315] In a possible scenario of the present application, when the negative one screen application requests to create a quick application card on the negative one screen interface, the operation management application receives the request and obtains the card resource data from the operation cloud. The card resource data carries the second tracking identifier, which is the tracking identifier generated by the operation cloud for this request. The operation management application stores the card resource data carrying the second tracking identifier locally, and sends the card resource data carrying the second tracking identifier to the negative one screen application for creating a quick application card on the negative one screen interface.

[0316] In a possible scenario of the present application, as shown in reference 19, the electronic device displays a negative one-screen interface and displays a quick application card in the negative one-screen interface. In this case, the negative one-screen application can notify the operation management application of the occurrence of a card exposure event and a second tracking identifier. Accordingly, the operation management application can obtain the card resource data from the electronic device locally according to the second tracking identifier, and then determine the card business data related to the card exposure event according to the card resource data, the event information of the card exposure event, and the device OAID. Then, the operation management application reports the card business data related to the card exposure event to the cloud server.

[0317] In a possible scenario of the present application, as shown in reference 19, the electronic device receives a user's touch operation on a functional control (such as a food control) of a quick application card. In this case, the quick application engine application can sense that a card click event has occurred, and then send the event information of the card click event and the second tracking identifier to the operation management application. Accordingly, the operation management application can obtain the card resource data from the local electronic device according to the second tracking identifier, and then determine the card business data related to the card click event based on the card resource data, the event information of the card click event, and the device OAID. Then, the operation management application reports the card business data related to the card click event to the cloud server.

[0318] In a possible scenario of the present application, as shown in reference 19, the electronic device receives a touch operation of a user on a function control of a quick application card, and the function control (such as a food control) is associated with an application (such as a food application). In this case, the food application will be triggered to start, and the electronic device will jump from the negative one screen interface to the main interface of the food application. In this case, the quick application engine application can sense that a card application pull-up event has occurred, and send the event information of the card click event and the second tracking identifier to the operation management application. Accordingly, the operation management application can obtain the card resource data from the local electronic device according to the second tracking identifier, and then determine the card business data related to the card application pull-up event based on the card resource data, the event information of the card click event, and the device OAID. Then, the operation management application reports the card business data related to the card application pull-up event to the cloud server.

[0319] In a possible scenario of the present application, when a desktop application requests to create a quick application card on the desktop interface, the operation management application receives the request and obtains card resource data from the operation cloud, and the card resource data carries a first tracking identifier, which is a tracking identifier generated by the operation cloud for this request. The operation management application stores the card resource data carrying the second tracking identifier locally, and sends the card resource data carrying the first tracking identifier to the desktop application for creating a quick application card on the desktop interface.

[0320] Fig. 20 A schematic diagram of the user interaction interface of the desktop quick application card is shown. Fig. 20 As shown in (a) in the figure, the electronic device can switch between displaying the weather clock card and displaying the quick app card in response to the user operation. Specifically, if the user wants to view the quick app card recommended by the electronic device based on the user's order and the current application scenario, the user can slide his finger on the weather quick app card in the direction indicated by the arrow to trigger the electronic device to display the quick app card. Fig. 20 As shown in (b), in response to a user operation, the electronic device switches the weather clock card displayed on the desktop to a YOYO suggestion bar, and the YOYO suggestion bar can be used to display quick application cards.

[0321] In a possible scenario of the present application, as shown in reference 20, the electronic device displays a desktop interface and displays a quick application card on the desktop interface. In this case, the desktop application can notify the operation management application of the occurrence of a card exposure event and a first tracking identifier. Accordingly, the operation management application can obtain card resource data from the electronic device locally according to the first tracking identifier, and then determine the card business data related to the card exposure event according to the card resource data, the event information of the card exposure event, and the device OAID. Then, the operation management application reports the card business data related to the card exposure event to the cloud server.

[0322] In a possible scenario of the present application, as shown in reference 20, the electronic device receives a user's touch operation on a functional control (such as a food control) of a quick application card. In this case, the quick application engine application can sense that a card click event has occurred, and then send the event information of the card click event and the first tracking identifier to the operation management application. Accordingly, the operation management application can obtain the card resource data from the local electronic device according to the first tracking identifier, and then determine the card business data related to the card click event based on the card resource data, the event information of the card click event, and the device OAID. Then, the operation management application reports the card business data related to the card click event to the cloud server.

[0323] In a possible scenario of the present application, as shown in reference 20, the electronic device receives a touch operation of a user on a function control of a quick application card, and the function control (such as a food control) is associated with an application (such as a food application). In this case, the food application will be triggered to start, and the electronic device will jump from the desktop interface to the main interface of the food application. In this case, the quick application engine application can sense that a card application pull-up event has occurred, and send the event information of the card click event and the first tracking identifier to the operation management application. Accordingly, the operation management application can obtain the card resource data from the local electronic device according to the first tracking identifier, and then determine the card business data related to the card application pull-up event based on the card resource data, the event information of the card click event, and the device OAID. Then, the operation management application reports the card business data related to the card application pull-up event to the cloud server.

[0324] The above example of setting up a quick application card through YOYO suggestion is used to exemplarily illustrate the method for reporting the quick application card service data provided by the embodiment of the present application. The following example of adding a card through the quick service center is used to illustrate the method for reporting the quick application card service data provided by the embodiment of the present application.

[0325] Fig.21 The figure shows an interface diagram of finding a quick application card through the quick service center entrance and adding the quick application card to the negative one screen. Fig.21 As shown in (a) of FIG. 1 , the electronic device displays an interface of the negative one screen, and the interface of the negative one screen displays an entry control 81 of the quick service center. The electronic device receives the user's operation on the entry control 81. Fig.21 As shown in (b) in FIG. 1 , the electronic device jumps from the interface of the negative one screen to the quick service center interface in response to the user operation. The quick service center interface displays a quick application card bar and an "add to negative one screen" control 82. The electronic device receives the user's operation on the "add to negative one screen" control 82. Fig.21As shown in (c), the electronic device jumps from the quick service center interface to the interface of the negative one screen in response to the user operation, and a quick application card bar is newly displayed in the interface of the negative one screen.

[0326] In an embodiment of the present application, at least one of the following cards can be displayed in the quick app card bar: quick app cards such as travel services, flight services, schedule services, travel services, and local life services.

[0327] The specific settings can be preset by the system or customized by the user.

[0328] It should be noted that the classification of quick app cards here is for illustrative purposes only. In actual implementation, quick app cards can also be divided into other possible forms according to other scenarios, which is not limited in the embodiments of the present application. For the sake of convenience, quick app cards of various user scenario types such as travel services, flight services, schedule services, travel services, and local life services are used as examples for illustrative purposes.

[0329] After a quick app card is added to the interface of the negative one screen, if the electronic device does not detect a user order or a current application scenario, the electronic device may display default content in the quick app card bar.

[0330] If the electronic device detects a user order and a current application scenario, the electronic device recommends a quick app card of a specific user scenario type in real time according to the user order and the current application scenario, and displays the recommended quick app card in the quick app card bar.

[0331] For example, Fig.21 As shown in (d) in the figure, when the electronic device detects a flight order triggered by a user on the electronic device, the electronic device generates a quick app card corresponding to the flight order, and displays a flight service quick app card in the quick app card column in the interface of the negative one screen. When the electronic device detects a flight order triggered by a user on the electronic device, the electronic device generates a quick app card corresponding to the flight order, and recommends a flight service quick app card in the quick service center interface.

[0332] In the present application, flight service quick application cards can be used to display flight order information (such as flight departure time, airport and terminal information), as well as maps of the corresponding airports, boarding pass information, nearby food and drink information. Quick application cards can also be used to provide navigation or taxi service entrances from the current location to the airport.

[0333] It should be noted that the above quick application card is displayed on the negative one screen. Figure 2 Another quick app card display method is described, in which the quick app card is displayed with the desktop as the host.

[0334] Fig. 22 The following is a schematic diagram showing the interface of recommending quick application cards on the negative one screen and adding quick application cards to the desktop by the user. Fig. 22 As shown in (a) of FIG. 1 , the electronic device displays an interface of the negative one screen, and displays a quick application card and an “add” control 91 in the interface of the negative one screen. The electronic device receives the user's operation on the “add” control 91. Fig. 22 As shown in (b) in FIG. 1 , the electronic device jumps from the interface of the negative one screen to the quick application card setting interface in response to the user operation. In the quick application card setting interface, multiple pages can be displayed alternately, and each page displays a type of quick application card thumbnail. Fig. 22 As shown in (b) in the figure, the quick app card setting interface includes an "Add to negative one screen" control and an "Add to desktop" control. Fig. 22 As shown in (c) and (d), the electronic device receives the user's operation on the "Add to Desktop" control 92. In response to the user's operation, the electronic device jumps from the quick app card setting interface to the desktop and displays the quick app card on the desktop.

[0335] The electronic device can recommend quick application cards of specific user scenario types in real time based on the user order and the current application scenario, and the electronic device updates and displays quick application cards of different user scenario types. In other words, the electronic device can switch to display quick application cards corresponding to different user scenarios as the user scenario changes.

[0336] The above embodiments of the present application take YOYO suggestions, negative one screen, and desktop as examples to illustrate the reporting method of the quick application card business data provided by the embodiments of the present application. In actual implementation, the quick application card can also be displayed with other interfaces as the host.

[0337] The various embodiments described herein may be independent solutions or may be combined according to internal logic, and all of these solutions fall within the protection scope of this application.

[0338] The above mainly describes the solution provided by the embodiment of the present application from the perspective of method steps. It is understandable that, in order to achieve the above functions, the electronic device implementing the method includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of protection of the present application.

[0339] The embodiment of the present application can divide the functional modules of the electronic device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other feasible division methods in actual implementation.

[0340] The present application also provides a chip, which is coupled to a memory and is used to read and execute computer programs or instructions stored in the memory to execute the methods in the above embodiments.

[0341] The present application also provides an electronic device, which includes a chip, and the chip is used to read and execute a computer program or instruction stored in a memory, so that the method in each embodiment is executed.

[0342] This embodiment also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the method for reporting quick application card business data in the above-mentioned embodiment.

[0343] This embodiment further provides a computer program product, wherein the computer-readable storage medium stores program code. When the computer program product is run on a computer, the computer executes the above-mentioned related steps to implement the method for reporting quick application card business data in the above-mentioned embodiment.

[0344] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer execution instructions, and when the device is running, the processor can execute the computer execution instructions stored in the memory to enable the chip to execute the quick application card business data reporting method in the above-mentioned method embodiments.

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

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

[0347] The term "and / or" in this article is a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The symbol " / " in this article indicates that the associated objects are in an or relationship, for example, A / B means A or B.

[0348] The terms "first" and "second" in the specification and claims herein are used to distinguish different objects rather than to describe a specific order of objects. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" refers to two or more than two, for example, multiple processing units refer to two or more processing units, etc.; multiple elements refer to two or more elements, etc.

[0349] It should be noted that, in the embodiments of the present application, "greater than" can be replaced by "greater than or equal to", "less than or equal to" can be replaced by "less than", or "greater than or equal to" can be replaced by "greater than", and "less than" can be replaced by "less than or equal to".

[0350] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for reporting quick application card service data, characterized in that: Applied to electronic equipment, the method comprises: When the electronic device meets a first preset condition, obtaining card resource data from a first server, the card resource data including a card URL parameter set with a first tracking identifier and a preset storage duration of the card resource data on the electronic device side; storing the card resource data on the electronic device side with the first tracking identifier as an index; creating and displaying a first quick app card according to the card resource data, the first quick app card carrying the first tracking identifier; A first operation of the user is received, where the first operation triggers a first event to occur in the first quick app card; the first event is a card exposure event, a card click event, or a card application launch event; In response to the first event occurring in the first quick app card, obtaining card resource data corresponding to the first quick app card from the electronic device according to the first tracking identifier carried by the first quick app card; Determine card service data of the first quick app card according to the card resource data and the event information of the first event; the card service data includes a monitoring link and card collection data of the first event; The card collection data is sent to the second server, and the monitoring link of the first event is sent to the third server.

2. The method according to claim 1, characterized in that: The first server is an operation cloud server, the second server is a big data collection cloud server, and the third server is a business promotion cloud server and / or a third-party server.

3. The method according to claim 1, characterized in that The first preset condition includes that the electronic device displays a first interface, where the first interface is an interface configured to display a quick application card; When the electronic device meets the first preset condition, acquiring the card resource data from the first server includes: In response to a second operation by the user, the electronic device displays the first interface; In response to the electronic device displaying the first interface, sending a first request message to the first server, where the first request message is used to request creation of a quick app card; A first response message sent by the first server according to the first request message is received, where the first response message includes the card resource data.

4. The method according to claim 3, characterized in that The first preset condition also includes that the current user scenario information of the electronic device satisfies the preset scenario information; The sending a first request message to the first server in response to the electronic device displaying the first interface includes: In response to the electronic device displaying the first interface, determining whether current user scenario information of the electronic device meets the preset scenario information; When it is determined that the user scenario information satisfies the preset scenario information, the first request message is sent to the first server, the first request message includes the user scenario information, and the card resource data is data determined based on the user scenario information.

5. The method according to claim 3, characterized in that: The first request message includes a request identifier, where the request identifier is used to request creation of the first quick app card, and the first tracking identifier is an identifier generated by the first server according to the request identifier; When the request identifiers are different, the tracking identifiers obtained from the first server are different.

6. The method according to claim 5, characterized in that The first request message also includes a booth identifier, where the booth identifier is used to indicate a display position and a display size of the quick app card requested to be created, and the card resource data is data determined based on the booth identifier.

7. The method according to claim 4, characterized in that The creating and displaying the first quick app card according to the card resource data includes: displaying the first quick app card on the first interface; Among them, the first interface is a desktop interface or a negative one screen interface.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: If the accumulated storage time of the card resource data on the electronic device side is greater than the preset storage time, the card resource data stored on the electronic device side is deleted.

9. The method according to any one of claims 1 to 7, characterized in that After receiving the first operation of the user, the method further includes: In response to a first operation on the screen of the electronic device, the first interface is switched to the foreground display, the first operation being triggering unlocking the screen or sliding the screen; in response to the first interface being switched to the foreground display, it is determined that the card exposure event occurs in the first quick application card.

10. The method according to any one of claims 1 to 7, characterized in that After receiving the first operation of the user, the method further includes: In response to a first operation on the first quick app card, it is determined that the card click event occurs on the first quick app card; the first operation is a click operation on a preset area of ​​the first quick app card.

11. The method according to any one of claims 1 to 7, characterized in that After receiving the first operation of the user, the method further includes: In response to a first operation on the first quick app card, a first app is started and a page of the first app is displayed, and it is determined that a card-pull-up-app event occurs in the first quick app card; The first operation is selecting a first control in the first quick app card, and the first control is a control associated with the first application.

12. The method according to any one of claims 1 to 7, characterized in that Before determining the card service data of the first quick application card according to the card resource data and the event information of the first event, the method further includes: acquiring an anonymous identity of the electronic device; The determining, according to the card resource data and the event information of the first event, the card service data of the first quick app card includes: determining, according to the card resource data, the first event, and the anonymous identity of the electronic device, the card service data of the electronic device regarding the first quick app card.

13. The method according to any one of claims 1 to 7, characterized in that The monitoring link of the first event is a link transmitted back to the third server when the occurrence of the first event is monitored, and the monitoring link of the first event includes the event name, event type and / or event occurrence time of the first event; The card collection data is user behavior data collected for the first event according to preset rules.

14. The method according to any one of claims 1 to 7, characterized in that The creating and displaying a first quick app card according to the card resource data includes: Download the rpk package from the quick app engine cloud according to the card URL parameter, and create a view based on the rpk package to obtain the first quick app card.

15. The method according to any one of claims 1 to 7, characterized in that The electronic device includes an operation management application, a media application and a quick application engine application; the media application is a desktop application or a negative one screen application; the operation management application includes a data management module; When the electronic device meets the first preset condition, the card resource data is obtained from the first server, comprising: when the electronic device meets the first preset condition, the media application notifies the operation management application to obtain the card resource data; the operation management application obtains the card resource data from the first server; The storing the card resource data by using the first tracking identifier as an index on the electronic device side; and creating and displaying a first quick application card according to the card resource data, includes: The operation management application stores the card resource data in the data management module using the first tracking identifier as an index; The operation management application sends the card resource data to the media application; the media application calls the quick application engine application to create and display the first quick application card based on the card resource data.

16. The method according to claim 15, characterized in that After receiving the first operation of the user, the method further includes: The media application determines, in response to the first operation of the user, that the card exposure event occurs in the first quick application card; and sends the event information of the card exposure event and the first tracking identifier to the operation management application; or The quick application engine application determines, in response to the first operation of the user, that the card click event occurs on the first quick application card, and sends the event information of the card click event and the first tracking identifier to the operation management application; or The quick application engine application determines, in response to a first operation of the user, that the card application launch event occurs in the first quick application card, and sends event information of the card application launch event and the first tracking identifier to the operation management application.

17. The method according to claim 16, characterized in that The operation management application also includes an event management module; The acquiring, from the electronic device side, card resource data corresponding to the first quick application card according to the first tracking identifier carried by the first quick application card includes: the event management module of the operation management application acquiring, from the data management module, the card resource data corresponding to the first tracking identifier according to the first tracking identifier; The determining the card service data of the first quick app card according to the card resource data and the event information of the first event includes: the event management module of the operation management application determines the card service data of the first quick app card according to the card resource data and the event information of the first event.

18. A method for reporting quick application card service data, characterized in that: Applied to a first server, the method comprises: Receiving a first request message sent by an electronic device, where the first request message is used to request creation of a first quick app card; the first request message includes a request identifier; In response to the first request message, a first tracking identifier is generated according to the request identifier, and the first tracking identifier is concatenated with the URL parameter of the first quick app card; when the request identifier is different, the generated tracking identifier is different; Sending a first response message to the electronic device, the first response message including card resource data of the first quick app card, the card resource data including a URL parameter set with the first tracking identifier, and a preset storage duration of the card resource data on the electronic device side; On the electronic device side, the card resource data is stored with the first tracking identifier as an index; when a card event occurs, the card resource data corresponding to the first tracking identifier is obtained from the electronic device side according to the first tracking identifier; and the card service data of the first quick application card is determined according to the card resource data and event information of the card event.

19. The method according to claim 18, characterized in that The first request message also includes user scenario information; and the method further includes: The card resource data is determined according to the user scenario information.

20. The method according to claim 19, characterized in that The first request message also includes a booth identifier, where the booth identifier is used to indicate a display position and a display size of the quick app card requested to be created; The determining the card resource data according to the user scenario information includes: The card resource data is determined according to the user scenario information and the booth identification.

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: Determining the preset storage duration, and setting the preset storage duration in the card resource data; The preset storage time is defined as follows: when the storage time of the card resource data on the electronic device side is greater than the preset storage time, the card resource data will be deleted.

22. An electronic device, characterized in that: The electronic device comprises a processor, a memory, and a computer program stored in the memory, wherein the processor is configured to execute the computer program so that the electronic device implements the method according to any one of claims 1 to 17.

23. A server, characterized in that: The server comprises a processor, a memory and a computer program stored in the memory, wherein the processor is configured to execute the computer program so that the server performs the method according to any one of claims 18 to 21.

24. A communication system, characterized in that: Includes the electronic device as claimed in claim 22 and the server as claimed in claim 23.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 17, or the method according to any one of claims 18 to 21.

Images