CN118132120B

CN118132120B - Service system updating method and device, electronic equipment and storage medium

Info

Publication number: CN118132120B
Application number: CN202410552731.0A
Authority: CN
Inventors: 王翊
Original assignee: Chengdu Seres Technology Co Ltd
Current assignee: Chengdu Seres Technology Co Ltd
Priority date: 2024-05-07
Filing date: 2024-05-07
Publication date: 2024-07-02
Anticipated expiration: 2044-05-07
Also published as: CN118132120A

Abstract

The embodiment of the invention provides a service system updating method and device, electronic equipment and storage medium. The method comprises the following steps: acquiring first version information of a middle-stage system and second version information of the middle-stage system referenced by a service system in a test environment; the first version information includes one or more published versions and a snapshot version in development; when the second version information is detected to be a snapshot version, determining newly-added interface data of the middle platform system based on the first publishing version and the snapshot version which are currently used by the middle platform system, and controlling the middle platform system to fall back to the first publishing version; in the updating process of the service system, intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the newly added interface data. According to the embodiment of the invention, the business system automatically updates the edition without manual intervention, so that the edition efficiency and the edition quality are improved.

Description

Service system updating method and device, electronic equipment and storage medium

Technical Field

The present invention relates to the field of vehicle updating technologies, and in particular, to a service system updating method, a service system updating device, an electronic device, and a computer readable storage medium.

Background

In the development process, the service system of the vehicle completes communication by referring to an SDK (Software Development Kit ) of the middle platform system, interfaces and parameter information exposed outside the middle platform are packaged by the SDK, and the service system realizes remote call by the interfaces provided in the SDK. Because the development and the online (production) of the business system have own iteration plans, and the development and the online of the middle station system also have own iteration plans, the two have the condition of inconsistent versions.

Under the condition that the versions of the existing middle platform system and the service system are inconsistent, the service system needs to be put on line before the middle platform system is put on line, and the service system is put on line after the service system is put on line, or the function of putting on line part is delayed by means of manual annotation and restoring annotation codes, and the problem of low release efficiency and quality exists in the service system on-line release process.

Disclosure of Invention

In view of the foregoing, it is proposed to provide a service system updating method and apparatus, an electronic device, and a storage medium, which overcome or at least partially solve the foregoing problems, and include:

a method for updating a service system, which relates to a middle station system of a vehicle and the service system, the method comprises the following steps:

acquiring first version information of the middle platform system and second version information of the middle platform system referenced by the service system in a test environment; the first version information includes one or more published versions and snapshot versions in development;

When the second version information is detected to be the snapshot version, determining newly-added interface data of the middle platform system based on a first distribution version currently used by the middle platform system and the snapshot version, and controlling the middle platform system to fall back to the first distribution version;

And intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the newly added interface data in the updating process of the service system.

Optionally, the method further comprises:

and when the fact that the release version of the middle platform system is updated from the first release version to the second release version corresponding to the snapshot version is detected, updating the service system again based on the second release version.

Optionally, the updating the service system again based on the second release version includes:

updating the second version information of the middle platform system referenced by the service system into the second release version;

deleting the newly added interface data and executing an interception task based on the newly added interface data;

and recompiling the service system based on the second release version to update the service system.

Optionally, in the process of updating the service system, intercepting, according to the new interface data, target interface request information associated with the new interface data, which is sent by the service system to the intermediate system, includes:

writing the newly added interface data into a pre-created proxy file, and sending the proxy file to the service system;

And in the updating process of the service system, intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the proxy file.

Optionally, the acquiring the first version information of the middle platform system includes:

Creating a monitoring item for detecting a version of the center system for each center system in the vehicle, the monitoring item including a code warehouse address of the center system;

and based on the monitoring item, acquiring the first version information of the middle platform system from the code warehouse corresponding to the code warehouse address.

Optionally, after obtaining the first version information of the middle-stage system and obtaining the second version information of the middle-stage system referenced by the service system in the test environment, the method further includes:

When the second version information is detected to be not the snapshot version, judging whether the second version information is a first distribution version currently used by the middle platform system or not;

when the second version information is a first version of the distribution currently used by the middle platform system, controlling the service system to update the distribution based on the first version of the distribution;

And when the second version information is other release versions except the first release version, determining interface difference data between the other release versions and the first release version, and updating the release of the service system according to the difference type of the interface difference data.

Optionally, the method further comprises:

generating response data for the intercepted target interface request information according to a preset interception processing rule, and/or forwarding the intercepted target interface request information to a preset interface for processing according to the preset interception processing rule.

An updating device of a service system relates to a middle platform system of a vehicle and the service system, and the device comprises:

The version identification module is used for acquiring first version information of the middle platform system and acquiring second version information of the middle platform system referenced by the service system in a test environment; the first version information includes one or more published versions and snapshot versions in development;

the version rollback module is used for determining newly-added interface data of the middle platform system based on a first publishing version and the snapshot version which are currently used by the middle platform system when the second version information is detected to be the snapshot version, and controlling the middle platform system to rollback to the first publishing version;

And the interface request interception module is used for intercepting target interface request information which is related to the newly-added interface data and is sent to the middle station system by the service system according to the newly-added interface data in the updating process of the service system.

An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, which computer program, when executed by the processor, implements a method of updating a business system as described above.

A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method of updating a business system as described above.

The embodiment of the invention has the following advantages:

According to the embodiment of the invention, by identifying the version conditions of the middle platform system and the service system reference, when the second version information is detected to be the snapshot version, based on the first publishing version and the snapshot version which are currently used by the middle platform system, the newly-added interface data of the middle platform system are determined, and the middle platform system is controlled to fall back to the first publishing version; in the updating process of the service system, the target interface request information which is transmitted to the middle station system by the service system and is related to the newly added interface data is intercepted according to the newly added interface data, so that the interface request interception can be carried out through the newly added interface data, the interface request corresponding to the newly added interface data is not forwarded to the middle station system, the middle station system is caused to be abnormally thrown, the updating process of the service system is automatic updating, manual participation is not needed, and the publishing efficiency and quality of the service system are improved.

Drawings

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

FIG. 1a is a schematic diagram of a business system interacting with a central system;

FIG. 1b is an online schematic diagram of a central office system and a business system;

Fig. 2 is a flowchart of a method for updating a service system according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a method for updating a service system according to another embodiment of the present invention;

FIG. 4 is a flowchart illustrating steps of another method for updating a service system according to an embodiment of the present invention;

FIG. 5 is a method for synchronously updating a central system and a service system by using a version identification and proxy system according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an updating device of a service system according to an embodiment of the present invention.

Detailed Description

In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

Related noun interpretation in the embodiment of the invention:

SNAPSHOT (snapshot): snapshot generally refers to a technology or a method for capturing and saving images or data at a certain moment, and SNAPSHOT in the embodiment of the present invention represents that the system is in a development iteration state, and a developer can continuously submit codes in development and continuously update the state.

RELEASE ("RELEASE" or "RELEASE"): "release" or "release" generally refers to the public of a product, software, information, or resource, such that it may be used or obtained by the public or a particular group. The present embodiment of the invention represents that the current iteration has been stabilized and has been deployed online (production), i.e., each RELEASE version of the system is cured in stages, without change.

In the field of software development, with the continuous development of technology and continuous change of requirements, software architecture is also continuously evolving. Initial software development was based on a single project, i.e., all of the functionality and business logic were developed and deployed in one project. With the ever-increasing size and increasing complexity of software, microservice architectures have evolved. The micro-service architecture can split a large application into multiple small, mutually independent services, each of which can be independently developed, deployed and extended. With the popularity of micro-service architecture, mid-platform architecture is gaining attention. The middle platform architecture is an architecture mode which further evolves on the basis of a micro-service architecture, abstracts general functions and business logic into middle platform services, and provides unified basic services and supporting capability for various business fields.

In the field of Internet of vehicles, all systems can be abstracted into two types as required, one type is a business system, and the other type is a middle platform system. The service system is a system for independently completing certain service operation, and generally needs to use the capability provided by certain middle station systems and combine the own service of the service system to realize the user requirement. The service system is responsible for specific service support to meet the requirements of users/devices, such as TSP (TELEMATICS SERVICE Provider, internet of vehicles service Provider) can be in butt joint with a vehicle end to complete relevant service processing, and APP-SERVER (application SERVER) and APP are in butt joint to complete relevant service processing of users; the middle platform system is an abstract concept, and comprises a plurality of independently operated systems, each system provides capability support for a specified service, and the middle platform system is a relatively thin, universal and centralized independent system which is split according to the service, for example, a middle platform of a user is only responsible for the service and data processing related to the user, a middle platform of a vehicle is only responsible for the service and data processing related to the vehicle, and other subdivisions such as a file middle platform, a message middle platform and the like. The middle platform system provides various capability supports for the outside (service system), belongs to a platform system, and is relatively universal in design and realization. Fig. 1a is a schematic diagram showing interaction between a service system and a central system. The TSP and the equipment center station in the service system interact with the equipment related service; the APP-SERVER in the service system can interact with the user related service with the user middle station, and the APP-SERVER in the service system can also interact with the user related service with the message middle station; the VHR (Vehicle History Record, vehicle history) of the service system interacts with the user-related services of the user center; the OTA (Over-the-Air Technology) of the business system can interact with the user related business with the user center station, and the OTA (Over-the-Air Technology) of the business system can also interact with the file center station with the file related business.

In the development process, the service system completes communication by referring to the SDK of the middle station system, the SDK encapsulates the externally exposed interface and parameter information of the middle station, and the service system realizes remote call by the interface provided in the SDK. Because the development of the business system and the online (production) have own iteration plans, the development of the middle station system also has own iteration plans, the two can be inconsistent, and the online process often has some problems: service system online (production) deployment problem and version inconsistency problem:

Examples of business system online (production) deployment problems: generally, a business system must wait until the dependent version of the middle system is first brought on line (produced) before the release can be normally deployed. However, in the actual development process, 10 functional modules may be developed and the bug generated by some previous versions may be solved by one iteration of the service system, and only 1 middle platform is required to make synchronous development support call in the iteration; if the business system and the corresponding intermediate station complete development and test preparation are on-line (production), and the intermediate station system is not on-line (production) for 1 latest function, 10 functions are iterated at this time and cannot be normally on-line (production).

Version inconsistency problem examples: during system development, the version typically has two concepts SNAPSHOT and RELEASE. If the initial version of a system is 1.0.0-SNAPSHOT, after one iteration period is finished, a 1.0.0-RELEASE version is generated and all current source codes are solidified, and meanwhile, the development version is increased to 1.0.1-SNAPSHOT, and developers continue to develop in the 1.0.1-SNAPSHOT version. Therefore SNAPSHOT exists in the development and test process, the development environment and the test environment can use SNAPSHOT to conduct joint debugging and testing, and RELEASE represents the formal version on the production line, and the version of software is continuously and iteratively updated.

In one development iteration, the business system and corresponding one or more middle stage systems may need to be developed synchronously, the SNAPSHOT (snapshot) version used in the middle stage system development process is 1.0.1-SNAPSHOT, and the SDK dependency of the middle stage in the same business system reference is 1.0.1-SNAPSHOT used in the development and test processes. The development and test of the service system are finished as soon as possible on line (production), particularly the situation that the iteration function points are more and urgent is related, and the previous version bug is solved; the snapshot version is unstable, so that 1.0.1-SNAPSHOT cannot appear in an online formal environment, namely, the 1.0.1-RELEASE version of the middle station system is required to be online by the service system, but the middle station system on which the current service system depends temporarily does not send the 1.0.1-RELEASE version.

For the above problems, common solutions are as follows:

After waiting for the central station system to be on line with the 1.0.1-RELEASE version, the service system is on line, and the condition that the service system function point or the solved bug is not urgent is possible, and the waiting time is possible for a few days or two weeks.

Secondly, the version of the middle platform referenced by the current service system is rolled back to the last version, namely the version of 1.0.0-RELEASE, after the middle platform system is rolled back, newly developed codes of the latest dependent middle platform (1.0.1-SNAPSHOT) in the SDK are not available, so that the related codes related to the latest interface development/call in the referenced codes are not compiled, and the related codes related to the latest call of the middle platform are temporarily annotated to ensure the compiling; after the latest version (1.0.1-RELEASE) of the waiting platform is online (produced), the service system restores the relevant annotated code postrelease. Therefore, the functional points and the solved bug can be added first, and the related business newly developed by the middle station is relied on for delay adding.

The first mode has long waiting time, the whole research and development of the second mode needs to be carried out twice to online (production) plate making, manual annotation and restoration of related codes are also needed, and a great deal of time is consumed in research and development, namely, the plate making efficiency and quality of the two modes are low.

As shown in fig. 1b, in the iterative development of the TSP of the service system, a function point needs to be synchronously developed and supported by the user's middle station, the TSP is expected to be on line for 3 months and 15 days, and when the TSP is on line, the user's middle station is not on line; the user middle station needs to provide support for TSP, VHR and other business systems in iterative development, and the expected online time and offline time of the user middle station are 3 months and 20 days; in the iterative development of the VHR in the service system, a functional point needs synchronous development support of the user platform, the expected online time is 3 months and 25 days, and when the VHR is online, the user platform is online.

In the embodiment of the invention, the first version information of the middle-stage system can be acquired, and the second version information of the middle-stage system referenced by the service system in the test environment can be acquired; the first version information includes one or more published versions and a snapshot version in development; when the second version information is detected to be a snapshot version, determining newly-added interface data of the middle platform system based on the first publishing version and the snapshot version which are currently used by the middle platform system, and controlling the middle platform system to fall back to the first publishing version; in the updating process of the service system, intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the newly added interface data. Therefore, the service system can be automatically updated without manual intervention, and the service system update failure is avoided by determining newly added interface data and executing interception and applying a mode of combining a static agent and a dynamic agent. Improving the plate-making efficiency and plate-making quality.

Referring to fig. 2, a step flow chart of a service system updating method provided by an embodiment of the present invention relates to a middle platform system of a vehicle and a service system, and specifically may include the following steps:

s201, acquiring first version information of a middle platform system and second version information of the middle platform system referenced by a service system in a test environment; the first version information includes one or more published versions and a snapshot version in development;

in the embodiment of the invention, in the iterative development process of the middle platform system and the service system, version identification can be carried out on the middle platform system and the service system, and particularly, on the one hand, the version identification can acquire the first version information of the middle platform system, and the first version information can comprise each release version released by the middle platform system in the past and a snapshot version in the current iterative development process; on the other hand, the version identification can acquire the second version information of the platform system in the service system test process reference, and the functional online release of the iterative development of the service system needs to depend on the related interface call of the second version information.

In an embodiment of the present invention, obtaining first version information of a central station system includes: creating a monitoring item for detecting the version of the center system for each center system in the vehicle, wherein the monitoring item comprises a code warehouse address of the center system; based on the monitoring item, first version information of the middle platform system is obtained from a code warehouse corresponding to the code warehouse address.

In practical application, the SDK source code (i.e., the first version information) may be obtained from the code repository by setting the monitoring item, where the SDK source code may include and record the SDK code from the initial version 1.0.0-RELEASE to the latest online running.

In an example, after obtaining the SDK source code, the interface differences between the RELEASE versions may be extracted through code reflection analysis, and the interface differences are displayed, where the interface differences may include which interfaces (parameters) are newly added between the versions, which interfaces (parameters) are modified, and which interfaces are deleted.

Code reflectance analysis refers to the process of examining and analyzing metadata of program code to understand its structure, function, dependencies, or other characteristics during programming.

S202, when the second version information is detected to be a snapshot version, determining newly-added interface data of the middle platform system based on a first distribution version and the snapshot version which are currently used by the middle platform system, and controlling the middle platform system to fall back to the first distribution version;

After the first version information and the second version information are acquired, the snapshot version in the first version and the second version information can be matched, whether the second version information is the snapshot version or not is judged, when the second version information is matched with the snapshot version, the second version information is determined to be the snapshot version, and when the second version information is not matched with the snapshot version, the second version information is determined to be the non-snapshot version, but the release version released in the past by the middle platform system is determined.

When the second version information is a snapshot version in the iterative development process of the middle-stage system, the snapshot version is unstable, and the service system updates the release after the release corresponding to the snapshot version is required to be online due to the unstable snapshot version.

In order to avoid delaying the function of urgent online, in the embodiment of the invention, when the second version information is a snapshot version, newly added interface data of the middle platform system can be determined according to the interface difference between the first distribution version and the snapshot version which are currently used by the middle platform system. And then the console system is controlled to fall back to a first distribution version which is a stepwise stable version, so that the service system can perform function update iteration based on the first distribution version.

When the middle platform system carries out rollback operation, the middle platform system can lose related interface codes when the middle platform system is iteratively developed into a snapshot version from a first distribution version.

The static proxy in the embodiment of the invention refers to the proxy of the class and the entity object referenced in the use and the calling process of the new interface of the middle platform, such as the generation of similar codes.

S203, in the process of updating the service system, intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the newly added interface data.

When the middle platform system is retracted to the release version and the service system is updated, an interface calling request can be sent to the middle platform system, so that the middle platform system can be relied on to update the fall. In the embodiment of the invention, the snapshot version is quoted in the test process of the service system, under the condition that the middle system is in rollback, if the function of the iterative update of the service system is a new function or a bug for solving the previous version, the new function and the bug for solving the previous version can directly call the currently rolled-back release version of the middle system to update the release, and when the iterative update function of the service system needs to quote the newly increased interface data with difference between the release version and the snapshot version of the middle system, the middle system is in rollback to the release version, and at the moment, no corresponding interface code exists, if the service system directly sends interface request information for requesting to call an interface to the middle system, the service system cannot be successfully compiled, and the update release fails.

In the embodiment of the invention, a dynamic agent can be set based on the newly added interface data, and the dynamic agent can intercept the interface request information sent by the service data according to the condition, wherein the interception condition is that the target interface request information is intercepted when the interface request information sent by the service system to the middle station system is determined to be the target interface request information related to the newly added interface data. The interface request of the service system is intercepted through the dynamic proxy, so that the interface request which cannot be called is prevented from being sent to the middle platform system, the exception of throwing of the middle platform system is prevented, and smooth compiling and running of the service system are ensured.

The dynamic proxy in the embodiment of the invention refers to the operation of intercepting and rewriting the realization of the service on the existing code.

In an embodiment of the present invention, after S203, the method further includes: generating response data for the intercepted target interface request information according to a preset interception processing rule, and/or forwarding the intercepted target interface request information to a preset interface for processing according to the preset interception processing rule.

The preset interception processing rule in the embodiment of the invention is a processing mode of intercepted target interface request information, and the interception processing rule can be set according to an actual scene, so that the method is not excessively limited in the embodiment of the invention.

The response data can be used for feeding back the processing condition of the current target interface request information, for example, the response data can be set as 'related service in development', and the response data can be used for informing a user that the service system can not be online at present, and the service system can be online only after the middle platform system is developed.

In this embodiment of the present invention, the preset interface may be 404 interface. "404" is an HTTP status code that indicates that the resource requested by the client is not present or found on the server. This typically means that the web page or resource that the user is attempting to access has been deleted, moved, or never exists. When a Web server receives a request, but does not find the resource corresponding to the request URL on its server, the server returns the status code.

In the embodiment of the invention, by identifying the version conditions of the middle platform system and the service system, when the second version information is detected to be the snapshot version, based on the first publishing version and the snapshot version which are currently used by the middle platform system, the newly-added interface data of the middle platform system is determined, and the middle platform system is controlled to fall back to the first publishing version; in the updating process of the service system, the target interface request information which is transmitted to the middle station system by the service system and is related to the newly added interface data is intercepted according to the newly added interface data, so that the interface request interception can be carried out through the newly added interface data, the interface request corresponding to the newly added interface data is not forwarded to the middle station system, the middle station system is caused to be abnormally thrown, the updating process of the service system is automatic updating, manual participation is not needed, and the publishing efficiency and quality of the service system are improved.

Referring to fig. 3, a flowchart illustrating steps of another method for updating a service system according to an embodiment of the present invention may specifically include the following steps:

s301, acquiring first version information of a middle-stage system and second version information of the middle-stage system referenced by a service system in a test environment; the first version information includes one or more published versions and a snapshot version in development;

S302, when the second version information is detected to be a snapshot version, determining newly-added interface data of the middle platform system based on a first distribution version and the snapshot version which are currently used by the middle platform system, and controlling the middle platform system to fall back to the first distribution version;

s303, writing the newly added interface data into a pre-created proxy file, and sending the proxy file to a service system;

After the newly added interface data is determined, a proxy file can be generated, the naming of the proxy file is distinguished from the naming of the original file storing the newly added interface data, the newly added interface data can be written into the proxy file, and the proxy file is sent to a service system to realize static proxy.

S304, in the updating process of the service system, intercepting target interface request information which is related to newly added interface data and is sent to the middle platform system by the service system according to the proxy file;

The service system receives the proxy file, and in the process of updating the service system, the service system needs to execute interface request interception by adopting the proxy file when sending interface request information to the middle station system each time.

S305, when the fact that the release version of the middle platform system is updated from the first release version to the second release version corresponding to the snapshot version is detected, the business system is updated again based on the second release version.

By rollback of the intermediate station system and interception of service system interface requests, the service system can issue smoothly, mainly aiming at bug repair and function independent of the latest intermediate station interface, but the solution of the proxy is not enough to enable the actual intermediate station to generate utility for the newly added interface, and the service system issue can be performed after formally issuing the corresponding intermediate station aiming at the relevant function corresponding to the information of the newly added interface or waiting for the corresponding intermediate station. In the embodiment of the invention, a monitoring task can be further arranged, and the monitoring task is used for polling and monitoring the version update state of the middle station system according to a preset period, and when the fact that the version is updated from the first version to the second version corresponding to the snapshot version is detected, the service system can update the version based on the version updated by the middle station system due to the fact that the function of intercepting the interface request is not online. In other words, the functional online of the service system in the embodiment of the invention belongs to the function of the part of updating online first, and the service system updates online again after the release version of the middle platform system is updated to the second release version aiming at the data of which part depends on the newly added interface data.

In an embodiment of the present invention, updating the service system again based on the second release version includes the following sub-steps:

S11, updating the second version information of the middle platform system referenced by the service system into a second release version;

In practical application, when the middle system completes the update of the release version corresponding to the snapshot version, the service system can update the referenced second version information from the snapshot version to the second release version, and the second release version is a stable version, so that the update of the service system is realized.

S12, deleting the newly added interface data and executing the interception task based on the newly added interface data;

In the embodiment of the invention, the newly added interface data and the interception task corresponding to the newly added interface data can ensure the smooth updating of the service system when the middle system is retracted to the first release version, so that the exception of throwing of the middle system is avoided, and the newly added interface data and the interception task executed based on the newly added interface data can be deleted when the middle system is updated to the second release version, so that the service system can update the service system functions which cannot be realized due to interception before the second release version is completed.

In the embodiment of the invention, the deletion of the newly added interface data and the interception task executed based on the newly added interface data can be realized by deleting the static agent and the dynamic agent.

S13, recompiling the service system based on the second release edition to update the service system.

In the embodiment of the invention, after the service system is recompiled, the construction of a version pipeline of the service system can be restarted; and deleting the monitoring task of the central system.

In the embodiment of the invention, when the middle system is returned to the first release version, partial update of the service system is realized through interception in the update of the service system, and when the middle system is updated to the second release version, the service system can be updated again, and the manual participation is not needed in the update process of the service system, so that the release efficiency and the release quality are improved.

Referring to fig. 4, a flowchart illustrating steps of another method for updating a service system according to an embodiment of the present invention may specifically include the following steps:

s401, acquiring first version information of a middle-stage system and second version information of the middle-stage system referenced by a service system in a test environment; the first version information includes one or more published versions and a snapshot version in development;

S402, when the second version information is detected to be a snapshot version, determining newly-added interface data of the middle platform system based on a first distribution version and the snapshot version which are currently used by the middle platform system, and controlling the middle platform system to fall back to the first distribution version;

After the first version information and the second version information are acquired, the snapshot version in the first version and the second version information can be matched, whether the second version information is the snapshot version or not is judged, when the second version information is matched with the snapshot version, the second version information is determined to be the snapshot version, S402 to S403 are executed, when the second version information is not matched with the snapshot version, the second version information is determined to be not the snapshot version, but the release version which is released in the past by the middle platform system is determined, and S404 is executed.

S403, in the process of updating the service system, intercepting target interface request information which is related to the newly added interface data and is sent to the middle station system by the service system according to the newly added interface data.

S404, when the non-snapshot version of the second version information is detected, judging whether the second version information is the first distribution version currently used by the middle system;

when the second version information of the service system is detected to be the non-snapshot version, it may be further determined whether the second version information is the first release version currently used by the middle system, S405 is executed when the second version information is the first release version currently used by the middle system, and S406 is executed when the second version information is other release versions than the first release version.

S405, when the second version information is the first version of the distribution currently used by the middle platform system, the control service system updates the distribution based on the first version of the distribution;

The first distribution version is a stable version currently used by the middle platform system, so that the business system can directly complete updating distribution of all functions based on the first distribution version.

And S406, when the second version information is other release versions except the first release version, determining interface difference data between the other release versions and the first release version, and updating the release of the service system according to the difference type of the interface difference data.

When the second version information is other release versions except the first release version, the interface difference data of the other release versions and the first release version can be compared, so that the difference type of the interface difference data is determined, and different update release modes can be set according to different difference types.

Specifically, when the difference type is the type of the newly added interface or the field is reduced, the update of the service system is not affected, and the service system can directly update the release based on other release versions.

When the difference type is the difference of the modification field, an adapter can be newly added to carry out adaptation conversion aiming at the source field and the target field, and specifically, the adapter can realize dynamic proxy aiming at the actual request process of a specific interface, and further, when a business system accesses the interface with the modification field, the interface request can be intercepted, and further, the conversion is carried out according to the adaptation rule in the adapter, so that the field modification of the business data is realized. The field modified case may include a field type modification or a field structure modification, e.g., a forward value of 1,0, now changed to boolean true, false.

In the embodiment of the invention, the update and the edition issuing of the service system can be realized through different edition information conditions between the service system and the middle platform system, manual participation is not needed in the whole process, and the edition issuing efficiency and the edition issuing quality of the service system are improved.

Referring to fig. 5, in an embodiment of the present invention, a method for synchronously updating a central system and a service system by using a version identification and proxy system, as shown in fig. 5, relates to a proxy system, where the proxy system is a version identification and proxy system developed in the embodiment of the present invention, and has the main functions of: identifying each version of the middle platform system and the difference between the versions through a connecting code warehouse, and simultaneously confirming whether the version (SNAPSHOT) of the middle platform system referenced by the service system to be released is on line (RELEASE), if the version (second version information) of the service system referenced by the SDK is higher than the target middle platform system (for example, 1.0.1-SNAPSHOT is higher than 1.0.0-RELEASE), smoothly releasing the service system by backing the dependent version and adopting a mode of combining a static agent and a dynamic agent; for the service system using the agent, a detection task can be created to monitor the version of the middle system at any time, if the latest version of the middle system is monitored, the service system refers to the latest formal version, removes the agent, and recompiles the latest function of the service system to be truly on line.

The version identification and proxy system in the embodiment of the invention can have the functions of: 1) Identifying and comparing the on-line (production) SDK versions; 2) Generating a proxy interface and related parameter entity codes through reflection, namely generating static codes by using a static proxy, ensuring compiling, intercepting processing services by using a dynamic proxy, and ensuring operation; 3) Enabling a platform version updating condition in task monitoring; 4) Reconstructing the service system.

Specifically, the version identification and proxy system functions are as follows:

1) Identifying the on-center line (production) SDK version:

The method comprises the steps of firstly creating monitoring items by taking a middle platform system as a unit, recording basic information of all the middle platform systems, including code management warehouse (GIT) addresses, then acquiring SDK source codes from the code management warehouse according to the code management warehouse addresses, wherein the SDK source codes can comprise SDK codes from an initial version 1.0.0-RELEASE to a latest line; and then, the interface differences among the RELEASE versions can be extracted for display through code reflection analysis, wherein the differences comprise which interfaces (parameters) are newly added, which interfaces (parameters) are modified and which interfaces are deleted.

The version identifying function can also determine the SDK (real-time, usually SNAPSHOT) information of a certain middle station referenced by the service system in the test environment (the formal pre-release environment), and compare the SDK information (namely the second version information) with the on-line (production) version (namely the first version information) of the existing middle station system for release reference.

This function corresponds to the get all middle project release case and detail SDK (Software Development Kit ) in FIG. 5.

2) Generating proxy interfaces and related parameter entities (ensuring compilation and operation) by reflection:

In practical application, in the synchronous development process of the middle platform system and the service system, the version conditions of the middle platform system and the service system can be divided into the following categories:

a. The business system references SNAPSHOT version of the current middlebox system:

SNAPSHOT of a certain middle platform system used by a current development version of a service system is as 1.0.1-SNAPSHOT, which is generally the case of synchronous development and iteration of the middle platform system and the service system, and the RELEASE of the last version, namely 1.0.0-RELEASE, is currently used on a corresponding middle platform project line (production). Since the online system cannot use SNAPSHOT (snapshot version is unstable), the RELEASE service system can only return the version of the middle system to 1.0.0-RELEASE, and at this time, the call of the relevant latest code starts to be compiled and does not pass. The service system is compiled through without annotating the code of the relevant code, and the solution is to use a proxy.

The proxy in the version identification and proxy system in the embodiment of the invention can comprise a static proxy and a dynamic proxy, wherein the static proxy refers to the proxy for the class and the entity object referenced in the use and the calling process of the new interface of the middle platform, and generally generates similar codes; the dynamic proxy refers to the operation of intercepting and rewriting the realization of the service on the existing code.

The static agent generated by the service system by using the new interface ensures that compiling passes, but the service system is on line (production) and the related service of the interface still has no intermediate support because the latest formal version of the intermediate is not realized by the related interface on line (production), so that the intermediate throwing abnormality can be prevented by intercepting the request.

Static agent implementation: the static proxy needs to temporarily patch up the interface (parameters) to which the service system is newly referenced. The related codes are not existed on the middle line (production), the service system is required to fall back to the last RELEASE version and is not related codes, the related codes are required to be complemented by a static agent to be compiled, and the complemented codes are transmitted to a code warehouse of the service system for version RELEASE, so that the compiling is ensured to pass.

By means of the version identification module, comparing the difference (i.e. newly added interface data) between the RELEASE version (e.g. 1.0.0-RELEASE) on the (production) line and the SNAPSHOT (e.g. 1.0.1-SNAPSHOT) of the latest intermediate station SDK referenced by the service system, the difference comprising interface information and related interface parameters, and the difference can be presented to the user;

In practical application, a reflection generation mode may be adopted to perform static proxy, specifically, a proxy file name is generated, the proxy file name needs to be different from an original target file (such as proxyxxxinterface. Java), and then all specifically added interfaces and relevant parameters are generated into the proxy file, in this process, it is required to ensure that all interface addresses, parameters, entities, package names and the central system SNAPSHOT (such as 1.0.1-SNAPSHOT) are kept consistent except for class names (such as ProxyXxxInterface). The generation of the reflection on the physical object (i.e. the interface parameter) is relatively simple, a uniform file (including the full path class name) is directly generated, and the content is generated through the reflection.

According to the static agent, the code generated by reflection can ensure that the service system is successfully compiled under the condition of rollback of the dependent version. A static proxy process as shown in section 2.1 of fig. 5.

Dynamic proxy implementation: after the static agent is completed, the interface request is intercepted by AOP (tangential plane oriented), and user-defined processing logic (such as interception processing rules) can be used for the intercepted interface request, so that the interface request cannot be forwarded to a middle system to throw exception, and the processing mode of the intercepted request in the user-defined logic can be a user-defined response result (such as that related business is being developed) or forwarded to other interface processing (such as 404). A dynamic proxy process is shown as 2.2 in fig. 5.

B. The RELEASE version referenced by the service system is the corresponding on-line (production) version of the center station (i.e., the first RELEASE version):

When the version of the middle-stage SDK used by the service system is the RELEASE version, that is, the reference is the stable version of the middle-stage system, only the RELEASE referenced by the service system and the corresponding on-line (production) version of the middle-stage are compared to determine whether the version is a unified version, and if the version is the same version, the version is not affected.

C. the RELEASE version referenced by the business system does not correspond to the on-line (production) version of the center station (i.e., the first RELEASE version):

When the version distinction between the service system reference RELEASE and the on-line (production) version of the middle station only comprises any one or more of newly added interfaces, newly added interface parameters and reduced fields, the general development considers that the compatibility problem does not need to be processed, and the version is not affected.

When the business system references RELEASE, the version of the RELEASE is distinguished from the version of the current online (production) version of the center station as a field modification, wherein the field modification may include a type modification or a structure modification. At this time, a new adapter is needed, the adaptation conversion is performed for the source field and the target field, specifically, the dynamic proxy is performed for the actual request process of the specific interface, when the interface is accessed, the request is intercepted, and the conversion is performed according to the adaptation rule.

3) Enabling task monitoring center version updating:

After the processing of the step 1) and the step 2), the business system can smoothly issue the edition, mainly aiming at bug repair and the function which is irrelevant to the latest intermediate platform interface is on line, but the actual intermediate platform generates utility for the newly added interface through the solution of the proxy after all, and the problem is really solved or the edition is issued formally by the corresponding intermediate platform.

By starting the timing task, the version-making condition of the corresponding middle-stage system is continuously polled, the latest formal version is pulled in a timing manner (such as every 5 minutes), and if the version of the middle-stage system is detected to be updated, the corresponding service system is started to be synchronously updated.

As shown in fig. 5, the TSP may use an agent to come online and initiate a task detection target middle station version.

4) Reconstructing a target service system:

according to the monitoring task, the SDK of the target middle station system can be confirmed to be updated, and then the code branches to be transmitted are prepared for transmitting, wherein the method mainly comprises the following steps: modifying the referenced version of the SDK to the latest version; deleting the prior static agent code and the dynamic agent code; recompilation of the business system; restarting the construction of a plate-issuing pipeline; and deleting the corresponding monitoring version task.

As shown in fig. 5, upon monitoring an on-line version update of the subscriber's midship system, the TSP is upgraded to rely on the SDK version, the pre-delete agent is triggered, and the TSP pipeline is triggered to reissue.

The embodiment of the invention can realize the automatic construction from task monitoring without manual participation in the synchronous iteration process of the service system and the middle system through the version identification and the proxy system, thereby saving the version release period and improving the version release quality.

It should be noted that, for simplicity of description, the method embodiments are depicted as a series of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts are not necessarily required by the embodiments of the invention.

Referring to fig. 6, a schematic structural diagram of an updating device of a service system according to an embodiment of the present invention may specifically include the following modules:

The version identification module 601 is configured to obtain first version information of the middle platform system, and obtain second version information of the middle platform system referenced by the service system in a test environment; the first version information includes one or more published versions and snapshot versions in development;

the version rollback module 602 is configured to determine, when detecting that the second version information is the snapshot version, new interface data of the intermediate system based on a first distribution version currently used by the intermediate system and the snapshot version, and control the intermediate system to rollback to the first distribution version;

And an interface request interception module 603, configured to intercept, according to the new interface data, target interface request information associated with the new interface data, which is sent by the service system to the intermediate system, in the service system update process.

In an embodiment of the invention, the apparatus further comprises:

and the business system re-updating module is used for re-updating the business system based on the second release version when the release version of the middle platform system is detected to be updated from the first release version to the second release version corresponding to the snapshot version.

In an embodiment of the present invention, the service system re-updating module may include the following sub-modules:

a reference version updating sub-module, configured to update second version information of the middle platform system referenced by the service system to the second release version;

The data deleting sub-module is used for deleting the newly-added interface data and the interception task executed based on the newly-added interface data;

And the recompilation sub-module is used for recompilating the business system based on the second release edition so as to update the business system.

In an embodiment of the present invention, the interface request intercepting module 603 may include the following sub-modules:

the agent file creation and transmission sub-module is used for writing the newly added interface data into a pre-created agent file and transmitting the agent file to the service system;

And the proxy file interception sub-module is used for intercepting target interface request information which is related to the newly added interface data and is sent to the middle platform system by the service system according to the proxy file in the updating process of the service system.

In an embodiment of the present invention, the version identification module 601 may include the following sub-modules:

a monitoring item creation sub-module for creating, for each intermediate system in the vehicle, a monitoring item for detecting a version of the intermediate system, the monitoring item including a code warehouse address of the intermediate system;

And the first version information acquisition sub-module is used for acquiring the first version information of the middle platform system from the code warehouse corresponding to the code warehouse address based on the monitoring item.

In an embodiment of the invention, the apparatus further comprises:

the version judging module is used for judging whether the second version information is a first distribution version currently used by the middle platform system or not when the second version information is detected to be not the snapshot version;

The first distribution version module is used for controlling the business system to update the distribution version based on the first distribution version when the second version information is the first distribution version currently used by the middle platform system;

and the other release version module is used for determining interface difference data between the other release versions and the first release version when the second version information is other release versions except the first release version, and updating the release of the service system according to the difference type of the interface difference data.

In an embodiment of the invention, the apparatus further comprises:

The response data generation module is used for generating response data for the intercepted target interface request information according to a preset interception processing rule, and/or the request forwarding module is used for forwarding the intercepted target interface request information to a preset interface for processing according to the preset interception processing rule.

In the embodiment of the invention, by identifying the version conditions of the middle platform system and the service system, when the second version information is detected to be the snapshot version, based on the first publishing version and the snapshot version which are currently used by the middle platform system, newly-added interface data of the middle platform system are determined, and the middle platform system is controlled to fall back to the first publishing version; in the updating process of the service system, target interface request information which is transmitted to the middle platform system by the service system and is related to the new interface data is intercepted according to the new interface data, so that the interface request interception can be carried out through the new interface data, and the interface request corresponding to the new interface data is not forwarded to the middle platform system, so that the middle platform system is abnormal in throwing, and the updating process of the service system is automatic and does not need to be manually participated, thereby improving the publishing efficiency and quality of the service system.

An embodiment of the present invention further provides an electronic device, which may include a processor, a memory, and a computer program stored in the memory and capable of running on the processor, where the computer program when executed by the processor implements a method for updating a service system as described above.

An embodiment of the present invention further provides a computer readable storage medium, where a computer program is stored, where the computer program when executed by a processor implements a method for updating a service system as described above.

For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.

In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.

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

The foregoing describes in detail a method and apparatus for updating a service system, an electronic device, and a storage medium, and specific examples are applied to illustrate the principles and embodiments of the present invention, where the foregoing examples are only used to help understand the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.

Claims

1. A method for updating a service system, the method being characterized by involving a center station system of a vehicle and the service system, the method comprising:

2. The method as recited in claim 1, further comprising:

3. The method of claim 2, wherein the updating the business system again based on the second release version comprises:

4. The method according to claim 1, wherein intercepting, in the service system update process, target interface request information associated with the new interface data, which is sent by the service system to the intermediate system, according to the new interface data, comprises:

5. The method according to any one of claims 1 to 4, wherein the obtaining the first version information of the midship system includes:

6. The method according to claim 1 or 4, further comprising, after obtaining the first version information of the middle stage system and obtaining the second version information of the middle stage system referenced by the service system in a test environment:

7. The method according to any one of claims 1 to 4, further comprising, after intercepting, according to the new interface data, target interface request information associated with the new interface data, which is sent by the service system to the intermediate system, the method further comprising:

8. A service system updating apparatus, characterized by involving a center station system of a vehicle and a service system, comprising:

9. An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, which computer program, when executed by the processor, implements a method of updating a business system according to any one of claims 1 to 7.

10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements a method of updating a business system according to any of claims 1 to 7.