CN115098157A - Method and device for processing public service data - Google Patents

Abstract

The invention discloses a method and a device for processing public service data, relates to the technical field of software development, and mainly aims to solve the problems of low updating efficiency and poor flexibility caused by the fact that public service components need to be completely updated when public service data are updated. The method comprises the following steps: loading a version mapping relation bound by a public service component, wherein the version mapping relation is configured with mapping contents between different service item versions and different public service component versions; when a public service data calling request of a client is received, determining a target service item version and a target public service component version which are matched with a target service item carried by the public service data calling request based on the version mapping relation; and calling target public service data corresponding to the target public service component version according to the target service project version, and feeding back the target public service data to the client.

Description

Method and device for processing public service data

technical field

The invention relates to the technical field of software development, in particular to a method and device for processing public service data.

Background technique

With the diversified development of application development, one application can be connected to the application components corresponding to the development of multiple business projects to realize different business operations. Wherein, for the same or common business requests in an application component, each business item needs to request the server to retrieve common business data in the common business component to support the execution of business operations.

At present, when requesting the server to retrieve public business data, it usually directly retrieves the public business data matching the business item in the public business component. If the public business data is updated, the public business component needs to be completely updated, including data update. Also includes development code updates, and re-develop test releases after the update. However, the complete update of public business components will consume a lot of time and labor costs, and cannot meet the flexibility of normal operation of business projects, which greatly reduces the processing efficiency of public business data.

SUMMARY OF THE INVENTION

In view of this, the present invention provides a method and device for processing public service data, which mainly aim to solve the problem of low processing efficiency of the existing public service data.

According to one aspect of the present invention, a method for processing public service data is provided, comprising:

Loading the version mapping relationship bound by the common business component, where the mapping content between different business item versions and different common business component versions is configured in the version mapping relationship;

When receiving the public service data retrieval request from the client, determine the target service item version and the target public service component version matching the target service item carried in the public service data retrieval request based on the version mapping relationship;

The target public service data corresponding to the target public service component version is retrieved according to the target service item version, and the target public service data is fed back to the client.

Further, determining the target service item version and target public service component version matching the target service item carried in the public service data retrieval request based on the version mapping relationship includes:

Parse the version identifier of the target business item, and look up the version of the target business item corresponding to the version identifier in the version mapping relationship;

If the target business item version is found, determining a target public service component version matching the target business item version based on the mapping content in the version mapping relationship;

If the target business item version is not found, the preset standby common business component version is determined as the target common business component version.

Further, before the loading of the version mapping relationship bound by the common service component, the method further includes:

When it is detected that the update operation of the public service component is completed, an update request of the public service component is sent to the update operator;

The version mapping relationship bound by the loading public service components includes:

In response to the update feedback information of the update request, the public service component is updated, and the version mapping relationship bound by the public service component is loaded.

Further, after the loading of the version mapping relationship bound by the common service component, the method further includes:

Send the first version mapping relationship update request according to the first preset time interval, and update the version mapping relationship bound to the common service component based on the received second update feedback information; or,

Obtain the execution business item version corresponding to the execution business operation in the client;

If the execution business item version is different from at least one of each of the business item versions in the version mapping relationship, send a second version mapping relationship update request, and update the public domain based on the received third update feedback information. The version mapping relationship bound to the business component is updated.

Further, before the target public service data corresponding to the target public service component version is retrieved according to the target service item version, and the target public service data is fed back to the client, the method further includes:

After receiving the service rollback request, determine the version of the service item to be rolled back and/or the version of the common service component to be rolled back according to the service rollback object carried in the service rollback request;

If the version of the business item to be rolled back is the target business item version, update and determine the target business item version from the historical business item version and the preset business item version;

If the public service component version to be rolled back is the target public service component version, update and determine the target public service component version from the historical public service component version and the preset public service component version.

Further, after retrieving the target public service data corresponding to the target public service component version according to the target service item version, the method further includes:

Parse the business data type in the target public business data, and the item type of the business item;

If the service data type does not match the item type, a verification request is sent to the client, and the verification request carries the service verification authority, so that when the client passes the verification, the target public service is fed back data.

According to another aspect of the present invention, a device for processing public service data is provided, comprising:

a loading module, used for loading the version mapping relationship bound by the common business component, where the mapping content between different business item versions and different common business component versions is configured in the version mapping relationship;

The matching module is configured to determine, based on the version mapping relationship, a target service item version and a target public service matching the target service item carried in the public service data retrieval request when receiving the public service data retrieval request of the client component version;

An execution module, configured to retrieve target public service data corresponding to the target public service component version according to the target service item version, and feed back the target public service data to the client.

According to yet another aspect of the present invention, a storage medium is provided, wherein at least one executable instruction is stored in the storage medium, and the executable instruction enables a processor to perform operations corresponding to the above-mentioned method for processing public service data.

According to yet another aspect of the present invention, a computer device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, and the processor, the memory, and the communication interface can communicate with each other through the communication bus. communication;

The memory is used for storing at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the above-mentioned method for processing public service data.

With the above technical solutions, the technical solutions provided by the embodiments of the present invention have at least the following advantages:

The present invention provides a method and device for processing public service data. Compared with the prior art, the embodiment of the present invention loads the version mapping relation bound by the public service component, and the version mapping relation is configured with different service items The mapping content between the version and different public service component versions; when receiving the public service data retrieval request from the client, based on the version mapping relationship, determine the target service item that matches the public service data retrieval request. The target service item version and the target public service component version; the target public service data corresponding to the target public service component version is retrieved according to the target service item version, and the target public service data is fed back to the client. In the process of application development, the client can provide different versions of public business components according to the requirements of different business project versions, so as to retrieve public business data of different versions. If the public service data needs to be updated, the method of the present invention does not need to completely update the public service components, which not only saves time cost but also saves labor cost. The invention also facilitates the version management of business items, satisfies the flexibility requirements for normal operation of business items, and greatly improves the efficiency of public business data processing.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

1 shows a flowchart of a method for processing public service data provided by an embodiment of the present invention;

2 shows a flowchart of another method for processing public service data provided by an embodiment of the present invention;

FIG. 3 shows a block diagram of the composition of a device for processing public service data provided by an embodiment of the present invention;

FIG. 4 shows a schematic structural diagram of a computer device provided by an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

An embodiment of the present invention provides a method for processing public service data. As shown in FIG. 1 , the method includes:

101. Load the version mapping relationship bound by the public business component;

In the embodiment of the present invention, since the common service components are updated to save different versions, including a preset standby common service component version, a historical common service component version, and the latest public service Retrieve public business data of different versions. In order to meet the needs of different business projects in the client for different versions of public business data, the public business components of different versions are packaged separately, and the version mapping relationship is bound. The current execution end obtains the mapping content between different business item versions and different common business component versions by loading the version mapping relationship bound by the common business component. Business items are used to represent the content of different types of business operations performed in the application. Business items include but are not limited to banking business projects, insurance business projects, life service business projects, office business projects, etc. Each has its corresponding specific business scope to realize different business operations, which is not specifically limited in the embodiment of the present invention. Public business components are components used to provide public data for different business projects. They are developed and released in the form of static js files, including but not limited to public user basic data, public transportation data, and public accommodation resource data required by business projects. . In the version mapping relationship, the mapping content between different business project versions and different common business component versions, such as "version 1.0 of business project A → version 2.0 of common business components", "version 2.0 of business project B → common business components" "Version 1.0 of the service item C" and "Version 3.0 of the business item C→Version 3.0 of the public service component", where "→" represents a specific mapping relationship, which is not specifically limited in this embodiment of the present invention.

It should be noted that when the public business components need to be updated due to modification, upgrade, function iteration, etc., only the code of the public business components needs to be modified and updated, which can be published in the form of static js files. According to the needs of its own business scope, the business project decides whether to establish a mapping relationship between its business project version and the latest version of the public business component. The current execution end can be a cloud server that communicates data with the client, and can load the version mapping relationship bound to the common service component in real time or at time intervals, and store it in the current execution end for adjustment when step 102 is executed. Pick.

102. When receiving the public service data retrieval request from the client, determine the target service item version and the target public service component version matching the target service item carried in the public service data retrieval request based on the version mapping relationship;

In the embodiment of the present invention, the user triggers the corresponding target service item through the application program in the client, and determines the public service data that needs to be requested, so as to send the public service data retrieval request. After receiving the public service data retrieval request from the client, the current execution end reads the target service item version matched with the target service item carried in the public service data retrieval request, and uses the version mapping relationship between the target service item version and the target service item version in the version mapping relationship. The mapping content of the corresponding target public business component version, find the target public business component version. For example, the target business item A of the current client sends a public service data retrieval request. After receiving the request, first read the version of the target business item matched by the target business item A, such as version 1.0, etc., and a description of the specific version format , the embodiments of the present invention are not specifically limited. Find the target public service component version corresponding to version 1.0 of target business item A based on the mapping content in the version mapping relationship, for example, "version 1.0 of business item A→version 2.0 of public service component", which is not specifically limited in this embodiment of the present invention .

103. Retrieve target public service data corresponding to the target public service component version according to the target service item version, and feed back the target public service data to the client.

In this embodiment of the present invention, after determining the target public service component version corresponding to the target service item version, the current execution end extracts the target public service data corresponding to the target public service component version, and sends the target public service data to the client , so that the client can perform business operations based on the target public business data. In addition, since the public service data includes but is not limited to public user basic data, public transportation data, public accommodation resource data, etc., the applicable scenarios for the public service data processing implemented in steps 101-103 in this embodiment of the present invention include: However, it is not limited to scenarios such as electronic product payment, medical health, insurance products, etc., to meet the needs of different clients to flexibly request public business data for business projects.

It should be noted that when loading public business data, the client preferably loads it asynchronously. The advantage of using asynchronous loading is that it does not affect the normal operation of the current target business project, which can improve user experience.

In another embodiment of the present invention, in order to further limit and illustrate, as shown in FIG. 2 , in the step, based on the version mapping relationship, a target service that matches the target service item carried in the public service data retrieval request is determined. Project version and target common business component version, including:

201. Parse the version identifier of the target business item, and search for the target business item version corresponding to the version identifier in the version mapping relationship;

In the embodiment of the present invention, the current execution end parses the version identifier of the target business item version matched by the target business item in the client that sends the public business data request, and the target business item version includes but is not limited to an internal beta version, an early version, A candidate version (Release Candidate), an official release version, a generally available version (General Availability), and a stable version are not specifically limited in this embodiment of the present invention. The version identifiers corresponding to each target business project version introduced above are Alpha, Beta, RC, Release, GA, and Stable, respectively. It is also possible to add a phase identifier to the version identifier to express the number of file modifications in the same version and the same phase, and to add a person's name or abbreviation to the version identifier to distinguish different submitters of the same file. After parsing the version identifier of the target business item, the current execution end finds the version of the target business item corresponding to the resolved version identifier according to the content in the version mapping relationship. For example, the version identifier of target business project A is "Alpha_b1", which means that the target business project A is the first modified internal beta version in the design stage, and the target business project identified as "Alpha_b1" version is found in the version mapping relationship A, the embodiments of the present invention are not specifically limited.

202. If the target business item version is found, determine a target public service component version matching the target business item version based on the mapping content in the version mapping relationship;

203. If the target service item version is not found, determine the preset standby public service component version as the target public service component version.

In the embodiment of the present invention, according to the content in the version mapping relationship, when the target business item identifier is parsed, there may be two situations in which the target business item version corresponding to the target business item identifier is found or not found. When the version of the target business item is selected, the version of the target public business component matched by the version of the target business item can be obtained directly according to the mapping content in the version mapping relationship. When the target business item version is not found, the target business item corresponding to the version identifier for which the target business item version is not found is matched with a preset standby common business component version. The preset standby version of the public service component is a preset default version, which may be the main version, the most stable version in actual use, or the like, which is not specifically limited in the embodiment of the present invention.

It should be noted that when the public service component needs to be updated due to modification, upgrade, function iteration, etc., the preset standby version of the public service component will not undergo any update operations such as modification, upgrade, and function iteration.

Targeted search is performed for the mapping content in the mapping relationship, which satisfies the requirements for common business data of different business projects in the client, and improves the flexibility of business projects to retrieve common business data.

In another embodiment of the present invention, in order to further define and illustrate, before the step of loading the version mapping relationship bound to the common service component, the method further includes:

When it is detected that the update operation of the public service component is completed, an update request of the public service component is sent to the update operator;

In the embodiment of the present invention, in order to enable the client to retrieve the latest version of the public service component, that is, the client to retrieve the latest public service data, it is necessary to periodically or irregularly update the public service component. detection. During detection, the current execution terminal sends an update detection signal to the update operation terminal, and after receiving the update detection signal, the update operation terminal performs the update operation detection by itself; if the update operation terminal detects that the public service component has an update dynamic, after the update dynamic is completed, the update operation is performed. The terminal feeds back an update operation trigger signal to the current execution terminal. After receiving the update operation trigger signal fed back by the update operation terminal, the current execution terminal sends an update request of the common service component to the update operation terminal that fed back the update operation trigger signal. Conversely, if the update operator does not detect that the public service component has update dynamics, it does not need to feed back an update operation trigger signal to the current execution end, and does not trigger the current execution end to send an update request for the public service component. The update operation terminal includes but is not limited to a background manager, a server, a storage, and the like, which is not specifically limited in the embodiment of the present invention.

Correspondingly, the version mapping relationship bound by the loading public service components includes:

In response to the update feedback information of the update request, the public service component is updated, and the version mapping relationship bound by the public service component is loaded.

In this embodiment of the present invention, after the current execution end sends an update request for the public service component to the update operation end, the update operation end provides feedback on the update request, that is, the update request is bound to the public service component that needs to be updated. The version mapping relationship is packaged, and the version mapping relationship bound by the packaged public business component is sent to the current execution end. After receiving the version mapping relationship bound by the packaged public service component, the current execution end loads the version mapping relationship of the public service component.

It should be noted that when the current execution end performs an update operation on the public service component after responding to the update feedback information from the update operator, the version file of the original public service component is saved as the version file of the historical public service component, and the versions of all historical public service components are saved. Files are not lost by updating to a new version, but are saved as separate file packages with version numbers. The version files of public business components with version numbers can be published to different addresses in the form of js file packages to achieve separate storage. This saving method does not cover the version files of any public business components, which is convenient for public business components. It also provides a basis for loading different versions of common business components.

In another embodiment of the present invention, in order to further define and illustrate, after the step of loading the version mapping relationship bound by the common service component, the method further includes:

The first version mapping relationship update request is sent according to the first preset time interval, and the version mapping relationship bound to the common service component is updated based on the received second update feedback information.

In the embodiment of the present invention, in order to keep the version of the business item executed by the client consistent with the version of the public business component actually called in the version mapping relationship, a first preset time interval needs to be set, such as 3 hours, 1 day, 1 week, etc. , the embodiments of the present invention are not specifically limited. Under the control of the first preset time interval, the current execution end sends a first version mapping relationship update request to the update operation end of the version mapping relationship. After receiving the first version mapping relationship update request, the update operator sends second update feedback information to the current execution end, that is, packages the version mapping relationship bound to the public service component and sends it to the current execution end. Based on the received version mapping relationship bound to the packaged public business component, the current execution end performs an update operation on the stored version mapping relationship bound to the public business component.

In another embodiment of the present invention, in order to further define and illustrate, after the step of loading the version mapping relationship bound by the common service component, the method further includes:

Obtain the execution business item version corresponding to the execution business operation in the client;

If the execution business item version is different from at least one of each of the business item versions in the version mapping relationship, send a second version mapping relationship update request, and update the public domain based on the received third update feedback information. The version mapping relationship bound to the business component is updated.

In the embodiment of the present invention, in order to keep the version of the business item executed by the client consistent with the version of the public service component actually called in the version mapping relationship, the version of the executed business item corresponding to the business operation executed in the client can also be obtained by obtaining , and then parse the version ID of the execution business item version, and compare the parsed version ID with the version ID of the business item version in the version mapping relationship. The second version mapping relationship update request. The second version mapping relationship update request carries a version mapping relationship modification instruction, and after receiving the second version mapping relationship update request, the update operator performs a modification operation on the version mapping relationship according to the version mapping relationship modification instruction carried in the second version mapping relationship, The updated version mapping relationship is sent to the current execution end in the form of third update feedback information. The current execution end performs an update operation on the version mapping relationship bound to the common service component based on the received third update feedback information.

It should be noted that the business operations described in the embodiments of the present invention include but are not limited to business operations such as ordering meals, purchasing insurance products, and paying telephone bills, which are not specifically limited in the embodiments of the present invention.

In another embodiment of the present invention, in order to further define and illustrate, the step retrieves the target public service data corresponding to the target public service component version according to the target service item version, and feeds back the target public service data to the client. Before the business data, the method further includes:

After receiving the service rollback request, determine the version of the service item to be rolled back and/or the version of the common service component to be rolled back according to the service rollback object carried in the service rollback request;

If the version of the business item to be rolled back is the target business item version, update and determine the target business item version from the historical business item version and the preset business item version;

If the public service component version to be rolled back is the target public service component version, update and determine the target public service component version from the historical public service component version and the preset public service component version.

In the embodiment of the present invention, when the common business component needs to perform operations such as business iteration or bug repair, it is necessary to perform a rollback operation on the common business component or the business project bound with the common business component. The client sends a business rollback request. After the current execution end receives the business rollback request, it needs to first find the object in the request that needs to be rolled back according to the business rollback request, that is, to determine the business item to be rolled back or the business item to be rolled back. Roll back the common business component; then parse the business item version or common business component version corresponding to the business item to be rolled back or the public business component to be rolled back; The version of the common business component is rolled for judgment. If the version of the business item to be rolled back is consistent with the version of the target business item, the business item version to be rolled back is selected from the historical business item version or the preset business item version. Among them, the historical business item version is all the business item versions saved due to the update operation except the current business item version and the preset business item version; the preset business item version is the default version set in advance, which can be the main version, the actual The most stable version in use, etc., is not specifically limited in this embodiment of the present invention. If the version of the public service component to be rolled back is the same as the version of the target public service component, select the version of the public service component that needs to be rolled back from the historical public service component version or the preset public service component version. Among them, the historical public service component version is all the public service component versions saved due to the update operation except the current public service component version and the preset public service component version; the preset public service component version is a preset default version, which can be It is the main version, the most stable version in actual use, etc., which is not specifically limited in the embodiment of the present invention.

It should be noted that when the business is rolled back, not only can it be rolled back for different target business projects, but also for different versions of common business components. This optional rollback method makes every rollback possible. The released content is controllable, and there is no need to perform a full return of all business projects, which not only reduces the release risk, but also saves return manpower.

In another embodiment of the present invention, in order to further limit and illustrate, after the step calls the target public service data corresponding to the target public service component version according to the target service item version, the method further includes:

Parse the business data type in the target public business data, and the item type of the business item;

If the service data type does not match the item type, a verification request is sent to the client, and the verification request carries the service verification authority, so that when the client passes the verification, the target public service is fed back data.

In the embodiment of the present invention, in order to improve the processing accuracy of the target public service data fetched by the public service component, thereby improving the efficiency of feeding back the target public service data to the client for processing, the service data types and services in the target public service data are analyzed. The item type of the item. Since public business data includes public user basic data, public transportation data, public accommodation posture data, etc., and business items include but are not limited to banking business projects, insurance business projects, life service business projects, etc., public business data , analyze the data type corresponding to the business project, and obtain the business data type and project type, wherein the business data type includes but is not limited to digital type, image type, text type, financial resource type, and the project type includes but is not limited to transaction type , data processing class, data query class, etc., which are not specifically limited in the embodiments of the present invention. For example, the public user basic data in the public business data belongs to the text type, image type, and number type. In this case, it can match the project type of the business project, such as the data processing type, or the data query type, but not the transaction type. Matching, the embodiment of the present invention does not make specific limitations.

It should be noted that when the business data type is matched with the project type, it can be matched with the pre-written matching rules. For example, the matching rule contains the transaction type in the project type that can only match the financial resource type in the business data type. Therefore, the business item of the transaction type performs business processing based on the public business data of the financial resource type, which is not specifically limited in the embodiment of the present invention. If the business data type does not match the project type, it means that the business project does not have the right to perform data processing based on the fetched target public business data, so a verification request is sent to the client. At this time, the verification request sent by the current execution terminal carries the service verification authority, so that the client can feed back the target public service data after passing the verification. Specifically, the business verification authority is used to instruct the user to verify and enter the business authority. For example, if the user is a vip user, when the business item s is triggered, the current execution end determines the project type of the business item s and the public business data requested to be retrieved. If the type of business data does not match, the business verification authority is sent. After the user enters the verification authority belonging to the vip, the verification is passed, so that the current execution end feeds back the unmatched public business data to the client, so as to meet the needs of different users for public business data. Process demand.

In another embodiment of the present invention, in order to further limit and illustrate, the method for processing public service data in any of the above method embodiments further includes:

Counting the number of requests for the retrieval request within the second preset time interval;

If the number of requests matches the preset number of times threshold, an update request for the public service component is sent to request to update the public service component.

In the embodiment of the present invention, in order to be able to change the update frequency of the public service component according to the change of the client's demand for the public service data in the public service component, a second preset time interval is set in the current execution end, Used to count the number of requests made by the client to retrieve public service data. For example, first set the number of statistics to 0. Whenever it is detected that the client requests to retrieve public service data, the number of statistics is incremented by 1. If the second preset is set If the time interval is 4 hours, count the number of public service data retrieval commands sent by the client within 4 hours. After the second preset time interval of 4 hours has passed, the number of counts will be cleared, and the next 4 hours will be counted; If the second preset time interval is set to 1 day, the number of public service data retrieval instructions sent by the client in 1 day is counted. After the second preset time interval has passed for 1 day, the number of statistics is cleared, and the next 1 The statistics of the day are not specifically limited in this embodiment of the present invention.

When the number of requests counted by the current execution end reaches a preset number of times threshold, it automatically sends an update request for the public service component to the update operation end to implement the update operation for the public service component. The number of times threshold setting may be a fixed number of times threshold, such as 2000, 10000, etc., and the number of times threshold may be set by time period according to the different usage frequency of the user in each time period, which is not specifically limited in this embodiment of the present invention.

Further, as an implementation of the method shown in FIG. 1, an embodiment of the present invention provides an apparatus for processing public service data. As shown in FIG. 3, the apparatus includes:

The loading module 31 is used to load the version mapping relationship bound by the common business component, and the mapping content between different business item versions and different common business component versions is configured in the version mapping relationship;

The matching module 32 is configured to, when receiving the public service data retrieval request of the client, determine the target service item version and the target public service matching the target service item carried in the public service data retrieval request based on the version mapping relationship. business component version;

The execution module 33 is configured to retrieve the target public service data corresponding to the target public service component version according to the target service item version, and feed back the target public service data to the client.

Further, the matching module 32 also includes:

a parsing unit for parsing the version identifier of the target business item, and searching for the version of the target business item corresponding to the version identifier in the version mapping relationship;

The determining unit firstly judges whether the target business item version is found, and if the target business item version is found, then determines the target public service component matching the target business item version based on the mapping content in the version mapping relationship version; if the target business item version is not found, the preset standby public business component version is determined as the target public business component version.

Further, the device also includes:

an update detection module, when detecting that the update operation of the public service component is completed, sending an update request of the public service component to the update operator;

The loading module 31 is further configured to update the common service component in response to the update feedback information of the update request, and load the version mapping relationship bound by the common service component.

Further, the device also includes:

a first update request sending module, configured to send a first version mapping relationship update request according to a first preset time interval, and update the version mapping relationship bound to the public service component based on the received second update feedback information;

The first update request sending module is further configured to obtain the execution business item version corresponding to the execution business operation in the client; if the execution business item version and each of the business item versions in the version mapping relationship are at least If one is different, send a second version mapping relationship update request, and update the version mapping relationship bound to the common service component based on the received third update feedback information.

Further, the device also includes:

A business rollback module, the business rollback module includes a business rollback item determination unit, and after receiving a business rollback request, determines the version of the business item to be rolled back and the business rollback object carried in the business rollback request according to the business rollback object. / or the version of the public business component to be rolled back;

The business rollback module further includes a business rollback execution unit, and if the version of the business item to be rolled back is the target business item version, the target business item version is updated and determined from the historical business item version and the preset business item version. ;

If the public service component version to be rolled back is the target public service component version, update and determine the target public service component version from the historical public service component version and the preset public service component version.

Further, the device also includes:

a verification module, the verification module includes a data type analysis unit for analyzing the business data type in the target public business data; the verification module further includes an item type analysis unit for analyzing the project type of the business project;

The verification module also includes a verification execution unit, and if the business data type does not match the item type, a verification request is sent to the client, and the verification request carries a business verification authority, so that when the client After passing the verification, the terminal feeds back the target public service data.

Further, the device also includes:

a second update request sending module, configured to count the number of times of the retrieval request within the second preset time interval;

The second update request sending module is further configured to judge whether the number of requests reaches a preset number threshold, and if the number of requests matches the preset number threshold, send an update request for the public service component to request the Common business components are updated.

According to an embodiment of the present invention, a storage medium is provided, the storage medium stores at least one executable instruction, and the computer-executable instruction can perform operations corresponding to the method for processing public service data in any of the foregoing method embodiments.

FIG. 4 shows a schematic structural diagram of a computer device according to an embodiment of the present invention. The specific embodiment of the present invention does not limit the specific implementation of the computer device.

As shown in FIG. 4 , the computer device may include: a processor (processor) 402 , a communications interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .

The processor 402 , the communication interface 404 , and the memory 406 communicate with each other through the communication bus 408 .

The communication interface 404 is used for communicating with network elements of other devices such as clients or other servers.

The processor 402 is configured to execute the program 410, and specifically may execute the relevant steps in the foregoing embodiments of the method for processing public service data.

Specifically, the program 410 may include program code including computer operation instructions.

The processor 402 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in the computer equipment may be the same type of processors, such as one or more CPUs; or may be different types of processors, such as one or more CPUs and one or more ASICs.

The memory 406 is used to store the program 410 . Memory 406 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

The program 410 can specifically be used to cause the processor 402 to perform the following operations:

Loading the version mapping relationship bound by the common business component, where the mapping content between different business item versions and different common business component versions is configured in the version mapping relationship;

When receiving the public service data retrieval request from the client, determine the target service item version and the target public service component version matching the target service item carried in the public service data retrieval request based on the version mapping relationship;

The target public service data corresponding to the target public service component version is retrieved according to the target service item version, and the target public service data is fed back to the client.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general-purpose computing device, which can be centralized on a single computing device, or distributed in a network composed of multiple computing devices Alternatively, they may be implemented in program code executable by a computing device, such that they may be stored in a storage device and executed by the computing device, and in some cases, in a different order than here The steps shown or described are performed either by fabricating them separately into individual integrated circuit modules, or by fabricating multiple modules or steps of them into a single integrated circuit module. As such, the present invention is not limited to any particular combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method for processing public service data is characterized by comprising the following steps:

loading a version mapping relation bound by a common service component, wherein mapping contents between different service item versions and different common service component versions are configured in the version mapping relation;

when a public service data calling request of a client is received, determining a target service item version and a target public service component version which are matched with a target service item carried by the public service data calling request based on the version mapping relation;

and calling target public service data corresponding to the target public service component version according to the target service project version, and feeding back the target public service data to the client.

2. The method of claim 1, wherein the determining, based on the version mapping relationship, a target service item version and a target common service component version that match a target service item carried by the common service data invocation request comprises:

analyzing the version identification of the target service item, and searching the version of the target service item corresponding to the version identification in the version mapping relation;

if the target service item version is found, determining a target public service component version matched with the target service item version based on the mapping content in the version mapping relation;

and if the target service project version is not found, determining the public service component version for the preset equipment as the target public service component version.

3. The method of claim 2, wherein before the loading the version mapping relationship to which the common business component is bound, the method further comprises:

when the completion of the updating operation of the public service assembly is detected, sending an updating request of the public service assembly to an updating operation terminal;

the loading of the version mapping relationship bound by the common service component comprises:

and responding to the update feedback information of the update request, updating the public service component, and loading the version mapping relation bound by the public service component.

4. The method of claim 2, wherein after loading the version mapping relationship to which the common business component is bound, the method further comprises:

sending a first version mapping relation updating request according to a first preset time interval, and updating the version mapping relation bound by the public service component based on the received second updating feedback information; or the like, or, alternatively,

acquiring an execution service project version corresponding to execution service operation in the client;

and if the execution service item version is different from at least one of the service item versions in the version mapping relationship, sending a second version mapping relationship updating request, and updating the version mapping relationship bound by the public service component based on the received third updating feedback information.

5. The method according to claim 1, wherein before the retrieving the target public service data corresponding to the target public service component version according to the target service project version and feeding back the target public service data to the client, the method further comprises:

after a service rollback request is received, determining a version of a service item to be rolled back and/or a version of a common service component to be rolled back according to a service rollback object carried by the service rollback request;

if the service item version to be rolled back is the target service item version, updating and determining the target service item version from the historical service item version and the preset service item version;

and if the common service component version to be rolled back is the target common service component version, updating and determining the target common service component version from the historical common service component version and the preset common service component version.

6. The method according to claim 1, wherein after the target common service data corresponding to the target common service component version is called according to the target service project version, the method further comprises:

analyzing the service data type in the target public service data and the item type of the service item;

and if the service data type is not matched with the project type, sending a verification request to the client, wherein the verification request carries a service verification authority so as to feed back the target public service data after the client passes the verification.

7. The method according to any one of claims 1-6, further comprising:

counting the request times of the calling request in a second preset time interval;

and if the request times are matched with a preset time threshold, sending an updating request of the public service assembly to request for updating the public service assembly.

8. An apparatus for processing public service data, comprising:

the loading module is used for loading a version mapping relation bound by the public service component, and mapping contents between different service item versions and different public service component versions are configured in the version mapping relation;

the matching module is used for determining a target service item version and a target public service component version which are matched with a target service item carried by a public service data calling request based on the version mapping relation when the public service data calling request of a client is received;

and the execution module is used for calling the target public service data corresponding to the target public service component version according to the target service project version and feeding back the target public service data to the client.

9. A storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to perform operations corresponding to the processing method of public service data according to any one of claims 1 to 7.

10. A computer device comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface are communicated with each other through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the processing method of the public service data according to any one of claims 1-7.

Images