Service processing method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a service processing method and device, equipment, a storage medium and a program product, and the method comprises the steps that an application page of a mother application program is displayed, a target service component is displayed in the application page of the mother application program, and the target service component is used for providing a target application service; in response to a triggering operation on the target service component, calling at least one sub-application program corresponding to the target application service, and obtaining service data of the target application service; the mother application program and the child application program have an affiliation relationship; and rendering the service data through the mother application program to obtain a service detail page of the target application service, and displaying the service detail page. Therefore, the efficiency of reaching the target application service by the user can be improved through the service component, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a service processing method, apparatus, device, storage medium, and program product. Background Art

[0002] With the development of computer technology, at least one sub-application can be embedded in a certain parent application. Through the operation of the parent application, each sub-application can provide application services different from the parent application (such as travel accommodation, restaurant reservation services, etc.) as a service carrier. After the user consumes content in the parent application, the service closed-loop can be completed in the sub-application. In this way, diversified application services can be provided for the user through the sub-application. However, at present, the parent application presents less service information for decision-making and judgment to the user, and it is necessary to jump to the application page of the sub-application to use the application service, and the efficiency of the user reaching the application service is not high, thus affecting the user experience. Summary of the Invention

[0003] Embodiments of this application provide a service processing method, apparatus, device, storage medium, and program product, which can improve the efficiency of the user reaching the target application service through a service component and improve the user experience.

[0004] On the one hand, embodiments of this application provide a service processing method, which includes:

[0005] Display the application page of the parent application, and a target service component for providing a target application service is displayed on the application page of the parent application;

[0006] In response to a trigger operation on the target service component, call at least one sub-application corresponding to the target application service, and obtain service data of the target application service; there is a subordinate relationship between the parent application and the sub-application;

[0007] Render the service data through the parent application to obtain a service details page of the target application service, and display the service details page.

[0008] On the other hand, embodiments of this application provide a service processing method, which includes:

[0009] Display the application page of the parent application, and a target service component is displayed on the application page of the parent application;

[0010] In response to a trigger operation on the target service component, display a service details page, and the service details page includes service controls, and the service controls are rendered and displayed by the parent application calling the business data of the sub-application. There is a subordinate relationship between the parent application and the sub-application;

[0011] In response to a trigger operation on a service control, the target application service corresponding to the service control is called by the parent application to execute the sub-application.

[0012] On the other hand, an embodiment of the present application provides a service processing method, which includes:

[0013] Determine a target service component template provided by the parent application, where the target service component template includes at least one attribute;

[0014] Obtain the first attribute information required by the target service component template, where the first attribute information is provided by the service provider according to the attributes included in the target service component template;

[0015] Construct a target service component based on the target service component template and the first attribute information, where the target service component is used to provide a target application service, and the target application service corresponds to at least one sub-application;

[0016] Obtain the service data of the target application service according to the target service component and at least one sub-application, and provide the service data to the parent application, where there is a subordinate relationship between the parent application and the sub-application.

[0017] On the other hand, an embodiment of the present application provides a service processing device, which includes:

[0018] A display unit for displaying the application page of the parent application, where the target service component for providing the target application service is displayed on the application page of the parent application;

[0019] An acquisition unit for calling at least one sub-application corresponding to the target application service in response to a trigger operation on the target service component, and obtaining the service data of the target application service; there is a subordinate relationship between the parent application and the sub-application;

[0020] A rendering unit for rendering the service data through the parent application to obtain the service details page of the target application service, and displaying the service details page.

[0021] On the other hand, an embodiment of the present application provides a service processing device, which includes:

[0022] A display unit for displaying the application page of the parent application, where the target service component is displayed on the application page of the parent application;

[0023] The display unit is further configured to display the service details page in response to a trigger operation on the target service component, where the service details page includes a service control, and the service control is rendered and displayed by the parent application by calling the business data of the sub-application, and there is a subordinate relationship between the parent application and the sub-application;

[0024] An execution unit, configured to, in response to a trigger operation on a service control, call a sub-application through a parent application to execute a target application service corresponding to the service control.

[0025] On the other hand, an embodiment of the present application provides a service processing apparatus, which includes:

[0026] A determination unit, configured to determine a target service component template, which is provided by a parent application and includes at least one attribute;

[0027] An acquisition unit, configured to acquire first attribute information required by the target service component template, where the first attribute information is provided by a service provider according to the attributes included in the target service component template;

[0028] A construction unit, configured to construct a target service component according to the target service component template and the first attribute information, where the target service component is used to provide a target application service, and at least one sub-application corresponds to the target application service;

[0029] The acquisition unit is further configured to acquire service data of the target application service according to the target service component and at least one sub-application, and provide the service data to the parent application, and there is a subordinate relationship between the parent application and the sub-application.

[0030] On the other hand, an embodiment of the present application provides a computer device, which includes: a processor, adapted to execute a computer program; a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by the processor, the service processing method as described above is implemented.

[0031] On the other hand, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by the processor to implement the service processing method as described above.

[0032] On the other hand, an embodiment of the present application provides a computer program product, which includes a computer program or computer instructions, and when the computer program or computer instructions are executed by a processor, the service processing method as described above is implemented.

[0033] In the embodiments of the present application, an application page of a parent application can be displayed. A target service component is displayed on the application page of the parent application, and the target service component is used to provide a target application service. In response to a trigger operation on the target service component, at least one sub-application corresponding to the target application service is called, and service data of the target application service is obtained. Then, the service data is rendered by the parent application to obtain a service detail page of the target application service and display the service detail page. It can be seen that based on the target service component, the service detail page can be directly rendered and displayed in the parent application without jumping to the sub-application for rendering and display. In this way, it is possible to avoid the direct response of some sub-applications with poor performance, and the target application service can also be used in the service detail page rendered by the parent application, improving the efficiency of users reaching the target application service; through the target service component, the target application service can be transmitted to the public domain of the parent application, and service information for assisting decision-making and judgment can also be presented to the user, facilitating the user to use the application service through the target service component and enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is an architecture diagram of a service processing system provided by an embodiment of the present application;

[0035] Figure 2 is a schematic flowchart of a service processing method provided by an embodiment of the present application;

[0036] Figure 3a is a schematic diagram of the decomposition of an application service provided by an embodiment of the present application;

[0037] Figure 3b is a schematic diagram of a service detail page provided by an embodiment of the present application;

[0038] Figure 3c is an operation flowchart of executing a target application service through a service detail page provided by an embodiment of the present application;

[0039] Figure 4 is a schematic flowchart of another service processing method provided by an embodiment of the present application;

[0040] Figure 5a is a schematic flowchart of an operation of mounting a target service component provided by an embodiment of the present application;

[0041] Figure 5b is a schematic diagram of an application scenario of a service component provided by an embodiment of the present application;

[0042] Figure 6 is a schematic flowchart of another service processing method provided by an embodiment of the present application;

[0043] Figure 7aIt is a schematic diagram of attribute data of a target service component provided by an embodiment of the present application;

[0044] Figure 7b It is a schematic architecture diagram of creating a service component provided by an embodiment of the present application;

[0045] Figure 7c It is a schematic diagram of the layered design of a service system provided by an embodiment of the present application;

[0046] Figure 8a It is a schematic structural diagram of a service processing device provided by an embodiment of the present application;

[0047] Figure 8b It is a schematic structural diagram of another service processing device provided by an embodiment of the present application;

[0048] Figure 9 It is a schematic structural diagram of a computer device provided by an embodiment of the present application. Detailed implementation manners

[0049] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0050] The present application proposes a service processing method. The service processing method can display the application page of the parent application. The application page of the parent application displays a target service component, and the target service component is used to provide a target application service. In response to a trigger operation on the target service component, at least one sub-application corresponding to the target application service is called, and the service data of the target application service is obtained. Then, the service details page of the target application service is rendered through the parent application and the service details page is displayed. It can be seen that based on the target service component, the service details page can be directly rendered and displayed in the parent application without jumping to the sub-application for rendering and display. In this way, it is possible to avoid the direct response of some sub-applications with poor performance and improve the efficiency of users reaching the target application service. Through the target service component, the target application service can be transmitted to the public domain of the parent application and information for assisting decision-making and judgment can be presented to the user. The user can use the application service through the target service component, improving the user experience.

[0051] In this application, there is a subordinate relationship between the parent application and the child application. The so-called subordinate relationship means that one application depends on another application in terms of function, resources, or data. The dependent application is called the child application (i.e., the subordinate application), and the application it depends on is called the parent application (i.e., the master application). For example, when a map service application is accessed as a mini-program in a social media application, there is a subordinate relationship between the social media application and the map service application. Based on this dependency relationship, the parent application can call the child application to obtain the service data of the target application service and then render each page element in the service details page, such as statically displayed text, images, or interactive controls, and display them.

[0052] The target service component is one of at least one service component, and the target service component is a service component instance (or simply referred to as a component instance) constructed by the service provider. A service component is a capability integration tool. A service component defines at least one service capability, which can be understood as a set of capabilities. Each service capability can provide a specific service to support the application service. For example, the service capabilities of the target service component include a transaction capability and a product capability. Through the transaction capability, an order placement service can be provided, and through the product capability, a product details (such as inventory, price, etc.) display service can be provided. Each service capability is defined by at least one attribute, that is, each service capability can be understood as a set of attributes. For example, if the service capability includes a product capability, then the attributes under the product capability include products, inventory, and price. That is to say, a service component can bind at least one attribute (including the attributes under at least one capability), and a service component can also dock resources (including the instantiation access of the resources of the attributes or data mounting synchronization, etc.). The docked resources can be stored as attribute values. It should be noted that in this application, the term "at least one" means one or more, and the meaning of "multiple" is two or more; for example: at least one attribute means one, two, or more than two attributes.

[0053] Next, the architecture of the service processing system provided by the embodiments of this application will be introduced with reference to the accompanying drawings.

[0054] Please refer to Figure 1 , which is an architecture diagram of a service processing system provided by an exemplary embodiment of this application. As Figure 1As shown in the figure, the service processing system includes terminal devices (including the first terminal device 101a and the second terminal device 101b) and an application server 102; a communication connection can be established between the terminal devices and the application server 102 in a wired or wireless manner. Among them, the terminal devices include but are not limited to: smart phones, tablet computers, smart wearable devices, smart voice interaction devices, smart home appliances, personal computers, vehicle-mounted terminals, smart cameras, and other devices, and the present application does not limit this. Regarding the number of terminal devices, the present application does not make any restrictions. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, but is not limited thereto. Regarding the number of servers, the present application does not make any restrictions.

[0055] The first terminal device 101a can use the target application service provided by the target service component. The first terminal device is the terminal device used by the consumer, where the consumer refers to the user of the parent application. The first terminal device 101a can execute the following service processing flow: ① Display the application page of the parent application. The application page of the parent application includes, but is not limited to: session page, content details page, comment page, live broadcast page, search page, and location information page. The target service component is displayed in the application page of the parent application. The target service component can be displayed in the application page of the parent application by means of mounting or recall, and the target service component can be presented in the form of a component link. For example, in the comment page of the parent application, there is a component link of the target service component mounted by a certain user. This component link is similar to the link identifier of a small program and includes an image and text. The target service component is used to provide the target application service. The target application service is, for example, one or more of the following: food ordering service, seat reservation service, accommodation reservation service, and movie ticket purchasing service. The target service component can be triggered by any user. If the consumer triggers the target service component in the application page of the parent application, then: ② The first terminal device 101a can, in response to the trigger operation on the target service component, call at least one sub-application corresponding to the target application service and obtain the service data of the target application service. There is a subordinate relationship between the parent application and the sub-application. The first terminal device 101a can interact with the application server 102 to obtain the service data of the target application service. In one embodiment, the service data of the target application service includes the business data of the sub-application. The first terminal device can send a data acquisition request to the application server 102. This data acquisition request is used to request to call the corresponding application to obtain the service data. The application server 102, in response to this data acquisition request, calls the sub-application to obtain the business data of the sub-application and returns it to the first terminal device 101a. In another embodiment, the service data of the target application service includes the business data of the sub-application and the content ecosystem data associated with the target service component in the parent application. The first terminal device 101a can not only call the sub-application to obtain the business data of the sub-application, but also call the parent application to obtain the content ecosystem data (such as content data, POI data) of the parent application associated with the target service component. Both the business data and the content ecosystem data can be obtained by the application server and returned to the first terminal device 101a. ③ Render the service data through the parent application to obtain the service details page of the target application service and display the service details page. In one embodiment, the service details page includes service controls. The service controls can be obtained by rendering the service data through the parent application. A service control refers to a control that supports interactive operations (such as clicking, inputting). Based on the trigger of the service control, the target application service can be executed.In addition to service controls, the service details page may also include other service content. This service content is related to the target application service and is rendered based on the service data obtained by invoking the sub-application. It can be presented through relevant page elements. For example, on the details page of a ticket booking service, the selection modules for movies, showtimes, and cinemas can be rendered and displayed based on the service data.

[0056] The application server 102 can create a target service component based on the target service component template. The application server 102 can execute the following service processing procedures: ① Determine the target service component template, which is provided by the parent application. The target service component template contains at least one attribute. The second terminal device 101b is the terminal device used by the developer (belonging to the service provider). In one embodiment, the second terminal device 101b can send a component creation instruction to the application server 102. The component creation instruction contains the template identifier of the service component template selected by the developer. Based on the template identifier, the target service component template can be determined. ② Obtain the first attribute information required by the target service component template. The first attribute information is provided by the service provider according to the attributes contained in the target service component template. In one embodiment, the second terminal device 101b can send the first attribute information required by the target service component template to the application server 102. In another embodiment, the application server 102 can obtain the first attribute information required by the target service component template through resource access. ③ Construct the target service component according to the target service component template and the first attribute information. When constructing the target service component, it can be understood that the first attribute information is passed as a parameter into the target service component template to generate the target service component. The target service component is used to provide the target application service, and the target application service corresponds to at least one sub-application. The service data of the target application service can include the business data of each sub-application. ④ Obtain the service data of the target application service according to the target service component and at least one sub-application, and provide the service data to the parent application. In one embodiment, after the target service component is triggered, the first terminal device 101a can send a data acquisition request to the application server. The application server 102 can acquire the service data of the target application service in response to the data acquisition request, and then send the service data to the first terminal device 101a.

[0057] In the service processing system provided by the embodiments of the present application, the first terminal device can consume the target service component. The target service component can be displayed on the application page of the parent application. Based on the trigger of the target service component, at least one sub-application corresponding to the target application service can be called to obtain the service data of the target application service, and the service details page can be rendered and displayed based on the service data. Furthermore, the target application service can be completed on the service details page. Through the service component, the application service can be structured, enabling the parent application to understand the application service and transmit it to the public domain of the parent application (such as the comment area, live broadcast room, notes, etc.). Users can use the application service through the service component, and the parent application can also obtain the results of users using the application service. The application server and the second terminal device can jointly execute the creation process of the target service component. By providing the target service component template, the target service component can be quickly created, and when the first terminal device consumes the target service component, the service data of the target application service can be provided to the first terminal device.

[0058] Next, the service processing method provided by the embodiments of the present application will be introduced.

[0059] Please refer to Figure 2 , which is a schematic flowchart of a service processing method provided by an exemplary embodiment of the present application. This service processing method can be executed by a terminal device (such as Figure 1 the first terminal device 101a in the service processing system shown) and can include the following content.

[0060] S201, display the application page of the parent application. The target service component is displayed on the application page of the parent application, and the target service component is used to provide the target application service.

[0061] The parent application can have one or more of the following functions: social (such as content publishing, content browsing, interaction, community, etc.) functions, shopping (such as commodity purchase, service purchase, etc.) functions, live broadcast functions, etc. The parent application can be a multi-functional application. The application page of the parent application is used to display the content ecological data of the parent application. The application page of the parent application can include any one of the following: search page, content details page, live broadcast page, location information page (i.e., POI page, POI stands for Point of Interest, which refers to a specific location on the map). Exemplarily, the POI page can be used to display POI information, including but not limited to: service location information such as stores, parks, restaurants, bus stops, etc. On the POI page, content objects related to the service location (such as notes, comments, service components, etc.) can also be aggregated and accompanied by a map.

[0062] The target service component is a component instance created by the service provider based on the service component template and passed the review. The service provider refers to an individual developer or organization with development capabilities. In this application, the service provider can be understood as a merchant. The target service component can be a mounted service component or a recalled service component. Through mounting or recall, the target service component can be displayed in the public domain of the parent application. The so-called public domain can be understood as the domain accessible to all users of the parent application, or can be understood as the application interface accessible to all users.

[0063] The target application service provided by the target service component is an instance of an application service. For example, the target application service is a movie ticket purchasing service, a reservation service for a certain restaurant, or a reading service for a certain novel, etc. Classified by function, application services can include local services, tool services, and content services. Local services refer to services with specific business processing logics. This type of service has corresponding business operation processes. For example, the order service includes business processing logics such as order creation, modification, and cancellation. Local services include but are not limited to: ticket purchasing services (such as movie ticket purchasing, exhibition ticket purchasing), reservation services (such as restaurant reservation), room reservation services (such as homestay reservation, hotel reservation), rental services (such as house rental). Tool services and content services refer to services that provide general functions, such as providing basic tool or content services. Tool services include but are not limited to: AI tool services, calorie calculation tool services. Content services include but are not limited to: novel reading services. Each application service is synchronized by the developer to the parent application in the form of a service unit and connected to users in the parent application. A service unit is the smallest granular service that conforms to the intuitive understanding of users. For example, a service unit can be a movie, an exhibition, or a room voucher. It is the service unit that connects users in the public domain (such as in the search or comment area) of the parent application. For local services, there is also service affiliated information, which includes but is not limited to: service location (such as multiple cinemas associated with the movie ticket purchasing service), reservation information (such as calendar inventory, price, etc.), and other affiliated information, etc. Optionally, the service location can be used to recall the service component to provide the target application service, or the service location may not determine the recall of the target service component. For the decomposition of application services, reference can be made to Figure 3a, the deconstructed content of the local class service includes service units and service affiliated information. The service units include movies, seat reservations, exhibitions, room vouchers, and houses. Each service unit is associated with service location as the service affiliated information, including: movies are associated with Cinema 1, Cinema 2, and Cinema 3; seat reservations are associated with restaurants; exhibitions are associated with art galleries; room vouchers are associated with Store 1 to Store n; houses are associated with communities. The service affiliated information under each service unit also includes reservation information (such as calendar inventory, price, etc.) and other affiliated information. From the user's perspective, application services can be displayed at some service locations, and the service affiliated information does not determine the POI or guarantee a certain recall in searches. For tool-based services and content-based services, since there is no complex business logic, there is no need to disassemble them, but they are connected to users in the form of service units. For example, the service unit of an AI tool is the tool, and the service unit of a novel reading service is the novel.

[0064] S202, in response to a trigger operation on a target service component, call at least one sub-application corresponding to the target application service to obtain the service data of the target application service.

[0065] In one implementation, the target service component is displayed in the application page of the parent application in the form of a link. This link can be a text link, a card link, or a link similar to a mini-program. Through the link, information for decision-making and judgment can be provided to the user. For example, if the target service component is a reading component for a certain novel, the text link of the target service component can include the name of the novel. By showing the name of the novel to the user, it can assist the user in deciding whether to read the novel.

[0066] The trigger operation on the target service component includes but is not limited to: click operation, preset gesture operation, etc. The target application service corresponds to at least one sub-application. This correspondence means that the target application service is one of the at least one application service provided by the sub-application. By triggering the target service component, the business data of the sub-application can be called. For example, if the target application service is the food ordering service of Restaurant A, the at least one sub-application corresponding to the target application service can provide the food ordering service of Restaurant A. One sub-application can be associated with at least one service component. Through different service components, a certain service of the sub-application can be directly accessed without having to jump to the sub-application for other operations, thus shortening the operation path and improving the user's efficiency in accessing the service. For example, if the sub-application is a seat reservation application, this sub-application is associated with two service components for providing seat reservation services for different types of meals (such as Chinese food and Western food), and the user can directly select a service component to reserve a certain type of meal.

[0067] In one embodiment, the service data includes the business data of at least one sub-application. When the terminal device executes S202, it can, in response to the triggering of the target service component, call at least one sub-application corresponding to the target application service to obtain the business data of each sub-application. The business data of the sub-application refers to the data related to the application service provided by the sub-application. For example, if the sub-application provides a food ordering service, the business data may include: data such as the available food ordering times and the number of people ordering food. In another embodiment, the service data includes the business data of at least one sub-application and the content ecological data of the parent application associated with the target service component. When the terminal device executes S202, it can, in response to the triggering of the target service component, call at least one sub-application corresponding to the target application service to obtain the business data of each sub-application, and call the parent application to obtain the content ecological data of the parent application associated with the target service component. That is to say, not only can the business data of the sub-application be obtained, but also the content ecological data related to the target application service in the parent application can be obtained. The content ecological data is, for example, content data and POI data. In the above embodiments, the business data of the sub-application can be obtained through an Application Programming Interface (API interface; which allows communication and interaction between different applications).

[0068] S203, render the service data through the parent application to obtain the service details page of the target application service, and display the service details page.

[0069] When rendering the service data through the parent application and then displaying the service details page, the service data can be embedded in the component page template (such as an HTML template) corresponding to the target service component to generate and present the service details page. The service details page is an application page rendered in the parent application, rather than an application page that jumps to the sub-application for rendering and display; various services such as free reservation, group buying, exhibition performances, paid reservation, and books, movies, and music can be realized through the service details page.

[0070] The terminal device can be used as a client (or user side) that runs the parent application. The style of the service details page on the C side (i.e., the consumer side, user side) is determined according to the service component template selected by the service provider and the style layout data configured for the service component template. The page style of this service details page can be rendered according to the style layout data configured for the service component template. One service component template configures one set of style layout data, and different service component templates configure different style layout data. If different service providers select the same service component template, based on the style layout data configured for this service component template, the service components created by different service providers can use the same style layout data. Then, for the service details pages of the same application service provided, relatively unified style layouts and interactive displays can be used in the parent application to ensure the user experience of the service components. If different service providers select different service component templates, since different service component templates are configured with different style layout data, the service components created by different service providers can not only provide different application services, but also, based on the style layout data of different service components, the page styles of the service details pages displayed by different service components are also different. Exemplarily, taking the target application service as the food ordering service provided by a certain restaurant as an example, the service details page can be as Figure 3b shown, Figure 3b shows two service details pages, and the page layouts of the service details pages are different. These two service details pages are the results rendered according to different style layout data. Different service components can be constructed by using different service component templates, and the service details pages with corresponding styles are presented based on the service components. Based on different style layout data, there are differences in page elements, element positions, element styles, etc. in the service details page. As Figure 3b shown in (1) of Figure 3b , the service details page shows content such as the restaurant picture, name, reservation price, reservation time, number of people, and reservation instructions. As Figure 3b shown in (2) of

[0071] , in addition to showing basic information such as the restaurant picture, per capita consumption price, rating, and food ordering time, the service details page is also divided into interactive modules such as à la carte, courtesy, and discounts.

[0071] In one embodiment, the service data includes the business data of a sub-application, and the business data of the sub-application is used to render service controls on a service details page. A service control refers to a control that supports interactive operations (such as clicking, swiping, or inputting, etc.), and can be used to confirm and submit the service content selected on the service details page. The visual manifestation form of the service control can be a button, an icon, a text box, etc. The number of service controls can include at least one, and each service control undertakes a specific function, such as ticket purchasing, reservation, etc. Based on the business data of the sub-application, in addition to rendering service controls, other page elements related to the target application service can also be rendered to present the service content, such as text, images related to the target application service, and other operable selection modules. Exemplarily, as described above Figure 3b the service details page shown in (1) of the above is the seat reservation details page of a certain restaurant. The service controls include a control for immediate reservation. In addition, the service details page also includes multiple selection controls, such as a date selection control, a time selection control, and a number of people selection control, as well as other function controls (such as a favorite control and a share control) and other content, such as the service location, business hours, reservation instructions, etc. If the service data further includes content ecosystem data, and the content ecosystem data includes at least one of the following: content data and geographical location data (i.e., location data / POI data), the content data is used to render at least one note associated with the target application service on the service details page, and the geographical location data is used to render at least one service location associated with the target application service on the service details page. In this application, a note refers to: the content created and shared by the user of the parent application in the parent application, and the note can be content such as pictures, texts, and videos published by the user. When displaying the service location, specifically, the evaluation, recommendation created by the user based on the service location, or the picture and text content related to the location can be displayed.

[0072] In one embodiment, service controls are displayed on the service details page. The service controls are rendered based on the service data of the target application service and include controls rendered and displayed based on the business data of the sub-application. The terminal device can, in response to a trigger operation on the service control, call the sub-application through the parent application to execute the target application service corresponding to the service control. The trigger operation on the service control can be a click operation, a preset gesture operation, a selection operation, etc. The service controls include, but are not limited to: reservation controls, purchase controls, reading controls, etc. For example, if the service control includes a movie ticket purchase control, after all the service contents related to movie ticket purchase on the service details page are selected, the movie ticket purchase control can be triggered, and the movie ticket purchase program can be called through the parent application to execute the movie ticket purchase service. When calling the sub-application to execute the target application service, the terminal device can jump to the application page of the sub-application and continue to execute the target application service through the service control on the application page of the sub-application. Executing the target application service involves data acquisition, processing, storage, and transmission. For example, executing the target application service can include: acquiring service content data (such as the number of service people, service location, etc.), generating service order information based on the service content data. After acquiring the service order information, the service order information can be stored in the parent application and can also be transmitted to the service provider.

[0073] Exemplarily, as Figure 3c shown in the schematic diagram of the operation process of executing the target application service through the service details page, the target application service is a movie ticket purchase service. The service details page can display service pictures, service names, service sub-specifications, service prices, service inventories, service locations, service dates, and customer service. Among them, the service location, service date, and customer service are all operable selection controls. When clicking "Next", the service selection process can be entered. In the service selection process, the service location can be selected based on the service location selection control, such as "a certain cinema". The seat can be selected based on the seat selection control. The date, specific time, session, and price can also be selected based on the service date selection control. When the above service selection process is completed, based on the completed selection operation, the selected service information (including service location, seat, date, time, session, and price, etc.) and the user contact information can be displayed on the service submission confirmation page. After clicking "Submit", the submission result can be output, and the submission result is used to indicate successful submission. Further, in one embodiment, the service order information of the target application service can be generated by executing the target application service, and the service order information can be transmitted to the application server of the parent application and / or the service provider so that the application server or the service provider can analyze the situation of the user consuming the target application service.

[0074] The service processing method provided by the embodiment of the present application can trigger a target service component in the application page of the parent application, call a sub-application to obtain service data of the target application service, and render the service data through the parent application to display a service details page, and the target application service can be executed through the service details page. In this way, there is no need to jump to the sub-application, but the service data for rendering is obtained by calling the sub-application, and the information for assisting the user in making a decision and determining whether to use the service is pre-displayed through the service details page, improving the efficiency of the user's decision-making and enhancing the user experience of the target application service.

[0075] Please refer to Figure 4 , which is a schematic flowchart of a service processing method provided by another exemplary embodiment of the present application. This service processing method can be executed by a terminal device (such as Figure 1 the first terminal device 101a in the service processing system shown), and this service processing method can include the following content.

[0076] S401, display the application page of the parent application, and the application page of the parent application displays a target service component.

[0077] In one embodiment, the target service component can be displayed in the application page of the parent application in any of the following ways:

[0078] (1) Make the target service component display in the application page of the parent application by means of mounting.

[0079] The terminal device can respond to a service mounting operation, mount the target service component to at least one service scenario of the parent application, and the mounted target service component is displayed in the application page of the parent application in the form of a link. Based on the mounting of the target service component in the corresponding service scenario, the application page displayed by the target service component corresponds to the mounted service scenario. This correspondence means that the application page can carry the service scenario, and specifically, the service function can be presented to the user through page elements and guide the user to complete the operation process of the carried service scenario. Mounting the target service component to at least one service scenario can also be regarded as field distribution. Through field distribution, any user of the parent application can trigger the target service component and thus experience the target application service.

[0080] In one embodiment, the service scenarios include at least one of the following: comment scenario, conversation scenario, live broadcast scenario, store scenario, content display scenario, etc., and the present application does not make limitations. The application pages of the parent application may include at least one of the following: comment page, conversation page (which can be a page for group conversation or personal conversation), live broadcast page, product browsing page, and content details page. The corresponding relationships are as shown in ①-⑤ below: ① If the mounted service scenario includes a comment scenario, the application page displayed by the target service component includes a comment page. In the comment page, the target service component coexists with the comments, and the display form can be a text link. By coexisting with the comments through the text link, the comment content of a certain comment in the comment page can include the target service component. ② If the mounted service scenario includes a conversation scenario, the application page displayed by the target service component includes a conversation page. In the conversation page, the target service component can be included in the conversation message, for example, included in the conversation message in the form of a text link. The conversation message can also include other text content or information, or the target service component is separately displayed in the form of an ark message (a structured message including a title, subtitle, picture, and jump link). Clicking on the ark message represents triggering the target service component. ③ If the mounted service scenario includes a live broadcast scenario, the application page displayed by the target service component includes a live broadcast page. In the live broadcast scenario, the target service component can be mounted by the anchor in the live broadcast room and displayed in the live broadcast page in a form similar to a product link. Alternatively, the target service component can be mounted by the audience to the live broadcast room and published in the comment area of the live broadcast page in the form of a text link. ④ If the mounted service scenario includes a store scenario, the application page displayed by the target service component includes a product browsing page. In the store scenario, the product browsing page can display products and at least one service component in zones. Here, the product refers to a physical product, and the at least one service component includes the target service component. The at least one service component can be displayed in a list form, and each service component is displayed in a form similar to a product link. ⑤ If the mounted service scenario includes a content display scenario, the application page displayed by the target service component includes a content details page. In the content display scenario, the target service component can be mounted by the content publisher during the content editing process. And in the content details page, the target service component can be nested with the content (including text, picture, or video) for display, or can be separately displayed. For example, the target service component is displayed through a text link and text content, or is displayed together with a picture, and is independently displayed with the content in the form of a card link. Exemplarily, the target service component is a novel reading service component. In the parent application, users can browse the notes published by others. In the note details page, the note content can be viewed, and a text link to the novel reading service component is displayed in the note content.

[0081] Through the mounting of the target service component, the target service component can be displayed on the group chat page, personal chat page, live page, content details page, etc. The terminal device on the consumer side can consume the target service component, including mounting and displaying the target service component on different channels of the parent application, and using the target service component in the public domain of the parent application. Optionally, the target application service is a paid service, and the users of the parent application can purchase services on the target service component. For example, in scenarios such as POI details, conversations (such as group chats, private messages), searches, and live broadcasts, the target application services provided can be purchased based on the target service component.

[0082] In one embodiment, the service mounting operation includes an operation of selecting the target service component, and at least one service scenario includes a first service scenario, which can be any one of the service scenarios listed above. For example, the first service scenario is a comment scenario. Here, the process of mounting the service component will be introduced taking the first service scenario as an example. The terminal device can, in response to the service mounting operation, mount the target service component into the first service scenario of the parent application. The specific operation process may include the following: In response to the component addition operation in the first service scenario, display a service component list, which includes the target service component; receive the selection operation on the target service component in the service component list, and mount the target service component into the first service scenario of the parent application.

[0083] The first service scenario can be the service scenario corresponding to the application page of the parent application. When the terminal device displays the application page of the parent application, it means that it is in the first service scenario. For example, the first service scenario is a comment scenario, and the application page of the parent application is a comment page. Before the target service component is mounted into the first service scenario, the application page corresponding to the first service scenario does not display the target service component, but can display other service components different from the target service component. The service component list displayed based on the component addition operation can be an independent list page or a display area in the application page. In response to the component addition operation, the terminal device can call the sub-application to read the data of the target service component to be added and render and display the target service component based on the data of the target service component.

[0084] Optionally, the component addition operation may include: a triggering operation for adding an entry for a service component, where the entry for adding the service component is provided on the application page of the parent application. The entry for adding the service component may be hidden in the application page of the parent application and be awakened and displayed through a preset operation, or the entry for adding the service component may be fixedly set in the application page of the parent application. Through the entry for adding the service component, the target service component can be mounted to the application page. For example, the application page is a content details page, and the content details page includes a comment editing area. Through the comment editing area, comments on the content displayed in the content details page can be edited and published. The entry for adding the service component may be provided in the comment editing area, so as to mount the target service component to the comment area. Another example is that the application page is the content editing page of the parent application. In the content editing page, note content can be edited and published in the parent application. The entry for adding the service component may be provided in the content editing page. By providing the entry for adding the service component in the content editing page, the target service component can be added to the content details and displayed on the content details page. When other users view the content details, they can directly see the mounted target service component and trigger the target service component to consume the target application service.

[0085] In one implementation, there is an addition control corresponding to the target service component. The selection operation for the target service component may be a triggering operation for the addition control corresponding to the target service component. By triggering the addition control, the target service component can be mounted to the first service scenario of the parent application, so that the target service component can be displayed on the application page corresponding to the first service scenario. For example, the first service scenario is a comment scenario, and through the above mounting process, the target service component can be displayed on the comment page.

[0086] In one embodiment, the service component list includes, in addition to the target service component, at least one service component to be added. The display methods of the service components in the service component list include at least one of the following: classified display according to service categories, random arrangement display, arrangement display according to popularity, arrangement display according to the number of views, and arrangement display according to usage time. The service categories can be distinguished based on service functions. For example, they can be classified and displayed according to service categories such as seat reservation services, novel reading services, and tool services. The popularity of each service component in the parent application can be understood as the degree of popularity, which can be determined based on the uv volume (the number of independent visitors, that is, the number of users with different IP addresses accessing the target service component). The higher the uv volume, the higher the popularity, that is, the higher the heat. Multiple service components can be arranged and displayed in descending order of popularity; they can also be arranged and displayed in descending order of the number of views, or multiple service components can be arranged and displayed in the order from the most recent to the oldest in terms of usage time, or arranged and displayed in descending order of service relevance. The service relevance refers to the relevance between the content of the first service scenario and the application service provided by the service component, which can be determined by the terminal device based on the content data of the first service scenario and the text tags used to describe the service scope of the application service.

[0087] Optionally, each sub-application corresponding to the target application service is associated with at least one service component. In response to a component addition operation, the terminal device can call at least one sub-application corresponding to the target application service to read the data of at least one service component associated with each of them. The data includes the component name and the component image identifier. At least one service component is rendered and displayed through the read data of the service component. The at least one service component includes the target service component; the at least one service component to be added is displayed in the parent application in the form of a service component list, and each service component is provided with an addition control for adding the service component.

[0088] Exemplarily, such as Figure 5aAs shown, taking the application page of the parent application as the comment page as an example, the terminal device can display the comment page. When any user has a need to post a comment, the terminal device can respond to a comment editing operation (such as an operation of clicking on the comment editing box), wake up the service component addition entry, and by clicking on the service component addition entry, a service component list can be displayed. The service component list contains at least one service component to be added, each service component carries an addition control, and each service component is displayed classified according to the associated sub-application. When the addition control of the target service component (such as the service component marked by label 5001) is clicked, it means that the target service component is selected, so that the selected target service component can be displayed in the comment editing area. Through the confirmation operation of the comment editing area, the target service component is displayed in the comment page of the terminal device in a form similar to a mini-program link. The target service component coexists with the comment in the form of a deep link (a form of link that directly points to specific content within an application, used to facilitate access to specific content). What the user sees is a service component link with a mini-program mark and a similar jump link. After other users see it and click, they can directly enter the service details page to complete subsequent operations.

[0089] (2) Making the target service component be displayed on the application page of the parent application through a recall method.

[0090] The terminal device can obtain the recall keyword of the parent application; according to the preset recall strategy, recall the target service component based on the recall keyword; and display the target service component on the application page of the parent application.

[0091] In one embodiment, the recalled keywords include: search keywords or geographical location keywords; the search keywords can be the text input by the user or the text extracted from an image. For example, the search keyword is: "restaurant". The geographical location keywords can be automatically generated based on the geographical location information of the user or actively input by the user. When automatically generating, the parent application can obtain the geographical location information of the user and extract keywords from the geographical location information as the geographical location keywords. If the recalled keywords include search keywords, the application page of the parent application includes a search page. If the recalled keywords include location keywords, the application page of the parent application includes a location information page. Or rather, the terminal device can recall the target service component in the service scenario, so as to display the recalled target service component in the application page corresponding to the service scenario. If the service scenario includes a search scenario and the obtained recalled keyword is a search keyword, then the recalled target service component can be displayed in the search page; in the search page, the target service component is a service component related to the search keyword, and the target service component is mounted by other users to the corresponding service scenario (such as a live broadcast, conversation or comment scenario) and displayed in the search page by means of recall. If the service scenario includes a POI scenario, then the recalled target service component can be displayed in the location information page of the parent application. In the location information page, the target service component can be displayed in the form of a card link, and a virtual map is displayed in the location details page. The virtual map simulates the geographical space of the real world and provides a map for the user to navigate, locate and search. The target service component can be associated and displayed at the location corresponding to the virtual map. For example, if the target service component is a seat reservation service component and the seat reservation service provided by the seat reservation service component involves a restaurant location, then the card link of the target service component can be displayed at that location in the virtual map. For the target service component recalled in the search scenario or the POI scenario, it can be pre-mounted by other users in the content display scenario, comment scenario, live broadcast scenario or store scenario and displayed in a specific page by means of recall.

[0092] In one implementation manner, if the recalled keywords include search keywords, each service component carries at least one text label, and each text label is used to describe the service scope. Then when recalling the target service component according to the preset recall strategy based on the recalled keywords, at least one service component with a search relevance that meets the requirements can be recalled according to the search relevance between the search keyword and the text label of the service component. At least one of the recalled service components includes the target service component, and the search relevance between the text label of the target service component and the search keyword meets the requirements. Optionally, the search relevance can refer to the semantic matching degree between the search keyword and the text label used to describe the service scope, and the search relevance meeting the requirements means that the semantic matching degree is greater than or equal to the preset semantic matching degree.

[0093] In one embodiment, if the recalled keywords include geographical location keywords, and the application services provided by some service components have service affiliated information such as service location, then when recalling target service components according to the preset recall strategy based on the geographical location keywords, the location relevance of each service component can be determined based on the geographical location keywords and the service locations corresponding to each service component, and at least one service component can be recalled based on the location relevance of each service component. The at least one service component includes the target service component. Optionally, the location relevance may include semantic matching degree or physical distance. For example, the physical distance between the service location corresponding to the recalled target service component and the user's location is less than or equal to the preset physical distance, or the semantic matching degree is greater than the preset semantic matching degree.

[0094] In another embodiment, at least one candidate service component can be recalled based on the recalled keywords. The terminal device can perform metric detection on each candidate service component. For any candidate service component, if the metric detection of the candidate service component passes, the candidate service component can be used as the target service component and displayed on the application page of the parent application. The metric detection performed on the candidate service component can follow the following rules: internal and external relevance, and whether the performance of the sub-application meets the standard. Internal and external relevance refers to the matching degree between the keyword and the service scope corresponding to the service component. If the matching degree is less than the preset matching degree, it is determined that the candidate service component does not meet the standard, and the candidate service component is not displayed on the application page. Otherwise, it is determined that the candidate service component meets the standard, and the candidate service component that meets the standard can be displayed on the application page. Whether the performance of the sub-application meets the standard can be determined from at least one of the following dimensions: the response time is less than the preset time, the data processing speed is greater than the preset processing speed, and the number of users supporting concurrent processing is greater than the preset number of users, etc.

[0095] In one embodiment, the at least one recalled service component can be sorted according to priority. Sorting according to priority can follow the following sorting rules: the service components developed by the service provider are displayed prior to the native service components of the parent application, the service components with more uv (uv means unique visitors, that is, the number of users with different IP addresses accessing the target service component), more service orders are displayed prior, the service components with inventory are displayed prior to the service components without inventory, and the service components synchronized first are displayed prior.

[0096] In one embodiment, at least one service component is displayed in the application interface of the parent application, and the at least one service component includes a target service component. The at least one service component can be recalled by the terminal device through a recall method or obtained through a mounting method. That is, the terminal device can recall at least one service component according to the recall keyword, and at least one service component can be displayed on the application page of the parent application. The at least one service component includes the target service component, so the target service component can be displayed on the application page of the parent application. Through the mounting method, if multiple users can each mount different service components (including the target service component) in the same service scenario through the terminal device, then in addition to displaying the target service component on the application page of the parent application, the terminal device can also display other service components; based on multiple users mounting the target service component in the same service scenario, multiple identical target service components can be displayed at different positions on the application page of the parent application. For example, different users' comments are displayed in the comment area, and the comment content of these users all contains service component A. When the user selects to trigger the target service component, a service details page can be displayed, and the target application service provided by the target service component can be executed through the service details page. When the user selects to trigger other service components, the corresponding application service can be executed according to a process similar to that of triggering the target service component.

[0097] It should be noted that the methods for displaying the target service component on the application page of the parent application shown in the above-mentioned (1) and (2) are also applicable to Figure 2 the relevant steps in the embodiments shown.

[0098] S402, in response to a trigger operation on the target service component, display a service details page, and the service details page includes service controls.

[0099] The service controls are rendered and displayed by the parent application invoking the business data of the sub-application. There is a subordinate relationship between the parent application and the sub-application. The sub-application is associated with the target service component, and this association means that the business data of the sub-application can be invoked by triggering the target service component. The number of service controls can be at least one, and each service control can be rendered and displayed based on the business data of the sub-application. In addition to being used to render the service controls on the service details page, the business data can also be used to render other contents of the service details page, including but not limited to: text contents such as service names and service locations, image contents such as service pictures, and selectable contents such as dates and times. For example, if the business data includes the meal ordering time and the number of people ordering meals, then at least one selectable time and date rendered based on the meal ordering time, and at least one selectable number of people rendered based on the number of people ordering meals.

[0100] The service details page can be rendered by the parent application from the service data of the target application service. The service data includes at least the business data of the sub-application. Based on the rendering of the business data, service controls and other page elements for guiding users to use the target application service can be displayed on the service details page. Optionally, the service data can also include the content ecosystem data of the parent application associated with the target service component. Based on the rendering of the content ecosystem data, content related to the target service component, such as notes, POIs, etc., can be displayed on the service details page.

[0101] In one embodiment, a service component template is configured with a style layout data for rendering and displaying a page style. The service component created through the service component template corresponds to the style layout data. The terminal device can obtain the style layout data corresponding to the target service component and render the style layout data to obtain the page style of the service details page. If the same service component has the same style layout data, it means that different service components providing the same type of application service are created based on the same service component template. Based on the trigger of the service component, the page styles of the service details pages rendered through the style layout data are the same. For example, service component A and service component B are both built based on service component template M1 and can provide food ordering services. Then these two service components can use the same style layout data. Based on the trigger of service component A and service component B, service details pages with the same style are rendered. However, due to the different attribute data of different service components, different service contents can be displayed on the service details page. For example, both service component A and service component B are used to provide food ordering services, but the page contents of the service details page, such as restaurant name, inventory, location, selectable number of people, time, etc., are different.

[0102] S403. In response to the trigger operation on the service control, the parent application calls the sub-application to execute the target application service corresponding to the service control.

[0103] In one embodiment, the triggering operation on the service control can be a click operation. For example, the service control includes a food ordering control. After clicking the food ordering control, the food ordering application can be called to execute the food ordering service. In addition to the service control, the service details page also includes other service contents. In response to the triggering operation on the service control, the terminal device can generate service content data based on the selected service contents in the service details page. For example, in the movie ticket booking service details page, a certain movie, time, screening, cinema, location, and service location can be selected. When the ticket booking control is triggered, service content data can be generated, and the service content data includes the selected movie name, time, screening, cinema, location, and service location. When the parent application calls the sub-application to execute the target application service corresponding to the service control, the service content data can be obtained and sent to the sub-application. The sub-application can perform business processing (such as transaction processing) based on the service content data to obtain a service execution result. For example, after selecting relevant service contents and submitting them in the movie ticket booking service details page, the movie ticket booking service data can be sent to the movie ticket booking program. The movie ticket booking program can confirm the price based on the movie ticket booking service data and execute the payment process to output a payment result (a type of service execution result). If the payment result indicates successful payment, it means that the movie ticket booking service has been completed. Optionally, the service execution result can also be returned to the parent application, and the service execution result is used to generate service order information.

[0104] In one embodiment, when calling the sub-application to execute the target application service, the terminal device can jump to the application page of the sub-application and continue to execute the target application service through the service control in the application page of the sub-application. For example, the target application service is the movie ticket booking service. After selecting a movie ticket for a certain location and screening in the service details page and submitting it, the payment interface can be displayed in the sub-application, and the payment methods can be displayed on the payment interface. When the user selects a certain payment method and confirms the payment, the result of successful payment can be displayed. Optionally, the ticket code of the movie ticket can also be displayed, which can avoid the user viewing the ticket code through a new operation path and improve the service experience.

[0105] In one embodiment, the target service component is created by the service provider. The target service component supports mounting commodities. Here, mounting commodities can be understood as that the target application service provided by the target service component is a service that needs to be exchanged with electronic resources, that is, a paid service. For example, movie ticket purchasing services, accommodation services, etc. all support mounting commodities, and the mounted commodities are movie tickets, rooms, etc. The terminal device can obtain the service order information generated by executing the target application service through the service details page; optionally, after calling the sub-application to execute the target application service and obtaining the service execution result, the service order information can be generated based on the service content data and the service execution result. For example, the movie ticket purchasing order information is generated based on the service content selected on the movie ticket purchasing details page and the payment result obtained by calling the movie ticket purchasing program to execute the payment process. The service order information refers to the detailed information of the user's request to purchase the target application service. The service order information may include at least one of the following: service description information (such as service type, specification, and requirements), service quantity, service location, service time, and price, etc. Whether the target service component mounts commodities or not, the service order information can be generated to manage the usage progress of the target application service. Based on the service order information, the target application service can be delivered to the user. For example, the user can exchange the movie ticket voucher offline and watch the movie with the movie admission ticket. If the target service component does not mount commodities, the service order information is stored in the parent application; that is to say, if the target service component does not mount commodities, that is, the usage of the target application service does not involve commodity sales, such as reserved seats, reserved free tickets, etc., the service order information can be stored locally or in the background of the parent application, but not sent to the service provider, which can save data resources. If the target service component mounts commodities, the service order information is stored in the parent application and the service provider. If the usage of the target application service involves commodity sales, the generated service order information can be stored in the background of the parent application and can be sent to the service provider. By storing the service order information in the background of the parent application, the parent application can analyze the user's consumption situation through the service order information, provide other similar application services that meet the individual needs of the user, and improve the user's personalized usage experience.

[0106] It should be noted that the relevant content introduced in this embodiment can also be applied to Figure 2 the embodiment shown. For example, the rendering display of the page style of the service details page, the processing of the service order information, and other relevant content can all be implemented on the basis of Figure 2 the embodiment shown.

[0107] Based on the introduction of the embodiments of the present application, the following can be provided as Figure 5bSchematic diagram of the application scenario of the service component shown. Taking the sub-application as a mini-program as an example, developers of the sub-application (such as developers of mini-programs in industry A, industry B, and industry C, etc.) can create service components through an open platform, which is a platform provided by the parent application to support component creation (it can be a web site). After the service component is created and passes the review, both the mounting and recall of the service component can be read by the parent application from the development platform. The application service provided by the service component can be understood as a non-physical commodity. Through the service component, users can use the services of the sub-application (such as mini-program services). In addition, developers of the sub-application (such as developers of mini-programs in industry D, industry E, etc.) can also create commodity components through the open platform, and users can purchase physical commodities through the commodity components. After passing the platform review, the service component can be displayed in the public domain of the parent application. For example, users actively mount the service component (which is also equivalent to mounting the service) to scenarios such as note comments and live broadcasts, and recall the service component (which is also equivalent to recalling the service) to scenarios such as search or location information POI according to the platform strategy. By displaying the service component in the public domain of the parent application, any user can consume the corresponding application service through the service component, generate an order and system messages and display them on the user side.

[0108] The service processing method provided in the embodiment of the present application includes a technical solution of using a target service component on the consumption side. By mounting or recalling the target service component on the consumption side, the target service component can be passed through to the public domain of the parent application. All users of the parent application can consume the target application service through the target service component. In this way, through the target service component, the application service needs of users can be better met in various service scenarios of the parent application (such as note, comment, store, search, etc.) scenarios, providing a more perfect experience for users.

[0109] Please refer to Figure 6 , which is a schematic flowchart of a service processing method provided by another exemplary embodiment of the present application. This service processing method can be executed by a server (such as Figure 1 the application server 102 in the service processing system shown), and this service processing method can include the following contents.

[0110] S601, determine the target service component template.

[0111] The target service component template is provided by the parent application, which can provide at least one service component template. The target service component template refers to one of the at least one service component templates provided by the parent application. A service component template can be understood as a component solution (or component scheme). The solutions defined by the parent application include, but are not limited to: travel and hotel solutions, catering solutions, novel solutions, game solutions, ticketing solutions, etc. The service component template defines a visual framework and service capabilities. The visual framework can define the page style of the service details page for interacting with users through style layout data. If different service providers select the same service component template to create service components, then based on the style layout data configured in the service component template, different service providers can use the same visual framework, and for the same type of services provided by different service providers, relatively unified styles and interaction displays can be used to enhance the user experience. Service capabilities include, but are not limited to: basic capabilities (such as whether the service requires time selection, whether the service requires immediate confirmation, etc.), category capabilities, store capabilities, and product capabilities, etc. Each capability can be understood as a set of attributes. Different service component templates have different attributes and capabilities; for example, the service component templates that the parent application can provide include Component A and Component B, and Component A defines transaction capabilities and product capabilities. The transaction capability includes the order placement attribute, and the product capability includes attributes such as products, inventory, and prices; Component B defines reservation capabilities and POI capabilities. The reservation capability includes the order placement attribute, and the POI capability includes POI attributes. If different service providers select the same service component template, then similar attribute information can be provided according to the attributes included in the service component template for creating and updating component instances. Similar attribute information refers to different attribute values under the same attribute. For example, if Service Provider 1 and Service Provider 2 both select the service component template for movie ticketing services, then the attribute values of attributes such as product identification, inventory type, inventory details, price type, and price details provided by these two service providers are different as attribute information.

[0112] In one implementation, the service provider can select one service component template from the at least one service component template provided by the parent application according to its own business scope. The service scope of the service component template matches the business scope of the service provider. The selected service component template can be used as the target service component template for constructing the target service component. Each service component template has a template identifier (such as template ID). When determining the target service component template, the server can, in response to a component creation instruction, select the service component template with the same template identifier as the one carried in the component creation instruction from the at least one service component template as the target service component template. The selected target service component template is used to create the target service component and implement the capabilities of the created target service component in the relevant sub-application.

[0113] S602. Obtain the first attribute information required for the target service component template.

[0114] The target service component template includes at least one attribute, and each attribute is an attribute whose attribute value is to be set. For example, the target service component template includes at least one of the following attributes to be input: store list, product ID, inventory details, price details, content ID, etc. The attributes included in the target service component template are used to construct the attribute data of the component. The first attribute information is provided by the service provider according to the attributes included in the target service component template. The first attribute information may include the attribute values of each attribute included in the target service component template. In one embodiment, when the server obtains the first attribute information required for the target service component template, the following steps may be performed: according to the attributes included in the target service component template, obtain the resource data of each attribute from at least one business channel; use the obtained resource data of each attribute as the attribute value corresponding to the attribute. Among them, the at least one business channel includes: product library, merchant library, payment, e-commerce, and local, etc. Through at least one business channel, resource data can be mounted and the resource data can be connected to the open platform for creating service components. These resource data can be provided by the service provider. The server can access the sub-application through an open interface (an API interface). Based on the attributes included in the service component template, after accessing the sub-application through the open interface, the resource data of the sub-application can be stored in the database (such as the product library, merchant library, etc.). These resource data can be used as the attribute values (or called resource values) of the corresponding attributes later. When the resource data of each attribute included in the target service component template are all obtained, then the first attribute information can be obtained.

[0115] S603. Construct a target service component according to the target service component template and the first attribute information, and the target service component is used to provide the target application service.

[0116] In one embodiment, the first attribute information includes the attribute values of each attribute of the target service component template. The implementation steps of S603 may include the following: construct key-value pairs for each attribute according to the attribute keys of each attribute of the target service component template and the attribute values in the first attribute information; store the constructed key-value pairs of each attribute in the resource management pool; after the key-value pairs of each attribute in the target service component template are all stored in the resource management pool, obtain the target service component.

[0117] The attributes included in the target service component template correspond to attribute keys (property keys), but the attribute values (property values) are to be set. The first attribute information is obtained based on the resource data of the accessed sub-application. When constructing the key-value pairs of the attributes, the attribute keys (property keys) of the service component template, the component identifier (such as component ID), and the sub-application identifier (such as APP ID) can be combined to obtain the component attribute key (Key). The attribute values in the first attribute information include the resource data of the attributes (i.e., resource values). The key-value pairs of the attributes include the component attribute key and the attribute value. The constructed target service component has at least one type of attribute data, and the attribute data of the target service component includes the key-value pairs of each attribute of the service component template. For example, the target service component is a component instance for movie ticket purchasing (i.e., the movie ticket purchasing component), and the attribute data of this component instance is as Figure 7a shown. The service capabilities defined by the movie ticket purchasing component include: basic capabilities, store capabilities, commodity capabilities, and content capabilities. Each service capability is a set of attributes, and each set of attributes includes at least one attribute. The attribute data of each attribute includes an attribute key and an attribute value. For example, the attributes under the content capability include content id and content type, and both content id and content type correspond to an attribute key and an attribute value. For the attributes under other service capabilities, reference can be made to the Figure 7a text content, which will not be elaborated here.

[0118] In one implementation, a service component can be created in the open platform provided by the parent application. This open platform can open API interfaces for service providers to use. Developers of service providers can access the sub-application through the API interfaces and select a certain service component template. Based on the accessed sub-application, attribute data is obtained, and then a target service component is created based on the service component template and the attribute data. In this way, an association can be formed between the created target service component and the sub-application. This association means that through the target service component, at least one associated sub-application can be called to provide business data; subsequently, the attribute data of the target service component can be read according to the target service component and the called sub-application, and this attribute data includes the business data of the sub-application.

[0119] In one embodiment, in addition to creating a target service component, the service provider can also update and maintain the created target service component. The server can: in response to a component editing instruction, obtain the component data of the target version of the target service component, update the component data of the target service component according to the component data of the target version, and obtain the updated target service component. The component data of the updated target service component includes the component data of the target version. The component data of the updated target service component is the component data of the current version, and the target version can be a historical version of the current version (such as the previous version), and the component data of the target service component is updated to the component data of the historical version. The current version can also be a historical version of the target version, and the component data of the target service component is updated to the component data of the new version. If the component data includes: attribute data, the attribute data of the target service component can be updated through component editing, so as to obtain the attribute data of the historical version or the new version, thereby updating the page elements of the service details page (such as service location, inventory, and price, etc.). If the target service component template supports replacing the style layout data, then the component data can also include the style layout data. In this way, when the service provider updates the target service component, the page style of the updated service details page can also be updated by updating the style layout data. It can be seen that by supporting multiple versions of the component data of the service component, version editing can be performed according to the relevant information of the service component and the data of the target version, and the service component can be flexibly edited forward (that is, upgraded from the current version to the next version) or backward (that is, rolled back from the current version to the previous version), realizing flexible changes to the service component version and meeting the construction or upgrade requirements of developers.

[0120] By providing a pre-designed service component template in this application, the service provider can select a suitable service component template as needed to construct a target service component. The target service component is a service form that aggregates different service capabilities and entities, and can support various services such as free reservation, group purchase, exhibition performance, paid reservation, books, videos, and music to exist in the form of components; this application also provides the concepts and implementations of the service component template-component capability-component attribute-component instance dimension, which can be used to support extensible complex component forms.

[0121] Based on the above-introduced creation process of the target service component, an architecture diagram for creating a service component as shown in Figure 7b can be provided. As shown in Figure 7b , on the production side, it involves an open platform, local or others. The development platform can provide at least one service component template (i.e., a component solution), and each service component template defines at least one service capability, such as Figure 7bThe component solutions shown include: Component A (defined with transaction and commodity capabilities), Component B (defined with reservation and POI capabilities), Component C (defined with coupon collection and POI capabilities), and Component D (defined with content and transaction capabilities, applicable to novels / audio-visuals / games, etc.). The service ability defines an attribute set, and under the attribute management module, at least one attribute under a service ability can be managed; such as Figure 7b As shown, the attributes under the POI ability include POI, the attributes under the commodity ability include commodity, inventory, and price, the attributes under the transaction ability include placing an order, and the attributes under the content ability include media assets. The resource data of the attributes can be managed through a resource management pool (K-V pool). In the K-V pool, at least one key-value pair is managed. The key (i.e., K) represents component-attribute-APP, and the value (i.e., V) is the resource value. The resource management pool can be mounted on at least one channel service, including but not limited to: local, e-commerce, commodity library, merchant library, payment, and others, thereby realizing the instantiated access of the resource data of the attributes. The development platform can open API interfaces to developers. Relationship maintenance includes: developers can access sub-applications through the API interfaces and instantiate target service components based on the target service component template (i.e., pre-service decoration). When the target service component is called, it can read the attribute data (including resource data) of the target service component and display it on the front end (i.e., in-service call), and can also analyze the service orders generated based on the target application component (i.e., post-service analysis). On the consumer side, the target service component, as a component instance, can be displayed in the public domain of the parent application through field distribution, and there can also be multiple supplies for aggregation / decision-making problems placed at one component location.

[0122] S604, obtain the service data of the target application service according to the target service component and at least one sub-application, and provide the service data to the parent application.

[0123] There is a subordinate relationship between the parent application and the sub-application. The way to provide the service data to the parent application can be to send the service data to the client running the parent application. By providing the service data to the parent application, the service data can be rendered in the parent application and then the service details page can be displayed. Through the service details page, the target application service can be executed.

[0124] In one embodiment, when the server obtains the service data of the target application service according to the target service component and at least one sub-application, the following steps A - B may be executed: Step A: Obtain the attribute data of the target service component from the resource management pool according to the target service component and at least one sub-application; Step B: Add the obtained attribute data of the target service component to the service data of the target application service. The target service component is associated with at least one sub-application, and this association means that the attribute data of the target service component is obtained based on the access of the sub-application. The attribute data of the target service component is stored in the form of key-value pairs in the resource management pool. The attribute data of the target service component includes a component attribute key and an attribute value. The instantiated form of the component attribute key is: component - attribute - APP, and the attribute value is a resource value. The server can obtain the attribute data of the target service component from the resource management pool according to the target service component and the sub-application, and the attribute data of the target service component includes the business data of each associated sub-application. Exemplarily, the target service component is associated with sub-applications APP1 and APP2, and the attribute data of the target service component includes the business data of sub-application APP1 and the business data of sub-application APP2. The attribute data of the target service component can be added to the service data of the target application service.

[0125] Based on the above content, another schematic diagram of the hierarchical design of the service system as shown in Figure 7c can be provided. In Figure 7cIn the shown hierarchical design schematic diagram, it includes: a business identity layer, a solution layer, a service capability layer, and a domain service layer. In the business identity layer, the business identity includes at least one sub-application (such as including APP1, APP2, APP3, APP4, APP5, and APP6). The R & D modes of these sub-applications include self-developed and third-party. Based on different R & D modes, one can choose to open with the entry + solution or the way of authorization for application instantiation (APPID). Specifically, it can be instantiated into different carriers, such as mini-programs, web pages / mobile / personal pages, etc. The solution layer includes solutions for wine and travel, ticketing, catering, novels, sweet potato group activities, games, etc. Between the solution layer and the service capability layer, it can be mounted through an interface package, and can provide the ability of endorsement payment or direct connection to provide different service capabilities for the solutions in the solution layer, such as account capabilities (such as authorization, account opening, account closing), transaction capabilities (such as placing an order, payment, performance), commodity capabilities (such as synchronization, listing, and delisting), and POI capabilities (such as querying, claiming). It can also obtain third-party open service capabilities (thirdopenservice) through business orchestration. The capabilities in the service capability layer are provided by mounting the domain service layer through an interface. The domain service layer includes services such as accounts, orders, commodities, categories, marketing, settlement, or others. Future customization and expansion can also expand other content to expand the component form. For the definition of open standards, it also includes the following capabilities: basic, category, store, storefront, commodity, order, fee, marketing, after-sales, logistics, POI, distribution, sharing, customer service, group chat, and media assets, etc. These capabilities can be selected through corresponding rules (including conditions, resources, and cost control), etc.

[0126] The service processing method provided by the embodiment of the present application includes a technical solution of creating a service component instance based on a service component template on the production side. The parent application can provide the service component template, and the service component template defines a specific visual framework and service capabilities. The service provider can select the target service component template and provide the data content required by the target service component template to construct the target service component. As a capability integration tool, the target service component can bind different attributes and dock with different resources. By constructing the target service component, after developers access it, they can strengthen the structured understanding of the service content of the application service, meet the structured storage of the attributes of the current mini-program service and non-mini-program scenarios, and be able to provide application services for users in multiple scenarios of the parent application in the future, improving the user experience.

[0127] Please refer to Figure 8a , Figure 8a is a structural schematic diagram of a service processing device provided by an exemplary embodiment of the present application. The service processing device can be set in a computer device that executes the embodiment of the present application. Figure 8aThe service processing device 800 shown may be a computer program (including program code) running on a computer device, and the service processing device 800 may be used to execute Figure 2 Some or all of the steps in the method embodiments shown. Please refer to Figure 8a , the service processing device 800 may include the following units:

[0128] A display unit 801, configured to display an application page of a parent application, where a target service component is displayed in the application page of the parent application, and the target service component is used to provide a target application service;

[0129] An acquisition unit 802, configured to, in response to a trigger operation on the target service component, call at least one sub-application corresponding to the target application service and acquire service data of the target application service; there is a subordinate relationship between the parent application and the sub-application;

[0130] A rendering unit 803, configured to render the service data through the parent application to obtain a service details page of the target application service and display the service details page.

[0131] In one embodiment, a mounting unit 804 is configured to: in response to a service mounting operation, mount the target service component into at least one service scenario of the parent application, and the mounted target service component is displayed in the application page of the parent application in the form of a link.

[0132] In one embodiment, the application page displayed by the target service component corresponds to the mounted service scenario, and the service scenario includes at least one of the following: a comment scenario, a session scenario, a live broadcast scenario, a store scenario, and a content display scenario; if the mounted service scenario includes a comment scenario, the application page displayed by the target service component includes a comment page; if the mounted service scenario includes a session scenario, the application page displayed by the target service component includes a session page; if the mounted service scenario includes a live broadcast scenario, the application page displayed by the target service component includes a live broadcast page; if the mounted service scenario includes a store scenario, the application page displayed by the target service component includes a product browsing page; if the mounted service scenario includes a content display scenario, the application page displayed by the target service component includes a content details page.

[0133] In one embodiment, the service mounting operation includes a selection operation on the target service component, and the at least one service scenario includes a first service scenario. The mounting unit 804 is specifically configured to: in response to a component addition operation in the first service scenario, display a service component list, where the service component list includes the target service component; receive a selection operation on the target service component in the service component list, and mount the target service component into the first service scenario of the parent application.

[0134] In one embodiment, the component addition operation includes: a triggering operation for adding an entry of a service component, where the service component addition entry is provided on the application page of the parent application; the service component list further includes at least one service component to be added, and the display modes of the service components in the service component list include at least one of the following: classified display according to service categories, random arrangement display, arrangement display according to popularity, arrangement display according to the number of views, and arrangement display according to usage time.

[0135] In one embodiment, the recall unit 805 is configured to: obtain the recall keywords of the target application; recall the target service component according to the preset recall policy based on the recall keywords; the display unit 801 is configured to display the target service component on the application page of the parent application; wherein, if the recall keywords include: search keywords, the application page of the parent application includes a search page, and if the recall keywords include location keywords, the application page of the parent application includes a location information page.

[0136] In one embodiment, the acquisition unit 802 is further configured to: obtain the style layout data corresponding to the target service component; the rendering unit 803 is configured to: render the style layout data to obtain the page style of the service details page; wherein, if the same service component has the same style layout data, the page styles of the rendered service details pages are the same.

[0137] In one embodiment, the service data includes the business data of at least one sub-application and the content ecosystem data of the parent application associated with the target service component; the acquisition unit 802 is specifically configured to: in response to the triggering of the target service component, call at least one sub-application corresponding to the target application service to obtain the business data of each sub-application, and call the parent application to obtain the content ecosystem data of the parent application associated with the target service component; wherein, the business data of the sub-application is used to render and display the service controls in the service details page, and the content ecosystem data includes at least one of the following: content data and geographical location data, the content data is used to render and display at least one note associated with the target application service in the service details page, and the geographical location data is used to render and display at least one service location associated with the target application service in the service details page.

[0138] In one embodiment, the service details page includes service controls, and the service controls are rendered and displayed based on the service data of the target application service; the execution unit 806 is configured to: in response to the triggering operation of the service control, call the sub-application through the parent application to execute the target application service.

[0139] In one embodiment, the target service component is created by the service provider. The target service component supports mounting goods. The obtaining unit 802 is configured to: obtain the service order information generated by executing the target application service through the service details page; the storage unit 807 is configured to: if the target service component does not mount goods, store the service order information in the mother application; if the target service component mounts goods, store the service order information in the mother application and the service provider.

[0140] In one embodiment, as Figure 8a shown, the service processing device 800 can also be used to execute Figure 4 some or all of the steps in the method embodiment shown:

[0141] The display unit 801 is configured to display the application page of the mother application, and the application page of the mother application displays the target service component;

[0142] The display unit 801 is further configured to, in response to a trigger operation on the target service component, display the service details page. The service details page includes service controls, and the service controls are rendered and displayed by the mother application invoking the business data of the sub-application. There is a subordinate relationship between the mother application and the sub-application;

[0143] The execution unit 806 is configured to, in response to a trigger operation on the service control, call the sub-application through the mother application to execute the target application service corresponding to the service control.

[0144] Please refer to Figure 8b , Figure 8b which is a schematic structural diagram of a service processing device provided by an exemplary embodiment of the present application. The service processing device can be set in a computer device that executes the embodiment of the present application. Figure 8b The service processing device 810 shown can be a computer program (including program code) running in a computer device. The service processing device 810 can be used to execute Figure 6 some or all of the steps in the method embodiment shown. Please refer to Figure 8b , and the service processing device 810 can include the following units:

[0145] The determining unit 811 is configured to: determine the target service component template, which is provided by the mother application and contains at least one attribute;

[0146] The obtaining unit 812 is configured to obtain the first attribute information required by the target service component template, and the first attribute information is provided by the service provider according to the attributes included in the target service component template;

[0147] A construction unit 813 is configured to construct a target service component according to a target service component template and first attribute information. The target service component is used to provide a target application service, and the target application service corresponds to at least one sub-application program.

[0148] An obtaining unit 812 is further configured to obtain service data of the target application service according to the target service component and at least one sub-application program, and provide the service data to a mother application program. There is a subordinate relationship between the mother application program and the sub-application programs.

[0149] In one embodiment, the first attribute information includes attribute values corresponding to each attribute included in the target service component template. The obtaining unit 812 is configured to: obtain resource data of each attribute from at least one business channel according to the attributes included in the target service component template; use the obtained resource data of each attribute as the attribute value corresponding to the attribute.

[0150] In one embodiment, the first attribute information includes attribute values corresponding to each attribute of the target service component template. The construction unit 813 is configured to: construct a key-value pair for each attribute according to the attribute key of each attribute of the target service component template and the attribute value in the first attribute information, where each key-value pair includes an attribute key and an attribute value; store the constructed key-value pairs of each attribute in a resource management pool; after the key-value pairs of each attribute of the target service component template are stored in the resource management pool, obtain the target service component.

[0151] In one embodiment, the target service component is associated with at least one sub-application program corresponding to the target application service. The obtaining unit 812 is specifically configured to: read attribute data of the target service component from the resource management pool according to the target service component and at least one sub-application program, where the attribute data includes business data of at least one sub-application program; add the obtained attribute data of the target service component to the service data of the target application service.

[0152] In one embodiment, an updating unit 814 is configured to: in response to a component editing instruction, obtain component data of a target version of the target service component, where the component data includes attribute data; update the component data of the target service component according to the component data of the target version to obtain an updated target service component, and the component data of the updated target service component includes the component data of the target version.

[0153] It can be understood that the specific functions of the units of the service processing device described in the embodiments of the present application can be specifically implemented according to the methods in the above method embodiments. The specific implementation process can refer to the relevant descriptions of the above method embodiments and will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either.

[0154] An exemplary embodiment of the present application further provides a schematic structural diagram of a computer device. The schematic structural diagram of the computer device can be seen in Figure 9 ; The computer device may include: a processor 901, an input device 902, an output device 903, and a memory 904. The above-mentioned processor 901, input device 902, output device 903, and memory 904 are connected through a bus. The memory 904 is used to store a computer-readable storage medium, and the computer-readable storage medium includes a computer program. The processor 901 is used to execute the computer program stored in the memory 904 (including computer program 1, computer program 2,... computer program n).

[0155] In one embodiment, the computer device is a terminal device. The processor 901 performs the following operations by running the computer program in the memory 904: displaying an application page of a parent application, where a target service component is displayed in the application page of the parent application, and the target service component is used to provide a target application service; in response to a trigger operation on the target service component, calling at least one sub-application corresponding to the target application service and obtaining service data of the target application service; there is a subordinate relationship between the parent application and the sub-application; rendering the service data through the parent application to obtain a service details page of the target application service and displaying the service details page.

[0156] In another embodiment, the processor 901 performs the following operations by running the computer program in the memory 904: displaying an application page of a parent application, where a target service component is displayed in the application page of the parent application; in response to a trigger operation on the target service component, displaying a service details page, where the service details page includes service controls, and the service controls are rendered and displayed by the parent application by calling business data of the sub-application, and there is a subordinate relationship between the parent application and the sub-application; in response to a trigger operation on the service controls, calling the sub-application through the parent application to execute the target application service corresponding to the service controls.

[0157] In one embodiment, the processor 901 is used to: in response to a service mounting operation, mount the target service component into at least one service scenario of the parent application, and the mounted target service component is displayed in the application page of the parent application in the form of a link.

[0158] In one embodiment, the application page displayed by the target service component corresponds to the mounted service scenario. The service scenario includes at least one of the following: comment scenario, conversation scenario, live broadcast scenario, store scenario, and content display scenario. If the mounted service scenario includes a comment scenario, the application page displayed by the target service component includes a comment page. If the mounted service scenario includes a conversation scenario, the application page displayed by the target service component includes a conversation page. If the mounted service scenario includes a live broadcast scenario, the application page displayed by the target service component includes a live broadcast page. If the mounted service scenario includes a store scenario, the application page displayed by the target service component includes a product browsing page. If the mounted service scenario includes a content display scenario, the application page displayed by the target service component includes a content details page.

[0159] In one embodiment, the service mounting operation includes a selection operation on the target service component. At least one service scenario includes a first service scenario. The processor 901 is configured to: in response to a component addition operation in the first service scenario, display a service component list, where the service component list includes the target service component; receive a selection operation on the target service component in the service component list, and mount the target service component into the first service scenario of the parent application.

[0160] In one embodiment, the component addition operation includes: a triggering operation on the service component addition entry, where the service component addition entry is provided on the application page of the parent application. The service component list further includes at least one service component to be added. The display mode of each service component in the service component list includes at least one of the following: classified display according to service category, random arrangement display, arrangement display according to popularity, arrangement display according to page view volume, and arrangement display according to usage time.

[0161] In one embodiment, the processor 901 is configured to: obtain the recall keyword of the target application; recall the target service component according to the preset recall policy based on the recall keyword; display the target service component on the application page of the parent application. Wherein, if the recall keyword includes: a search keyword, the application page of the parent application includes a search page. If the recall keyword includes a location keyword, the application page of the parent application includes a location information page.

[0162] In one embodiment, the processor 901 is configured to: obtain the style layout data corresponding to the target service component; render the style layout data to obtain the page style of the service details page. Wherein, if the same service component has the same style layout data, the page styles of the rendered service details pages are the same.

[0163] In one embodiment, the service data includes the business data of at least one sub-application and the content ecosystem data of the parent application associated with the target service component; the processor 901 is configured to: in response to the triggering of the target service component, call at least one sub-application corresponding to the target application service to obtain the business data of each sub-application, and call the parent application to obtain the content ecosystem data of the parent application associated with the target service component; wherein, the business data of the sub-application is used to render and display the service controls in the service details page, and the content ecosystem data includes at least one of the following: content data and geographical location data, the content data is used to render and display at least one note associated with the target application service in the service details page, and the geographical location data is used to render and display at least one service location associated with the target application service in the service details page.

[0164] In one embodiment, the service details page includes service controls, and the service controls are rendered and displayed based on the service data of the target application service; the processor 901 is configured to: in response to the triggering operation on the service control, call the sub-application through the parent application to execute the target application service.

[0165] In one embodiment, the target service component is created by the service provider, and the target service component supports mounting commodities. The processor 901 is configured to: obtain the service order information generated by executing the target application service through the service details page; if the target service component does not mount commodities, store the service order information in the parent application; if the target service component mounts commodities, store the service order information in the parent application and the service provider.

[0166] In another embodiment, the computer device is a server, and the processor 901 executes the following operations by running the computer program in the memory 904: determine the target service component template, which is provided by the parent application and contains at least one attribute; obtain the first attribute information required by the target service component template, and the first attribute information is provided by the service provider according to the attributes contained in the target service component template; construct the target service component according to the target service component template and the first attribute information, and the target service component is used to provide the target application service, and the target application service corresponds to at least one sub-application; obtain the service data of the target application service according to the target service component and at least one sub-application, and provide the service data to the parent application, and there is a subordinate relationship between the parent application and the sub-application.

[0167] In one embodiment, the first attribute information includes the attribute values corresponding to each attribute contained in the target service component template. The processor 901 is configured to: obtain the resource data of each attribute from at least one business channel according to the attributes contained in the target service component template; use the obtained resource data of each attribute as the attribute value corresponding to the attribute.

[0168] In one embodiment, the first attribute information includes the attribute values corresponding to each attribute of the target service component template; the processor 901 is configured to: construct a key-value pair for each attribute according to the attribute key of each attribute of the target service component template and the attribute value in the first attribute information, where each key-value pair includes an attribute key and an attribute value; store the constructed key-value pairs of each attribute in the resource management pool; and obtain the target service component after the key-value pairs of each attribute of the target service component template are stored in the resource management pool.

[0169] In one embodiment, the target service component is associated with at least one sub-application corresponding to the target application service; the processor 901 is configured to: read the attribute data of the target service component from the resource management pool according to the target service component and the at least one sub-application, where the attribute data includes the business data of the at least one sub-application; and add the obtained attribute data of the target service component to the service data of the target application service.

[0170] In one embodiment, the processor 901 is configured to: in response to a component editing instruction, obtain the component data of the target version of the target service component, where the component data includes attribute data; update the component data of the target service component according to the component data of the target version to obtain the updated target service component, and the component data of the updated target service component includes the component data of the target version.

[0171] It should be understood that the computer device described in the embodiments of the present application can execute the description of the service processing method in the corresponding previous embodiments, and can also execute the description of the service processing device in the corresponding previous embodiments, which will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either.

[0172] In addition, it should be noted here that: the embodiments of the present application also provide a computer-readable storage medium, and a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions. When the processor executes the above program instructions, it can execute the methods in the corresponding previous Figure 2 、 Figure 4 and Figure 6 embodiments, so it will not be elaborated here.

[0173] According to one aspect of the present application, a computer program product is provided. The computer program product includes a computer program, and the computer program is stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device can execute the previous Figure 2 、 Figure 4 and Figure 6The method in the corresponding embodiment will not be elaborated here.

[0174] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the computer-readable storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0175] The above disclosure is only a preferred embodiment of the present application. Of course, the scope of rights of the present application cannot be limited thereby. Those of ordinary skill in the art can understand all or part of the processes of the above embodiments, and the equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A service processing method, characterized in that: The method comprises: Displaying an application page of a parent application, wherein the application page of the parent application displays a target service component, wherein the target service component is used to provide a target application service; In response to a trigger operation on the target service component, at least one sub-application corresponding to the target application service is called to obtain service data of the target application service; the parent application and the sub-application have a subordinate relationship; The service data is rendered by the parent application to obtain a service details page of the target application service, and the service details page is displayed.

2. A service processing method, characterized in that: The method comprises: Displaying an application page of a parent application, wherein the application page of the parent application displays a target service component; In response to a trigger operation on the target service component, a service details page is displayed, wherein the service details page includes a service control, wherein the service control is rendered and displayed by the parent application calling the business data of the child application, and there is a subordinate relationship between the parent application and the child application; In response to the triggering operation on the service control, the parent application program calls the child application program to execute the target application service corresponding to the service control.

3. The method according to claim 1 or 2, characterized in that The method further comprises: In response to the service mounting operation, the target service component is mounted to at least one service scene of the parent application, and the mounted target service component is displayed in the application page of the parent application in the form of a link.

4. The method according to claim 3, characterized in that The application page displayed by the target service component corresponds to the mounted service scenario, and the service scenario includes at least one of the following: comment scenario, conversation scenario, live broadcast scenario, store scenario and content display scenario; If the mounted service scene includes a comment scene, the application page displayed by the target service component includes a comment page; If the mounted service scenario includes a conversation scenario, the application page displayed by the target service component includes a conversation page; if the mounted service scenario includes a live broadcast scenario, the application page displayed by the target service component includes a live broadcast page; if the mounted service scenario includes a store scenario, the application page displayed by the target service component includes a product browsing page; if the mounted service scenario includes a content display scenario, the application page displayed by the target service component includes a content details page.

5. The method according to claim 3, characterized in that The service mounting operation includes a selection operation on a target service component, the at least one service scenario includes a first service scenario, and in response to the service mounting operation, mounting the target service component to the at least one service scenario of the parent application program includes: In response to the component adding operation in the first service scenario, displaying a service component list, wherein the service component list includes the target service component; A selection operation on a target service component in the service component list is received, and the target service component is mounted to a first service scene of the parent application.

6. The method according to claim 5, characterized in that The component adding operation includes: a triggering operation of adding an entry to a service component, wherein the service component adding entry is located on an application page of the parent application; The service component list also includes at least one service component to be added, and the display method of each service component in the service component list includes at least one of the following: display by service category, random arrangement, popularity, page views and usage time.

7. The method according to claim 1 or 2, characterized in that: The method further comprises: Obtaining the recall keywords of the target application; According to the preset recall strategy, the target service component is recalled according to the recall keyword; Displaying the target service component in an application page of the parent application; If the recall keyword includes a search keyword, the application page of the parent application includes a search page; if the recall keyword includes a location keyword, the application page of the parent application includes a location information page.

8. The method according to claim 1 or 2, characterized in that: The method further comprises: Obtaining style layout data corresponding to the target service component; Rendering the style layout data to obtain a page style of the service details page; If the same service component is configured with the same style layout data, the rendered service details page will have the same page style.

9. The method according to claim 1, characterized in that The service data includes business data of at least one sub-application and content ecological data of the parent application associated with the target service component; the response to the triggering operation on the target service component, calling at least one sub-application corresponding to the target application service, and obtaining the service data of the target application service, includes: In response to triggering the target service component, calling at least one sub-application corresponding to the target application service to obtain business data of each of the sub-applications, and calling the parent application to obtain content ecology data of the parent application associated with the target service component; Among them, the business data of the sub-application is used to render and display the service controls in the service details page, and the content ecology data includes at least one of the following: content data and geographic location data. The content data is used to render and display at least one note associated with the target application service in the service details page, and the geographic location data is used to render and display at least one service location associated with the target application service in the service details page.

10. The method according to claim 1, characterized in that The service details page includes a service control, and the service control is rendered and displayed based on the service data of the target application service; the method further includes: In response to the triggering operation on the service control, the target application service is executed by calling the child application through the parent application.

11. The method according to claim 1 or 2, characterized in that: The target service component is created by a service provider, and the target service component supports mounting commodities. The method further includes: Acquire service order information generated by executing the target application service through the service details page; If the target service component does not mount a product, storing the service order information in the parent application; If the target service component has a commodity mounted thereon, the service order information is stored in the parent application and the service provider.

12. A service processing method, characterized in that: The method comprises: Determine a target service component template, where the target service component template is provided by a parent application, and the target service component template includes at least one attribute; Acquire first attribute information required by the target service component template, where the first attribute information is provided by a service provider according to attributes included in the target service component template; A target service component is constructed according to the target service component template and the first attribute information, the target service component is used to provide a target application service, and the target application service corresponds to at least one sub-application; The service data of the target application service is obtained according to the target service component and the at least one sub-application, and the service data is provided to the parent application, and there is a subordinate relationship between the parent application and the sub-application.

13. The method according to claim 12, characterized in that The first attribute information includes an attribute value corresponding to each attribute included in the target service component template, and the first attribute information required for obtaining the target service component template includes: According to the attributes included in the target service component template, resource data of each attribute is acquired from at least one business channel; The resource data of each attribute obtained is used as the attribute value corresponding to the attribute.

14. The method according to claim 12, characterized in that The first attribute information includes an attribute value corresponding to each attribute of the target service component template; and constructing a target service component according to the target service component template and the first attribute information includes: Constructing a key-value pair of each attribute according to the attribute key of each attribute of the target service component template and the attribute value in the first attribute information, wherein each key-value pair includes an attribute key and an attribute value; The key-value pairs of each attribute constructed are stored in the resource management pool; After the key-value pairs of the attributes of the target service component template are stored in the resource management pool, the target service component is obtained.

15. The method according to any one of claims 12 to 14, characterized in that The target service component is associated with at least one sub-application corresponding to the target application service; The acquiring the service data of the target application service according to the target service component and the at least one sub-application comprises: Reading attribute data of the target service component from a resource management pool according to the target service component and the at least one sub-application, wherein the attribute data includes business data of the at least one sub-application; The acquired attribute data of the target service component is added to the service data of the target application service.

16. The method according to any one of claims 12 to 14, characterized in that The method further comprises: In response to the component editing instruction, obtaining component data of a target version of the target service component, the component data including attribute data; The component data of the target service component is updated according to the component data of the target version to obtain an updated target service component, wherein the component data of the updated target service component includes the component data of the target version.

17. A service processing device, characterized in that: The device comprises: A display unit, configured to display an application page of a parent application, wherein the application page of the parent application displays a target service component, wherein the target service component is configured to provide a target application service; an acquisition unit, configured to, in response to a trigger operation on the target service component, call at least one sub-application corresponding to the target application service to acquire service data of the target application service; the parent application and the sub-application have a subordinate relationship; A rendering unit is used to render the service data through the parent application to obtain a service details page of the target application service, and display the service details page.

18. A computer device, characterized in that: include: a processor suitable for executing a computer program; A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by the processor, the service processing method according to any one of claims 1 to 16 is executed.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the service processing method according to any one of claims 1 to 16 is executed.

20. A computer program product, characterized in that The computer program product comprises a computer program or a computer instruction, and the computer program or the computer instruction is executed by a processor to implement the service processing method according to any one of claims 1 to 16.

Images