CN112337099B

CN112337099B - Service management method and device

Info

Publication number: CN112337099B
Application number: CN202011162366.0A
Authority: CN
Inventors: 马达
Original assignee: Tencent Technology Beijing Co Ltd
Current assignee: Tencent Technology Beijing Co Ltd
Priority date: 2020-10-27
Filing date: 2020-10-27
Publication date: 2024-01-12
Anticipated expiration: 2040-10-27
Also published as: CN112337099A

Abstract

The embodiment of the application provides a service management method and a device, after a data source is created based on service requirements, service composition data and service components are generated by executing selection operation on a service composition selection interface, corresponding services are generated by executing triggering operation, configuration operation, association path adding operation and setting operation on a service configuration interface, so that operators can quickly generate a new operation application by directly operating on the interface, and the operators can directly and independently operate in the whole process of constructing the operation application without communicating with game development and system development personnel back and forth, thereby greatly reducing labor cost, reducing steps for constructing the operation application, and having shorter whole process period and simplicity and easiness in operation. In addition, by setting the association options in the service association area, operators can set the service association relation among the service components according to the needs, thereby meeting the personalized requirements of the operation.

Description

Service management method and device

Technical Field

The present invention relates to the field of computers, and in particular, to a service management method and apparatus.

Background

In the prior art, when the game operation application is constructed, the operation firstly refines and abstracts the game characteristics of each game, related requirements are arranged, then the functional modules related to the requirements are grouped and classified, related requirement documents are written and communicated with system developers, the system developers evaluate the included characteristics according to the related requirement documents, then the evaluation results are returned to the operation, the operation writes further requirement documents according to the evaluation results and sends the further requirement documents to the game developers, the game developers and the system developers assist in working to complete the requirements, and finally the test is successful and then the operation delivery is carried out. In this process, both parties need to repeatedly develop some identical or similar modules with assistance from game and system developers, and the more involved people also make the communication cost greater, thus making the time taken from demand determination to system floor delivery longer.

In addition, if the operation is imperfect and needs to be supplemented when the operation is required, the whole process needs to be carried out again, and the workload is multiplied. That is, the process of constructing the game operation application in the prior art is complicated and has a long period.

Content of the application

The embodiment of the application provides a service management method and device, which can be used for solving the problems of complicated construction, operation and application processes and long period.

In one aspect, the present application provides a service management method, including:

acquiring a service demand, and creating a data source based on the service demand;

displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data;

the method comprises the steps of displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area;

receiving triggering operation through the component display area, and displaying candidate service components of the service corresponding to the triggering operation in the component display area;

receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area;

receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation;

And receiving setting operation of the association options through the service association area, and adding the service association relation generated according to the setting operation to a source service component and a downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation.

In one aspect, the present application provides a service management apparatus, including:

the creation module is used for acquiring service requirements and creating a data source based on the service requirements;

the generation module is used for displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service assembly for the service composition data;

the first display module is used for displaying a service configuration interface, and the service configuration interface comprises a component display area, a service configuration area and a service association area;

the second display module is used for receiving triggering operation through the component display area and displaying candidate service components of the service corresponding to the triggering operation in the component display area;

the first adding module is used for receiving configuration operation through the service configuration area and adding the service component corresponding to the configuration operation to the service configuration area;

The third display module is used for receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises the steps of adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation;

and the second adding module is used for receiving the setting operation of the association options through the service association area, and adding the service association relation generated according to the setting operation to the source service component and the downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation.

In one embodiment, the third display module comprises:

the determining unit is used for determining the service component corresponding to the initial point of the associated path as a source service component and determining the service component corresponding to the point of the associated path as a downstream service component according to the associated path adding operation;

the display unit is used for displaying association options between the source service component and the downstream service component in the service association area, wherein the association options comprise a service association relation establishment option, a downstream service component trigger type option and a downstream service component filling position option.

In one embodiment, the service management device further includes a receiving module, where the receiving module is configured to receive, through the service configuration area, an association identifier adding operation, where the association identifier adding operation includes adding, based on a downstream service component pointed by the association path, an association identifier corresponding to the downstream service component on the association path.

In one embodiment, the creation module includes:

the first acquisition unit is used for acquiring the storage type of the service data based on the service requirement;

the second acquisition unit is used for receiving a connection identifier selection operation through a service data selection interface, determining a connection identifier corresponding to the storage type according to the connection identifier selection operation, and acquiring the service data from a storage address corresponding to the connection identifier;

and the creation unit is used for determining a display field according to the field selection operation of the service data and creating a data source according to the display field.

In one embodiment, the generating module includes:

the first generation unit is used for receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, and generating a corresponding front-end service component for the front-end page data;

The second generating unit is used for receiving a background flow selection operation through a background flow selection interface, generating background flow data according to a background flow template corresponding to the background flow selection operation and the data source, and generating a corresponding background service component for the background flow data.

In one embodiment, the first generation unit includes:

the first receiving unit is used for receiving a first preset template selection operation through the front-end page selection interface;

the second receiving unit is used for displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving the first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation;

the first association unit is used for associating the data source with the target preset front-end page template to generate front-end page data.

In one embodiment, the first generation unit further comprises:

the third receiving unit is used for receiving the first custom template selection operation through the front-end page selection interface;

a fourth receiving unit, configured to display a custom front-end page template generating interface corresponding to the first custom template selecting operation, receive a layout selecting operation and a control selecting operation through the custom front-end page template generating interface, determine a required layout according to the layout selecting operation, determine a required control according to the control selecting operation, and generate a custom front-end page template according to the layout and the control;

And the second association unit is used for associating the data source with the custom front-end page template to generate front-end page data.

In one embodiment, the second generating unit includes:

a fifth receiving unit, configured to receive a second preset template selection operation through a background flow selection interface;

a sixth receiving unit, configured to display a preset background flow template selection interface corresponding to the second preset template selection operation, receive, through the preset background flow template selection interface, a second template selection operation, and determine a target preset background flow template according to the second template selection operation;

and the third association unit is used for associating the data source with the target preset background flow template to generate background flow data.

In one embodiment, the second generating unit further comprises:

the seventh receiving unit is used for receiving a second custom template selection operation through a background flow selection interface;

an eighth receiving unit, configured to display a custom background flow template generating interface corresponding to the second custom template selecting operation, receive a processor configuration operation and a processor connection operation through the custom background flow template generating interface, determine a configuration parameter of a processor according to the processor configuration operation, and generate a custom background flow template according to the processor connection operation;

And the fourth association unit is used for associating the data source with the self-defined background flow template to generate background flow data.

In one aspect, embodiments of the present application provide a server including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method as described above when the processor executes the program.

In one aspect, the present application provides a computer-readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor to perform the steps in the above-described method.

The embodiment of the application provides a service management method and device, based on the method, service requirements are acquired, and a data source is created based on the service requirements; displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data; the method comprises the steps of displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area; receiving triggering operation through the component display area, and displaying candidate service components of the service corresponding to the triggering operation in the component display area; receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area; receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation; and receiving setting operation of the association options through the service association area, and adding the service association relation generated according to the setting operation to a source service component and a downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation. After the data source is created based on the service requirement, the service composition data and the service components are generated by executing the selection operation on the service composition selection interface, and the corresponding service is generated by executing the triggering operation, the configuration operation, the association path adding operation and the setting operation on the service configuration interface, so that an operator can quickly generate a new operation application by directly operating on the interface, the operator can directly and independently operate in the whole process of constructing the operation application without communicating with the game development and system development personnel, the labor cost is greatly reduced, the steps of constructing the operation application are reduced, and the whole process period is shorter and simple and easy to operate. In addition, by setting the association options in the service association area, operators can set the service association relation among the service components according to the needs, and various operations such as automatically increasing and decreasing front-end pages, automatically changing switching actions among the front-end pages, automatically establishing and disconnecting connection between the front-end pages and background flows can be realized when the operators do not communicate with developers, so that the personalized requirements of the operation are met.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic view of a scenario of a service management system provided in an embodiment of the present application;

fig. 2 is a first flowchart of a service management method provided in an embodiment of the present application;

FIG. 3 is a logic block diagram of creating a data source in a business management method provided by an embodiment of the present application;

FIG. 4 is a logic block diagram of generating front-end page data in a service management method provided in an embodiment of the present application;

FIG. 5 is a schematic diagram of a custom front-end page template in a business management method according to an embodiment of the present application;

FIG. 6 is a logic block diagram of generating background flow data in a service management method according to an embodiment of the present application;

fig. 7 is a first schematic diagram of a service configuration interface in the service management method provided in the embodiment of the present application;

fig. 8 is a second schematic diagram of a service configuration interface in the service management method provided in the embodiment of the present application;

Fig. 9 is a third schematic diagram of a service configuration interface in the service management method provided in the embodiment of the present application;

fig. 10 is a schematic diagram of a front end page of a service in the service management method provided in the embodiment of the present application;

fig. 11 is an overall flow diagram of constructing an operation application in the service management method provided in the embodiment of the present application;

fig. 12 is a second flowchart of a service management method provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of a game interface augmentation activity in a business management method according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a service management device provided in an embodiment of the present application;

fig. 15 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The embodiment of the application provides a service management method and device, a server and a computer readable storage medium. The service management device may be integrated in a server, which may be a device such as a terminal.

The service management method provided by the embodiment of the application relates to the construction of game operation application. After acquiring service requirements, creating a data source based on the service requirements, receiving selection operation through a service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, generating corresponding service components for the service composition data, receiving triggering operation through a component display area, displaying candidate service components of the triggering operation corresponding to the service in the component display area on a service configuration interface comprising the component display area, receiving configuration operation through the service configuration area, adding the service components corresponding to the configuration operation to the service configuration area, receiving association path adding operation through the service configuration area, and displaying association options between source service components corresponding to association paths and downstream service components in the service association area according to the association path adding operation; and finally, receiving setting operation of the association options through the service association area, and adding the service association relation generated according to the setting operation to the source service component and the downstream service component corresponding to the association path to generate a service corresponding to the triggering operation, thereby completing the construction of the game operation application.

Referring to fig. 1, fig. 1 is a schematic view of a service management system provided in an embodiment of the present application, where the system may include terminals and servers, and the terminals, the servers, and the terminals and the servers are connected to each other for communication through the internet formed by various gateways, and the application scenario includes a user terminal 11 and a server 12; wherein:

the user terminal 11 includes, but is not limited to, a tablet computer, a notebook computer, a personal computer (PC, personal Computer), a mini-processing box, or other device, etc.;

server 12 includes a local server and/or a remote server, etc.

The user terminal 11 and the server 12 are located in a wireless network or a wired network, and perform data interaction.

The server 12 creates a data source after acquiring service requirements, the user terminal 11 performs a selection operation on a service composition selection interface, the server 12 receives the selection operation through the service composition selection interface, generates service composition data according to a service composition template corresponding to the data source and the selection operation, generates corresponding service components for the service composition data, then the user terminal 11 performs a triggering operation on a service configuration interface comprising a component display area and a service configuration area, the server 12 receives the triggering operation through the component display area, displays candidate service components of the service corresponding to the triggering operation in the component display area, the user terminal 11 re-performs a configuration operation, the server 12 receives the configuration operation through the service configuration area, adds the service components corresponding to the configuration operation to the service configuration area, re-performs an association path adding operation, the server 12 receives the association path adding operation through the service configuration area, displays association options between source service components corresponding to the association path and downstream service components in the service association area according to the association path adding operation, finally the user terminal 11 performs a setting operation on the association options, the server 12 receives the setting operation through the service association area, adds the association options generated according to the setting operation to the association path corresponding to the service components corresponding to the association path adding operation, and the service corresponding to the service components corresponding to the source and downstream service components are triggered to complete the operation.

It should be noted that, the schematic diagram of the system office shown in fig. 1 is only an example, and the servers and the office described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the system and the appearance of a new service office, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems. The following will describe in detail. The following description of the embodiments is not intended to limit the preferred embodiments.

Referring to fig. 2, fig. 2 is a first flowchart of a service management method according to an embodiment of the present application, which is applied to the server, and the service management method includes:

201: acquiring service requirements and creating a data source based on the service requirements.

In the application, the service refers to an operation application which is wanted to be constructed by a game operator according to operation requirements, and after the game is released, the operator operates the game through the constructed operation application so as to monitor, manage, maintain and the like the whole life cycle of the game. The service requirement refers to that an operation application needs to be built to operate a game to achieve a certain operation target, such as increasing the charge rate of a player, increasing the number of players, increasing the duration of a game of the player, and the like. A plurality of operation applications can be built on the SAAS platform according to different operation requirements, each operation application is an independent application on the SAAS platform after being built, and the operation application can be directly opened to see operation data related to a game after being opened for use, and operation operations such as adding recharging rebate activities and the like can be executed in the operation application, so that activities corresponding to the operation operations can be displayed in the game. Multiple operation applications can be built on the SAAS platform according to different service demands, each operation application is an independent application, the multiple operation applications can be presented in a list form on the SAAS platform, and an operator selects one of the operation applications to operate the game according to the needs.

The SAAS is an abbreviation of Software As A Service, meaning that software is a service, the SAAS platform is a software application platform for providing software service based on the Internet, the SAAS provider builds all network infrastructures, software and hardware operation platforms required by informatization for enterprises and is responsible for a series of services such as implementation in all earlier stages, maintenance in later stages and the like, the enterprises can rent the software service to the SAAS provider according to actual needs without purchasing software and hardware, building a machine room and recruiting IT personnel, and the information system is used through the Internet. In the application, a game enterprise sends a requirement for constructing an operation application to an SAAS provider, and the SAAS provider adds a corresponding construction function on an SAAS platform according to the requirement so that a user can autonomously generate a service corresponding to the service requirement on the SAAS platform.

The game comprises game characteristics, wherein the game characteristics comprise parameters such as play methods of the game, incentive mechanisms of the game, activities of the game and the like, after the game is released, game developers or game operators can adjust the game characteristics according to feedback of the players, namely, the game characteristics are different in different time periods after the game is released, when the operators need to construct a service, the operators firstly acquire the current game characteristics from the game, then determine service requirements according to the current game characteristics, if the incentive mechanisms in the current game characteristics are acquired, the players can get a specific gift bag for logging in for a plurality of days continuously, the players can get a high-value gift bag at a certain level, the activities are needed to be charged for buying certain props, and the like, and the lack of the incentive mechanisms which can improve the paying rate of the players is found, so that the service requirements are determined to be a service which can improve the paying rate of the players.

After the service requirement is acquired, an operator needs to acquire service data related to the service first, a data source is created according to the service data, the service data comprises data related to operation such as account data, game activity data, data of a data storage node and the like of a player, the required service data is different based on different service requirements, if the required service data is required to improve the paying rate of the player, the service data such as the current charging number and charging amount of the player needs to be acquired, and the service data such as the online time length of the player needs to be increased, and the online number and the current online time length of the player needs to be acquired. The step of creating a data source includes: acquiring a storage type of service data based on service requirements; receiving a connection identifier selection operation through a service data selection interface, determining a connection identifier corresponding to a storage type according to the connection identifier selection operation, and acquiring service data from a storage address corresponding to the connection identifier; and determining a presentation field according to a field selection operation on the service data, and creating a data source according to the presentation field.

As shown in fig. 3, the user 100 is a game operator, and the user 100 first obtains the type 21 of the service data storage based on the service requirement. The game will generate game data during running, the service data related to operation, such as player data, game activity data, data of data storage nodes, etc., will be stored in different types of locations, such as in the database of the system where the SAAS platform is located, such as mysql database or redis database, etc., and may also be stored in other systems, so after the type 21 of service data storage is obtained, it is determined, based on the type 21, whether the service data needs to be remotely invoked from other systems or directly obtained from the database of the present system, then a connection identifier selection operation is performed on the service data selection interface, a connection identifier corresponding to the storage type is selected, the service data is obtained from the storage address corresponding to the connection identifier, specifically, if the service data is remotely invoked, the connection identifier selected on the service data selection interface is in the interface form 22, and the communication protocol 23 of the target system is further selected; if obtained directly from the database, the connection selected on the traffic data selection interface is identified as database form 24 and the database address 25 of the target database is further selected or entered on the interface. After the above steps are completed, the service data corresponding to the connection identifier can be associated with the operation application, that is, the service data is obtained, and because the data volume of the service data in other systems or databases is larger, operators do not need to display all the service data, after the service data is obtained, field selection operation is performed on the service data selection interface, the field selection display 26 is selected, part of the data is selected from the service data to be displayed as a display field, and the display is performed in the form of the field, so that the display effect is more visual, wherein the fields can be the account number of the player, the role of the player, the starting time and the ending time of the game, and the like. After the field is extracted, a field configuration 27 is further required, where the field configuration refers to defining parameters such as a field, a field length, a field type, etc., so as to ensure that the extracted field is displayed in a specified format, and facilitate the verification of the validity of the field. After all operations have been performed on the service data selection interface, a data source is created on the SAAS platform by configuring the selection operations and configuration operations 20. In actual operation, more service data is required for operation, so that the above steps need to be repeated to create multiple data sources. The operator can generate data source identifiers for the created multiple data sources, specifically, the names or numbers of the data sources, and the corresponding data sources can be quickly searched according to the data source identifiers when the data sources need to be searched and selected later.

Through the step, operators can directly perform selection operation and configuration operation on the service data selection interface to acquire the data source, and the whole process is simple and easy to implement.

202: displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to a service composition template and a data source corresponding to the selection operation, and generating a corresponding service component for the service composition data.

For a complete service, the service composition comprises a front-end page and a background process, the front-end page needs to be generated at the front end to display service data needed by operators, the background process needs to be generated at the background to provide relevant logic for display of the front-end page data, interaction between operators and the front-end page and the like, wherein the background process refers to operations of adding, deleting, changing, searching, condition judging, calculating, uploading files and the like of the service data corresponding to the triggering operation by the operators after the triggering operation is carried out on the front-end page control or data by the operators, the background process is started based on triggering of related events, the related events refer to actions or operations such as clicking, pointer suspension and the like needed to be carried out by the background process, for example, the clicking is set to be one related event of the background process, and when the operators click a query button on the front-end page, the background process is started in response to the triggering operation, the background process carries out query operation on the service data needing to be displayed on the front-end page to display the queried service data. The method comprises the steps that after association is needed between a front-end page and a background process, normal operation of a service can be achieved, wherein association refers to selection of the front-end page and the background process on an interface of an SAAS platform, a mapping relation is established between the two selected objects at the rear end of the SAAS platform, and after the mapping relation is established, relevant logic corresponding to the front-end page is provided by the background process associated with the front-end page.

After the creation of the data source is completed, a service composition interface is displayed, a game operator performs selection operation on a service composition selection interface of the SAAS platform to select a service composition template, wherein the service composition selection interface comprises a front-end page selection interface and a background flow selection interface, and the service composition template comprises a front-end page template and a background flow template.

In one embodiment, the step of generating the business component specifically includes: receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template and a data source corresponding to the front-end page selection operation, and generating a corresponding front-end service component for the front-end page data; receiving a background flow selection operation through a background flow selection interface, generating background flow data according to a background flow template and a data source corresponding to the background flow selection operation, and generating a corresponding background business component for the background flow data.

And selecting a front-end page template on the front-end page selection interface, associating the front-end page template with a data source, namely selecting two objects, namely the front-end page template and the data source, on the front-end page selection interface of the SAAS platform, and establishing a mapping relation between the two selected objects at the rear end of the SAAS platform so that the data sources can be displayed in the front-end page template to generate front-end page data capable of displaying the data sources, and then generating a front-end service component corresponding to the front-end page data. There are two ways to generate the front page data.

In one embodiment, the step of generating front end page data includes: receiving a first preset template selection operation through a front-end page selection interface; displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving the first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation; and associating the data source with a target preset front-end page template to generate front-end page data. As shown in fig. 4, the user 100 is a game operator, and the user 100 first selects the creation type 31 of the front-end page template based on the service requirement. Before an operation application is built, the layout and the format of front end pages in all operation modes in the current industry are summarized to form a plurality of standard page templates, each standard page template has a specific layout and a specific control, then the standard page templates are added into a system where an SAAS platform is located to be used as a preset front end page template, when a user 100 executes a first preset template selection operation, namely, a selection creation type 31 is standard, a preset front end page template selection interface corresponding to the first preset template selection operation is displayed on the SAAS platform, operators can directly select a required target preset front end page template in all standard page templates 32 of the preset front end page template selection interface, specifically, a data source 110 which is wanted to be displayed on a front end page is firstly selected on the front end page selection interface, then a first template selection operation is executed in the standard page template 32 of the preset front end page template selection interface, namely, a page template selection 33 is executed, a required target front end page template is selected, a data source 110 and the selected target preset front end page template are displayed, and the data source and the front end page control are related to the front end page data of the front end page control are displayed in the front end page, and the front end page control data are displayed in the front end page layout, and the front end page control data are displayed in the front end page control and the front end page control. After the above operations are performed, the configuration storage 30 is performed, so that the generation and storage of the front-end page data are completed, and then when the operating application is constructed, the front-end page will display the target preset front-end page template selected at this time, and the control in the target preset front-end page template will display the data source selected at this time.

In one embodiment, the step of generating front end page data includes: receiving a first custom template selection operation through a front-end page selection interface; displaying a custom front-end page template generating interface corresponding to the first custom template selecting operation, receiving layout selecting operation and control selecting operation through the custom front-end page template generating interface, determining a required layout according to the layout selecting operation, determining a required control according to the control selecting operation, and generating a custom front-end page template according to the layout and the control; and associating the data source with the self-defined front-end page template to generate front-end page data. As shown in fig. 4, when the user 100 does not find a desired template in the existing standard page templates, a first custom template selection operation is performed, that is, the creation type 31 is selected as a custom, specifically, the first custom template selection operation is performed on the front-end page selection interface, the custom is selected, then the SAAS platform displays a custom front-end page template generation interface corresponding to the first custom template selection operation, an operator performs a layout selection operation and a control selection operation in the custom front-end page template generation interface, that is, performs a drag layout 34 to form a desired layout, performs a drag control 35 to form a desired control in the desired layout, generates a custom front-end page template, and then binds a data source 110 for each control in the custom front-end page template, so that the content of the data source 110 can be displayed by the control, then the data source 110 is associated with the selected custom front-end page template, and front-end page data 36 is generated in the SAAS platform according to the association result, where the front-end page data includes the layout of the front-end page control, the setting position of each control, the data source to be displayed in each control, and so on. After the above operations are performed, the configuration storage 30 is performed, so that the generation and storage of the front-end page data are completed, and the custom front-end page template selected at this time is displayed on the front-end page when the operating application is constructed later, and the control in the custom front-end page template displays the data source selected at this time.

As shown in fig. 5, to generate the custom front-end page template generation interface, the custom front-end page template generation interface in fig. 5 includes a first function area 51, a display area 52, an attribute area 53, and a second function area 54. The first functional area 51 is provided with a layout container and basic field options, and a plurality of controls are displayed under each option, for example, the controls of the layout container options comprise grid layout, horizontal dividing lines, dynamic tables, tabs tab pages and the like, and the controls of the basic field options comprise navigation menus, input boxes, text boxes and the like. The display area 52 and the attribute area 53 are blank areas in the initial state, and the second function area 54 is provided with a return list button, a reset button and a save button, and is further used for displaying the generated identifier of the custom front-end page template, where the identifier includes the name and the number of the template, such as [ CFM week war ] query page- (186).

When the custom front-end page template is generated, one of the controls is selected from the layout container options in the first functional area 51, and then dragged to the display area 52, at this time, the layout corresponding to the control is displayed in the display area 52, for example, when the grid layout control is selected, the layout presented in the display area 52 is the grid layout, and the required control can be added in each grid in the grid layout. If the associated layout is not selected in the layout container, the initial blank layout is defaulted, and if the dynamic form control is selected to be dragged to the display area 52, a dynamic form control is displayed in the display area 52. Based on the business requirement, a plurality of controls are selected in the layout container to be dragged to the display area 52, and accordingly, the plurality of controls are displayed in the display area 52, and the positions of the controls can be adjusted in the display area 52 to generate the required custom front-end page template. When the control in the display area 52 is initially represented by a blank control 522, the user 100 adds fields to the blank control 522 according to the self-requirement when generating the custom front-end page template based on the service requirement, so that the blank control 522 becomes a function control 521 with a specific function, for example, when the custom front-end page template to be generated is a query page, fields such as a start date selection frame, an end date selection frame, a query button and the like are added to a blank control 522, and specifically, the method is operated to select a corresponding field from basic field options of the first function area 51 and drag the corresponding field to the blank control 522, so that the corresponding field becomes the function control 521. In addition, after a control is selected, some basic attributes of the control, such as a table size, a table border, etc., are displayed in the attribute area 53, and the user 100 may set in the attribute area 53 to adjust the attribute of the corresponding control. A field & data option is further provided in the attribute area 53, when a data source is wanted to be displayed in a certain blank control 522, the option is triggered, a list of the data sources is displayed, then a required data source is selected from the list, the data sources are displayed in the blank control 522 in the display area 52, the blank control 522 is bound with the displayed data sources, at this time, the blank control 522 becomes a display control 523, in this embodiment, the display control 523 is formed by dragging a dynamic form control in an initial stage, and after the data sources are bound, the display control 523 is used for displaying dynamic form data.

After the required layout and the required controls are determined, a custom front-end page template is generated, fields or data sources are associated for each control in the custom front-end page template to generate corresponding functional controls and presentation controls, then an identifier is added for the custom front-end page template, the identifier comprises the name and number of the template, such as [ CFM week war report ] query page- (186), and a specific adding mode can be directly input in the second functional area 54. After all the operations are performed, the save button in the second functional area 54 is clicked, and the custom front-end page template generated at this time is saved into the system where the SAAS platform is located. When the front-end page template is selected next time, the template generated at this time can be used as a preset front-end page template for selection, namely, each user-defined front-end page template can be stored and used as a newly added standard page template, so that the body quantity of the standard page template is continuously increased, the larger the selectable range is when the front-end page template is selected, the less the condition of needing user definition is gradually needed, and the time for generating front-end page data is shortened.

In actual operation, there is more than one front page that the front end needs to display, so the above steps need to be repeated to create multiple front page data. The operator can generate page identifiers for the created plurality of front-end page data, specifically, the names, the numbers and the like of the pages, and when the corresponding front-end page data are required to be searched later, the corresponding front-end page data can be quickly searched according to the page identifiers. After generating the front-end page data, generating a corresponding front-end page component for each front-end page data, wherein the page component identification of the front-end page component can be the same as the page identification.

After the generation of the front-end page data is completed, game operators select a background flow template on a background flow selection interface of the SAAS platform and associate the background flow template with a data source, namely, select two objects, namely the background flow template and the data source, on the background flow selection interface of the SAAS platform, and establish a mapping relation between the two selected objects at the rear end of the SAAS platform so as to generate background flow data for realizing various application functions of operation application, and then generate a background business component corresponding to the background flow data. There are two ways to generate the background flow data.

In one embodiment, the step of generating background flow data comprises: receiving a second preset template selection operation through a background flow selection interface; displaying a preset background flow template selection interface corresponding to the second preset template selection operation, receiving the second template selection operation through the preset background flow template selection interface, and determining a target preset background flow template according to the second template selection operation; and associating the data source with the target preset background flow template to generate background flow data. As shown in fig. 6, the user 100 is a game operator, and the user 100 first selects the creation type 41 of the background flow template based on the service requirement. Before the operation application is built, background processes in all operation modes in the current industry are summarized to be a plurality of standard process templates, then the standard process templates are added to a system where an SAAS platform is located to be used as preset background process templates, when a user 100 executes a second preset template selection operation, namely, when the creation type 41 is selected as a standard, the SAAS platform displays a preset background process template selection interface corresponding to the second preset template selection operation, operators can directly select a required target preset background process template in all standard process templates 42 of the preset background process template selection interface, specifically, firstly select a data source 110 on the background process template selection interface, then execute a second template selection operation in the standard process templates 42 of the preset background process template selection interface, namely, perform process template selection 43, select a required target preset background process template, associate the data source 110 with the selected target preset background process template, and then package and issue the data source 110 as a corresponding target associated event template in the preset background process event. In the present application, the background process refers to related logic that needs to be implemented by an operation application, such as adding, deleting, and checking, etc., and the related event refers to an action or operation that needs to be performed by the background process, such as an action event that needs to process data before and after adding data, etc. After the above operations are executed, generating background flow data in the SAAS platform, where the background flow data includes configuration of a middle flow of the background flow, an event associated with the background flow, and the like, and then performing configuration storage 40 to complete generation and storage of the background flow data, and subsequently starting a corresponding background flow according to triggering of the associated event when the operating application is constructed.

In one embodiment, the step of generating background flow data comprises: receiving a second custom template selection operation through a background flow selection interface; displaying a custom background flow template generating interface corresponding to the second custom template selecting operation, receiving a processor configuration operation and a processor connecting operation through the custom background flow template generating interface, determining configuration parameters of a processor according to the processor configuration operation, and generating a custom background flow template according to the processor connecting operation; and associating the data source with the self-defined background flow template to generate background flow data. As shown in fig. 6, when the user 100 does not find the desired template in the existing standard flow template, a second custom template selection operation is performed, that is, the creation type 41 is selected to be custom, specifically, the second custom template selection operation is performed on the background flow selection interface to select custom, then the SAAS platform displays a custom background flow template generation interface corresponding to the second custom template selection operation, the operator performs a processor configuration operation and a processor connection operation in the custom background flow template generation interface, the processor configuration operation refers to selecting the background processor 44 to perform the background flow configuration 45, so that the background processor has the capability of processing the data according to the preset logic and steps after the data is acquired, and the configuration process may specifically include basic information configuration, input field configuration, related parameter configuration, output field configuration and the like, after configuration, each processor has its corresponding configuration parameters, which may be used to perform specific operations such as updating, querying, calculating, etc., and typically requires generating a plurality of process processors 46, each process processor 46 is configured to perform an operation, the processor connection operation includes concatenating the plurality of process processors 46 in a predetermined order, and specifically, after the configuration of each process processor 46 is completed, generating corresponding process components for each process processor 46, then arranging the process components in a predetermined order in a custom background process template generating interface, adding a process association path between adjacent components, that is, adding an association line with an arrow, the arrow pointing from the previous process to the next process, storing the arrangement operations and the path adding operations after adding the process association path between each process component, the processing logic of each flow processor 46 is combined with each other to form a complete set of processing logic to generate a custom background flow template, and then the data source 110 is associated with the custom background flow template, and corresponding association events 47 are selected for the flows in the custom background flow template after the data source is associated. After the above operations are performed, the background flow data is generated in the SAAS platform, and then configuration storage 40 is performed to complete generation and storage of the background flow data, and then when the operating application is constructed, the background starts the corresponding background flow according to the triggering of the related event.

In actual operation, the user on the front-end page interacts with the operation application in multiple ways, and multiple corresponding background processes are needed, so that the steps are needed to be repeated to create multiple background process data. The operator can generate a process identifier for the created plurality of background process data, specifically, the name, the number and the like of the process, and can quickly find the corresponding background process data according to the process identifier when the process is required to be found later. After the background flow data is generated, generating a corresponding background service component for each background flow data, wherein the flow component identifier of the background service component can be the same as the flow identifier.

Through the steps, operators can directly select the service composition templates and the data sources on the service composition interfaces and associate the service composition templates and the data sources, front-end page data and background flow data can be generated relatively simply and intuitively, repeated communication with developers, code writing and the like are not needed to generate the data, and the professional requirements on the operators are greatly reduced. And after each time the self-defined front end page template and the self-defined background process template are generated, the self-defined front end page template and the self-defined background process template can be stored and used as new pre-set front end page templates and pre-set background process templates, when other businesses are built later, the selectable template range can be gradually increased, namely, when the times of building businesses on the SAAS platform are more, the selectable template range is larger when the businesses are built, the self-defined conditions are less and less, and therefore, the business building efficiency is gradually improved.

203: and displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area.

The service configuration interface comprises a component display area, a service configuration area and a service association area, when the service configuration interface is initially entered, a list of each service is displayed in the component display area, each service in the list displays a respective service identifier, specifically, a service name and/or a service number, and the service configuration area and the service association area are blank areas. The front-end service components and the background service components generated in the steps are visualization components corresponding to the front-end service data and the background process data, are stored in the SAAS platform, and have the same service identifier, and when entering the service configuration interface, all the front-end service components and all the background service components belonging to the same service are located in a sub-list of the service to jointly form candidate service components of the service.

204: and receiving triggering operation through the component display area, and displaying candidate service components of the service corresponding to the triggering operation in the component display area.

And each service in the service list is provided with a corresponding sub-list, and when a triggering operation is received, the corresponding sub-list is displayed by the service corresponding to the triggering operation, and other services still only display the service identification. And displaying candidate service components corresponding to the service in the sub-list, wherein the candidate service components comprise front-end service components and background service components corresponding to the service. Since operators need to see the operation data and need the front-end page to display the data source, and meanwhile, operators have operation requirements on the front-end page and need the background process to provide processing logic for each operation, the front-end page data and the background process data are necessary components for forming a complete service, and the candidate service components need to comprise the front-end service components and the background service components in the application.

205: and receiving configuration operation through the service configuration area, and adding the service component corresponding to the configuration operation to the service configuration area.

The game operator performs configuration operation in the service configuration area, specifically, selecting a certain candidate service component in the component display area and dragging the candidate service component to the service configuration area, or selecting an inserted component in the service configuration area, and then selecting a certain candidate service component in the component display area, and then the server receives configuration operation through the service configuration area.

In the initial state, the service configuration area is blank, when configuration operation is received, candidate service components corresponding to the configuration operation in the component display area are added into the service configuration area, the service components can be placed at any position in the service configuration area, or grid layout is set in advance in the service configuration area, so that the service components can be placed at certain preset positions.

In one embodiment, the step comprises: and adding the front-end service components and the background service components corresponding to the configuration operation to the service configuration area. For the same service, front-end service components and background service components are displayed in a sub-list, templates corresponding to the two components are associated with a data source, but the front end and the background are still independent, so that when configuration operation is carried out, the front-end service components corresponding to the service requirement are selected from the sub-list displayed by the service, added into a service configuration area, and then the background service components corresponding to the front-end service components are determined according to the corresponding relation between the front-end pages corresponding to the added front-end service components and the background flow, and the background service components are also added into the service configuration area.

As shown in fig. 7, the service configuration interface includes a component display area 71 and a service configuration area 72, where a service list is displayed in the component display area 71, and a service may include a white list task, video rebroadcasting, CFM Zhou Zhanbao management, multimedia management, and the like, and when a certain service is triggered, candidate service components corresponding to the service are displayed, including a front-end service component and a background service component. Taking a white list task as an example, when the white list task is triggered, a front-end service component and a background service component corresponding to the white list task are displayed in a component display area 71, wherein the front-end service component may include a general white list front page 711, a white list 712, a service configuration list 713, a call-in white list 714, a newly added edit configuration 715 and a call-in callback configuration 716, and the background service component may include a setting service COOKIE721, a call-in query ReKey existence 722, a general white list 723, a call-in white list 724, a call-in configuration list 725 and a call-in configuration add edit 726.

The user 100 performs a configuration operation on the service configuration interface, where the configuration operation may specifically be dragging, and sequentially adds the front service component and the background service component corresponding to the whitelist task to the service configuration area 72. The front-end service components are sequentially arranged in the service configuration area 72 from top to bottom, between two front-end service components adjacent from top to bottom, the front-end page corresponding to the front-end service component below is a sub-page of the front-end service component above, that is, the front-end page corresponding to the front-end service component above is displayed first after entering the operation application, and the front-end page corresponding to the front-end service component below, that is, the sub-page, is displayed after the user 100 performs the selection operation on the page. For example, there may be two options of a white list and a service configuration list on the general white list top page, when the white list is selected, a front page corresponding to the front service component of the white list 712 is displayed, and when the white list introduction option is selected in the front page, a front page corresponding to the front service component of the white list 714 is displayed, and so on. Each background service component is determined according to the position of the front end service component when adding, when the front end page corresponding to a certain front end service component needs to use the flow corresponding to a certain back end service component, the back end service component is added above or below the front end service component, for example, after receiving the triggering event of importing the white list in the front end page corresponding to the white list 714, the background flow is needed to process the task of adding the white list, so that the task 724 of adding the white list in the front end service component is added below the white list 714.

When the service configuration interface does not find the required service components, the plug-in mode can be used first, i.e. the required service components are written and generated manually by using plug-in self-writing programs or interfaces provided by the system, embedded into the current SAAS platform for filling, and then the newly added service components are continuously related with the original service components on the service configuration interface through triggering operation, configuration operation and association operation to generate corresponding services. As shown in fig. 7, a component area 73 is further disposed on the right side of the service configuration area, and if a plug-in option is selected in the component area 73, a corresponding element of the plug-in can be selected and a corresponding code can be written to generate a new service component. By adopting the plug-in mode, the selection surface of operators is increased, the operation application is more flexible and changeable in construction, and more operation requirements are met.

206: and receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises the steps of adding association paths between corresponding service components, determining the direction for the association paths, and displaying association options between source service components and downstream service components corresponding to the association paths in the service association area according to the association path adding operation.

The game operator executes an associated path adding operation in the service configuration area, wherein the associated path adding operation is specifically to add an arrow-bearing line between the upper service component and the lower service component which are associated with each other, the arrow-bearing line represents an associated path between the two service components, and the arrow direction represents the direction of the associated path. After adding the association path, the component area 73 of the interface in the previous step becomes a service association area 75, and association options between the source service component and the downstream service component corresponding to the association path are displayed in the service association area 75.

In one embodiment, the steps specifically include: according to the association path adding operation, determining a service component corresponding to the association path starting point as a source service component, and determining a service component corresponding to the association path pointing point as a downstream service component; and showing association options between the source service component and the downstream service component in the service association zone, wherein the association options comprise a downstream service component trigger type option, a service association relation establishment option and a downstream service component filling position option. The associated path is a line with an arrow, the line comprises a starting point and a pointing point, after the associated path is added between two service components, the service component connected with the starting point of the line is used as a source service component, and the service component connected with the pointing point of the line is used as a downstream service component. Each time an association path is added in the service configuration area, association options between the source service component and the downstream service component corresponding to the association path are displayed in the service association area 75, and the association options include an option of whether to establish a service association relationship, an option of triggering a downstream service component, and an option of filling a position of the downstream service component. The association path may be added between two front-end service components, or between one front-end service component and one background service component. The content of the associated options correspondingly presented in the service association area 75 is also different for different ways of adding the associated paths.

When the associated path is added between the two front-end service components, the source service component and the downstream service component are both front-end service components, whether the service association relation option is established in the association option comprises whether the front-end page corresponding to the downstream service component can be entered through the triggering operation on the front-end page corresponding to the source service component, the downstream service component triggering type option comprises what type of triggering operation is executed on the front-end page corresponding to the source service component and can be entered on the front-end page corresponding to the downstream service component, and the downstream service component filling selection comprises what form the front-end page corresponding to the downstream service component is presented on the front-end page corresponding to the source service component. As shown in fig. 8, when the service components in the service configuration area 72 are arranged in sequence, and at this time, the user 100 performs an association path adding operation in the service configuration area 72, a line is added between two front-end service components associated with each other, an arrow points from a front-end service component at a previous stage to a front-end service component at a next stage, if an association path is added between the general whitelist front page 711 and the service configuration table 713, the association options displayed in the service association area 75 include menu items, trigger types, downstream component loading, downstream component filling up to an equal option, default display in the menu items [ on demand ] service component identifier "service configuration" corresponding to the service configuration table 713, the trigger types include none, loading, clicking, double clicking, changing, hovering and customizing, the downstream component loading includes yes and no, the downstream component filling up to include none, popup window, source component and flow entry.

When the association path is added between a front-end business component and a background business component, the source business component is the front-end business component, the downstream business component is the background business component, whether the business association relation option is established in the association option comprises whether the background process corresponding to the downstream business component can provide relevant logic for the front-end page corresponding to the source business component, the downstream business component triggering type option comprises what type of triggering operation is executed on the front-end page corresponding to the source business component and can start the background process corresponding to the downstream business component, and the downstream business component filling position option comprises what position triggering of the front-end page corresponding to the source business component can start the background process corresponding to the downstream business component. As shown in fig. 9, the service components in the service configuration area 72 are arranged in sequence, at this time, the user 100 performs an association path adding operation in the service configuration area 72, a line with an arrow is added between the front-end service component and the corresponding back-end service component, the arrow is pointed to by the front-end service component to the back-end service component, and if an association path is added between the [ on demand ] service configuration table 713 and the [ on demand ] configuration list 725, the association options displayed in the service association area 75 include the trigger element, the trigger type, the downstream component loading, the downstream component filling to, and the like, the trigger type includes none, loading, clicking, double clicking, changing, hovering, and customizing, and the downstream component loading includes yes and no, the downstream component filling to include the source component and the flow entry.

In one embodiment, after the step of receiving the association path adding operation through the service configuration area, the method further comprises: and receiving an association identifier adding operation through the service configuration area, wherein the association identifier adding operation comprises adding an association identifier corresponding to a downstream service component on the association path based on the downstream service component pointed by the association path. The related identifier adding operation specifically adds a text description on a line where adding is completed, where the content of the text description is based on the function of a downstream service component pointed by a related path, for example, the content of an identifier added on a line between the "on demand" import white list 714 and the "on demand" add white list task 724 is the "on demand" add white list task, and then the function of a background process corresponding to the background service component, which means the "on demand" add white list task 724, is used for executing the add white list task, where the content of an identifier of the related identifier in the present application is the same as the name of the downstream service component, but not limited by the content of the identifier, and the content of the identifier of the related identifier may not be consistent with the name of the service component, or may be other words added by operators based on own habits and understanding. After each service component and the associated path are added to the service configuration area 72, a tree structure is formed in the service configuration area 72, and when the operation application which is expected to be built is complex, the tree structure is complex and huge, and at this time, due to the associated identifier added to the associated path, an operator using the service configuration interface can intuitively see the association based on what logic is performed between each service component in the tree structure.

207: and receiving setting operation on the association options through the service association area, and adding the service association relation generated according to the setting operation to the source service component and the downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation.

After the association options are displayed in the service association area 75, setting operation is performed on each association option, service association relationships generated by different setting operations are different, service association relationships are established between corresponding service components according to the setting operation, when two service components which are associated with each other are front-end service components, the front-end page corresponding to the front-end service component is indicated to be a sub-page of the front-end service component, that is, after entering an operation application, a front-end page is displayed first, and after a control is triggered on the front-end page, a back-end page, that is, the sub-page corresponding to the control is displayed. When one of the two service components is a front-end service component and the other is a background service component, the corresponding flow of the background service component is used for starting after the front-end page corresponding to the front-end service component receives the trigger of the association event so as to perform corresponding data processing.

As shown in fig. 8, an association path is added between the general whitelist top 711 and the service configuration table 713, and then the association options displayed in the service association area 75 include menu items, trigger types, downstream component loading, downstream component filling and the like, and setting these association options to "yes" indicates that a service association relationship is to be added between the general whitelist top 711 and the service configuration table 713, a page of the service configuration table can be entered after the whitelist top performs a trigger operation, a trigger type is set to "one click", a page of the service configuration table can be entered after the whitelist top performs a one-click trigger operation, a downstream component filling is set to "source component", a second-level association option including a filling type, a filling type is set to "position selection", a third-level association option including a position and a filling mode is set to "cover", a position is selected and a filling mode is set to "cover", a page of the service configuration table can be entered after the whitelist top performs a trigger operation, a direct display of the whitelist is performed at the position of the whitelist top, and the service configuration table can be displayed directly. When the setting operation is different, the corresponding generated service association relationship is also different, for example, when the downstream component is set to be loaded as no, the fact that the association path is added between the two service components is shown, but the service association relationship is not actually established between the two service components, and after the white list first page is displayed, the page of the service configuration table is not displayed any more, namely, the number of front-end pages is automatically increased or decreased by setting the yes and the no loaded by the downstream component. For example, the trigger type is changed from 'clicking' to 'hovering', and the trigger operation when the white list home page is switched to the service configuration table page is changed from clicking on the white list home page to hover, namely, the switching action among the front-end pages is automatically changed by setting different trigger types.

As shown in fig. 9, if an association path is added between the on-demand service configuration table 713 and the on-demand configuration list 725, the association options displayed in the service association area 75 include a trigger element, a trigger type, a downstream component loading, a downstream component filling, and the like. Setting the downstream component to load as yes, meaning that a service association relationship is to be added between the service configuration table 713 and the service configuration list 725, setting a trigger element as "search" and a trigger type as "load" when a trigger operation is performed on a front page of the service configuration table, setting a corresponding configuration list background process as "source component" when a load operation is performed in a search box of the front page of the service configuration table, and setting the downstream component to fill as "source component", wherein a secondary association option including a filling type and a filling type as "position selection" appears, and a tertiary association option including a position and a filling mode appears, wherein the position is selected and the filling mode is set as "coverage", and the trigger operation is performed on the front page of the service configuration table according to the selected position, so that the configuration list background process is directly triggered, and the configuration list background process is associated with the front page of the service configuration table in a coverage mode. When the setting operation is different, the corresponding generated service association relationship is also different, for example, when the downstream component is set to be loaded as no, the fact that the association path is added between the two service components is shown, but the service association relationship is not actually established between the two service components, the background flow of the configuration list does not provide logic for the front end page of the service configuration list, namely, the connection between the front end page and the background flow is automatically established and disconnected through setting the yes and the no loaded by the downstream component, and certain unnecessary connections can be selectively disconnected according to the needs under some use scenes, so that the effect of simplifying the operation application is achieved.

After the business association relation is added for all corresponding business components, clicking and storing on a business configuration interface, associating the front-end page corresponding to the business components with the background flow according to the business association relation, forming an organic whole by all parts, generating business operation application corresponding to triggering operation on an SAAS platform according to the stored configurations, and enabling game operators to automatically allocate operation authorities in the operation application to determine which people can use and the using range. By setting the association options in the service association area, operators can set the service association relation among the service components according to the needs, and can also realize various operations such as automatically increasing and decreasing front-end pages, automatically changing switching actions among the front-end pages, automatically establishing and disconnecting connection between the front-end pages and background processes when not communicating with developers, namely, on the premise that only one tree structure is established in the service configuration area, different operation applications can be generated according to the different setting operations of the association options, so that the autonomy and flexibility of constructing the operation applications are greatly improved, and the personalized requirements of operation are met.

Before the SAAS platform builds the operation application, the SAAS platform provides an SDK (software development kit) for the game, a game developer imports the SDK into the game project, the game can pull up the SDK after entering the initialization, the SDK can be displayed in a presentation mode of temporarily covering a game panel, and can interact with game data at the bottom layer of the game through an interface or interact with the game data stored in other systems in a way of independently writing communication. After the operating application is built, some configurations by the game operator in the operating application will slide into the SDK and an interface is rendered in the game by the SDK to enable association between the operating application and the game.

As shown in fig. 10, after a service is generated on the SAAS platform, the service is directly entered, a displayed data source may be seen on a front page displayed, for example, a white list page is selected after a general white list first page is entered, when one or some data sources in the page need to be viewed, a selection operation is performed in the query area 81, for example, an application type, an application state, a region to which a game belongs, a platform to which the game belongs, a region to which the game belongs, and the like may be selected, then a click search is performed, a background process corresponding to the white list page is started based on the click operation, a search of the data source is performed based on the selected condition, then a data source list meeting the selection conditions is displayed in the data source display area 82, each piece of information in the data source list includes a task ID, an application name, a type, a size, creation information, a state, update information, and the like, then an operator can select a data source required by himself or herself, and click the data source to obtain further information.

Through the seven steps, after the data source is created based on the service requirement, the service composition data and the service components are generated by executing the selection operation on the service composition selection interface, the corresponding service is generated by executing the triggering operation, the configuration operation, the association path adding operation and the setting operation on the service configuration interface, so that an operator can quickly generate a new operation application by directly operating on the interface, and the operator can directly and independently operate the whole process of constructing the operation application without communicating with the game development and system development personnel back and forth, thereby greatly reducing the labor cost, reducing the steps of constructing the operation application, and having shorter period of the whole process and being simple and easy to operate. In addition, by setting the association options in the service association area, operators can set the service association relation among the service components according to the needs, and various operations such as automatically increasing and decreasing front-end pages, automatically changing switching actions among the front-end pages, automatically establishing and disconnecting connection between the front-end pages and background flows can be realized when the operators do not communicate with developers, so that the personalized requirements of the operation are met.

As shown in fig. 11, in the service management method of the present application, an operator firstly sends a request for refining characteristics to a game, the game returns all the characteristics, then the operator generates an operation requirement according to the characteristics, based on the requirement, sends a request for arranging a data source to an SAAS platform, then sequentially performs data source configuration, front-end page configuration and background flow configuration on the SAAS platform, builds an operation application after associating the front-end page with the background flow, and provides the operation application to a tester, the tester returns a test result to the operator after testing, and if the test result is passed, the operator can normally use the operation system. Compared with the prior art, operators can directly correlate between the front-end page and the background flow in a dragging mode on the SAAS platform after having operation demands, so that the required operation application can be quickly constructed, the need of writing demand documents for repeated communication and development of game developers and system developers is avoided, and operators who do not understand the development can also quickly generate the required operation application.

Fig. 12 is a second flowchart of a service management method provided in an embodiment of the present application, please refer to fig. 12, the service management method includes the following steps:

901: the first user terminal collates templates.

The first user terminal is a terminal used by any staff with SAAS platform access authority, the staff is usually a game operator, and the operator sorts all front-end pages and background processes in the current industry on the first user terminal, generates a preset front-end page template and a preset background process template, and uploads the front-end page template and the preset background process template to the server.

902: the server stores templates.

The server stores all templates uploaded by the first user terminal in a system where the SAAS platform is located, and when other authorized users access the SAAS platform, the templates can be obtained from the SAAS platform.

903: the second user terminal obtains game characteristics from the game.

The second user terminal is the terminal used by the game operator, and can be the same as or different from the first user terminal, when the game operator wants to construct an operation application, the current game characteristic of the game needs to be acquired first, and the game characteristic comprises parameters such as playing method of the game, motivation mechanism of the game, activity of the game and the like.

904: the second user terminal refines the traffic demand.

Based on the current game characteristics, operators of the second user terminal perform comparative analysis with the expected targets to extract service requirements, wherein the service requirements refer to what operation application needs to be constructed to achieve a certain operation target such as increasing the charge rate of players, increasing the number of players, increasing the game duration of the players and the like under the current game characteristics.

905: and the second user terminal displays a service data selection interface.

When it is clear what kind of service is to be constructed, the second user terminal needs to acquire the service data related to the service first, and the selection of the service data is performed on the service data selection interface displayed by the second user terminal.

906: the second user terminal receives a connection identification selection operation.

The service data is stored in different types of locations, such as a database of a system where the SAAS platform is located, such as a mysql database or a redis database, and the like, and also can be stored in other systems, so that a connection identifier corresponding to a storage type needs to be selected first, then the service data is acquired from a storage address corresponding to the connection identifier, after the corresponding connection identifier is selected, an operator selects different data calling forms according to different connection identifiers, and further selects or inputs a communication protocol or a database address corresponding to the connection identifier, and the like.

907: the second user terminal obtains service data from the server.

And the second user terminal sends the selected content to the server, so that the service data corresponding to the connection identifier can be obtained from the server.

908: the second user terminal receives the field selection operation.

Because the data volume of the acquired service data is large, the service data does not need to be displayed completely, after the service data is acquired, operators receive field selection operation at a service data selection interface, select part of the service data to be displayed as display fields, and display the display fields in the form of the fields, so that the display effect is more visual.

909: the second user terminal sends a data source creation request to the server.

After the presentation field is obtained, the second user terminal sends a data source creation request to the server requesting creation of the data source.

910: the server creates a data source.

And the server creates a data source corresponding to the service according to the request sent by the second user terminal and various selection contents on the service data selection interface.

911: and the second user terminal displays a service composition selection interface.

After the creation of the data source is completed, displaying a service composition interface, and selecting a service composition template by an operator on a service composition selection interface of the SAAS platform, wherein the service composition selection interface comprises a front-end page selection interface and a background flow selection interface, and the service composition template comprises a front-end page template and a background flow template.

912: the second user terminal receives the selection operation.

The second user terminal receives the selection operation, which may specifically include a front-end page selection operation and a background flow selection operation. An operator firstly selects a front-end page template on a front-end page selection interface of an SAAS platform, when the front-end page template preset in the SAAS platform can meet the requirements, the front-end page template required is directly determined from the front-end page template preset, and when the requirements cannot be met, a self-defined front-end page template is generated in a dragging layout and control mode. Then, operators select a background flow template on a background flow selection interface of the SAAS platform, when the preset background flow template in the SAAS platform can meet the requirements, the required background flow template is directly determined from the preset background flow template, and when the requirements cannot be met, the self-defined background flow template is generated by configuring and connecting a processor.

913: the second user terminal obtains the data source from the server.

After the front-end page template is determined, the data sources need to be displayed in the corresponding front-end page, and after the background flow template is determined, the corresponding data sources needing to be processed need to be selected, so that the second user terminal obtains the data sources created in the previous step from the server.

914: the second user terminal associates a data source with a service composition template.

The operator selects a front-end page template and a data source to be displayed on a front-end page selection interface displayed by the second user terminal, associates the front-end page template with the data source to be displayed, selects a background flow template and the data source to be processed on a background flow selection interface, associates the front-end page template with the data source to be processed, establishes a mapping relation for the selected front-end page template and the data source to be displayed on the background of the SAAS platform after the operator performs association operation on the interface, enables the front-end page to display the selected data source, enables the background flow to process the selected data source, and generates front-end page data and background flow data according to association results after association.

915: the second user terminal sends a request for generating a service component to the server.

After generating the front-end page data and the background flow data, the second user terminal sends a request for generating the service components to the server, and the request generates the front-end service components corresponding to the front-end page data and the background service components corresponding to the background flow data.

916: the server generates a business component.

After receiving the request, the server generates a corresponding front-end page component for each front-end page data, the page component identifier of the front-end page component may be the same as the page identifier, the server generates a corresponding background service component for each background process data, and the page component identifier of the background service component may be the same as the process identifier, where each service component is a visual component that may be displayed on the second user terminal interface.

917: and the second user terminal displays a service configuration interface.

The second user terminal displays a service configuration interface, the service configuration interface comprises a component display area, a service configuration area and a service association area, when the service configuration interface is initially entered, a list of each service is displayed in the component display area, each service in the list displays a respective service identifier, specifically, a service name and/or a service number, and the service configuration area and the service association area are blank areas.

918: and the second user terminal receives the triggering operation and displays the candidate service components.

The operator executes a triggering operation in the component display area, specifically, may click or touch the service identifier of a certain service in the service list, where the service corresponding to the triggering operation displays the corresponding sub-list, and other services still only display the service identifier. And displaying candidate service components corresponding to the service in the sub-list, wherein the candidate service components comprise front-end service components and background service components corresponding to the service.

919: and the second user terminal executes configuration operation and adds the service components to the service configuration area.

The operator performs the configuration operation in the service configuration area, specifically, selecting a certain candidate service component in the component display area and dragging the candidate service component to the service configuration area, or selecting an inserted component in the service configuration area, and then selecting a certain candidate service component in the component display area, and then the server receives the configuration operation through the service configuration area. And in the initial state, blank display is arranged in the service configuration area, and when the server receives the configuration operation, candidate service components corresponding to the configuration operation in the component display area are added into the service configuration area. For the same service, front-end service components and background service components are displayed in a sub-list, templates corresponding to the two components are associated with a data source, but the front end and the background are still independent, so that when configuration operation is received, the front-end service components corresponding to the sub-list displayed by the service are required to be added to a service configuration area, and then the background service components corresponding to each front-end service component are determined according to the corresponding relation between the front-end page corresponding to each added front-end service component and the background process, and the background service components are also required to be added to the service configuration area.

920: and the second user terminal executes the association path adding operation and displays association options.

The operator executes an association path adding operation in the service configuration area, wherein the association path adding operation is specifically to add an arrow-carrying line between an upper service component and a lower service component which are associated with each other, the line represents an association path between the two service components, the arrow direction represents the direction of the association path, the service component corresponding to the starting point of the association path is a source service component, the service component corresponding to the direction point is a downstream service component, and after the association path is added, association options between the source service component and the downstream service component corresponding to the association path are displayed in the service association area.

921: the second user terminal receives the setting operation.

After the association options are displayed in the service association area, an operator performs setting operation on each association option, and service association relations generated by different setting operations are different.

922: and the second user terminal sends a service association relation adding request to the server.

After the setting is completed, the second user terminal sends a service association relation adding request to the server, and the request is used for adding the association relation between the source service component and the downstream service component corresponding to the association path.

923: the server adds a business association relationship between the business components.

And the server establishes an association relation between the corresponding service components according to the association path and the specific setting content of the association option, and then establishes a mapping relation between front-end pages or background processes corresponding to the two service components added with the service association relation. When two service components which are mutually related are front-end service components, the front-end page corresponding to the front-end service component is indicated to be a sub-page of the front-end service component, namely, the front-end page is displayed first after the operation application is entered, and the back-end page, namely, the sub-page, corresponding to a control is displayed after the control is triggered on the front-end page. When one of the two service components is a front-end service component and the other is a background service component, the corresponding flow of the background service component is used for starting after the front-end page corresponding to the front-end service component receives the trigger of the association event so as to perform corresponding data processing.

924: the server generates a service.

After the association relation is added for all the corresponding service components, clicking and storing on the service configuration interface, associating the front-end page corresponding to the service components with the background flow according to the association relation, forming an organic whole by each part, generating a service corresponding to triggering operation, namely operation application, on the SAAS platform by the server according to the stored configurations, and automatically distributing operation authorities in the operation application by game operators to determine which personnel can be used and the using range.

The method and the system take the construction of the operation application for the second user terminal as an example, and the method and the system enable operators to generate a new operation application through selection operation, triggering operation, configuration operation, association path adding operation and setting operation, and do not need to communicate with game development and system developers back and forth, so that labor cost is greatly reduced, steps for constructing the operation application are reduced, and the whole process period is short and simple and easy to operate.

Taking service demand as an example to construct a service capable of improving the charging rate of a player, after the construction of an operation application is completed, entering the operation application, selecting a front page for displaying charging data of a user, acquiring the current charging number of the player, charging amount, charging rate and other data sources, selecting a front page for displaying property purchasing data, acquiring the charging amount of the player and purchasing the data sources such as the duty ratio of each property, after analysis, finding that a large proportion of players can choose to purchase one or a plurality of properties after charging, indicating that if the players return to a certain number of hot properties after charging, the charging rate of the players can be improved to a certain extent, therefore, an operator can add a recharging rebate activity on the operation platform, the activity slides down into the SDK interface of the X game and an activity interface is rendered in the game by the SDK, as shown in fig. 13, when a player enters the X game or clicks an 'activity' icon after entering the game, the player can play the daily recharging rebate activity on the game interface 131 or pops up the activity interface 132, recharging rebate activities of different gears are set in the activity, such as the accumulated recharging 20 rebate prop X1, the accumulated recharging 100 rebate prop X6, the accumulated recharging 300 rebate prop X25, the accumulated recharging 500 rebate prop X50 and the like, and an 'immediate recharging' button is displayed on each gear recharging activity, so that the player can carry out recharging activities of corresponding gears and obtain the rebate prop of the gear. Through the above process, after the operator obtains the game characteristics, determining the service requirement to construct a service capable of improving the charge rate of the player, based on the service requirement, obtaining service data related to the charge rate of the player, creating a data source according to the service data, displaying the data source on a corresponding front-end page under the processing of a background process after the operation application is constructed, analyzing the data, determining that a recharging rebate activity needs to be added, adding the activity on an operation platform and sliding down to the game, and finally enabling the player to enter the activity in the game to perform corresponding recharging operation so as to improve the charge rate of the player.

On the basis of the method described in the foregoing embodiments, this embodiment will be further described from the perspective of a service management device, and referring to fig. 14, fig. 14 specifically describes a service management device provided in this embodiment, which may include:

a creating module 101, configured to obtain a service requirement, and create a data source based on the service requirement;

the generating module 102 is configured to display a service composition selection interface, receive a selection operation through the service composition selection interface, generate service composition data according to the data source and a service composition template corresponding to the selection operation, and generate a corresponding service component for the service composition data;

a first display module 103, configured to display a service configuration interface, where the service configuration interface includes a component display area, a service configuration area, and a service association area;

a second display module 104, configured to receive a triggering operation through the component display area, and display, in the component display area, a candidate service component corresponding to a service of the triggering operation;

a first adding module 105, configured to receive a configuration operation through the service configuration area, and add a service component corresponding to the configuration operation to the service configuration area;

A third display module 106, configured to receive, through the service configuration area, an association path adding operation, where the association path adding operation includes adding an association path between corresponding service components, determining a direction for the association path, and displaying, according to the association path adding operation, association options between a source service component and a downstream service component corresponding to the association path in the service association area;

and the second adding module 107 is configured to receive, through the service association area, a setting operation for the association option, and add a service association relationship generated according to the setting operation to a source service component and a downstream service component corresponding to the association path, so as to generate a service corresponding to the triggering operation.

In one embodiment, the third display module 106 includes:

In one embodiment, the creation module 101 includes:

In one embodiment, the generation module 102 includes:

In one embodiment, the first generation unit includes:

In one embodiment, the first generation unit further comprises:

In one embodiment, the second generating unit includes:

In one embodiment, the second generating unit further comprises:

And the fourth association unit is used for associating the data source with the self-defined background flow template to generate the background flow number.

Compared with the prior art, the message management device provided by the application is characterized in that after a data source is created based on service requirements, service composition data and service components are generated by executing selection operation on the service composition selection interface, corresponding services are generated by executing triggering operation, configuration operation, association path adding operation and setting operation on the service configuration interface, so that operators can quickly generate a new operation application by directly operating on the interface, and the operators can directly and independently operate the whole process of constructing the operation application without communicating with game development and system development personnel back and forth, thereby greatly reducing labor cost, reducing steps of constructing the operation application, and having shorter whole process period and simplicity and easiness in operation. In addition, by setting the association options in the service association area, operators can set the service association relation among the service components according to the needs, and various operations such as automatically increasing and decreasing front-end pages, automatically changing switching actions among the front-end pages, automatically establishing and disconnecting connection between the front-end pages and background flows can be realized when the operators do not communicate with developers, so that the personalized requirements of the operation are met.

Correspondingly, the embodiment of the application further provides a server, as shown in fig. 15, which shows a schematic structural diagram of the server according to the embodiment of the application, specifically:

the server may include one or more processors 1101 of a processing core, memory 1102 of one or more computer readable storage media, a power supply 1103, and an input submodule 1104, among other components. Those skilled in the art will appreciate that the server architecture shown in fig. 15 is not limiting of the server and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. Wherein:

the processor 1101 is a control center of the server, and connects various parts of the entire server using various interfaces and lines, and performs various functions of the server and processes data by running or executing software programs and/or modules stored in the memory 1102, and calling data stored in the memory 1102, thereby performing overall monitoring of the server. Optionally, the processor 1101 may include one or more processing cores; preferably, the processor 1101 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., and a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1101.

The memory 1102 may be used to store software programs and modules, and the processor 1101 executes various functional applications and data processing by executing the software programs and modules stored in the memory 1102. The memory 1102 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the server, etc. In addition, memory 1102 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 1102 may also include a memory controller to provide the processor 1101 with access to the memory 1102.

The server also includes a power supply 1103 that provides power to the various components, and the power supply 1103 may be logically connected to the processor 1101 by a power management system, such that the functions of managing charging, discharging, and power consumption are performed by the power management system. The power supply 1103 may also include one or more of any of a direct current or alternating current power supply, recharging system, power failure detection circuit, power converter or inverter, power status indicator, etc.

The server may also include an input submodule 1104, which input submodule 1104 may be used to receive entered numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

Although not shown, the server may further include a display sub-module, etc., which will not be described herein. In particular, in this embodiment, the processor 1101 in the server loads executable files corresponding to the processes of one or more application programs into the memory 1102 according to the following instructions, and the processor 1101 executes the application programs stored in the memory 1102, so as to implement various functions as follows:

acquiring a service demand, and creating a data source based on the service demand; displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data; the method comprises the steps of displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area; receiving triggering operation through the component display area, and displaying candidate service components of the service corresponding to the triggering operation in the component display area; receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area; receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation; and receiving setting operation of the association options through the service association area, and adding the service association relation generated according to the setting operation to a source service component and a downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation.

In the foregoing embodiments, the descriptions of the embodiments are focused on, and the portions of an embodiment that are not described in detail in the foregoing embodiments may be referred to in the foregoing detailed description, which is not repeated herein.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.

To this end, embodiments of the present application provide a computer readable storage medium having stored therein a plurality of instructions capable of being loaded by a processor to perform the following functions:

The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.

Wherein the computer-readable storage medium may comprise: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.

Since the instructions stored in the computer readable storage medium may perform the steps in any of the methods provided in the embodiments of the present application, the beneficial effects that any of the methods provided in the embodiments of the present application can be achieved are detailed in the previous embodiments, and are not repeated herein.

The foregoing describes in detail a service management method and apparatus provided by the embodiments of the present application, and specific examples are applied to illustrate the principles and embodiments of the present application, where the foregoing description of the embodiments is only for helping to understand the method and core idea of the present application; meanwhile, those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, and the present description should not be construed as limiting the present application in view of the above.

Claims

1. A method of traffic management, comprising:

2. The service management method according to claim 1, wherein the step of displaying, in the service association area, association options between the source service component and the downstream service component corresponding to the association path according to the association path adding operation includes:

according to the association path adding operation, determining a service component corresponding to the association path starting point as a source service component, and determining a service component corresponding to the association path pointing point as a downstream service component;

and displaying association options between the source service component and the downstream service component in the service association area, wherein the association options comprise a service association relation establishment option, a downstream service component trigger type option and a downstream service component filling position option.

3. The service management method according to claim 1, further comprising, after the step of receiving an associated path adding operation through the service configuration area:

And receiving an association identifier adding operation through the service configuration area, wherein the association identifier adding operation comprises adding an association identifier corresponding to a downstream service component on the association path based on the downstream service component pointed by the association path.

4. The business management method of claim 1, wherein the step of creating a data source based on the business requirements comprises:

acquiring a storage type of service data based on the service requirement;

receiving a connection identifier selection operation through a service data selection interface, determining a connection identifier corresponding to the storage type according to the connection identifier selection operation, and acquiring the service data from a storage address corresponding to the connection identifier;

and determining a display field according to field selection operation on the service data, and creating a data source according to the display field.

5. The service management method according to claim 1, wherein the step of receiving a selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data, comprises:

Receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, and generating a corresponding front-end service component for the front-end page data;

receiving a background flow selection operation through a background flow selection interface, generating background flow data according to a background flow template corresponding to the background flow selection operation and the data source, and generating a corresponding background service component for the background flow data.

6. The service management method according to claim 5, wherein the step of receiving a front-end page selection operation through a front-end page selection interface, and generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, comprises:

receiving a first preset template selection operation through a front-end page selection interface;

displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving a first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation;

And associating the data source with the target preset front-end page template to generate front-end page data.

7. The service management method according to claim 5, wherein the step of receiving a front-end page selection operation through a front-end page selection interface, and generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, comprises:

receiving a first custom template selection operation through a front-end page selection interface;

displaying a custom front-end page template generating interface corresponding to the first custom template selecting operation, receiving layout selecting operation and control selecting operation through the custom front-end page template generating interface, determining a required layout according to the layout selecting operation, determining a required control according to the control selecting operation, and generating a custom front-end page template according to the layout and the control;

and associating the data source with the custom front-end page template to generate front-end page data.

8. The business management method of claim 5, wherein receiving a background process selection operation through a background process selection interface, generating background process data according to a background process template corresponding to the background process selection operation and the data source, comprises:

Receiving a second preset template selection operation through a background flow selection interface;

displaying a preset background flow template selection interface corresponding to the second preset template selection operation, receiving the second template selection operation through the preset background flow template selection interface, and determining a target preset background flow template according to the second template selection operation;

and associating the data source with the target preset background flow template to generate background flow data.

9. The business management method of claim 5, wherein receiving a background process selection operation through a background process selection interface, generating background process data according to a background process template corresponding to the background process selection operation and the data source, comprises:

receiving a second custom template selection operation through a background flow selection interface;

displaying a custom background flow template generating interface corresponding to the second custom template selecting operation, receiving a processor configuration operation and a processor connecting operation through the custom background flow template generating interface, determining configuration parameters of a processor according to the processor configuration operation, and generating a custom background flow template according to the processor connecting operation;

And associating the data source with the self-defined background flow template to generate background flow data.

10. A traffic management device, comprising: