CN115098157A - Method and device for processing public service data - Google Patents
Method and device for processing public service data Download PDFInfo
- Publication number
- CN115098157A CN115098157A CN202210845995.6A CN202210845995A CN115098157A CN 115098157 A CN115098157 A CN 115098157A CN 202210845995 A CN202210845995 A CN 202210845995A CN 115098157 A CN115098157 A CN 115098157A
- Authority
- CN
- China
- Prior art keywords
- version
- service
- target
- public service
- public
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Transfer Between Computers (AREA)
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
Technical Field
The present invention relates to the field of software development technologies, and in particular, to a method and an apparatus for processing public service data.
Background
With the development of diversity of application program development, application components corresponding to a plurality of business projects can be developed in a butt joint mode in one application program, so that different business operations can be realized. For the same or common service request in one application component, each service project needs to request the server to call the common service data in the common service component to support the execution of service operation.
At present, when a request server side calls public service data, the public service data matched with service items in a public service component is usually called directly, if the public service data is updated, the public service component needs to be updated completely, the public service component comprises data updating and development code updating, and development test release is carried out again after the public service data is updated. However, a great deal of time and labor cost are consumed for completely updating the public service components, the flexibility of normal operation of the service project cannot be met, and the processing efficiency of public service data is greatly reduced.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for processing public service data, and mainly aims to solve the problem of low processing efficiency of the existing public service data.
According to an aspect of the present invention, there is provided a method for processing public service data, including:
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.
Further, the determining, based on the version mapping relationship, a target service item version and a target common service component version that are matched with a target service item carried by the common service data retrieval request includes:
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 business project version is not found, determining the public business component version for the preset equipment as the target public business component version.
Further, before the loading the version mapping relationship bound by the common service component, the method further includes:
when the update operation of the public service assembly is detected to be completed, sending an update request of the public service assembly to an update operation terminal;
the loading of the version mapping relation bound by the common service component comprises the following steps:
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.
Further, after the loading the version mapping relationship bound by the common service component, the method further includes:
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 common service component based on the received third updating feedback information.
Further, before the calling of the target public service data corresponding to the target public service component version according to the target service project version and the feedback of the target public service data to the client, the method further includes:
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.
Further, after the target public service data corresponding to the target public service component version is called according to the target service project version, the method further includes:
analyzing the service data type in the target public service data and the item type of the service item;
if the service data type is not matched with the project type, sending a verification request to the client, wherein the verification request carries service verification permission so as to feed back the target public service data after the client passes the verification.
According to another aspect of the present invention, there is provided a processing apparatus for public service data, including:
the loading module is used for loading a version mapping relation bound by the common service component, and mapping contents between different service item versions and different common 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.
According to another aspect of the present invention, there is provided a storage medium, in which at least one executable instruction is stored, and the executable instruction causes a processor to perform operations corresponding to the processing method of the public service data.
According to still another aspect of the present invention, there is provided a computer apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the processing method of the public service data.
By the technical scheme, the technical scheme provided by the embodiment of the invention at least has the following advantages:
compared with the prior art, the embodiment of the invention loads the version mapping relation bound by the public service component, and the mapping contents between different service project versions and different public 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. The client side can provide different public service component versions according to the requirements of different service project versions in the application program development process, so that the public service data of different versions can be called. If the public service data needs to be updated, the method of the invention does not need to completely update the public service components, thereby not only saving the time cost, but also saving the labor cost. The invention also facilitates the version management of the business project, meets the flexibility requirement of normal operation of the business project and greatly improves the efficiency of processing the public business data.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
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 only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating a method for processing public service data according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating another processing method of public service data according to an embodiment of the present invention;
fig. 3 is a block diagram illustrating a processing apparatus for public service data according to an embodiment of the present invention;
fig. 4 shows a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
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 to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the 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. loading a version mapping relation bound by the public service component;
in the embodiment of the invention, because the public service component stores different versions after being updated, the versions comprise the preset standby public service component version, the historical public service component version and the latest public service component version, and the public service data of different versions can be called from the public service components of different versions. In order to meet the requirements of different business projects in a client on different versions of public business data, the public business components of different versions are independently packaged, and a version mapping relation is bound. And the current execution end obtains the mapping contents between different service item versions and different public service component versions by loading the version mapping relation bound by the public service component. The business items are used for representing contents of executing different types of business operations in the application program, the business items include but are not limited to banking business items, insurance business items, life service business items, office business items and the like, and each specific business item has a specific business range corresponding to the specific business item to realize different business operations. The public service component is a component for providing public data for different service projects, is developed and published in the form of a static js file, and can include but is not limited to public user basic data, public transportation data, public accommodation resource data and the like required by the service projects. In the version mapping relationship, mapping contents between different service item versions and different common service component versions, for example, "version 1.0 of service item a → version 2.0 of common service component", "version 2.0 of service item B → version 1.0 of common service component", "version 3.0 of service item C → version 3.0 of common service component", where "→" represents a specific mapping relationship, and embodiments of the present invention are not particularly limited.
It should be noted that when the common service component needs to be updated, such as modification, upgrade, function iteration, etc., only the code for updating the common service component needs to be modified, and the common service component can be issued in the form of a static js file. And the business item determines whether to establish a mapping relation between the business item version and the latest version of the public business component version according to the needs of the business range of the business item. The current execution end may be a cloud server in data communication with the client, and may load, in real time or at time intervals, the version mapping relationship bound to the common service component, and store the version mapping relationship in the current execution end, so as to invoke when step 102 is executed.
102. 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;
in the embodiment of the invention, a user triggers the corresponding target service item through an application program in the client, determines the public service data needing to be requested, and sends the public service data calling request. After receiving a public service data calling request of a client, a current execution end reads a target service item version matched with a target service item carried in the public service data calling request so as to find a target public service component version according to mapping contents of the target service item version and a corresponding target public service component version in a version mapping relation. For example, a target service item a of the current client sends a public service data retrieval request, and first, after receiving the request, a description of a specific version form, such as a 1.0 version and the like, of a target service item version matched with the target service item a is read. The version of the target common service component corresponding to the version 1.0 of the target service item a is searched based on the mapping content in the version mapping relationship, for example, "version 1.0 of the service item a → version 2.0 of the common service component", the embodiment of the present invention is not specifically limited.
103. 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.
In the embodiment of the invention, after the target public service component version corresponding to the target service project version is determined, 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 performs service operation based on the target public service 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, and the like, the scenes suitable for the public service data processing implemented in step 101-103 in the embodiment of the present invention include, but are not limited to, electronic product payment, medical health, insurance products, and the like, so as to meet the requirements of flexibly requesting to acquire the public service data for service items in different clients.
It should be noted that, the client preferably performs loading in an asynchronous loading manner when loading the public service data, and the advantage of using asynchronous loading is that normal operation of the current target service project is not affected, and the user experience effect can be improved.
In another embodiment of the present invention, for further limitation and explanation, as shown in fig. 2, the step of determining, based on the version mapping relationship, a target business item version and a target common business component version that match a target business item carried in the common business data invocation request includes:
201. 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;
in the embodiment of the present invention, the current execution end analyzes the version identifier of the target service item version matched with the target service item in the client that sends the public service data request, where the target service item version includes, but is not limited to, an instrumented version, an early version, a Candidate version (Release Candidate), a formal Release version, a General Availability version (General Availability), and a stable version, and the embodiment of the present invention is not specifically limited. The version identifiers corresponding to the introduced target service project versions are Alpha, Beta, RC, Release, GA and Stable respectively. The version identifier may also be added with a stage identifier for indicating the number of times of modifying the same file in the same stage in the same version, and a name or an abbreviation for distinguishing different submitters of the same file may also be added with the version identifier. After the version identification of the target service item is analyzed, the current execution end searches the version of the target service item corresponding to the analyzed version identification according to the content in the version mapping relation. For example, the version identifier of the target business item a is "Alpha _ b1," which indicates that the target business item a is an internal test version that is first modified in the design stage, and the target business item a identified as "Alpha _ b 1" version is found in the version mapping relationship, which is not specifically limited in the embodiment of the present invention.
202. 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;
203. 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.
In the embodiment of the invention, according to the content in the version mapping relationship, two situations of finding or not finding the target service item version corresponding to the target service item identifier may occur when the target service item identifier is resolved, and when the target service item version is found, the version of the target public service component matched with the target service item version can be obtained directly according to the mapping content in the version mapping relationship. And when the target business item version is not found, matching the target business item corresponding to the version identification of the target business item version which is not found with a preset standby public business component version. The preset standby public service component version is a default version which is set in advance, and can be a main version, a most stable version in actual use and the like, and the embodiment of the invention is not particularly limited.
It should be noted that, when the public service component needs to be updated, such as modification, upgrade, function iteration, etc., the preset standby version of the public service component does not have update operations, such as modification, upgrade, function iteration, etc.
The mapping content in the mapping relation is searched in a targeted manner, the requirements of different service items in the client on the public service data are met, and the flexibility of calling the public service data by the service items is improved.
In another embodiment of the present invention, for further definition and explanation, before the step of loading the version mapping relationship bound by the common service component, the method further includes:
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;
in the embodiment of the invention, in order to enable the client to call the latest version of the common service component, namely, the client can call the latest common service data, the update condition of the common service component needs to be detected regularly or irregularly. During detection, the current execution end sends an updating detection signal to the updating operation end, and the updating operation end automatically performs updating operation detection after receiving the updating detection signal; if the update operation terminal detects that the public service component has the update dynamic state, after the update dynamic state is completed, the update operation terminal feeds back an update operation trigger signal to the current execution terminal, and after the current execution terminal receives the update operation trigger signal fed back by the update operation terminal, the update operation terminal feeds back an update request of the public service component to the update operation terminal feeding back the update operation trigger signal. On the contrary, if the update operation end does not detect that the public service component has update dynamics, the update operation trigger signal does not need to be fed back to the current execution end, and the current execution end is not triggered to send the update request of the public service component. The update operation end includes, but is not limited to, a background manager, a server, a storage, and the like, and the embodiment of the present invention is not particularly limited.
Correspondingly, the loading of the version mapping relationship bound by the common service component includes:
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.
In the embodiment of the invention, after the current execution end sends the update request of the public service component to the update operation end, the update operation end feeds back the update request, namely, the version mapping relation bound by the public service component needing to be updated and carried in the update request is packaged, and the version mapping relation bound by the packaged public service component is sent to the current execution end. And the current execution end loads the version mapping relation of the public service component after receiving the version mapping relation bound by the packed public service component.
It should be noted that, when the front execution end performs an update operation on the public service component after responding to the update feedback information of the update operation end, the version file of the original public service component is saved as the version file of the historical public service component, and the version files of all historical public service components are not lost due to updating of the new version, but are saved in the form of an individual file package with a version number. The version file of the public service component with the version number can be released to different addresses in a js file packet mode to realize independent storage, and the storage method does not cover the version file of any public service component, thereby facilitating the version management of the public service component and providing a basis for loading the public service components with different versions.
In another embodiment of the present invention, for further definition and explanation, after the step of loading the version mapping relationship bound by the common service component, the method further includes:
and 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.
In the embodiment of the present invention, in order to keep the version of the service item executed by the client consistent with the version of the actually called public service component in the version mapping relationship, a first preset time interval needs to be set, for example, 3 hours, 1 day, 1 week, and the like, which is not specifically limited in the embodiment of the present invention. Under the control of a first preset time interval, the current execution end sends a first version mapping relation updating request to an updating operation end of the version mapping relation. And after receiving the first version mapping relation updating request, the updating operation end sends second updating feedback information to the current execution end, namely, the version mapping relation bound by the public service component is packaged and sent to the current execution end. And updating the stored version mapping relation bound by the public service component based on the received version mapping relation bound by the packaged public service component by the current execution end.
In another embodiment of the present invention, for further definition and explanation, after the step of loading the version mapping relationship bound by the common service component, the method further includes:
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.
In the embodiment of the invention, in order to keep the version of the service item executed by the client consistent with the version of the actually called public service component in the version mapping relationship, the version of the executed service item corresponding to the service operation executed in the client can be acquired, the version identifier of the version of the executed service item is analyzed, the analyzed version identifier is compared with the version identifier of the version of the service item in the version mapping relationship, and if the condition that the version identifiers are inconsistent is found in the comparison process, a second version mapping relationship updating request is sent to the updating operation terminal. And the updating operation terminal carries out modification operation on the version mapping relation according to the version mapping relation modification instruction carried in the second version mapping relation after receiving the second version mapping relation updating request, and sends the updated version mapping relation to the current execution terminal in the form of third updating feedback information. And the current execution end updates the version mapping relation bound by the public service component based on the received third updating feedback information.
It should be noted that the service operations described in the embodiment of the present invention include, but are not limited to, service operations of ordering a meal, purchasing an insurance product, and paying a telephone charge, and the embodiment of the present invention is not particularly limited.
In another embodiment of the present invention, for further limitation and explanation, before the step of calling the target public service data corresponding to the target public service component version according to the target service item version and feeding back the target public service data to the client, the method further includes:
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 project version to be rolled back is the target service project version, updating and determining the target service project version from the historical service project version and the preset service project version;
and if the version of the common service component 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.
In the embodiment of the invention, when the common service component needs to perform operations such as service iteration or bug repair, the rollback operation needs to be performed on the common service component or the service item bound with the common service component. A client sends a service rollback request, and after a current execution end receives the service rollback request, an object needing service rollback in the request needs to be found according to the service rollback request, namely, a service item to be rolled back or a common service component to be rolled back is determined; analyzing the business item version or the public business component version corresponding to the business item to be rolled back or the public business component to be rolled back; and finally, judging the analyzed version of the service item to be rolled back or the version of the common service component to be rolled back, and if the version of the service item to be rolled back is consistent with the version of the target service item, selecting the version of the service item to be rolled back from the historical version of the service item or the preset version of the service item. The historical business project version is all business project versions stored due to updating operation except the current business project version and the preset business project version; the preset service project version is a default version which is set in advance, and may be a main version, a most stable version in actual use, and the like. And if the version of the common service component to be rolled back is consistent with the version of the target common service component, selecting the version of the common service component needing to be rolled back from the historical version of the common service component or the preset version of the common service component. The historical common service component version is all common service component versions stored due to updating operation except the current common service component version and the preset common service component version; the preset version of the public service component is a default version which is set in advance, and can be a main version, a most stable version in actual use and the like.
It should be noted that, when the service is rolled back, not only the rolling back can be performed for different target service items, but also the rolling back can be performed for different versions of the public service components, and this selectable rolling back mode enables the content published during each rolling back to be controllable, and does not need to perform full regression on all the service items, thereby not only reducing the publishing risk, but also saving the regression labor.
In another embodiment of the present invention, for further limitation and description, after the step of calling the target public service data corresponding to the target public service component version according to the target service item version, the method further includes:
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.
In the embodiment of the invention, in order to improve the processing accuracy of the public service component for calling the target public service data, thereby improving the efficiency of feeding the target public service data back to the client for processing, and analyzing the service data type and the item type of the service item in the target public service data. Because the public service data includes public user basic data, public transportation data, public accommodation attitude data, and the like, and the service items include, but are not limited to, banking service items, insurance service items, life service items, and the like, the data types corresponding to the public service data and the service items are analyzed to obtain the service data types and the item types, wherein the service data types include, but are not limited to, a digital type, an image type, a text type, and a financial resource type, and the item types include, but are not limited to, a transaction type, a data processing type, a data query type, and the like. For example, the common user basic data in the common service data belongs to a text type, an image type, and a number type, and at this time, the common user basic data may be matched with an item type of a service item, such as a data processing type, or a data query type, but cannot be matched with a transaction type, and the embodiment of the present invention is not particularly limited.
It should be noted that, when the service data type is matched with the item type, the matching determination may be performed with a matching rule written in advance, for example, the matching rule includes that the transaction type in the item type may only be matched with the financial resource type in the service data type, so that the service item of the transaction type performs service processing based on public service data of the financial resource type, which is not specifically limited in the embodiment of the present invention. If the service data type is not matched with the project type, the service project is not authorized to perform data processing based on the called target public service data, and therefore, a verification request is sent to the client. At this time, the verification request sent by the current execution end carries the service verification authority, so that the client feeds back the target public service data after passing the verification. Specifically, the service verification authority is used for instructing a user to perform verification entry of service authority, for example, the user is a vip user, when a service item s is triggered, the current execution end determines that the item type of the service item s is not matched with the service data type of the public service data requested to be called, the service verification authority is sent, and after the user enters the verification authority belonging to the vip, the verification is performed, so that the current execution end feeds back the unmatched public service data to the client, and the processing requirements of different users on the public service data are met.
In another embodiment of the present invention, for further limitation and description, the method for processing common service data in any of the above method embodiments further includes:
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 component to request for updating the public service component.
In the embodiment of the invention, in order to change the update frequency of the public service component along with the change of the requirement condition of the client for the public service data in the public service component, a second preset time interval is set in the current execution end and is used for counting the request times of the client for calling the public service data, for example, the counting times are set to be 0 at first, when the client is detected to request for calling the public service data, the counting times are added to be 1, if the second preset time interval is set to be 4 hours, the counting times of sending the calling instructions of a total number of pieces of public service data by the client within 4 hours are counted, and the counting times are cleared after the second preset time interval is passed for 4 hours, and the next 4 hours are counted; if the second preset time interval is set to be 1 day, the method and the device count how many pieces of public service data are called out by the client in 1 day, and the count times are cleared after the second preset time interval is 1 day, and the next 1 day is counted.
And when the request times counted by the current execution terminal reach a preset time threshold, automatically sending an updating request of the public service component to the updating operation terminal, and realizing the updating operation of the public service component. The setting of the number threshold may be a fixed number threshold, such as 2000, 10000, and the like, and the number threshold may be set in different time periods according to different use frequencies of each time period of the user, which is not specifically limited in the embodiment of the present invention.
Further, as an implementation of the method shown in fig. 1, an embodiment of the present invention provides a device for processing public service data, and as shown in fig. 3, the device includes:
the loading module 31 is configured to load a version mapping relationship bound to a common service component, where mapping contents between different service item versions and different common service component versions are configured in the version mapping relationship;
the matching module 32 is configured to, when a public service data retrieval request of a client is received, determine, based on the version mapping relationship, a target service item version and a target public service component version that are matched with a target service item carried in the public service data retrieval request;
and the execution module 33 is configured to call target public service data corresponding to the target public service component version according to the target service project version, and feed back the target public service data to the client.
Further, the matching module 32 further includes:
the analysis unit is used for 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;
a determining unit, configured to first determine whether the target service item version is found, and if the target service item version is found, determine a target common service component version matched with the target service item version based on mapping content in the version mapping relationship; 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.
Further, the apparatus further comprises:
the update detection module is used for sending an update request of the public service component to an update operation terminal when the update operation of the public service component is detected to be completed;
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 a version mapping relationship bound to the common service component.
Further, the apparatus further comprises:
the first updating request sending module is used for sending a first version mapping relationship updating request according to a first preset time interval and updating the version mapping relationship bound by the public service component based on the received second updating feedback information;
the first updating request sending module is further used for acquiring an execution service project version corresponding to the 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 common service component based on the received third updating feedback information.
Further, the apparatus further comprises:
the service rollback module comprises a service rollback item determining unit, and after a service rollback request is received, the version of a service item to be rolled back and/or the version of a common service component to be rolled back are determined according to a service rollback object carried by the service rollback request;
the service rollback module also comprises a service rollback execution unit, and if the service item version to be rolled back is the target service item version, the target service item version is updated and determined from the historical service item version and the preset service item version;
and if the version of the common service component 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.
Further, the apparatus further comprises:
the verification module comprises a data type analysis unit and is used for analyzing the service data type in the target public service data; the verification module also comprises an item type analysis unit used for analyzing the item type of the service item;
the verification module further comprises a verification execution unit, and if the service data type is not matched with the project type, a verification request is sent to the client, wherein the verification request carries a service verification authority, so that the target public service data is fed back after the client passes verification.
Further, the apparatus further comprises:
the second updating request sending module is used for counting the request times of the calling request in a second preset time interval;
the second update request sending module is further configured to determine whether the request times reach a preset time threshold, and send an update request of the public service component to request for updating the public service component if the request times match the preset time threshold.
According to an embodiment of the present invention, a storage medium is provided, where the storage medium stores at least one executable instruction, and the computer executable instruction may perform an operation corresponding to the processing method of public service data in any method embodiment described above.
Fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the computer device.
As shown in fig. 4, the computer apparatus may include: a processor (processor)402, a Communications Interface 404, a memory 406, and a Communications bus 408.
Wherein: the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408.
A communication interface 404 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 may specifically perform relevant steps in the above embodiment of the method for processing public service data.
In particular, program 410 may include program code comprising computer operating 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 computer device includes one or more processors, which may be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 410 may specifically be configured to cause the processor 402 to perform the following operations:
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.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210845995.6A CN115098157A (en) | 2022-07-19 | 2022-07-19 | Method and device for processing public service data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210845995.6A CN115098157A (en) | 2022-07-19 | 2022-07-19 | Method and device for processing public service data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115098157A true CN115098157A (en) | 2022-09-23 |
Family
ID=83298045
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210845995.6A Pending CN115098157A (en) | 2022-07-19 | 2022-07-19 | Method and device for processing public service data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115098157A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115314421A (en) * | 2022-10-08 | 2022-11-08 | 北京国安广传网络科技有限公司 | Quantification management system based on network intelligent platform |
-
2022
- 2022-07-19 CN CN202210845995.6A patent/CN115098157A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115314421A (en) * | 2022-10-08 | 2022-11-08 | 北京国安广传网络科技有限公司 | Quantification management system based on network intelligent platform |
| CN115314421B (en) * | 2022-10-08 | 2022-12-23 | 北京国安广传网络科技有限公司 | Quantification management system based on network intelligent platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8407519B2 (en) | Remedying method for troubles in virtual server system and system thereof | |
| US8918377B2 (en) | Multiple source data management using a conflict rule | |
| US11086618B2 (en) | Populating a software catalogue with related product information | |
| US9811356B2 (en) | Automated software configuration management | |
| CN110968478B (en) | Log acquisition method, server and computer storage medium | |
| US7627662B2 (en) | Transaction request processing system and method | |
| CN111723313A (en) | Page jump processing method, device, equipment and storage medium | |
| US7613680B2 (en) | Computer system and the computer control method | |
| CN110633977A (en) | Payment exception processing method and device and terminal equipment | |
| CN112579692A (en) | Data synchronization method, device, system, equipment and storage medium | |
| CN115098157A (en) | Method and device for processing public service data | |
| CN114328029A (en) | Backup method and device of application resources, electronic equipment and storage medium | |
| CN114139161A (en) | Method, device, electronic equipment and medium for batch vulnerability detection | |
| CN113297153A (en) | Data export method, device, equipment and storage medium | |
| CN113360210A (en) | Data reconciliation method and device, computer equipment and storage medium | |
| CN111858585A (en) | Block chain strategy processing device, computer readable storage medium and terminal equipment | |
| US20030162559A1 (en) | Mobile communications terminal, information transmitting system and information receiving method | |
| CN115617768A (en) | Log management method, system, electronic device and storage medium | |
| CN115170152A (en) | Data distribution method, device, equipment and storage medium | |
| CN114039878A (en) | Network request processing method and device, electronic equipment and storage medium | |
| CN113407339A (en) | Resource request feedback method and device, readable storage medium and electronic equipment | |
| CN113763094A (en) | Service information processing method, device, server, medium and system | |
| CN112131025A (en) | Component transmission method and device, computer equipment and storage medium | |
| CN111045983A (en) | Nuclear power station electronic file management method and device, terminal equipment and medium | |
| CN107704557B (en) | Processing method and device for operating mutually exclusive data, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |