Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Generally, a business can access a service platform and publish a user applet related to the business, such as an applet of a physical store of the business, to a user client through the platform, so as to provide a function of performing an operation (such as commodity display, order information acquisition, order display, order placement, and the like) for the business to a user through the user applet. With the development of business of merchants, some display pages in applets released by the merchants may need to be updated, such as adding an interactive component corresponding to a new function, changing a display position and a display style of a currently existing interactive component, and the like.
In this regard, the embodiments of the present specification propose a scheme for directly configuring and updating an applet by a merchant: for an interactive component of a display page of a certain user applet for which a configuration operation is implemented by a merchant, a server generates a mapping relation between a page identifier and component configuration information generated according to the interaction operation; and then for a target display page requested to be displayed by the user applet configured with the interactive component, the server side can determine corresponding target component configuration information according to the mapping relation, and returns the information and the page data to the applet, so that the webpage data are rendered and displayed on the target display page through the interactive component indicated by the target component configuration information, wherein the interactive component displayed in the target display page is the interactive component configured by the merchant. As can be seen, the scheme can be directly configured by the merchant in a targeted manner for the display page of the user applet. This scheme is explained in detail below by means of specific examples.
Fig. 1 is a schematic diagram of an architecture of an applet page configuration system according to an exemplary embodiment. As shown in fig. 1, the system may include anapplet server 11, anapplication server 12, an electronic device used by a merchant (such as a cell phone 13), an electronic device used by a user (such as a cell phone 14), and a network 10.
Theapplet servers 11 and theapplication servers 12 may be physical servers including a separate host, or may be virtual servers carried by a host cluster. In the operation process, the server may operate a server-side program of a certain application to serve as a corresponding server to implement a related service function of the application. For example, theapplet server 11 may run a server-side program of the service platform to be implemented as a server side of the service platform; theapplication server 12 may run a server-side program of a user client used by the user to implement as a server for the application program.
Cell phone 13 andcell phone 14 represent one type of electronic device that may be used by a merchant and a user, respectively. Indeed, electronic devices of the type such as the following may also be used: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. During operation, the electronic device may run a client-side program of an application to implement a related service function of the application. For example, themobile phone 13 may run a merchant client program to be implemented as a merchant client, in which a merchant applet may be installed and run; accordingly, thecell phone 14 may run a user client program to be implemented as a user client in which a user applet may be installed and run. In addition, since the claims do not refer to the application server, the "server" in each claim may be understood as the applet server implemented by theapplet server 11 shown in fig. 1, and the description in the following description distinguishes between the "server" and the "application server", and is described here.
The network 10 may include various types of wired or wireless networks. For example, Network 10 may include the Public Switched Telephone Network (PSTN) and/or the Internet (Internet). Wherein, long connections can be established between thesmall program server 11 and the mobile phones 13-14, between theapplication server 12 and themobile phone 14, and between thesmall program server 11 and theapplication server 12 through the network 10 for communication.
Certainly, through cooperation between relevant parties in the applet page configuration system, the system can implement, in addition to the configuration of the user applet, other functions such as configuration page display, configuration operation detection, component configuration information generation, mapping relationship establishment, page data rendering display, and the like, which is not limited in this description embodiment.
Based on the architecture of the applet page configuration system, the specification provides an applet page configuration system, which comprises a merchant applet, a server and a user applet configured with an interactive component.
The system comprises a merchant applet, a server and a user applet, wherein the merchant applet displays a configuration page of a display page for the user applet, generates component configuration information according to configuration operation of a plurality of interactive components contained in the configuration page by a merchant, and sends a page identifier of the display page and the component configuration information to the server in a correlation manner;
the server establishes a mapping relation between the page identifier and the component configuration information; responding to a data acquisition request initiated by a user applet configured with an interactive component for a target display page, determining target component configuration information corresponding to the target display page according to the mapping relation, and returning the target component configuration information and page data of the target display page to the user applet configured with the interactive component;
and the user applet configured with the interactive component initiates the data acquisition request to the server, and renders and displays the page data through the interactive component indicated by the target component configuration information on the target display page under the condition of receiving the target component configuration information and the page data.
The merchant applet and the user applet in the system run on the merchant client and the user client respectively. Although named "user applet", the applet provides functions related to the merchant, such as a product browsing function, an order placing function, a payment function, and the like for the physical store of the merchant to the user. The merchant client is a tool for merchants to uniformly manage physical stores, user applets and the like. For a merchant who issues at least one user applet, the merchant can configure the display page in any one user applet through the merchant applet corresponding to the merchant, namely, the merchant configures and operates the interactive component in the display page in real time.
The above method is described in detail with reference to the following examples. Referring to fig. 2, fig. 2 is a flowchart of an applet page configuring method according to an exemplary embodiment. As shown in fig. 2, the method applied to the server may include the following steps:
step 202, establishing a mapping relation between a page identifier and component configuration information according to the page identifier and the component configuration information of a display page of a user applet, which are sent by merchant applet association; and the component configuration information is generated by the merchant applet after the configuration page aiming at the display page is displayed according to the configuration operation of the merchant aiming at a plurality of interactive components contained in the configuration page.
First, it should be noted that a merchant may register a merchant applet in advance through a service platform corresponding to a service end, and issue a user applet having a preset function in a user client program through an application platform corresponding to an application service end. One or more user applets can be issued by the same merchant, wherein in the case of issuing a plurality of user applets, any one of the user applets is the user applet. Any merchant registered merchant applet may be used to manage at least one user applet it publishes, and the specific functions of the merchant applet and the user applet are not limited in this specification.
The display page of the user applet usually includes a plurality of triggerable interactive components, for example, a home page of the applet can display a plurality of marketing booth components, and the user can control the applet to jump to a corresponding page by triggering any one of the components. After the merchant applet and the user applet are released, a developer (for example, an applet developer of a service platform corresponding to a server) may perform configuration update on an interactive component of any display page in the user applet, for example, develop an interactive component with a new function, update a display position, a display style, and the like of an interactive component with an original function. In order to distinguish the interaction component that has been published by the server from the newly published interaction component, the interaction component is hereinafter referred to as a history interaction component and an interaction component, respectively.
The developer can issue the developed interaction components corresponding to the new functions, the new positions, the new styles and the like to the server side, so that on one hand, the interaction components can be conveniently configured by a merchant, and on the other hand, the interaction components are configured by the user applet, so that the user applet can update the user applet. The process of issuing the interactive component in the service end by the merchant applet comprises the process of uploading and storing the developed interactive component in the service end.
After the interactive component is released, the service end can send a configuration notification message to the merchant applet, so that the service end can display the message to the merchant, and the merchant can decide whether to configure the newly released interactive component or not; or, a page configuration request may be initiated to the service by the merchant applet actively, for example, when it is detected that the merchant opens the management page for the user applet in the merchant applet, the merchant applet may initiate the request to the service, so that the service may determine whether there is an interaction component that has been issued and that the merchant applet has not configured yet in response to the request, and return the interaction component to the merchant applet if there is the interaction component, so that the merchant configures the interaction component in the merchant applet. Certainly, the page configuration request initiated by the merchant applet to the service end may also carry a page identifier of the page to be configured, so that the service end determines the interactive component (which may include a newly issued interactive component and a historical interactive component) that needs to be returned to the merchant applet according to the identifier. Further, the merchant applet may present the interactive component back to the merchant after receiving the component back from the service for the merchant to configure for the presented component.
In this embodiment, the merchant applet may generate component configuration information according to configuration operations implemented by the merchant for the interactive component, where the merchant configuration information may include component information, such as a component identifier, of the interactive component selected by the merchant. And for any interactive component of the configuration, the corresponding component configuration information can comprise at least one of component position, component size, component color, font size and the like. For a certain display page including multiple interactive components, a merchant may sequentially configure each interactive component, or may only configure some interactive components therein (for an interactive component that is not configured by the merchant, default component information set for the interactive component by a service end may be used as component configuration information of the interactive component). The component configuration information corresponding to a certain display page generated by the merchant applet is a set of component configuration information of each interactive component in the display page.
Further, the merchant applet may determine a page identification of the configured presentation page, such as a page number, a page name, a page URL (Uniform Resource Locator), and the like. Further, the merchant applet may send the page identifier and the component configuration information generated according to the component configuration operation to the server in an associated manner, so that the server establishes a mapping relationship between the page identifier and the component configuration information.
On the other hand, developers can correspondingly develop and support the new-version user applet of the newly-released interactive component and release the new-version user applet to the server, so that the user client updates the locally-installed user applet. For example, after releasing a new version of the applet, the server may notify the applet to perform an update, such as sending an update notification message to the applet, so that the applet triggers an update in response to the message (e.g., starting an automatic update upon receiving the message, or presenting the message to the user to determine whether to update, etc.). In fact, the updated new version user applet may be configured with the above-mentioned interactive components in the development phase, so as to update the process of the new version user applet, i.e. the process of configuring the newly released interactive components in the user applet, and accordingly, the updated new version user applet is configured with the newly released interactive components.
Step 204, in response to a data acquisition request initiated by the user applet configured with the interactive component for a target display page, determining target component configuration information corresponding to the target display page according to the mapping relationship, and returning the target component configuration information and page data of the target display page to the user applet configured with the interactive component, so that the user applet, in the case of receiving the target component configuration information and the page data, renders and displays the page data on the target display page through the interactive component indicated by the target component configuration information.
In the process that a user uses a new version user applet, for example, a home page of the user applet is opened, a certain interactive component of the user applet is clicked, a specific gesture action is made, and the like, the user applet can be triggered to display a corresponding target display page (namely, a display page configured in the above process), namely, the user applet requests a server to acquire page data, and after the page data and target page configuration information returned by the server are acquired, the page data is correspondingly rendered and displayed on the target display page through the interactive component indicated by the target component configuration information.
In an embodiment, the display page may be used to display store-related data of a physical store of a merchant, where the store-related data may be page data, such as store basic information, store new goods, a store goods list, and the like, and the store-related data may be registered by the merchant to the server. Therefore, the display of the store related data of the physical stores is realized through the target display page, and the online service is realized. At this time, the process of configuring the interactive component of the display page of the user applet by the merchant can be regarded as a process of decorating an online store of the physical store.
In fact, since the user applet is an applet running in the user client, and the user client is maintained by the application server and the corresponding service platform, the process of releasing the new version user applet by a developer at the server is essentially to upload the relevant installation files of the developed new version user applet to the server, and then the new version user applet is deployed in the user client by the server through the application server, so as to realize the process of updating the installed user applet in the user client. The user applet published in the application server is usually installed to the user client after official audit of the application server, and the application server needs a certain time for the audit process of the new version user applet, so that the configuration of the interactive component by the merchant applet can be completed, even the server establishes a mapping relationship according to the component configuration information and the page identifier uploaded by the merchant applet, but the audit of the new version user applet by the application server is still failed (i.e. the user client does not update the new version user applet). Or, because there are many users corresponding to the user applet, after the server issues the new version of the user applet successfully through the application server, there may still be a case where the user client of some users does not update the version of the user applet (for example, the user refuses to update, or the user opens the target display page corresponding to the user applet for the first time after the new version of the user applet is issued).
In the two cases, if the server receives a data acquisition request sent by a user applet of a non-latest version, even if the server returns the interactive component of the latest version to the user applet, the user applet cannot identify and normally display page data corresponding to the interactive component — because the user applet is not updated to the latest version at present, the user applet may directly display messy codes, blank pages, or an error, and the like, thereby affecting user experience.
In order to solve the problem, the server side can simultaneously maintain the user applets of multiple versions, and the user applets of different versions can be respectively configured with the interaction components of corresponding versions, so that the display pages of the user applets of different versions show different display effects. Correspondingly, the mapping relationship may further include a corresponding relationship between a version identifier of the user applet and the component configuration information of the interactive component, and the data acquisition request initiated by the user applet (of any version) configured with the interactive component (of any version) may include a target version identifier for characterizing a current version of the data acquisition request, so that the server may query, according to the mapping relationship, target component configuration information corresponding to the target version identifier in the component configuration information corresponding to the target presentation page. By the method, the target component configuration information returned to the user applet by the server is matched with the current version of the user applet, so that the user applet can be ensured to be capable of smoothly identifying and analyzing and displaying corresponding page data in a rendering mode according to the target component configuration information, and the problem that the user experience is influenced by messy codes, blank pages or errors is effectively avoided.
Of course, improvements can also be made to this problem at the publishing stage of the interactive components and user applets. If the new version of the interactive component can be released to a merchant, and after the mapping relation is established locally by the server, the new version of the user applet is released by the server, so that any user can directly acquire corresponding target component configuration information after the new version server is updated, and the page data is smoothly rendered and displayed.
Further, the service end may store interactive components of corresponding versions respectively configured by the user applets of different versions, so that the service end may return the interactive component of the version to the merchant applet in response to a page configuration request initiated by the merchant applet for a presentation page of the user applet of any version, so that the merchant applet presents the interactive component of the version in the configuration page. Therefore, the merchant can automatically specify the version of the user applet where the display page to be configured is located, and the flexibility of configuring the display page by the merchant is improved.
In an embodiment, after detecting the component configuration operation implemented by the merchant, the merchant applet may further generate a page presentation template according to the interaction component indicated by the component configuration information, where the page presentation template may include the interaction component indicated by the component configuration information; furthermore, the merchant applet can send the page display template to the server for storage, and then the server can determine a target page display template corresponding to the configuration information of the target component corresponding to the data acquisition request initiated by the user applet, and then return the target page display template and the page data of the template display page to the user applet. Correspondingly, because the user applet initiating the data acquisition request has already configured a new version of the interactive component, the user applet can query whether the target interactive component included in the target page presentation template has already been configured locally after receiving the target page presentation template and the page data returned by the server: if the target page display template exists, the target page display template indicates that the target page display template can display page data according to the target page display template (namely, the component version of a target interaction component contained in the target page display template is consistent with the small program version of the target interaction component), and further corresponding rendering display can be carried out; otherwise, if the target page display template does not exist, the target page display template indicates that the target page display template cannot display the page data per se (namely, the component version of the target interaction component included in the target page display template is inconsistent with the applet version of the target interaction component), and at this time, rendering display, error reporting and/or requesting the server side for obtaining the data again and the like can be stopped.
Of course, the page display template generated by the merchant applet may also include a component identifier (such as a number, a name, a hash, and the like), and accordingly, the user applet may locally store the interactive component of the version corresponding to the applet version. Therefore, after the user applet receives the target page display template and the page data returned by the server, whether the target interaction component corresponding to the target interaction component identifier contained in the target page display template is stored locally can be inquired: if the page is saved, the corresponding page display template can be used for corresponding rendering display; otherwise, if not, the rendering display can be terminated, an error can be reported, and/or the server can be requested to acquire data again, and the like, which is not described again. In addition, the page display module corresponding to the interactive component may also be generated by the server after receiving the component configuration information sent by the merchant applet, which is not limited in this specification.
Through the mode, the component configuration information of the interactive components can be analyzed and combined in advance to generate the integrated page display template, for example, the interactive components are determined firstly, then the interactive components are placed at corresponding positions according to the component configuration information, and are arranged according to corresponding word sizes, sizes and the like. Therefore, after the user applet receives the template page display template and the page data, the template can be directly displayed in the target page, and the target display page can be displayed by filling the page data into the template. The problem that the time consumption for display is long due to the fact that the user applet analyzes the configuration information of the target assembly one by one and displays the configuration information according to the corresponding information is solved, the display time of the target display page is greatly shortened, the page blockage is reduced, and the watching effect of the user is further improved.
In the embodiment, after the service platform issues the interactive component applied to a new version (such as a new function, a new style, and the like) of a certain display page through the service end, the merchant may configure the interactive component (such as a display parameter, and the like) through the merchant applet, and then after the service end establishes a corresponding mapping relationship, the user applet may render and display the component configured by the merchant in the display page, thereby implementing an effect of personalized configuration of the display effect of the component displayed by the user applet by the merchant.
Referring to fig. 3, fig. 3 is a flowchart of another applet page configuration method according to an exemplary embodiment. As shown in fig. 3, the method applied to a merchant applet may include the steps of:
step 302, a configuration page of a display page for the user applet is displayed, and component configuration information is generated according to configuration operations of a merchant for a plurality of interactive components included in the configuration page.
Step 304, sending the page identifier of the display page and the component configuration information to a server in an associated manner, establishing a mapping relation between the page identification and the component configuration information by the server side, and in response to a data acquisition request initiated by a user applet configured with the interactive component for a target presentation page, determining target component configuration information corresponding to the target display page according to the mapping relation, and returning the target component configuration information and the page data of the target presentation page to the user applet configured with the interactive component, such that upon receipt of said target component configuration information and said page data by the user applet, and rendering and displaying the page data on the target display page through the interaction component indicated by the target component configuration information.
Referring to fig. 4, fig. 4 is a flowchart illustrating a method for configuring a page of an applet according to an exemplary embodiment. As shown in fig. 4, the method is applied to a user applet configured with an interactive component, and may include the following steps:
step 402, a data acquisition request aiming at a target display page is sent to a server, so that the server determines target component configuration information corresponding to the target display page according to a mapping relation between a page identifier and component configuration information established by the server, and returns the target component configuration information and page data of the target display page to the user applet configured with an interactive component; the method comprises the steps that a merchant applet displays a configuration page aiming at a display page of a user applet, and the configuration information of the components is determined according to configuration operation of a plurality of interaction components contained in the configuration page by the merchant applet and then is sent to a server side.
Step 404, in a case that the target component configuration information and the page data are received, rendering and displaying the page data through an interaction component indicated by the target component configuration information on the target display page.
The specific embodiment corresponding to fig. 3 and fig. 4 may refer to the related embodiment of fig. 2, and is not described herein again.
Referring to fig. 5, fig. 5 is an interaction diagram of a method for configuring a page of an applet according to an exemplary embodiment. As shown in fig. 5, taking the target display page as the home page of the user applet of the physical store as an example, the process of configuring the interactive component for the merchant and displaying the page data in the target page by the user applet according to the target component configuration information will be described in detail. The interaction process may include the steps of:
step 502, the developer issues the interactive component through the server.
For the merchant applet and the user applet which are successfully released, a developer can perform configuration updating on an interactive component of any display page in the user applet, such as developing an interactive component with a new function, updating a display position and a display style of an original functional interactive component, and the like. In this embodiment, the following description will be given by taking an online store corresponding to an entity store of a merchant, which is a user applet, and an interactive component issued by a developer as a new product display component added to a home page of the user applet as an example.
The developer can issue the developed interaction components corresponding to the new functions, the new positions, the new styles and the like to the server side, so that on one hand, the interaction components can be conveniently configured by a merchant, and on the other hand, the interaction components are configured by the user applet, so that the user applet can update the user applet. The process of issuing the interactive component in the service end by the merchant applet comprises the process of uploading and storing the developed interactive component in the service end.
Corresponding to the new version of the interactive component, a developer can correspondingly develop a new version of the user applet operated based on the user client, and the user applet is released through the application server corresponding to the server and the user client, so that the user client can update the new version of the user applet. For example, after releasing a new version of the applet, the server may notify the user client of the update, such as sending an update notification message to the user client, so that the user client triggers the update in response to the message. Such as starting to update the user applet upon receipt of the message (i.e. updating the installed old version user applet to the newly released new version user applet), or presenting the message to the user for the user to decide whether to update, etc. The update notification message may include an installation file of the new-version user applet, so that the user applet may directly install the new-version user applet in response to the message, thereby implementing the update of the user applet. Or, the update notification message may not include the installation file of the new-version user applet, so that the user applet may obtain the installation file of the new-version user applet from the server when detecting an update confirmation operation performed by the user for the message, so as to avoid invalid data transmission when the user selects no update. In fact, the updated new version user applet may be configured with the above-mentioned interactive components in the development phase, so as to update the process of the new version user applet, i.e. the process of configuring the newly released interactive components in the user applet, and accordingly, the updated new version user applet is configured with the newly released interactive components. It should be noted that the "user applet" shown in fig. 5 is an updated new version user applet, that is, a user applet configured with a newly released interactive component.
In step 504, the service sends the component to be configured to the merchant applet.
After receiving the new commodity display component uploaded by the developer, the server may send the component to a merchant applet installed and running in the merchant client (i.e., the new commodity display component serves as a component to be configured). Of course, the interactive component developed by the developer may be generally applicable to a plurality of user applets corresponding to a plurality of merchants at the same time, so the service end may determine which merchant applets send the component according to the authority of the merchant applets. For example, in the case that the new product display component is a free component with a physical store address navigation function, the server may send the component to the merchant applets corresponding to the user applets of all physical stores, and the component is configured and used by the corresponding merchant — the user applets corresponding to non-physical stores do not need to be navigated, and therefore do not need to send the component to the merchant applets corresponding to such user applets. For another example, if the new commodity display component is a charging component, it may be determined to which merchant applets the component is sent according to payment conditions (such as annual fee payment conditions, member level conditions, and the like) of merchants corresponding to the merchant applets, and details are not repeated.
Further, the merchant applet may also present a configuration notification message to the merchant to alert the merchant to decide whether to configure the component. The configuration notification message may be presented in the form of an intra-applet dialog box, a popup, or the like. Further, the merchant may choose to configure (e.g., click "determine", "deconfigure", etc.) or not configure (e.g., click "cancel", "configure later", etc.). Accordingly, if the merchant chooses to configure, step 506 may be entered; otherwise, if the user chooses not to configure, the following process may be terminated.
At step 506, the merchant applet detects the configuration operations implemented by the merchant and generates component configuration information.
Step 508, the merchant applet sends the association of the component configuration information and the page identifier to the server.
The merchant applet may generate the component configuration information according to configuration operations that the merchant performs with respect to the new merchandise display component. Wherein the component configuration information may include at least one of a component position, a component size, a component color, a font size, and the like. Under the condition that the home page comprises a plurality of interactive components, the merchant can also respectively implement configuration operation for the interactive components so as to respectively configure the interactive components. In addition, for the interaction component which is not configured by the merchant in the home page, default component information set by the service end can be used as the component configuration information of the interaction component. The component configuration information corresponding to a certain display page generated by the merchant applet is a set of component configuration information of each interactive component in the display page.
In addition, under the condition that the new commodity display assembly is only suitable for the home page of the user applet, the merchant applet can directly determine the home page as a page to be configured; or, in a case that the new commodity display component is applicable to a plurality of display pages in the user applet, the merchant applet may further display a page selection control to the merchant, so that the user selects any page as a page to be configured from the plurality of display pages of the user applet, where the new commodity display component may be displayed.
Besides the new goods display component, the home page also comprises two other interaction components: a historical order query component and a personal account component. The component configuration information generated according to the component configuration operation performed by the user may be represented in the form of a text list, as shown in table 1 below:
TABLE 1
In table 1 above, C1, C2, and C3 identify the component identifications of the new merchandise display component, the historical order query component, and the personal account component, respectively. After the component configuration information is generated, the merchant applet can determine a page identifier of a home page (i.e., a display page where the configured component is located), and further can associate the page identifier and the component configuration information and send the page identifier and the component configuration information to the server.
In an embodiment, the merchant applet may further generate a page presentation template according to the interaction component indicated by the component configuration information, where the page presentation template may include the interaction component indicated by the component configuration information. Corresponding to table 1, a page display module generated according to the above component configuration information is shown in fig. 6. Thepresentation page 600 includes three interactive components: a newproduct display component 601, a historicalorder query component 602, and anindividual account component 603, where configuration parameters of the components respectively correspond to table 1 above. At this time, the merchant applet may associate the page display template with the page identifier and send the page display template to the server.
It can be understood that, by generating the page display template, the merchant applet (or the server) may parse and combine the component configuration information of the multiple interaction components in advance to generate an integrated page display template, so that after receiving the page identifier and the page display template, the user applet can directly display the template in the target page and fill page data into the template to display the target display page (see the following steps). The problem that the time consumption for display is long due to the fact that the user small program analyzes the configuration information of the target assembly one by one and displays the configuration information according to the corresponding information is solved, the display time of the target display page is shortened, and the watching effect of the user is further improved.
Step 510, the server establishes a mapping relationship between the page identifier and the component configuration information.
After receiving the page identifier and the component configuration information sent by the merchant applet, the server may establish a mapping relationship between the page identifier and the component configuration information. It can be understood that the same service end may be connected to merchant clients corresponding to multiple merchants, respectively, so that the service end may receive configuration information sent by multiple merchant applets, respectively, or receive multiple component configuration information sent by the same merchant applet and page identifiers corresponding to the component configuration information.
In addition, the mapping and relationship stored by the server may further include a corresponding relationship between the version identifier of the interactive component and the component configuration information. For example, the mapping relationship corresponding to the component configuration information after configuration of a certain merchant stored in the server may be as shown in table 2 below. The Information1 is component configuration Information generated by a merchant performing component configuration operation on the page P1 in the V1.0 version of the user applet, and may include component identifiers of interactive components included in the page, display positions of the components, component sizes, component colors, background pictures, fonts and/or word sizes of component characters, and the like, which is not limited in this specification. Other component configuration Information is similar to Information1 and will not be described in detail.
Of course, in the case of establishing the page display template corresponding to the component configuration information in step 510, a column of "component configuration information" in table 2 should record the page display template, which is not described again.
TABLE 2
At step 512, the user applet detects the page show operation performed by the user.
In step 514, the user applet sends a data acquisition request for the home page to the server.
At any time after the user applet is updated, the user may perform a page display operation in the user applet, for example, a home page opening operation, a component triggering operation, and the like, which is not limited in this specification. Therefore, after the user applet detects the operation, the corresponding display page needs to be displayed, and therefore a data acquisition request needs to be sent to the server to request for acquiring page data. The page obtaining request may include a page identifier of a target display page to be displayed (i.e., the top page) and a version identifier of the current user applet.
In step 516, the server determines the target component configuration information and the page data.
Assuming that the version of the current applet is V3.0 and the page id of the top page is P1, the data acquisition request includes "page id P1" and "version id of component V3.0", so that the server can determine the Information3 as the target component configuration Information of the target presentation page according to table 2.
In addition, a target display page can be determined according to the page identifier, and then page data of the current time of the page can be obtained. The page data may be registered in the server by the merchant in advance, or may be automatically updated or maintained by the server, which is not limited in this specification.
In step 518, the server sends the target component configuration information and page data to the user applet.
Step 520, the user applet renders the display page data in the home page according to the target component configuration information.
The server may return the target component configuration information and the page data determined in the above process to the user applet. Accordingly, the user applet can render the presentation page data in the home page in accordance with the target component configuration information.
For example, as adapted to the embodiment shown in fig. 6, the display effect of the page data can be as shown in fig. 7. Wherein, thehome page 700 includes a newmerchandise display component 701, in which a new merchandise (one-piece dress) in a physical store of a merchant is displayed, and when the component is detected to be triggered by a user, the applet can jump to a detail page of the new merchandise. A historicalorder query component 702 is also shown in thehome page 700, and when the component is detected to be triggered by the user, the applet can jump to a historical order page of the user; also shown is apersonal account component 703 that the applet can jump to the user's personal account details page upon detecting that the user triggered the component. The commodity picture displayed in the newcommodity display component 701, the character "order" displayed in the historicalorder query component 702, and the character "my" displayed in thepersonal account component 703 are page data of thehome page 700.
Fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment. Referring to fig. 8, at the hardware level, the apparatus includes aprocessor 802, aninternal bus 804, anetwork interface 806, amemory 808, and anon-volatile memory 810, but may also include hardware required for other services. Theprocessor 802 reads a corresponding computer program from thenon-volatile memory 810 into thememory 808 and runs the computer program, thereby forming an applet page configuration apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 9, in a software implementation, the applet page configuring apparatus applied to a server may include:
the relationship establishing unit 901 is configured to establish a mapping relationship between a page identifier and component configuration information according to the page identifier and the component configuration information of a display page of a user applet, which are sent by merchant applet association; the component configuration information is generated by the merchant applet after the configuration page aiming at the display page is displayed according to the configuration operation of a plurality of interactive components included in the configuration page by a merchant;
a data returning unit 902, configured to, in response to a data acquisition request initiated by a user applet configured with the interaction component for a target display page, determine, according to the mapping relationship, target component configuration information corresponding to the target display page, and return, to the user applet configured with the interaction component, the target component configuration information and page data of the target display page, so that the user applet, when receiving the target component configuration information and the page data, renders and displays the page data on the target display page through the interaction component indicated by the target component configuration information.
Optionally, the user applets of different versions are respectively configured with the interactive components of corresponding versions, the mapping relationship further includes a corresponding relationship between a version identifier of the user applet and component configuration information of the interactive components, the data acquisition request includes a target version identifier of the user applet configured with the interactive components, and the data returning unit 902 is further configured to:
and inquiring the target component configuration information corresponding to the target version identification in the component configuration information corresponding to the target display page according to the mapping relation.
Optionally, the server stores interactive components of each version, and the apparatus further includes:
the component returning unit 903 is configured to, in response to a page configuration request initiated by the merchant applet for a display page of any version of the user applet, return an interaction component corresponding to the user applet of any version to the merchant applet, so that the merchant applet displays the interaction component in the configuration page.
Alternatively to this, the first and second parts may,
the system further comprises a template generating unit 904, configured to generate a page display template according to the interactive component indicated by the component configuration information, where the page display template includes the interactive component indicated by the component configuration information;
the data return unit 902 is further configured to: and returning the target page display template and the page data of the target display page to the user applet.
Optionally, the display page is configured to display store-related data of a physical store of the merchant, where the store-related data is registered by the merchant to the server.
Referring to fig. 10, in a software implementation, the applet page configuring apparatus applied to a merchant applet may include:
the information generating unit 1001 is configured to display a configuration page of a display page for a user applet, and generate component configuration information according to configuration operations of a merchant for a plurality of interactive components included in the configuration page;
an information sending unit 1002, configured to send the page identifier of the display page and the component configuration information to a server in an associated manner, establishing a mapping relation between the page identification and the component configuration information by the server side, and in response to a data acquisition request initiated by a user applet configured with the interactive component for a target presentation page, determining target component configuration information corresponding to the target display page according to the mapping relation, and returning the target component configuration information and the page data of the target presentation page to the user applet configured with the interactive component, such that upon receipt of said target component configuration information and said page data by the user applet, and rendering and displaying the page data on the target display page through the interaction component indicated by the target component configuration information.
Referring to fig. 11, in a software embodiment, the applet page configuring apparatus, applied to a user applet configured with an interactive component, may include:
a request initiating unit 1101 that initiates a data acquisition request for a target display page to a server, so that the server determines target component configuration information corresponding to the target display page according to a mapping relationship between a page identifier and component configuration information established by the server, and returns the target component configuration information and page data of the target display page to the applet configured with the interactive component; the method comprises the steps that a merchant applet displays a configuration page aiming at a display page of a user applet, and configuration operation of a plurality of interaction assemblies contained in the configuration page is determined according to merchant configuration information and then sent to a server side;
the data display unit 1102 is configured to, when the target component configuration information and the page data are received, render and display the page data on the target display page through the interaction component indicated by the target component configuration information.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.