CN110827113B - Service data processing method, device and equipment - Google Patents
Service data processing method, device and equipment Download PDFInfo
- Publication number
- CN110827113B CN110827113B CN201910906871.2A CN201910906871A CN110827113B CN 110827113 B CN110827113 B CN 110827113B CN 201910906871 A CN201910906871 A CN 201910906871A CN 110827113 B CN110827113 B CN 110827113B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- identifier
- description field
- matched
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0631—Item recommendations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The application discloses a method, a device and equipment for processing service data, which relate to the technical field of data processing. The method comprises the following steps: when a generation instruction of service data is received, extracting an attribute description field matched with a service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction, and generating a service description field; merging the service description field and the pre-configured service information into a release link matched with the release identifier according to the release identifier carried by the generation instruction to generate service data; and inquiring and aggregating the service data generated by the same service identification merged into different release links, and displaying the aggregated service data as final service data.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a device for processing service data.
Background
With the rapid development of internet technology, more and more people choose to purchase on a network platform. Among them, the service industry such as hairdressing, massage, body building and the like is also popular among users. In general, a network platform sets up a special service channel, various service shops are arranged in the service channel, a user purchases service goods online, and enjoys the service goods online in the shop, for example, the user orders a hair dressing ticket online, and can use the hair dressing ticket online to perform hair dressing service in the shop.
When a user enters a service channel selection consuming store, each store can provide various service data online in order to attract the user and enrich online display contents, for example, a hair shop can display hair dressing service items, hair washing items, head nursing service items and the like, a fitness shop can display fitness cards and personal course service items at different times or times, and the like. Based on the online presentation of various service data, the user can know the service items in the shop in advance, so that a better purchasing decision can be made. In general, in order to facilitate users to use service items, the service platform may configure various purchasing modalities, such as group purchase, reservation, appointment, etc., for the service items, so that the users can purchase and use the service items in the desired purchasing modalities.
In the process of implementing the invention, the inventor finds that the related art has at least the following problems:
in order to make the displayed service items more flexibly match with the actual needs of users, merchants usually issue service data of various purchasing forms for the same service item. However, at present, distribution links corresponding to service data in different purchasing forms are independent from each other, and at a merchant end, service data in multiple purchasing forms need to be generated for the same service item, so that maintenance cost of the service data of the merchant is high, at a user end, the service data in multiple purchasing forms need to be generated by browsing the same service item, and the content of the service data in the same service item is the same, but the purchasing forms are different, so that the service data browsed by the user is limited.
Disclosure of Invention
In view of this, the present application provides a method, an apparatus, and a device for processing service data, and mainly aims to solve the problems in the prior art that the maintenance cost of merchant service data is high and the service data browsed by a user is limited.
According to an aspect of the present application, there is provided a method for processing service data, the method including:
when a generation instruction of service data is received, extracting an attribute description field matched with a service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction, and generating a service description field, wherein the pre-constructed service resource database records the attribute description fields of the service resource data on different attribute characteristics;
merging the service description field and the pre-configured service information into a release link matched with the release identifier according to the release identifier carried by the generation instruction to generate service data;
and inquiring and aggregating the service data generated by the same service identification merged into different release links, and displaying the aggregated service data as final service data.
Further, the extracting, according to the service identifier carried by the generation instruction, an attribute description field matched with the service identifier from a service resource database constructed in advance to generate a service description field specifically includes:
service resource data in the pre-constructed service resource database are inquired in a traversing mode according to the service identification carried by the generating instruction, and the service resource data matched with the service identification are obtained;
extracting attribute description fields of the service resource data matched with the service identifier on different attribute characteristics from the pre-constructed service resource database to obtain the attribute description fields matched with the service identifier;
and combining the attribute description fields matched with the service identification to generate a service description field.
Further, if the generation instruction indicates that multiple service identifiers are combined, the combining the attribute description fields matched with the service identifiers to generate the service description fields specifically includes:
combining the attribute description fields matched with each service identifier to obtain the service description field of each service identifier;
and splicing the service description fields of the plurality of service identifications to generate a final service description field according to the combination form of the plurality of service identifications indicated by the generation instruction.
Further, the splicing the service description fields of the plurality of service identifiers according to the combination form of the plurality of service identifiers indicated by the generation instruction to generate a final service description field specifically includes:
determining the splicing sequence of the service fields of the plurality of service identifiers according to the combination form of the plurality of service identifiers indicated by the generation instruction;
and splicing the service description fields of the plurality of service identifications to generate a final service description field according to the splicing sequence of the service fields of the plurality of service identifications.
Further, the merging, according to the release identifier carried by the generation instruction, the service description field and the preconfigured service information into the release link matched with the release identifier to generate service data specifically includes:
establishing an interactive relation between the service description field and a publishing system corresponding to the publishing identification according to the publishing identification carried by the generating instruction, wherein each publishing system shares a publishing link independently;
and merging the service description field and the pre-configured service information into a release link which is exclusively shared with the release system based on the interactive relation between the service description field and the release system corresponding to the release identification to generate service data.
Further, the querying and aggregating the service data generated by the same service identifier merged into different release links, and displaying the aggregated service data as final service data specifically includes:
inquiring service data corresponding to the same service identification merged into different release links;
and aggregating the service data corresponding to the same service identifier merged into different release links according to service information pre-configured for each service identifier, and generating and displaying final service data.
Further, when the generation instruction of the service data is received, extracting a description field matched with the service identifier from a service resource database constructed in advance according to the service identifier carried by the generation instruction, and before generating the service description field, the method further includes:
and constructing a service resource database based on the attribute characteristics of the service resource data in the service field.
According to another aspect of the present application, there is provided a service data processing apparatus, including:
the extracting unit is used for extracting an attribute description field matched with the service identifier from a pre-constructed service resource database according to the service identifier carried by the generating instruction when receiving a generating instruction of the service data, and generating the service description field, wherein the pre-constructed service resource database records the attribute description field of the service resource data on different attribute characteristics;
the merging unit is used for merging the service description field and the pre-configured service information into a publishing link matched with the publishing identification according to the publishing identification carried by the generating instruction to generate service data;
and the aggregation unit is used for inquiring and aggregating the service data generated by the same service identifier merged into different release links, and displaying the aggregated service data as final service data.
Further, the extraction unit includes:
the acquisition module is used for querying service resource data in the pre-constructed service resource database in a traversing manner according to the service identifier carried by the generation instruction, and acquiring the service resource data matched with the service identifier;
the extracting module is used for extracting attribute description fields of the service resource data matched with the service identifier on different attribute characteristics from the pre-constructed service resource database to obtain the attribute description fields matched with the service identifier;
and the generating module is used for combining the attribute description fields matched with the service identifications to generate service description fields.
Further, if the generation instruction indicates a combination of a plurality of service identifiers, the generation module includes:
the combination submodule is used for combining the attribute description fields matched with each service identifier to obtain the service description fields of each service identifier;
and the generation submodule is used for splicing the service description fields of the plurality of service identifications to generate a final service description field according to the combination form of the plurality of service identifications indicated by the generation instruction.
Further, the generating sub-module is specifically configured to determine a splicing order of the service fields of the multiple service identifiers according to a combination form of the multiple service identifiers indicated by the generating instruction;
the generating sub-module is specifically further configured to splice the service description fields of the multiple service identifiers according to the splicing order of the service fields of the multiple service identifiers to generate a final service description field.
Further, the merging unit includes:
the establishing module is used for establishing an interactive relation between the service description field and the issuing system corresponding to the issuing identification according to the issuing identification carried by the generating instruction, and each issuing system shares one issuing link;
and the merging module is used for merging the service description field and the pre-configured service information into a release link which is exclusively shared by the release system based on the interactive relation between the service description field and the release system corresponding to the release identification to generate service data.
Further, the polymerization unit includes:
the query module is used for querying service data corresponding to the same service identification merged into different release links;
and the aggregation module is used for aggregating the service data corresponding to the same service identifier merged into different release links according to service information pre-configured for each service identifier, and generating and displaying final service data.
Further, the apparatus further comprises:
and the construction unit is used for extracting a description field matched with the service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction when the generation instruction of the service data is received, and constructing the service resource database based on the attribute characteristics of the service resource data in the service field before the service description field is generated.
According to yet another aspect of the present application, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the above-described service data processing method.
According to still another aspect of the present application, there is provided a store search information processing entity device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the service data processing method when executing the program.
By means of the technical scheme, compared with the mode that a merchant needs to generate a plurality of service data in purchase forms for the same service item and display the service data to a user in the existing mode, the service data processing method, the service data processing device and the service data processing equipment can directly extract the service attribute description fields matched with the service identification for the merchant end through the service resource database which is constructed in advance, the service data can be generated in an accelerated mode without labor of the merchant, and the maintenance cost of the service data of the merchant is reduced. For the user side, the service data generated by the same service identification merged into different release links are aggregated and displayed, repeated service data in various shopping forms can be aggregated, the user does not need to spend time to browse the service data in each purchasing form, the service data in various purchasing forms can be triggered only when the user has a purchasing requirement, and the user can browse more service data and better accord with a decision path of the user when purchasing the service.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic flowchart illustrating a method for processing service data according to an embodiment of the present application;
fig. 2 is a schematic flow chart illustrating another service data processing method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating the composition of service items in a service resource database according to an embodiment of the present application;
FIG. 4 is a block diagram illustrating interaction between a service item and different purchase pattern publication systems provided by an embodiment of the present application;
fig. 5 is a schematic diagram illustrating service data rendered at a user side according to an embodiment of the present application;
fig. 6 is a schematic diagram illustrating another service data rendered at a user end according to an embodiment of the present application;
fig. 7 is a schematic structural diagram illustrating a service data processing apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram illustrating another service data processing apparatus according to an embodiment of the present application.
Detailed Description
The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In the service data processing process, a merchant terminal can generate service data in different purchasing forms based on the same service item, the service data in each purchasing form are independent, the maintenance cost of the merchant service data is high, a user terminal needs to browse the service data in each purchasing form, but the service data generated under the same service item are the same, only the purchasing forms are different, the service data browsed by a user is limited, and accurate service data are difficult to recommend to the user. In order to solve the problem, the present embodiment provides a method for processing service data, as shown in fig. 1, the method includes:
101. when a generation instruction of service data is received, extracting an attribute description field matched with the service identification from a pre-constructed service resource database according to the service identification carried by the generation instruction, and generating a service description field.
The service data is related data of various service items displayed in the network platform, related data of various bathing items such as milk bath, sweat steaming, vinegar rubbing and the like can be displayed in the bathing shop, and related data of various hair cutting items such as hair cutting, hair perming, nursing and the like can be displayed in the hair shop.
The generation instruction of the service data is an instruction sent by a merchant end for selling the in-store service on the network platform, the generation instruction will usually carry the relevant information of the service item requested by the merchant to be displayed on the network platform, and the service identifier here may be a service item name or a number configured for the service item in advance. The number of service identifiers is not limited here, and may be a service identifier of one service item, a service package in which a plurality of service items represented by a plurality of service identifiers are combined, or n-out-of-m service items represented by a plurality of service identifiers (n-out-of-m service items).
In order to facilitate a merchant to maintain service data, service data displayed on a network platform does not need to be arranged, various service resource data including all contents of various service projects are collected in advance at a service end, the service resource data are arranged according to attribute characteristics of the service resource data, corresponding description fields such as spa service projects are arranged according to the attribute characteristics of each service project, different efficacy description fields are arranged for each part according to the attribute characteristics of each service project, the service resource data are templated, a service resource database is constructed, the attribute description fields of the service resource data on different attribute characteristics are stored in the service resource database, and each service project is provided with service identifiers such as names or numbers. And further, based on the service identification, the attribute description field of the service item matched with the service identification can be quickly acquired from the service resource database, and the service description field is the service content displayed in the network platform, so that a merchant does not need to difficultly arrange the service content.
It should be noted that, in order to obtain more comprehensive service resource data, each service item recorded in the service resource database and the attribute description field of the service item may be continuously updated with the rise of an emerging service item, so that a merchant may quickly create related data of each service item based on the updated service resource database.
For the device or apparatus that the execution subject of this embodiment may be service data processing, a service description field may be generated based on a generation instruction that a merchant requests to generate service data, and certainly, in order to improve flexibility of service data display, a custom service description field may also be set for the merchant, so that the merchant may autonomously add text content related to a service item, except for an attribute description field of the service item in the service resource database.
102. And merging the service description field and the pre-configured service information into a publishing link matched with the publishing identification according to the publishing identification carried by the generating instruction to generate service data.
When a merchant issues a service item in a shop on a network platform, issuing channels of different purchasing forms are independent, and if the merchant wants to issue a group purchase and reserve two purchasing forms for one service item, the merchant needs to generate service data of the service item in an issuing link of the group purchase and a reserved issuing link respectively.
For the embodiment of the present invention, the service information configured in advance is service purchase information set by the merchant for different distribution channels, for example, information such as prices of service items, service rules of different purchase forms, service item use shops, and the like, it should be noted that, for the same service item and different distribution channels, the service description fields extracted from the service resource data are the same, while the service information configured by the merchant in different distribution channels is different, for example, for a service item in a group purchase form, the service item use time is generally more limited, the service item price is generally more favorable, for a service item in a predetermined purchase form, the service item use time needs to be predetermined, if the service use peak period generally has a higher service item price, if the service use peak period generally has a lower service item price, the configuration of the specific service information is determined by the merchant and is not limited herein.
103. And inquiring and aggregating the service data generated by the same service identification merged into different release links, and displaying the aggregated service data as final service data.
Because the service data generated by the same service identifier in different publishing links correspond to the same service item and are only different in publishing channels, the specific contents of the specific service items displayed by the user side are approximately the same, and only the service item use rules are different.
In general, the usage rules of the service items by the user may not be the contents of major concern, but the service items themselves of more concern, for the embodiment of the present invention, the service data generated by the same service identifier merged into different publishing links is aggregated by querying and displaying the aggregated service data as the final service data, so that the user preferentially browses the service items themselves when browsing the network platform, and if the user is interested in the service items, the service items of different publishing channels can be further selected by triggering a drop-down box.
Compared with the mode that a merchant needs to respectively generate a plurality of service data in purchase forms for the same service project and display the service data to a user in the existing mode, the service data processing method provided by the embodiment of the invention can directly extract the service attribute description field matched with the service identifier for the merchant end through the pre-constructed service resource database, can accelerate the generation of the service data without the labor of the merchant, and reduces the maintenance cost of the service data of the merchant. For the user side, the service data generated by the same service identification merged into different release links can be aggregated and displayed by inquiring and aggregating, repeated service data in various shopping forms can be aggregated, the user does not need to spend time to browse the service data in each purchasing form, the service data in various purchasing forms can be triggered only when the user has a purchasing requirement, and the user can browse more service data and better accord with a decision path of the user when purchasing the service.
Further, as a refinement and an extension of the specific implementation of the foregoing embodiment, in order to fully describe the specific implementation process of the present embodiment, the present embodiment provides another method for processing service data, as shown in fig. 2, the method includes:
201. and constructing a service resource database based on the attribute characteristics of the service resource data in the service field.
The service resource data may be description information of service items published by each merchant collected on the network platform, and different service items have specific attribute features in the service field, and specifically, a service resource database may be constructed according to the service item type and the attribute features of the service items derived from the industry standard, and attribute description fields of the service resource data on different attribute features are recorded in the service resource database, for example, attribute features of a pedicure including a part, a technique, a type, and the like, which may be specifically shown in fig. 3.
The embodiment of the invention extracts the service data displayed by the user side in a customized manner by constructing the service resource database, can realize the rapid configuration of different service projects, decouples the service projects, and can realize the industrial customization of the page without influencing a basic display link and a transaction link.
202. When a generation instruction of service data is received, service resource data in the pre-constructed service resource database is inquired in a traversing mode according to a service identifier carried by the generation instruction, and the service resource data matched with the service identifier is obtained.
Since the service resource database records the service resource data of various service items, after receiving the generation instruction of the service data, the generated service items are indicated to be capable of inquiring corresponding service resource data from the pre-constructed service resource database and comparing the service identifiers one by one, so that the service resource data matched with the service identifiers are obtained.
203. And extracting attribute description fields of the service resource data matched with the service identifier on different attribute characteristics from the pre-constructed service resource database to obtain the attribute description fields matched with the service identifier.
Because the service resource database records the attribute description fields of various service items on different attribute characteristics, the attribute description fields belonging to the service items can be further inquired from the pre-constructed service resource database, and the service identifications are compared one by one, so that the attribute description fields matched with the service identifications are obtained.
204. And combining the attribute description fields matched with the service identification to generate a service description field.
For this embodiment, the service data generated by the generation instruction may not be one service item, may be a combination of multiple service items, and is used to instruct the platform to sell the service items in combination, and a specific combination form may be a combination of all the service items, or a combination of m service items or n service items may be selected from m service items, for example, bath and catering snacks may be combined into a bath package to be sold, and both may be used in combination, or a selection of 1 for the foot therapy/cupping glass 2 allows the user to select the foot therapy or cupping service item autonomously, or a combination of hair dyeing and hair waving (selection of 1 for 2) into a hair beautifying package.
If the generation instruction indicates that a plurality of service identifiers are combined, specifically, in the process of combining the attribute description fields matched with the service identifiers and generating the service description fields, the attribute description fields matched with each service identifier are combined to obtain the service description field of each service identifier, the service identifier field is only used for describing one service identifier, and then the service description fields of the plurality of service identifiers are spliced into the final service description field according to the combination form of the plurality of service identifiers indicated by the generation instruction.
Specifically, in the process of generating the final service description field by splicing the service description fields of the plurality of service identifiers according to the combination form of the plurality of service identifiers indicated by the generation instruction, the splicing order of the service fields of the plurality of service identifiers may be determined according to the combination form of the plurality of service identifiers indicated by the generation instruction, and then the final service description field may be generated by splicing the service description fields of the plurality of service identifiers according to the splicing order of the service fields of the plurality of service identifiers. The combination form of the service items herein may include, but is not limited to, a combination form of all service item combinations or a combination form of selecting one from a plurality of service item packages, and the like, for all the service item combinations, the splicing sequence of the service fields may be the order of using the service items, and for a combination form of selecting one from a plurality of service item packages, the splicing sequence of the service fields is the order of popularity of the service items, which is not limited herein.
205. And establishing an interactive relation between the service description field and the issuing system corresponding to the issuing identification according to the issuing identification carried by the generating instruction.
Specifically, each service item or combination of service item packages can be applied to different purchase forms, and a mode of interacting with different purchase forms can be as shown in fig. 4, the left side in fig. 4 is a purchase form of a selling system, the right side is a service package after service item combination, Chinese pedicure earmuffs are respectively applied to three purchase forms of group purchase, reservation and reservation, either one of Thai foot massage and whole body spa is applied to the reservation purchase form, and only the predetermined purchase form is applied to Thai ancient hot compress and dampness removal.
It should be noted that each issuing system herein shares one issuing link, and by generating an issuing identifier carried by an instruction, the issuing system can be determined, and then an interaction relationship between the service description field and the issuing system corresponding to the issuing identifier is established, and for the same service item or service item package, an interaction relationship between the same service item or service item package and different issuing systems can be established through the issuing identifier.
206. And merging the service description field and the pre-configured service information into a release link which is exclusively shared with the release system based on the interactive relation between the service description field and the release system corresponding to the release identification to generate service data.
According to the embodiment of the invention, the service description field and the service information configured in advance are applied to the release links in different purchase forms, so that an association relationship can be established between one service item and one release link or a plurality of release links, and the service data is applied to service commodities in different purchase forms.
207. And inquiring the service data corresponding to the same service identification merged into different release links.
Because the service data corresponding to the same service identifier in different release links all reflect the same service item or the combination of the same service item, the service data corresponding to the same service identifier merged into different release links can be inquired, and the service data belonging to the same service item or service item package can be screened out.
208. And aggregating the service data corresponding to the same service identifier merged into different release links according to service information pre-configured for each service identifier, and generating and displaying final service data.
For the embodiment of the present invention, the service description fields corresponding to the same service identifier in different distribution links are substantially the same, and the service information pre-configured by the merchant for each service identifier in different distribution links is usually not used, for example, the price of the service item in the group purchase distribution link is usually better, the price of the service item in the predetermined distribution link is usually higher, the usage time of the service item in the group purchase distribution link is usually business hours, and the usage time of the service item in the predetermined distribution link is usually a fixed time period. By fusing the service data corresponding to the same service identifier fused into different release links, the service data corresponding to the same service item can be combined together for display, and a user can pay more attention to the content of the service item and browse more service data.
Specifically, in practical application, as shown in fig. 5, after service data corresponding to the same service identifier in different release links are aggregated, the generated final service data can be displayed in a pull-down menu form after being rendered at a user side, so that a user is supported to select a service item first, and then select a service item in a corresponding purchase form by triggering and viewing the pull-down menu according to a service item that the user tends to. After the user selects the service item in the corresponding purchase form, as shown in fig. 6, the details of the service item and the other service description fields are fused, so that the user can more fully understand the specific information of the service item in the selected purchase form.
Based on the above description of the embodiments as shown in fig. 1 and fig. 2, for better understanding, the following specific application scenarios are given below for the current prior art, but are not limited thereto:
the specific service data processing process can manage various service items in advance through a service data processing platform, the description information of the service items is summarized based on a merchant center, a sales center and an open platform, the service items are managed, service packages and the service items forming the service packages are structurally arranged according to an industry standard, a service resource database is further constructed, after a generation instruction of merchant-side service data is received, according to request information carried by the generation instruction, on one hand, attribute description fields of the service items matched with service identifiers, such as service item selling rules, service item package commodities and the like, are inquired and selected from the service resource database, on the other hand, service information, such as service applicable stores, service stocks and the like, is configured for the displayed service items, and then the issuing identifiers indicated by the generation instruction, the service data generated by the service items are merged into different release links, the same service data in the different release links are aggregated, the rendered service data are displayed on the C end through service rendering, a user is supported to preferentially select the service items on the C end, and then the service items in different purchasing forms are selected according to the user tendency.
Further, as a specific implementation of the method in fig. 1 and fig. 2, an embodiment of the present application provides a device for processing service data, as shown in fig. 7, the device includes: an extraction unit 31, an integration unit 32, and an aggregation unit 33.
The extracting unit 31 may be configured to, when a generation instruction of service data is received, extract an attribute description field matched with a service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction, and generate a service description field, where attribute description fields of the service resource data on different attribute features are recorded in the pre-constructed service resource database;
the merging unit 32 may be configured to merge the service description field and the preconfigured service information into the release link matched with the release identifier according to the release identifier carried by the generation instruction, so as to generate service data;
the aggregation unit 33 may be configured to query and aggregate service data generated by the same service identifier merged into different release links, and display the aggregated service data as final service data.
Compared with the mode that a merchant needs to generate a plurality of service data in purchase forms for the same service project and display the service data to a user in the conventional mode, the service data processing device provided by the embodiment of the invention can directly extract the service attribute description field matched with the service identifier for the merchant end through the pre-constructed service resource database, can accelerate the generation of the service data without the labor of the merchant, and reduces the maintenance cost of the service data of the merchant. For the user side, the service data generated by the same service identification merged into different release links can be aggregated and displayed by inquiring and aggregating, repeated service data in various shopping forms can be aggregated, the user does not need to spend time to browse the service data in each purchasing form, the service data in various purchasing forms can be triggered only when the user has a purchasing requirement, and the user can browse more service data and better accord with a decision path of the user when purchasing the service.
In a specific application scenario, as shown in fig. 8, the extracting unit 31 includes:
the obtaining module 311 may be configured to query service resource data in the pre-constructed service resource database in a traversal manner according to the service identifier carried by the generating instruction, and obtain service resource data matched with the service identifier;
an extracting module 312, configured to extract attribute description fields of the service resource data matched with the service identifier on different attribute features from the pre-constructed service resource database, so as to obtain attribute description fields matched with the service identifier;
the generating module 313 may be configured to combine the attribute description fields matching the service identifier to generate a service description field.
In a specific application scenario, as shown in fig. 8, if the generation instruction indicates a combination of multiple service identifiers, the generation module 313 includes:
a combining sub-module 3131, configured to combine the attribute description fields matching with each service identifier to obtain a service description field of each service identifier;
the generating sub-module 3132 may be configured to splice the service description fields of the multiple service identifiers to generate a final service description field according to a combination form of the multiple service identifiers indicated by the generating instruction.
In a specific application scenario, the generating sub-module 3132 may be specifically configured to determine a splicing order of service fields of the multiple service identifiers according to a combination form of the multiple service identifiers indicated by the generating instruction;
the generating sub-module 3132 may be further configured to splice the service description fields of the multiple service identifiers according to the splicing order of the service fields of the multiple service identifiers to generate a final service description field.
In a specific application scenario, as shown in fig. 8, the merging unit 32 includes:
the establishing module 321 may be configured to establish an interaction relationship between the service description field and the publishing system corresponding to the publishing identifier according to the publishing identifier carried by the generating instruction, where each publishing system shares a publishing link;
the merging module 322 may be configured to merge the service description field and the preconfigured service information into a publishing link that is unique to the publishing system based on an interaction relationship between the service description field and the publishing system corresponding to the publishing identifier, so as to generate service data.
In a specific application scenario, as shown in fig. 8, the aggregation unit 33 includes:
the query module 331 may be configured to query service data corresponding to the same service identifier incorporated into different release links;
the aggregation module 332 may be configured to aggregate the service data corresponding to the same service identifier merged into different release links according to service information preconfigured for each service identifier, and generate final service data for display.
In a specific application scenario, as shown in fig. 8, the apparatus further includes:
the constructing unit 34 may be configured to, when the generating instruction of the service data is received, extract a description field matched with the service identifier from a service resource database that is constructed in advance according to the service identifier carried by the generating instruction, and construct the service resource database based on the attribute feature of the service resource data in the service field before generating the service description field.
It should be noted that other corresponding descriptions of the functional units related to the service data processing apparatus provided in this embodiment may refer to the corresponding descriptions in fig. 1 and fig. 2, and are not described herein again.
Based on the methods shown in fig. 1 and fig. 2, correspondingly, the embodiment of the present application further provides a storage medium, on which a computer program is stored, and the program, when executed by a processor, implements the method for processing the service data shown in fig. 1 and fig. 2.
Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the implementation scenarios of the present application.
Based on the method shown in fig. 1 and fig. 2 and the virtual device embodiment shown in fig. 7 and fig. 8, in order to achieve the above object, an embodiment of the present application further provides an entity device for processing service data, which may specifically be a computer, a smart phone, a tablet computer, a smart watch, a server, or a network device, where the entity device includes a storage medium and a processor; a storage medium for storing a computer program; a processor for executing a computer program to implement the above-described service data processing method as shown in fig. 1 and 2.
Optionally, the entity device may further include a user interface, a network interface, a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WI-FI module, and the like. The user interface may include a Display screen (Display), an input unit such as a keypad (Keyboard), etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), etc.
Those skilled in the art will appreciate that the structure of the entity device for store search information processing provided by the present embodiment is not limited to the entity device, and may include more or less components, or some components in combination, or different component arrangements.
The storage medium may further include an operating system and a network communication module. The operating system is a program for managing hardware and software resources of the actual device for store search information processing, and supports the operation of the information processing program and other software and/or programs. The network communication module is used for realizing communication among components in the storage medium and communication with other hardware and software in the information processing entity device.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus a necessary general hardware platform, and can also be implemented by hardware. Compared with the existing mode, for the merchant end, the service attribute description field matched with the service identifier can be directly extracted through the service resource database which is constructed in advance, the service data can be generated at high speed without effort of the merchant, and the maintenance cost of the merchant service data is reduced. For the user side, the service data generated by the same service identification merged into different release links can be aggregated and displayed by inquiring and aggregating, repeated service data in various shopping forms can be aggregated, the user does not need to spend time to browse the service data in each purchasing form, the service data in various purchasing forms can be triggered only when the user has a purchasing requirement, and the user can browse more service data and better accord with a decision path of the user when purchasing the service.
Those skilled in the art will appreciate that the figures are merely schematic representations of one preferred implementation scenario and that the blocks or flow diagrams in the figures are not necessarily required to practice the present application. Those skilled in the art will appreciate that the modules in the devices in the implementation scenario may be distributed in the devices in the implementation scenario according to the description of the implementation scenario, or may be located in one or more devices different from the present implementation scenario with corresponding changes. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.
The above application serial numbers are for description purposes only and do not represent the superiority or inferiority of the implementation scenarios. The above disclosure is only a few specific implementation scenarios of the present application, but the present application is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present application.
Claims (16)
1. A method for processing service data, comprising:
when a generation instruction of service data is received, extracting an attribute description field matched with a service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction, and generating a service description field, wherein the pre-constructed service resource database records the attribute description fields of the service resource data on different attribute characteristics;
merging the service description field and the pre-configured service information into a release link matched with the release identifier according to the release identifier carried by the generation instruction to generate service data;
and inquiring and aggregating the service data generated by the same service identification merged into different release links, and displaying the aggregated service data as final service data.
2. The method according to claim 1, wherein the extracting, according to the service identifier carried by the generation instruction, the attribute description field matched with the service identifier from a service resource database constructed in advance to generate the service description field specifically includes:
service resource data in the pre-constructed service resource database are inquired in a traversing mode according to the service identification carried by the generating instruction, and the service resource data matched with the service identification are obtained;
extracting attribute description fields of the service resource data matched with the service identifier on different attribute characteristics from the pre-constructed service resource database to obtain the attribute description fields matched with the service identifier;
and combining the attribute description fields matched with the service identification to generate a service description field.
3. The method according to claim 2, wherein if the generation instruction indicates a combination of a plurality of service identifiers, the combining the attribute description field matched with the service identifier to generate a service description field specifically includes:
combining the attribute description fields matched with each service identifier to obtain the service description field of each service identifier;
and splicing the service description fields of the plurality of service identifications to generate a final service description field according to the combination form of the plurality of service identifications indicated by the generation instruction.
4. The method according to claim 3, wherein the splicing the service description fields of the plurality of service identifiers to generate a final service description field according to the combination form of the plurality of service identifiers indicated by the generation instruction specifically includes:
determining the splicing sequence of the service fields of the plurality of service identifiers according to the combination form of the plurality of service identifiers indicated by the generation instruction;
and splicing the service description fields of the plurality of service identifications to generate a final service description field according to the splicing sequence of the service fields of the plurality of service identifications.
5. The method according to claim 1, wherein the merging, according to the release identifier carried by the generation instruction, the service description field and the preconfigured service information into a release link matched with the release identifier to generate service data specifically includes:
establishing an interactive relation between the service description field and a publishing system corresponding to the publishing identification according to the publishing identification carried by the generating instruction, wherein each publishing system shares a publishing link independently;
and merging the service description field and the pre-configured service information into a release link which is exclusively shared with the release system based on the interactive relation between the service description field and the release system corresponding to the release identification to generate service data.
6. The method according to claim 1, wherein the querying and aggregating the service data generated by the same service identifier merged into different release links, and displaying the aggregated service data as final service data specifically comprises:
inquiring service data corresponding to the same service identification merged into different release links;
and aggregating the service data corresponding to the same service identifier merged into different release links according to service information pre-configured for each service identifier, and generating and displaying final service data.
7. The method according to any one of claims 1 to 6, wherein before the, when receiving a generation instruction of service data, extracting a description field matching the service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction, and generating a service description field, the method further includes:
and constructing a service resource database based on the attribute characteristics of the service resource data in the service field.
8. An apparatus for processing service data, comprising:
the extracting unit is used for extracting an attribute description field matched with the service identifier from a pre-constructed service resource database according to the service identifier carried by the generating instruction when receiving a generating instruction of the service data, and generating the service description field, wherein the pre-constructed service resource database records the attribute description field of the service resource data on different attribute characteristics;
the merging unit is used for merging the service description field and the pre-configured service information into a publishing link matched with the publishing identification according to the publishing identification carried by the generating instruction to generate service data;
and the aggregation unit is used for inquiring and aggregating the service data generated by the same service identifier merged into different release links, and displaying the aggregated service data as final service data.
9. The apparatus of claim 8, wherein the extraction unit comprises:
the acquisition module is used for querying service resource data in the pre-constructed service resource database in a traversing manner according to the service identifier carried by the generation instruction, and acquiring the service resource data matched with the service identifier;
the extracting module is used for extracting attribute description fields of the service resource data matched with the service identifier on different attribute characteristics from the pre-constructed service resource database to obtain the attribute description fields matched with the service identifier;
and the generating module is used for combining the attribute description fields matched with the service identifications to generate service description fields.
10. The apparatus of claim 9, wherein if the generation instruction indicates a combination of multiple service identifiers, the generation module comprises:
the combination submodule is used for combining the attribute description fields matched with each service identifier to obtain the service description fields of each service identifier;
and the generation submodule is used for splicing the service description fields of the plurality of service identifications to generate a final service description field according to the combination form of the plurality of service identifications indicated by the generation instruction.
11. The apparatus of claim 10,
the generation submodule is specifically configured to determine a splicing order of service fields of the multiple service identifiers according to a combination form of the multiple service identifiers indicated by the generation instruction;
the generating sub-module is specifically further configured to splice the service description fields of the multiple service identifiers according to the splicing order of the service fields of the multiple service identifiers to generate a final service description field.
12. The apparatus of claim 8, wherein the merging unit comprises:
the establishing module is used for establishing an interactive relation between the service description field and the issuing system corresponding to the issuing identification according to the issuing identification carried by the generating instruction, and each issuing system shares one issuing link;
and the merging module is used for merging the service description field and the pre-configured service information into a release link which is exclusively shared by the release system based on the interactive relation between the service description field and the release system corresponding to the release identification to generate service data.
13. The apparatus of claim 8, wherein the aggregation unit comprises:
the query module is used for querying service data corresponding to the same service identification merged into different release links;
and the aggregation module is used for aggregating the service data corresponding to the same service identifier merged into different release links according to service information pre-configured for each service identifier, and generating and displaying final service data.
14. The apparatus of claim 8, further comprising:
and the construction unit is used for extracting a description field matched with the service identifier from a pre-constructed service resource database according to the service identifier carried by the generation instruction when the generation instruction of the service data is received, and constructing the service resource database based on the attribute characteristics of the service resource data in the service field before the service description field is generated.
15. A storage medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements the processing method of service data of any one of claims 1 to 7.
16. A device for processing service data, comprising a storage medium, a processor and a computer program stored on the storage medium and executable on the processor, characterized in that the processor implements the method for processing service data according to any one of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906871.2A CN110827113B (en) | 2019-09-24 | 2019-09-24 | Service data processing method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906871.2A CN110827113B (en) | 2019-09-24 | 2019-09-24 | Service data processing method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110827113A CN110827113A (en) | 2020-02-21 |
| CN110827113B true CN110827113B (en) | 2022-02-25 |
Family
ID=69548194
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910906871.2A Active CN110827113B (en) | 2019-09-24 | 2019-09-24 | Service data processing method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110827113B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111667245A (en) * | 2020-06-09 | 2020-09-15 | 政采云有限公司 | Service item commercialization method and device |
| CN111859191A (en) * | 2020-07-27 | 2020-10-30 | 平安科技（深圳）有限公司 | GIS service aggregation method, device, computer equipment and storage medium |
| CN112884553B (en) * | 2021-02-23 | 2023-01-20 | 山东浪潮通软信息科技有限公司 | API resource management method, equipment and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9129323B1 (en) * | 2012-09-18 | 2015-09-08 | Intuit Inc. | Method and system for facilitating customer driven group sales and discounts |
| CN105590233A (en) * | 2014-12-19 | 2016-05-18 | 中国银联股份有限公司 | Method and system for releasing information of commodities or service |
| CN106096991A (en) * | 2016-05-19 | 2016-11-09 | 北京三快在线科技有限公司 | The automatic generation method of a kind of set meal and device |
| CN106161505A (en) * | 2015-03-30 | 2016-11-23 | 重庆邮电大学 | User is matched the method and device of execution business |
| CN107507032A (en) * | 2017-08-25 | 2017-12-22 | 宁波灵云科技信息服务有限公司 | E-commerce system and implementation method based on information identification |
| CN108287837A (en) * | 2017-01-09 | 2018-07-17 | 阿里巴巴集团控股有限公司 | A kind of method for processing resource and equipment |
| CN109428904A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | The publication of business object, acquisition methods, apparatus and system |
-
2019
- 2019-09-24 CN CN201910906871.2A patent/CN110827113B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9129323B1 (en) * | 2012-09-18 | 2015-09-08 | Intuit Inc. | Method and system for facilitating customer driven group sales and discounts |
| CN105590233A (en) * | 2014-12-19 | 2016-05-18 | 中国银联股份有限公司 | Method and system for releasing information of commodities or service |
| CN106161505A (en) * | 2015-03-30 | 2016-11-23 | 重庆邮电大学 | User is matched the method and device of execution business |
| CN106096991A (en) * | 2016-05-19 | 2016-11-09 | 北京三快在线科技有限公司 | The automatic generation method of a kind of set meal and device |
| CN108287837A (en) * | 2017-01-09 | 2018-07-17 | 阿里巴巴集团控股有限公司 | A kind of method for processing resource and equipment |
| CN109428904A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | The publication of business object, acquisition methods, apparatus and system |
| CN107507032A (en) * | 2017-08-25 | 2017-12-22 | 宁波灵云科技信息服务有限公司 | E-commerce system and implementation method based on information identification |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110827113A (en) | 2020-02-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110827113B (en) | Service data processing method, device and equipment | |
| CN109308652A (en) | Wholesale method, system, terminal device and storage medium on line | |
| CN104616190A (en) | Multi-terminal 3D somatosensory shopping method and system based on internet and mobile internet | |
| WO2014008765A1 (en) | Network transaction platform system and method having merchandise subscription structure | |
| KR101771006B1 (en) | Shopping method and system using an augmented reality and image search | |
| JP6175340B2 (en) | Coupon providing apparatus, coupon providing method, and coupon providing program | |
| WO2017059788A1 (en) | Information recommendation method, device and system | |
| KR20190060359A (en) | Service providing apparatus and method for providing product information based on video | |
| CN111580788B (en) | Template collocation information recommendation method and device and electronic equipment | |
| US20200104895A1 (en) | Systems and methods for discovering and purchasing products online | |
| CN110445821B (en) | Information pushing method, device and system for household appliance and information processing method | |
| WO2017166534A1 (en) | Method and apparatus for online purchasing of membership service | |
| CN115860869A (en) | Shop information recommendation method, equipment and storage medium | |
| CN109559188A (en) | Wholesale method, system, terminal device and storage medium on line | |
| KR102497411B1 (en) | Method for providing nail art service and System for providing nail art service | |
| KR20090000600A (en) | Shopping mall system and web shopping service method using the same | |
| KR20180101078A (en) | Apparatus and Method for online product purchase | |
| Fuchs et al. | Blended shopping: Interactivity and individualization | |
| CN111222934A (en) | Information issuing method, device and computer system | |
| JP6930768B1 (en) | Management server and whiskey sales method | |
| WO2017166536A1 (en) | Method and apparatus for buying film ticket online | |
| KR102293779B1 (en) | Method for distributing recipe and System for distributing recipe | |
| JP2013140439A (en) | Electronic commerce server and operation method thereof, electronic commerce system, and program | |
| CN115907592A (en) | Page interaction method and device, storage medium and computer equipment | |
| JP2019125266A (en) | Information providing device, information providing method and information providing program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |