CN112232751A

CN112232751A - Service data processing method, device, system, computer equipment and storage medium

Info

Publication number: CN112232751A
Application number: CN202010916173.3A
Authority: CN
Inventors: 谭造乐; 杨光宇
Original assignee: Weimin Insurance Agency Co Ltd
Current assignee: Weimin Insurance Agency Co Ltd
Priority date: 2020-09-03
Filing date: 2020-09-03
Publication date: 2021-01-15

Abstract

The application relates to a business data processing method, a business data processing device, a business data processing system, a computer device and a storage medium. The method comprises the following steps: receiving a current service login request, wherein the current service login request carries a current service identifier and a current service type; calling a target service domain service corresponding to the current service type according to the current service login request, and acquiring current service content corresponding to the current service identifier through the target service domain service; receiving a service content execution request corresponding to the current service content, responding to the service content execution request through a target service domain service, and acquiring a current service content execution state corresponding to the current service content; and calling the service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state and performs target service resource distribution according to the target service resource information. The scheme provided by the application can improve the processing efficiency of the activity business.

Description

Service data processing method, device, system, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, a computer device, and a storage medium for processing service data.

Background

At present, different activity services compile different service codes, each service code is placed in a background server, and the service codes corresponding to different activity services are coupled together, wherein different activity services may be of the same activity type, different activity services of the same activity type have different service codes, once a certain activity service needs to be iterated or changed, a set of service codes needs to be redeveloped, the development cycle is long, the activity service cannot be quickly online, the application of subsequent activity services is influenced, and the processing efficiency of the activity service is low.

Disclosure of Invention

In order to solve the above technical problem, the present application provides a service data processing method, an apparatus, a system, a computer device, and a storage medium, which can improve the processing efficiency of an active service.

The application provides a service data processing method, which comprises the following steps:

receiving a current service login request, wherein the current service login request carries a current service identifier and a current service type;

calling a target service domain service corresponding to the current service type according to the current service login request, and acquiring current service content corresponding to the current service identifier through the target service domain service;

receiving a service content execution request corresponding to the current service content, responding to the service content execution request through a target service domain service, and acquiring a current service content execution state corresponding to the current service content;

calling the service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state and performs target service resource distribution according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

The application provides a service data processing device, including:

a service login request acquisition module, configured to receive a current service login request, where the current service login request carries a current service identifier and a current service type;

the target service domain calling module is used for calling a target service domain service corresponding to the current service type according to the current service login request and acquiring the current service content corresponding to the current service identifier through the target service domain service;

a service content execution request acquisition module, configured to receive a service content execution request corresponding to current service content, and respond to the service content execution request through a target service domain service to acquire a current service content execution state corresponding to the current service content;

the service core domain calling module is used for calling the service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state and performs target service resource distribution according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

A business data processing system, the system comprising:

the service background server is used for receiving a current service login request, carrying a current service identifier and a current service type, and calling a target service domain server corresponding to the current service type calling according to the current service login request;

the target service domain server is used for acquiring the current service content corresponding to the current service identifier and returning the current service content to the service background server;

the service background server is also used for acquiring a service content execution request corresponding to the current service content and returning the service content execution request to the service background server;

the service background server is also used for sending the service content execution request to the target service domain server;

the target service domain server is also used for acquiring the current service content execution state corresponding to the service content execution request and returning the current service content execution state to the service background server;

the service background server is also used for calling service core domain service according to the current service content execution state;

and the service core domain server is used for acquiring corresponding target service resource information according to the current service content execution state and issuing target service resources according to the target service resource information.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method when executing the computer program.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.

The service data processing method, the device, the system, the computer equipment and the storage medium receive a current service login request, wherein the current service login request carries a current service identifier and a current service type; calling a target service domain service corresponding to the current service type according to the current service login request, and acquiring current service content corresponding to the current service identifier through the target service domain service; receiving a service content execution request corresponding to the current service content, responding to the service content execution request through a target service domain service, and acquiring a current service content execution state corresponding to the current service content; calling the service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state and performs target service resource distribution according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

Therefore, once a certain activity service needs to be iterated or changed, as long as the activity service type is not changed, the acquisition of service content and the distribution of service resources can be respectively realized through the target service domain service and the service core domain service without redeveloping a set of new service codes, thereby avoiding the long development period, influencing the application of subsequent activity services and improving the processing efficiency of the activity services. Moreover, the acquisition of the service content and the distribution of the service resources are processed by the corresponding domain services independently, the data of each domain service are independent and do not interfere with each other, and the influence of a plurality of active services due to the change of a certain active service can be avoided.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

FIG. 1 is a diagram of an application environment of a method for processing service data in one embodiment;

FIG. 2 is a flow chart illustrating a method for processing service data according to an embodiment;

FIG. 3 is a flow chart illustrating a method for processing service data according to an embodiment;

FIG. 4 is a flowchart illustrating a current service content obtaining step in one embodiment;

FIG. 5 is a flowchart illustrating the current service content execution state determination step in one embodiment;

FIG. 6 is a flow chart illustrating a method for processing service data according to an embodiment;

FIG. 7 is a timing diagram of a method of traffic data processing in one embodiment;

FIG. 8 is an interface diagram of an activity information configuration interface in one embodiment;

FIG. 9 is an interface diagram of a task information configuration interface in one embodiment;

FIG. 10 is a schematic interface diagram of a prize information configuration interface in one embodiment;

FIG. 11 is a block diagram of a business data processing apparatus in one embodiment;

FIG. 12 is a block diagram of a business data processing system in one embodiment;

FIG. 13 is a block diagram of the configuration of the personalization module access in one embodiment;

FIG. 14 is a system architecture diagram of a business data processing system in one embodiment;

FIG. 15 is a diagram showing an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is an application environment diagram of a service data processing method in an embodiment. Referring to fig. 1, the service data processing method is applied to a service data processing system. The service data processing system includes a terminal 110, a service background server 120, a target service domain server 130 and a service core domain server 140. The terminal 110 is connected to the service backend server 120 through a network, and the service backend server 120 is connected to the target service domain server 130 and the service core domain server 140 through a network, wherein the target service domain server 130 is determined from the candidate service domain server cluster. The terminal 110 may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The service background server 120, the target service domain server 130 and the service core domain server 140 may be implemented by independent servers or a server cluster composed of a plurality of servers.

Specifically, after acquiring a current service login request, the terminal 110 sends the current service login request to the service backend server 120 through a network connection, wherein the current service login request carries a current service identifier and a current service type, after receiving the current service login request, the service backend server 120 calls a target service domain server 130 corresponding to the current service type according to the current service login request, acquires current service content corresponding to the current service identifier through the target service domain server 130, receives a service content execution request corresponding to the current service content sent by the terminal 110, responds to the service content execution request through the target service domain server 130, acquires a current service content execution state corresponding to the current service content, calls the service core domain server 140 according to the current service content execution state, so that the service core domain server 140 obtains the corresponding target service resource information according to the current service content execution state, and performs target service resource distribution according to the target service resource information.

As shown in fig. 2, in one embodiment, a method for processing service data is provided. The embodiment is mainly illustrated by applying the method to the service backend server 120 in fig. 1. Referring to fig. 2, the service data processing method specifically includes the following steps:

step S201, receiving a current service login request, where the current service login request carries a current service identifier and a current service type.

Here, the current service registration request is used to request to register a current service, the current service may be a currently running service activity, and the service activity is a service-related activity, for example, the service activity may be a marketing activity service. The current service login request can be sent by the terminal to the service background server, the terminal can be provided with a current service activity login control, and the current service activity login request is triggered and generated by operating the current service activity login control, wherein the operation can be but is not limited to click operation, voice operation, timing event and the like. The current business activity login request can also be generated by performing operation triggering on the current business activity login link. The current business activity login link is a form of the current business activity, and a current business login request can be generated by operating and triggering the current business activity login link.

In another embodiment, the service background server may trigger generation of the current service login request by itself, may be that a current service activity login control is provided in the service background server, and the current service activity login control is operated to trigger generation of the current service login request, or may also be that a timing event is provided, and when the timing event is satisfied, the generation of the current service login request may be triggered.

The current service login request carries a current service identifier and a current service type, wherein the current service identifier is used for uniquely identifying the current service activity, different service activities correspond to different service identifiers, and the corresponding service activities can be determined through the service identifiers. The current service type refers to a service activity type corresponding to the current service activity, the service activity type is a category of the current service activity, and service activities of the same service activity type have a common point, wherein different service activities may correspond to the same service activity type, different service activities may also correspond to different service activity types, and the service activity type may be, for example, a task-type activity, a fission-type activity, a voting-type activity, and the like.

Step S202, according to the current service login request, calling the target service domain service corresponding to the current service type, and through the target service domain service, obtaining the current service content corresponding to the current service identifier.

The service domain service is used for service content management, comprises services of acquiring a service content list, obtaining service content, finishing service content and the like, and is an abstracted service activity function module with complete and independent functions. Wherein the service domain service may be a service deployed on a separate server. Wherein, different service types correspond to different service domain services, the matched service domain service can be determined from the candidate service domain services through the service type, and the target service domain service is the service domain service matched with the current service type in the current service login request. For example, if the service type is a task type activity, a task domain service needs to be invoked, and if the service type is a fission type activity, a service of a help domain needs to be invoked, that is, different service types invoke different service domain services, and the same service type invokes the same service domain service.

The service domain service only concerns related logic in its domain, i.e. general logic related to the service activity, for example, acquiring a service content list, getting service content, completing the service content, acquiring an execution state of a user under a certain service activity, whether the service content is finished, etc., but is not related to the specific related logic of the service content, and the service activity can use the capability provided by the service domain service to realize the service logic of the service activity itself. The business activity related logic comprises logic such as whether business activity is finished or not, business activity resource distribution and the like.

Specifically, after receiving the current service login request, since different service types correspond to different service domain services, the service domain services are used for service content management, and corresponding service contents need to be acquired through the service domain services, a target service domain service corresponding to the current service type can be called according to the current service type in the current service login request, and the target service domain service acquires the matched current service contents according to the current service identifier. The current service content is content related to the current service corresponding to the current service identifier, and may be, for example, a current service content list or the like.

Step S203, receiving a service content execution request corresponding to the current service content, responding to the service content execution request through the target service domain service, and acquiring a current service content execution state corresponding to the current service content.

The service content execution request is used to inform the execution situation of the current service content, and the execution situation of the current service content may be determined according to the service content execution request, and the execution situation of the current service content may be, but is not limited to, a current service content execution completion state and a current service content execution incomplete state. And the execution condition of the current service content can be determined only by checking through the target service domain service.

The current service content execution request can be sent by the terminal to the service background server, the terminal can be provided with a relevant control for judging whether the execution of the current service content is finished, the control is operated to trigger and generate the current service content execution request, and the terminal sends the current service content execution request to the service background server. Wherein the operation may be, but is not limited to, a click operation, a voice operation, a timed event, and the like.

Specifically, after acquiring the current service content corresponding to the current service identifier, the service background server may return the current service content to the user terminal, after receiving the current service content, the user terminal displays the current service content, a service content execution control is arranged in a display interface of the current service content, an operation on the service content execution control is acquired, and a service content execution request is generated according to the operation trigger, where the service content execution request carries the current service identifier and current service content attribute information, and the current service content attribute information is attribute information related to current service content execution, including but not limited to a completion condition of the current service content, attribute information of the current service content, an execution state of the current service content, and the like.

Further, after the user terminal generates a service content execution request, the service content execution request is sent to the service background server, the service background server receives the service content execution request, and then sends the service content execution request to the target service domain service, and the current service content execution state corresponding to the service content execution request is determined through the target service domain service, specifically, the target service domain service obtains corresponding target service content attribute information according to the current service identifier, where the target service content attribute information is standard service content attribute information corresponding to the current service identifier, the standard service content attribute information is information configured in advance according to service requirements, actual application scenarios or product requirements, and it can be determined whether the service content execution request corresponds to the service background server according to the current service content attribute information and the target service content attribute information being the same or not For example, when the current service content attribute information is the same as the target service content attribute information, it may be determined that the current service content execution state is the current service content execution completion state, and otherwise, when the current service content attribute information is different from the target service content attribute information, it may be determined that the current service content execution state is the current service content execution completion state.

Step S204, calling the service core domain service according to the current service content execution state, so that the service core domain service acquires corresponding target service resource information according to the current service content execution state, and issuing target service resources according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

The service core domain service is used for service resource distribution, the service core domain service is also an abstracted functional module with a complete and independent function, the service core domain service is used for service resource distribution, the service resource comprises at least one sub-service resource, for example, the sub-service resource can be fund, different sub-service resources can be sent through different service core sub-domain services, that is, the service core domain service can comprise a plurality of service core sub-domain services, and corresponding service sub-resources are sent through each service core sub-domain service. Similarly, the service core domain server may be a service deployed on a separate server, and the target service domain service and the service core domain service are independent from each other and do not interfere with each other.

Specifically, after the current service content execution state is obtained, the service core domain service may be invoked according to the current service content execution state, where all service resource transmissions are performed by the service core domain service for service resource distribution, regardless of the current service content execution state corresponding to the current service content of any service type, i.e., the service core domain service is independent of the service type. The current service content execution state can be a current service content execution completion state and a current service content execution unfinished state, and when the current service content execution state is the current service content execution completion state, the service core domain service can be called, and acquires corresponding target service resource information according to the current service content execution state, and performs target service resource distribution according to the target service resource information. The different target service resource information corresponds to different service core subdomain services, the corresponding service core subdomain service can be called through the target service resource information, and the target service resource corresponding to the target service resource information is issued through the service core subdomain service, for example, the target service resource corresponding to the target service resource information is sent to the corresponding user account.

The service data processing method comprises the following steps: receiving a current service login request, wherein the current service login request carries a current service identifier and a current service type; calling a target service domain service corresponding to the current service type according to the current service login request, and acquiring current service content corresponding to the current service identifier through the target service domain service; receiving a service content execution request corresponding to the current service content, responding to the service content execution request through a target service domain service, and acquiring a current service content execution state corresponding to the current service content; calling the service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state and performs target service resource distribution according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

In one embodiment, as shown in fig. 3, the service data processing method further includes:

step S301, obtaining each candidate service content configuration information, wherein each candidate service content configuration information comprises a corresponding candidate service type.

Step S302, according to the configuration information of each candidate service content, configuring the candidate service domain service corresponding to the candidate service type, and establishing the relationship between each candidate service type and the corresponding candidate service domain service.

Each candidate service domain service comprises a corresponding candidate service type, and the incidence relation between the candidate service domain service and the corresponding candidate service type can be established in advance through service requirements, application scenes or product requirements. Specifically, the configuration information of each candidate service content may be obtained, where the configuration information of the candidate service content is configuration information related to the candidate service content, different candidate service contents correspond to different configuration information of the candidate service content, and the configuration information of the candidate service content corresponding to the candidate service content may be determined according to service requirements, actual application scenarios, and product requirements. And each candidate service content configuration information comprises a corresponding candidate service type.

Further, the candidate service domain service corresponding to the candidate service type may be configured according to the candidate service content configuration information, specifically, the corresponding candidate service domain service may be determined according to the candidate service type, the candidate service domain service may be configured according to the corresponding candidate service content configuration information, and then, the relationship between each candidate service type and the corresponding candidate service domain service may be established. Therefore, after the relationship between the candidate service type and the corresponding candidate service domain service is established, the target service domain service can be determined and obtained subsequently according to the current service type in the current service login request and the candidate service type corresponding to each candidate service domain service.

Step S303, obtaining the candidate service type matched with the current service type, determining the candidate service domain service corresponding to the matched candidate service type as the target service domain service, and calling.

The service domain service is used for service content management, comprises services of acquiring a service content list, obtaining service content, finishing service content and the like, and is an abstracted service activity function module with complete and independent functions. Wherein the service domain service may be a service deployed on a separate server. The different service types correspond to different service domain services, the matched service domain service can be determined from each candidate service domain service through the service types, each candidate service domain service comprises a corresponding candidate service type, and the incidence relation between the candidate service domain service and the corresponding candidate service type can be established in advance through service requirements, application scenes or product requirements.

And the target service domain service is the service domain service matched with the current service type in the current service login request. For example, if the service type is a task type activity, a task domain service needs to be invoked, and if the service type is a fission type activity, a service of a help domain needs to be invoked, that is, different service types invoke different service domain services, and the same service type invokes the same service domain service. The target service domain service may be determined from each candidate service domain service according to the current service type, specifically, the matched target service domain service is determined according to the current service type and the candidate service type corresponding to each candidate service domain service, for example, the candidate service domain service corresponding to the candidate service domain service having the same current service type may be determined as the target service domain service. And finally, after the target service domain service is determined, the service background server calls the target service domain service according to the current service login request, and then sends the current service login request to the target service domain service.

In one embodiment, as shown in fig. 4, acquiring the current service content corresponding to the current service identifier through the target service domain service includes:

step S501, sending the current service login request to the target service domain service, so that the target service domain service determines the matched current service content from the candidate service contents corresponding to the candidate service content configuration information according to the current service identifier in the current service login request, wherein each candidate service content comprises the corresponding candidate service identifier, and returns the current service content.

Step S502, receiving the current service content.

After the target service domain service is determined, the current service login request is sent to the target service domain service, the target service domain service can determine matched current service content from candidate service content according to a current service identifier in the current service login request, wherein each candidate service content comprises a corresponding candidate service identifier, when the candidate service content is configured, the corresponding candidate service identifier is configured, and the candidate service content and the corresponding candidate service identifier can be configured in advance according to service requirements, actual application scenes, product requirements and the like.

Specifically, the service background server sends the current service login request to the target service domain service, and after receiving the current service login request, the target service domain service determines the matched current service content according to the current service identifier in the current service login request and the candidate service identifiers corresponding to the respective candidate service contents, for example, determines the candidate service content corresponding to the candidate service identifier that is the same as the current service identifier as the current service content, where the current service content is related to the current service corresponding to the current service identifier, and may be, for example, a current service content list or the like. Further, the target service domain service may return the current service content to the service backend server.

In one embodiment, as shown in fig. 5, receiving a service content execution request corresponding to a current service content, and acquiring a current service content execution state corresponding to the service content execution request through a target service domain service includes:

step S601, returning the current service content to the user terminal, so that the user terminal displays the current service content, obtains an operation on a service content execution control in a display interface of the current service content, and generates a service content execution request according to an operation trigger, where the service content execution request carries a current service identifier and current service content attribute information.

Specifically, after receiving the current service content corresponding to the current service identifier, the service background server may return the current service content to the user terminal, and after receiving the current service content, the user terminal displays the current service content, and a service content execution control is arranged in a display interface of the current service content, acquires an operation on the service content execution control, and generates a service content execution request according to the operation trigger, where the service content execution request carries the current service identifier and current service content attribute information, where the current service content attribute information is attribute information related to the current service content execution, including but not limited to a completion condition of the current service content, attribute information of the current service content, and the like.

The operation of the service content execution control set on the display interface of the current service content may be, but is not limited to, a click operation, a voice operation, a timing event, and the like. And finally, the user terminal sends the service content execution request to the service background server.

Step S602, receiving the service content execution request, sending the service content execution request to the target service domain service, so that the target service domain service obtains corresponding target service content attribute information according to the current service identifier in the service content execution request, and determines the current service content execution state corresponding to the service content execution request according to the current service content attribute information and the target service content attribute information.

Specifically, after the user terminal generates a service content execution request, the service content execution request is sent to the service background server, the service background server receives the service content execution request, and then sends the service content execution request to the target service domain service, and the current service content execution state corresponding to the service content execution request is determined by the target service domain service, specifically, the target service domain service obtains corresponding target service content attribute information according to the current service identifier, where the target service content attribute information is standard service content attribute information corresponding to the current service identifier, and can determine the current service content execution state corresponding to the service content execution request according to the current service content attribute information and the target service content attribute information, specifically, whether the current service content attribute information matches with the target service content attribute information is compared, if the attribute information of the current service content is matched with the attribute information of the target service content, the execution state of the current service content can be determined to be the execution completion state of the current service content, otherwise, if the attribute information of the current service content is not matched with the attribute information of the target service content, the execution state of the current service content can be determined to be the execution completion state of the current service content.

In one embodiment, the service core domain service includes a service resource management domain service and a service resource distribution domain service, and the service core domain service is called according to the current service content execution state, so that the service core domain service acquires corresponding target service resource information according to the current service content execution state, and performs target service resource distribution according to the target service resource information, including: and when the current service content execution state is the current service execution completion state, calling the service resource management domain service to enable the service resource management domain service to acquire corresponding target service resource information according to the current service identifier, calling the corresponding service resource distribution domain service according to the target service resource information, wherein different target service resource information correspond to different service resource distribution domain services, so that the service resource distribution domain service determines a target user account according to the current service identifier and distributes the target service resource corresponding to the target service resource information to the target user account.

The service core domain service is used for service resource distribution, the service core domain service is also an abstracted functional module with a complete and independent function, the service core domain service is used for service resource distribution, the service resource comprises at least one sub-service resource, for example, the sub-service resource can be fund, different sub-service resources can be sent through different service core sub-domain services, that is, the service core domain service can comprise a plurality of service core sub-domain services, and corresponding service sub-resources are sent through each service core sub-domain service. Wherein, likewise, the service core domain server may be a service deployed on a separate server.

The service resource management domain service can be used for managing, acquiring and the like service resources, and the service resource information can be acquired through the service resource management domain service.

Specifically, after the current service content execution state is obtained, when the current service content execution state is the current service execution completion state, it is indicated that the current service content is completed, and resource distribution can be performed, therefore, when the current service content execution state is the current service execution completion state, a service resource management domain service is called, the service resource management domain service acquires corresponding target service resource information according to the current service identifier, wherein different service resource information may correspond to different service resource distribution domain services, the corresponding service resource distribution domain service can be called according to the target service resource information, the service resource distribution domain service determines a target user account according to the current service identifier, and distributes the target service resource corresponding to the target service resource information to the target user account.

In one embodiment, as shown in fig. 6, the service data processing method further includes:

step S701, receiving a target service resource withdrawal request, wherein the target service resource withdrawal request carries a target service identifier.

Step S702, according to the target service resource withdrawal request, calling a target service resource issuing domain service corresponding to the target service identifier, so that the target service resource issuing domain service determines a corresponding target service account according to the target service identifier, and obtains a target service resource value corresponding to the target service account.

The target service resource withdrawal request is used for requesting to withdraw the target service resource, the target service resource withdrawal request carries a target service identifier, the target service resource withdrawal request can be provided with a service resource withdrawal control at a terminal, the service resource withdrawal control is operated to trigger and generate a resource withdrawal request, and the terminal sends the target service resource withdrawal request to a service background server.

Specifically, the service background server receives a target service resource withdrawal request, calls a target service resource issuing domain service corresponding to the target service identifier according to the target service resource withdrawal request, determines a corresponding target service account according to the target service identifier, and then acquires a target service resource value corresponding to the target service account. The target business resource value here may be a target business resource fund, and the target business resource fund is brought back.

Step S703, sending the target service resource value to the service resource management domain service, so that the service resource management domain service issues the service resource value to the target service resource value.

Specifically, after obtaining the target business resource value, the target business resource value is returned to the business background server by the target business resource issuing domain service, and the business background server sends the target business resource value to the business resource management domain service, and issues the target business resource value through the business resource management domain service.

In a specific application scenario, as shown in fig. 7, fig. 7 shows a timing diagram of a service data processing method in an embodiment, where a current service identifier is a task activity identifier, a current service type is a task class retention activity, a target service domain service is a task domain service, a service core domain service includes an active core domain service and a virtual fund domain service, a service background server is an active background, and the service data processing method may specifically be:

1. and receiving a current service login request, wherein the current service login request carries a current service identifier and a current service type.

Specifically, a user enters an activity page through pushing or linking, and operates and triggers the activity page to generate an activity login request, wherein the activity login request comprises an activity identifier and an activity service type.

2. And calling a target service domain service corresponding to the current service type according to the current service login request, and acquiring the current service content corresponding to the current service identifier through the target service domain service.

Specifically, after receiving the activity login request, the activity background calls a corresponding activity task domain according to the activity service type in the activity login request, the activity task domain determines an activity task list through the activity identifier in the activity login request, and returns the activity task list to the terminal where the user is located.

Further, before determining the target service domain service, the method further includes:

3. acquiring the configuration information of each candidate service content, wherein each candidate service content configuration information comprises a corresponding candidate service type;

the candidate service content configuration information further includes, but is not limited to: candidate service identification, candidate service content name, candidate service type, candidate service content admission condition, etc. For example, as shown in fig. 8, fig. 8 is a schematic interface diagram illustrating an activity information configuration interface in an embodiment, and the candidate service content configuration information of fig. 8 is activity configuration information, which includes an activity identifier, an activity name, an activity type, participation conditions, a start time, an end time, and the like.

4. And configuring candidate service domain services corresponding to the candidate service types according to the candidate service content configuration information, and establishing a relation between each candidate service type and the corresponding candidate service domain service.

The relevant service domain service parameters may include: candidate service identification, candidate service content name, candidate service type, candidate service content admission condition, and the like.

5. Before the activity task domain determines the activity task list through the activity identifier in the activity login request, the method further comprises the following steps:

the relevant information of the activity, such as admission conditions, online and offline times and issuing conditions (white lists), can be set, and if the relevant information is met, the corresponding activity task list is called out.

6. And clicking a target task card from the active task list by the user, sending a request to the active background, and calling a corresponding task domain by the active background according to the service type (task class retention activity) in the request to retrieve the task. When the task is completed, the task domain checks according to the attribute of the active task configured in advance, and judges whether the task is successfully completed or not.

Further, before that, relevant task information may be configured, for example, as shown in fig. 9, fig. 9 shows an interface schematic diagram of a task information configuration interface in one embodiment, and the task information configuration information of fig. 9 includes: task identification, task name, belonging activity, task type, task period, task upper limit, start time and end time.

7. And when the task is completed successfully, calling the activity core domain to obtain the relevant prize, acquiring the relevant prize information by the activity core domain, calling the relevant service according to the prize to realize prize issuing, and calling the virtual fund service to store the fund into the corresponding virtual account of the user if the virtual fund is generated.

8. The activity page is provided with a cash withdrawal control, and a user can check the own fund balance and the related running water of the account through the cash withdrawal control arranged on the activity page, and then sends a cash withdrawal request to the activity background.

9. If the withdrawal condition is met, the virtual fund service is called to extract the balance from the corresponding account, and then the active core service is called to release the fund.

Further, prior to this, relevant prize information may be configured, for example, as shown in fig. 10, fig. 10 shows an interface schematic diagram of a prize information configuration interface in one embodiment, and the prize information configuration information of fig. 10 includes: activity identification, prize type, prize name, prize inventory, amount dispensed, and conditions dispensed, etc.

The business data processing method realizes the construction of a marketing activity platform based on a domain model, and supports the quick development of the business of various activities commonly used at present through domain services such as an activity core domain, a task domain, a power-assisted domain, a virtual fund domain and the like. All domain services are decoupled and independently deployed, data are independent, and the operation stability and efficiency of the active service are improved. Meanwhile, by matching with a marketing activity configuration management system, the activity type and the service characteristic parameters of all relevant domains can be defined through configuration, development is not needed, and online is fast.

It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the above-described flowcharts may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, as shown in fig. 11, there is provided a service data processing apparatus 900, including:

a service login request obtaining module 902, configured to receive a current service login request, where the current service login request carries a current service identifier and a current service type.

And a target service domain calling module 904, configured to call a target service domain service corresponding to the current service type according to the current service login request, and obtain, through the target service domain service, current service content corresponding to the current service identifier.

A service content execution request obtaining module 906, configured to receive a service content execution request corresponding to current service content, and obtain a current service content execution state corresponding to the current service content by responding to the service content execution request through a target service domain service.

A service core domain calling module 908, configured to call a service core domain service according to the current service content execution state, so that the service core domain service obtains corresponding target service resource information according to the current service content execution state, and performs target service resource allocation according to the target service resource information; wherein the target service domain service and the service core domain service are independent from each other.

In an embodiment, the target service domain invoking module 904 is further configured to obtain each candidate service domain service, where each candidate service domain service includes a corresponding candidate service type, determine a target service domain service from each candidate service domain service according to the candidate service type and the current service type, and invoke the target service domain service according to the current service login request.

In an embodiment, the target service domain invoking module 904 is further configured to obtain configuration information of each candidate service content, where each candidate service content configuration information includes a corresponding candidate service type, configure a candidate service domain service corresponding to the candidate service type according to each candidate service content configuration information, and establish a relationship between each candidate service type and the corresponding candidate service domain service.

In one embodiment, the target service domain invoking module 904 is further configured to send the current service login request to the target service domain service, so that the target service domain service determines a matched current service content from candidate service contents according to a current service identifier in the current service login request, where each candidate service content includes a corresponding candidate service identifier, and returns the current service content to receive the current service content.

In an embodiment, the service content execution request obtaining module 906 is further configured to return the current service content to the user terminal, so that the user terminal displays the current service content, obtain an operation on a service content execution control in a display interface of the current service content, generate a service content execution request according to an operation trigger, where the service content execution request carries a current service identifier and current service content attribute information, receive the service content execution request, send the service content execution request to the target service domain service, so that the target service domain service obtains corresponding target service content attribute information according to the current service identifier in the service content execution request, and determine a current service content execution state corresponding to the service content execution request according to the current service content attribute information and the target service content attribute information.

In one embodiment, the service core domain service includes a service resource management domain service and a service resource distribution domain service, and the service core domain calling module 908 is further configured to call the service resource management domain service when the current service content execution state is the current service execution completion state, so that the service resource management domain service obtains corresponding target service resource information according to the current service identifier, and calls the corresponding service resource distribution domain service according to the target service resource information, where different target service resource information corresponds to different service resource distribution domain services, so that the service resource distribution domain service determines a target user account according to the current service identifier, and distributes the target service resource corresponding to the target service resource information to the target user account.

In an embodiment, the service data processing apparatus 900 is further configured to receive a target service resource withdrawal request, where the target service resource withdrawal request carries a target service identifier, call a target service resource issuing domain service corresponding to the target service identifier according to the target service resource withdrawal request, so that the target service resource issuing domain service determines a corresponding target service account according to the target service identifier, obtains a target service resource value corresponding to the target service account, and sends the target service resource value to the service resource management domain service, so that the service resource management domain service issues the service resource value to the target service resource value.

In one embodiment, as shown in fig. 12, there is provided a business data processing system 1000 comprising:

and the service background server 1004 is configured to receive a current service login request, where the current service login request carries a current service identifier and a current service type, and call a target service domain server corresponding to the current service type call according to the current service login request.

And the target service domain server 1006 is configured to obtain current service content corresponding to the current service identifier, and return the current service content to the service background server.

The service background server 1004 is further configured to obtain a service content execution request corresponding to the current service content, and return the service content execution request to the service background server.

The service background server 1004 is further configured to send the service content execution request to the target service domain server.

The target service domain server 1006 is further configured to obtain a current service content execution state corresponding to the service content execution request, and return the current service content execution state to the service background server.

The service background server 1004 is further configured to invoke a service core domain service according to the current service content execution state.

And the service core domain server 1008 is configured to obtain corresponding target service resource information according to the current service content execution state, and issue a target service resource according to the target service resource information.

In one embodiment, the service core domain server 1008 includes a service resource management domain server and a service resource issuing domain server, wherein:

and the service background server is also used for calling the service resource management domain server when the current service content execution state is the current service execution completion state.

And the service resource management domain server is used for acquiring corresponding target service resource information according to the current service identifier, calling the corresponding service resource distribution domain server according to the target service resource information, and enabling different target service resource information to correspond to different service resource distribution domain services.

And the service resource issuing domain server is used for determining a target user account according to the current service identifier and issuing the target service resource corresponding to the target service resource information to the target user account.

In one embodiment, the business data processing system 1000 further comprises: and the service content configuration server is used for acquiring the configuration information of each candidate service content, configuring the candidate service domain server corresponding to the candidate service type according to the configuration information of each candidate service content, and establishing the relationship between each candidate service type and the corresponding candidate service domain server.

The service content configuration server is further configured to obtain configuration information of each candidate service resource, where the configuration information of each candidate service resource includes a corresponding candidate service identifier, and configure the service core domain server according to the configuration information of each candidate service resource and the corresponding candidate service identifier.

In one embodiment, the corresponding service content related information and service resource information can be configured in the service content configuration server, and the universal module is accessed in the service background server, so that the development of repeated codes is avoided, the rapid development and online of the service content are achieved, if the service related personalized characteristics need to be added on the universal module, the personalized module only needs to be packaged on the upper layer of the universal module, and then the universal module interface is called in the personalized module, and the personalized module is embedded in the universal module. For example, a delay award task activity is designed in such a manner that an award is issued not immediately after a task is completed but only after a certain time elapses without changing the task state. The personalized characteristic of delayed award dispensing does not exist in the general module, but the delayed award dispensing logic related to the service can be packaged in the outer layer, and then the delayed award dispensing module can be embedded into the downstream of the task module through the external interface of the general module, so that the delayed award dispensing function after the task is completed can be realized. The personalized module embedding is realized by providing an interface to the outside so as to realize the modularization flexibility. For example, as shown in FIG. 13, FIG. 13 illustrates a block diagram of the structure of the personalized module access in one embodiment.

In an embodiment, as shown in fig. 14, fig. 14 is a schematic diagram of a system architecture of a service data processing system in an embodiment, each domain service in fig. 14 has an independent data storage system, so that the overall architecture is lighter and more reliable, and a service background server obtains an activity type and its related domain services (a service domain server and a service core domain server, where the service background server includes a service resource management domain server and a service resource issuing domain server) through a service content configuration server, so as to invoke the related domain services according to service logic at an upper layer to implement activity related logic. For example, for a common marketing model, a general logic can be implemented in the service background server, i.e., the service background server can be simply configured, and the service background server can be quickly online without development.

FIG. 15 is a diagram showing an internal structure of a computer device in one embodiment. The computer device may specifically be the service backend server 120 in fig. 1. As shown in fig. 15, the computer apparatus includes a processor, a memory, a network interface, and an input device connected via a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the service data processing method. The internal memory may also have stored therein a computer program that, when executed by the processor, causes the processor to perform the business data processing method. The input device of the computer equipment can be a touch layer covered on a display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 15 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the service data processing apparatus provided in the present application may be implemented in the form of a computer program, and the computer program may be run on a computer device as shown in fig. 15. The memory of the computer device may store various program modules constituting the service data processing apparatus, such as a service login request acquisition module, a target service domain calling module, a service content execution request acquisition module, and a service core domain calling module shown in fig. 11. The program modules constitute computer programs that cause the processors to execute the steps of the business data processing methods of the embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 15 may execute receiving, by a service login request obtaining module in the service data processing apparatus shown in fig. 11, a current service login request, where the current service login request carries a current service identifier and a current service type. And the target service domain calling module executes calling of a target service domain service corresponding to the calling of the current service type according to the current service login request, and acquires the current service content corresponding to the current service identifier through the target service domain service. The service content execution request acquisition module receives a service content execution request corresponding to the current service content, and acquires a current service content execution state corresponding to the service content execution request through the target service domain service. The service core domain calling module executes calling of the service core domain service according to the current service content execution state, so that the service core domain service acquires corresponding target service resource information according to the current service content execution state, and performs target service resource distribution according to the target service resource information.

In one embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the steps in any embodiment of the business data processing method are implemented.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps of any of the embodiments of the above-mentioned business data processing method.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the steps of any embodiment of the business data processing method.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing service data, the method comprising:

receiving a service content execution request corresponding to the current service content, responding to the service content execution request through the target service domain service, and acquiring a current service content execution state corresponding to the current service content;

and calling a service core domain service according to the current service content execution state so that the service core domain service acquires corresponding target service resource information according to the current service content execution state, and issuing target service resources according to the target service resource information, wherein the target service domain service is independent from the service core domain service.

2. The method of claim 1, further comprising:

acquiring candidate service content configuration information, wherein the candidate service content configuration information comprises corresponding candidate service types;

configuring candidate service domain services corresponding to the candidate service types according to the candidate service content configuration information, and establishing a relationship between each candidate service type and the corresponding candidate service domain service;

the calling of the target service domain service corresponding to the current service type according to the current service login request comprises:

and acquiring a candidate service type matched with the current service type, determining the candidate service domain service corresponding to the matched candidate service type as the target service domain service, and calling.

3. The method according to claim 2, wherein said obtaining the current service content corresponding to the current service identifier through the target service domain service comprises:

sending the current service login request to the target service domain service, so that the target service domain service determines matched current service content from candidate service content corresponding to the candidate service content configuration information according to the current service identifier in the current service login request, wherein each candidate service content comprises a corresponding candidate service identifier, and returns the current service content;

and receiving the current service content.

4. The method according to claim 1, wherein said receiving a service content execution request corresponding to the current service content, and acquiring a current service content execution state corresponding to the service content execution request through the target service domain service comprises:

returning the current service content to a user terminal to enable the user terminal to display the current service content, acquiring operation of a service content execution control in a display interface of the current service content, and generating a service content execution request according to the operation trigger, wherein the service content execution request carries the current service identifier and the attribute information of the current service content;

receiving the service content execution request, sending the service content execution request to the target service domain service so as to enable the target service domain service to obtain corresponding target service content attribute information according to the current service identifier in the service content execution request, and determining a current service content execution state corresponding to the service content execution request according to the current service content attribute information and the target service content attribute information.

5. The method according to claim 1, wherein the service core domain service includes a service resource management domain service and a service resource distribution domain service, and the invoking of the service core domain service according to the current service content execution state enables the service core domain service to obtain corresponding target service resource information according to the current service content execution state, and perform target service resource distribution according to the target service resource information includes:

and when the current service content execution state is a current service execution completion state, calling a service resource management domain service to enable the service resource management domain service to acquire corresponding target service resource information according to the current service identifier, calling a corresponding service resource distribution domain service according to the target service resource information, wherein different target service resource information correspond to different service resource distribution domain services, so that the service resource distribution domain service determines a target user account according to the current service identifier and distributes the target service resource corresponding to the target service resource information to the target user account.

6. The method of claim 5, further comprising:

receiving a target service resource withdrawal request, wherein the target service resource withdrawal request carries a target service identifier;

calling a target service resource issuing domain service corresponding to the target service identifier according to the target service resource presentation request, so that the target service resource issuing domain service determines a corresponding target service account according to the target service identifier and acquires a target service resource value corresponding to the target service account;

and sending the target service resource numerical value to the service resource management domain service so that the service resource management domain service can issue the service resource numerical value to the target service resource numerical value.

7. A service data processing apparatus, characterized in that the apparatus comprises:

a service login request obtaining module, configured to receive a current service login request, where the current service login request carries a current service identifier and a current service type;

a target service domain calling module, configured to call a target service domain service corresponding to the current service type according to the current service login request, and obtain, through the target service domain service, current service content corresponding to the current service identifier;

a service content execution request obtaining module, configured to receive a service content execution request corresponding to the current service content, and obtain a current service content execution state corresponding to the current service content by responding to the service content execution request through the target service domain service;

a service core domain calling module, configured to call a service core domain service according to the current service content execution state, so that the service core domain service obtains corresponding target service resource information according to the current service content execution state, and performs target service resource distribution according to the target service resource information, where the target service domain service and the service core domain service are independent of each other.

8. A business data processing system, the system comprising:

the system comprises a service background server, a service domain server and a service domain server, wherein the service background server is used for receiving a current service login request, the current service login request carries a current service identifier and a current service type, and the target service domain server corresponding to the current service type calling is called according to the current service login request;

the service background server is further configured to obtain a service content execution request corresponding to the current service content, and return the service content execution request to the service background server;

the target service domain server is further configured to acquire a current service content execution state corresponding to the service content execution request, and return the current service content execution state to the service background server;

9. The system of claim 8, wherein the service core domain server comprises a service resource management domain server and a service resource issuing domain server, wherein:

the service background server is also used for calling the service resource management domain server when the current service content execution state is the current service execution completion state;

the service resource management domain server is used for acquiring corresponding target service resource information according to the current service identifier, calling a corresponding service resource distribution domain server according to the target service resource information, and enabling different target service resource information to correspond to different service resource distribution domain services;

10. The system of claim 8, further comprising:

a service content configuration server, configured to obtain configuration information of each candidate service content, where each candidate service content configuration information includes a corresponding candidate service type, configure a candidate service domain server corresponding to the candidate service type according to each candidate service content configuration information, and establish a relationship between each candidate service type and the corresponding candidate service domain server;

the service content configuration server is further configured to obtain configuration information of each candidate service resource, where each candidate service resource configuration information includes a corresponding candidate service identifier, and configure a service core domain server according to each candidate service resource configuration information and the corresponding candidate service identifier.

11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 6 are implemented when the computer program is executed by the processor.

12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.