Service update method, device, electronic device and storage medium

Abstract

The present disclosure relates to a service update method, device, electronic device and storage medium, wherein the method comprises: when receiving an update instruction for an original service, obtaining a configuration file of the original service, creating a service to be updated according to the configuration file of the original service, and then updating the service to be updated in response to the update instruction to obtain a target service, and when receiving a release instruction for the target service, setting the status of the target service to an online status, and updating the status of the original service to an invalid status. Since the present disclosure is based on the configuration file of the original service when creating the service to be updated when updating the original service, it is possible to achieve real-time update of the configuration file. In addition, the present disclosure takes the original service offline only after the updated target service is released and online, so the use of the original service will not be affected during the update process, thereby achieving a smooth transition between the original service and the target service.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and in particular to a service updating method, device, electronic device and storage medium. Background Art

[0002] With the development of Internet technology, the application of open platforms is becoming more and more widespread. Open platforms provide API interfaces (Application Programming Interface) and messages to third parties for secondary development. Third parties often need to continuously develop new versions for specific businesses, which leads to continuous version iteration of API interfaces and messages.

[0003] In the related art, for the iterative upgrade of API interfaces and messages, the solution adopted is to launch a new version of the service online to replace the old version, and then modify the corresponding configuration documents.

[0004] However, since it takes a certain amount of time to modify the configuration document, during the upgrade process, the callers of the API interface and the receivers of the message do not have normal services, which affects normal use and user experience. Summary of the invention

[0005] The present disclosure provides a service update method, device, electronic device and storage medium to at least solve the problem in the related art that service update affects the normal use of the service. The technical solution of the present disclosure is as follows:

[0006] According to a first aspect of an embodiment of the present disclosure, a service updating method is provided, including:

[0007] When receiving an update instruction for an original service, obtaining a configuration file of the original service, where the original service is an online service in the open platform;

[0008] Create a service to be updated according to the configuration file of the original service;

[0009] In response to the update instruction, the service to be updated is updated to obtain a target service;

[0010] When a publishing instruction for the target service is received, the state of the target service is set to an online state, and the state of the original service is updated to an invalid state.

[0011] In one of the embodiments, there are multiple original services and target services, and each has a corresponding version identifier; the method also includes: when receiving an offline instruction for any service that is already online, the offline instruction carries the version identifier of the service, and the service is any original service or target service that is already online; updating the status of the service corresponding to the version identifier to an invalid state.

[0012] In one of the embodiments, the method also includes: receiving a rollback request for a historical service, the rollback request carrying a version identifier of the historical service; obtaining a configuration file of the historical service corresponding to the version identifier, and generating a rollback service corresponding to the historical service based on the configuration file of the historical service; executing the rollback request, and updating the status of the rollback service to an online status.

[0013] In one of the embodiments, the method further includes: in response to an account's request to view historical services corresponding to any service, obtaining an iterative service corresponding to any service, wherein the iterative service includes historical services with different version identifiers generated by any service during an iteration process; and displaying the iterative service to the account, wherein the iterative service is used to instruct the account to determine the historical service to be rolled back from the iterative service.

[0014] In one of the embodiments, after updating the status of the rollback service to an online state, the method further includes: obtaining the status of an iterative service corresponding to the historical service; when the status of the iterative service is an online state, updating the status of the iterative service to an invalid state.

[0015] In one of the embodiments, the original service has a corresponding version identifier; after creating the service to be updated according to the configuration file of the original service, the method further includes: generating a version identifier of the target service based on the version identifier of the original service.

[0016] According to a second aspect of an embodiment of the present disclosure, a service updating device is provided, including:

[0017] A service configuration acquisition module, configured to execute, when receiving an update instruction for an original service, acquiring a configuration file of the original service, wherein the original service is a service that has been online in the open platform;

[0018] A service creation module, configured to create a service to be updated according to a configuration file of the original service;

[0019] A service update module, configured to execute in response to the update instruction, update the service to be updated, and obtain a target service;

[0020] The service publishing module is configured to execute, when receiving a publishing instruction for the target service, setting the state of the target service to an online state and updating the state of the original service to an invalid state.

[0021] In one of the embodiments, there are multiple original services and target services, and each has a corresponding version identifier; the device also includes a status update module, which is configured to execute: when receiving an offline instruction for any service that is already online, the offline instruction carries the version identifier of the service, and the service is any original service or target service that is already online; updating the status of the service corresponding to the version identifier to an invalid state.

[0022] In one of the embodiments, the device also includes a service rollback processing module, which is configured to perform: receiving a rollback request for a historical service, the rollback request carrying a version identifier of the historical service; obtaining a configuration file of the historical service corresponding to the version identifier, and generating a rollback service corresponding to the historical service based on the configuration file of the historical service; executing the rollback request, and updating the status of the rollback service to an online status.

[0023] In one of the embodiments, the device also includes a historical service display module, which is configured to perform: in response to an account's request to view the historical service corresponding to any service, obtain an iterative service corresponding to any service, wherein the iterative service includes historical services with different version identifiers generated by any service during an iteration process; and display the iterative service to the account, wherein the iterative service is used to instruct the account to determine the historical service to be rolled back from the iterative service.

[0024] In one of the embodiments, the service rollback processing module is further configured to execute: obtaining the status of the iterative service corresponding to the historical service; when the status of the iterative service is an online status, updating the status of the iterative service to an invalid status.

[0025] In one of the embodiments, the original service has a corresponding version identifier; the device further includes: a version identifier generation module configured to generate a version identifier of the target service based on the version identifier of the original service.

[0026] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the service update method as described in any one of the first aspects above.

[0027] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the service update method as described in any one of the first aspects above.

[0028] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes instructions, and is characterized in that when the instructions are executed by a processor of an electronic device, the electronic device is enabled to execute the service update method as described in any one of the first aspects above.

[0029] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0030] When an update instruction for the original service is received, the configuration file of the original service is obtained, and the service to be updated is created according to the configuration file of the original service. Then, in response to the update instruction, the service to be updated is updated to obtain the target service. When a release instruction for the target service is received, the state of the target service is set to an online state, and the state of the original service is updated to an invalid state. Since in this embodiment, when the original service is updated, the service to be updated is created based on the configuration file of the original service, real-time update of the configuration file can be achieved. In addition, in this embodiment, the original service is taken offline only after the updated target service is released and launched. Therefore, the use of the original service will not be affected during the update process, thereby achieving a smooth transition between the original service and the target service.

[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0033] Figure 1 The present invention is a flowchart of a service updating method according to an exemplary embodiment.

[0034] Figure 2 is a schematic diagram showing updating of a service status according to an exemplary embodiment.

[0035] Figure 3 The invention is a flowchart of a service updating method according to another exemplary embodiment.

[0036] Figure 4 The present invention is a flowchart of a service updating method according to yet another exemplary embodiment.

[0037] Figure 5 is a schematic diagram showing a service update application according to an exemplary embodiment.

[0038] Figure 6 The figure is a block diagram of a service updating device according to an exemplary embodiment.

[0039] Figure 7 It is a block diagram of an electronic device according to an exemplary embodiment.

[0040] Figure 8 is a block diagram of an electronic device according to another exemplary embodiment. DETAILED DESCRIPTION

[0041] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0042] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0043] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0044] The present disclosure provides a service update method, such as Figure 1 As shown, the following steps are included.

[0045] In step S110, when an update instruction for the original service is received, a configuration file of the original service is obtained.

[0046] Among them, the original service is the service that has been launched in the open platform. Open platform refers to the process in the software industry and the Internet where the website's services are packaged into a series of computer-readable data interfaces or function modules that are open to third-party developers. This behavior is called Open API, and the platform that provides Open API is itself called an open platform. The original service can be a data interface or function module that has been packaged and launched in the open platform and can be used by third-party developers. Among them, the online status means that the service has been released in the open platform and can be used normally by third-party developers. When a service is in an invalid state, it means that the service cannot be used. Therefore, in order to facilitate management, each service in the open platform has a corresponding status.

[0047] A configuration file is a computer file. In this embodiment, the configuration file is the computer-executable related parameters and initial settings configured for the service, including but not limited to the basic information of the service, input parameters, output parameters, security information, and sample documents. Update instructions are instructions or commands for updating the original service. For example, when R&D personnel need to upgrade or modify the function of a service in the open platform, they can initiate corresponding update instructions based on the computer device. When the computer device receives an update instruction for a service, it obtains the configuration file of the service. Among them, the computer device can be but is not limited to various personal computers, laptops, smart phones, tablets, Internet of Things devices, portable wearable devices, etc. The computer device can also be a server, such as an independent server or a server cluster composed of multiple servers.

[0048] In step S120, the service to be updated is created according to the configuration file of the original service.

[0049] The service to be updated refers to a service that needs to be functionally upgraded or modified based on the original service. In this embodiment, since the service to be updated is a service obtained by upgrading or modifying the original service, the configuration file of the original service can be directly copied, and the service to be updated can be created based on the copied configuration file of the original service. Since the service to be updated is created by copying the configuration file of the original service, that is, the original service remains unchanged, the use of the original service is not affected in this process.

[0050] In step S130, in response to the update instruction, the service to be updated is updated to obtain the target service.

[0051] Among them, the target service refers to the service obtained after updating the service to be updated created above. In this embodiment, the computer device obtains the configuration file of the original service based on the update instruction of the original service, and creates the service to be updated according to the configuration file of the original service, and then responds to the update instruction to update the service to be updated, thereby obtaining the target service. Specifically, updating the service to be updated can be to modify the corresponding configuration file, such as modifying the basic information, input parameters, output parameters, security information, and sample documents in the configuration file.

[0052] In step S140, when a publishing instruction for a target service is received, the state of the target service is set to an online state, and the state of the original service is updated to an invalid state.

[0053] Among them, the release instruction refers to an instruction or command to release the target service to the open platform. The online state refers to the state in which the corresponding service has been released in the open platform and can be used normally by third-party developers, while the invalid state means that the corresponding service has been offline in the open platform and cannot be used by third-party developers. In this embodiment, when the computer device receives the release instruction for the target service, the target service is released to the open platform, and the state of the target service is set to the online state, so that third-party developers can use the target service normally. Since the target service is an iterative service that is upgraded and transformed from the original service, therefore, after the target service is released in the open platform, the state of the original service that has been online in the open platform can be updated to the invalid state at the same time, that is, the original service of the lower version is taken offline, thereby achieving a smooth transition between the original service and the target service.

[0054] In the above service update method, when an update instruction for the original service is received, the configuration file of the original service is obtained, and the service to be updated is created according to the configuration file of the original service, and then the service to be updated is updated in response to the update instruction to obtain the target service, and when a release instruction for the target service is received, the state of the target service is set to an online state, and the state of the original service is updated to an invalid state. Since in this embodiment, when the original service is updated, the service to be updated is created based on the configuration file of the original service, real-time update of the configuration file can be achieved. In addition, in this embodiment, the original service is taken offline only after the updated target service is released and launched, so the use of the original service will not be affected during the update process, thereby achieving a smooth transition between the original service and the target service.

[0055] In an exemplary embodiment, the original service has a corresponding version identifier; then in step S120, after creating the service to be updated according to the configuration file of the original service, the above method may also include: generating a version identifier of the target service based on the version identifier of the original service. Among them, the version identifier is used to identify a series of services obtained after a service is put into use and has been run for a period of time and has undergone functional upgrades or transformations. Therefore, for the same service with different version identifiers, the corresponding functions or other aspects will be more or less different. The version identifier is usually represented by a number, such as v4.20.11. Since the target service is obtained on the basis of the original service, in this embodiment, the version identifier of the target service is generated based on the version identifier of the original service, that is, it is generated on the basis of the original service. For example, it can be obtained by adding 1 to the version identifier of the original service, or it can also be obtained by updating the version identifier of the original service based on the update rule of the predefined version identifier. In this embodiment, since different services have their own corresponding version identifiers, it is convenient to manage the services.

[0056] In an exemplary embodiment, the original service and the target service both have multiple, and each has a corresponding version identifier, then the above service update method may also include: when receiving an offline instruction for any service that has been online, updating the state of the corresponding service to an invalid state. Wherein, the service includes any original service or target service that has been online. The offline instruction refers to an instruction or command to offline a service that has been online in the open platform. Since each service has a corresponding version identifier, in this embodiment, in order to accurately identify the service that needs to be offline, the version identifier of the corresponding service can be carried in the offline instruction. Specifically, when a user needs to offline a service that has been online in the open platform, an offline instruction carrying the version identifier of the corresponding service that needs to be offline can be initiated. When the computer device receives the offline instruction for the service, the state of the service is updated to an invalid state based on the version identifier of the service that needs to be offline, so that the service is offline from the open platform, that is, the third-party developer can no longer use the service, thereby facilitating the effective management of the services in the open platform.

[0057] In an exemplary embodiment, various states of a service are further described, such as Figure 2As shown, when a user creates a new service in the open platform, he first completes the configuration of the service, that is, fills in the basic information of the service, input parameters, output parameters, security information, sample documents, etc. At this time, the service is in the "editing" state. When the user publishes the service, it becomes the "online" state. Then the user can edit the "online" service again, and the service becomes the "pending update" state. When the user publishes the "pending update" service, it becomes the "online" state. The user can also take the "online" service offline, and the corresponding service becomes the "invalid" state. This embodiment reduces the management cost of services in the open platform by controlling the status of the service.

[0058] In an exemplary embodiment, if Figure 3 As shown, the above service update method may also include the following steps:

[0059] In step S310 , a rollback request for a historical service is received.

[0060] Among them, the rollback request is a request for rolling back the historical service. The rollback request carries the version identifier of the corresponding historical service, that is, the version identifier of the historical service that needs to be rolled back. Specifically, when a service has undergone a series of upgrades and iterations, the latest version of the service is usually used, and the old version of the service is generally directly replaced by the new version of the service, which makes the old version of the service unusable.

[0061] In this embodiment, since each service update is based on the original service to increase the iterative version of the service, and each service has a corresponding version identifier, when it is necessary to roll back to the old version of the service in some scenarios, a corresponding rollback request can be initiated to the computer device, and the version identifier of the historical service to be rolled back can be carried in the rollback request, so as to facilitate the rollback process of the computer device.

[0062] In step S320, a configuration file of the historical service corresponding to the version identifier is obtained, and a rollback service corresponding to the historical service is generated according to the configuration file of the historical service.

[0063] The rollback service is an iterative version of the service created based on the configuration file of the historical service, that is, the configuration file of the rollback service is the same as the configuration file of the historical service that needs to be rolled back. In this embodiment, when the computer device receives a rollback request for the historical service, it obtains the configuration file of the historical service based on the version identifier of the historical service carried in the rollback request, and then generates a rollback service corresponding to the historical service.

[0064] In step S330, the rollback request is executed, and the status of the rollback service is updated to an online status.

[0065] Specifically, after the computer device generates a rollback service corresponding to the historical service, it executes the rollback request and updates the status of the rollback service to an online status, that is, publishes the rollback service to an open platform for use by third-party developers.

[0066] In the above embodiment, by receiving a rollback request for the historical service, the configuration file of the historical service corresponding to the version identifier is obtained, and a rollback service corresponding to the historical service is generated. Then, the rollback request is executed, and the status of the rollback service is updated to an online status to implement the rollback processing of the historical service.

[0067] In an exemplary embodiment, if Figure 4 As shown, in step S310, before receiving the rollback request for the historical service, the above method may further include the following steps:

[0068] In step S410, in response to an account's request to view historical services corresponding to any service, an iterative service corresponding to any service is obtained.

[0069] The iterative service includes the historical services with different version identifiers generated by any service during the iterative process. That is, the iterative service is the service with all different version identifiers generated by a certain service during the iterative process. In this embodiment, when a user needs to view the historical service of a certain service, a request to view the historical service of the service can be initiated, and the computer device responds to the user's request to view the historical service of the service, and then obtains the iterative service corresponding to the service.

[0070] In step S420, the iterative service is displayed to the account.

[0071] Specifically, after the computer device obtains the iterative service corresponding to the historical service, it can display the corresponding iterative service to the user, so that the user can not only view each version of the historical service, but also select the historical service that needs to be rolled back from the iterative service for rollback, thereby improving the user experience.

[0072] In an exemplary embodiment, in step S330, after updating the status of the rollback service to the online state, the above service update method may further include: obtaining the status of the iterative service corresponding to the historical service, and when the status of the iterative service is the online state, updating the status of the iterative service to the invalid state. Usually, in some scenarios, for each service, only a service with a version identifier is allowed to go online. Therefore, in this embodiment, when the computer device executes the above rollback request and updates the status of the rollback service corresponding to a historical service to the online state, the status of the iterative service corresponding to the historical service that is currently in the online state should be updated to the invalid state, that is, the iterative service corresponding to the historical service that is in the online state should be taken offline, thereby achieving flexible and effective management of service online and service offline.

[0073] In an exemplary embodiment, if Figure 5 As shown, the above service update method is further described below. This embodiment introduces the concept of iterative version to separate the status of the iterative version from the status of the original service. The specific update process is as follows:

[0074] When a user creates a new service in the open platform, he can create an iterative version of the service (i.e., the original service) with a status of "under editing", and then he can edit and improve the service. If the user puts the original service under "under editing" online, the original service becomes "online". After that, the user can take the original service offline, and the original service becomes "invalidated". When the user needs to modify the original service that has been online, the original iterative version of the original service remains unchanged, and a new iterative version of the service to be updated (i.e., the target service) is added to the background. The version identifier of the target service is increased by 1 based on the version identifier corresponding to the original service. At this time, the target service is in the "to be updated" state. When the user publishes the target service, the target service is updated to the online state. Then the user can take the online target service offline, and the target service becomes "invalidated".

[0075] In some scenarios, when only one version of the same service is allowed to go online, when the corresponding new version of the service goes online, the status of the corresponding old version is automatically updated to "invalidated".

[0076] In some other scenarios, there may be a need for version rollback. Therefore, in this embodiment, the user can view the historical iteration version of any service and roll back a historical iteration version of the task. In the specific processing process, the background can create a new iteration version for the historical iteration version that needs to be rolled back, and copy all the information of the historical iteration version selected by the user to the new iteration version. By launching this iteration version, the service rollback is achieved.

[0077] In the above service update method, since when the original service is updated, the service to be updated is created based on the configuration file of the original service, real-time update of the configuration file can be achieved. In addition, the original service is taken offline only after the updated target service is released online. Therefore, the use of the original service will not be affected during the update process, thereby achieving a smooth transition between the original service and the target service, and enabling viewing and rollback of various versions of services, which is conducive to flexible management and control of services.

[0078] It should be understood that although Figure 1-Figure 5 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1-Figure 5 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0079] It can be understood that the same / similar parts between the various embodiments of the above method in this specification can refer to each other, and each embodiment focuses on the differences from other embodiments. For related points, please refer to the description of other method embodiments.

[0080] Figure 6 FIG. 1 is a block diagram of a service updating device according to an exemplary embodiment. Figure 6 The device includes a service configuration acquisition module 602, a service creation module 604, a service update module 606 and a service publishing module 608.

[0081] The service configuration acquisition module 602 is configured to acquire a configuration file of the original service when receiving an update instruction for the original service, wherein the original service is a service that has been online in the open platform;

[0082] A service creation module 604 is configured to create a service to be updated according to a configuration file of the original service;

[0083] The service update module 606 is configured to execute in response to the update instruction, update the service to be updated, and obtain the target service;

[0084] The service publishing module 608 is configured to execute, when receiving a publishing instruction for the target service, setting the state of the target service to an online state and updating the state of the original service to an invalid state.

[0085] In an exemplary embodiment, there are multiple original services and target services, and each has a corresponding version identifier; the device also includes a status update module, which is configured to execute: when an offline instruction for any service that is already online is received, the offline instruction carries the version identifier of the service, and the service is any original service or target service that is already online; the status of the service corresponding to the version identifier is updated to an invalid state.

[0086] In an exemplary embodiment, the device also includes a service rollback processing module, which is configured to perform: receiving a rollback request for a historical service, the rollback request carrying a version identifier of the historical service; obtaining a configuration file of the historical service corresponding to the version identifier, and generating a rollback service corresponding to the historical service based on the configuration file of the historical service; executing the rollback request, and updating the status of the rollback service to an online status.

[0087] In an exemplary embodiment, the device also includes a historical service display module, which is configured to perform: in response to an account's request to view the historical service corresponding to any service, obtain an iterative service corresponding to any service, wherein the iterative service includes historical services with different version identifiers generated by any service during an iteration process; and display the iterative service to the account, wherein the iterative service is used to instruct the account to determine the historical service to be rolled back from the iterative service.

[0088] In an exemplary embodiment, the service rollback processing module is further configured to execute: obtaining the status of the iterative service corresponding to the historical service; when the status of the iterative service is an online state, updating the status of the iterative service to an invalid state.

[0089] In an exemplary embodiment, the original service has a corresponding version identifier; the device further includes: a version identifier generation module configured to generate a version identifier of the target service based on the version identifier of the original service.

[0090] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0091] Figure 71 is a block diagram of an electronic device Z00 for service update according to an exemplary embodiment. For example, the electronic device Z00 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0092] Reference Figure 7 The electronic device Z00 may include one or more of the following components: a processing component Z02, a memory Z04, a power component Z06, a multimedia component Z08, an audio component Z10, an input / output (I / O) interface Z12, a sensor component Z14, and a communication component Z16.

[0093] The processing component Z02 generally controls the overall operation of the electronic device Z00, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component Z02 may include one or more processors Z20 to execute instructions to complete all or part of the steps of the above-described method. In addition, the processing component Z02 may include one or more modules to facilitate interaction between the processing component Z02 and other components. For example, the processing component Z02 may include a multimedia module to facilitate interaction between the multimedia component Z08 and the processing component Z02.

[0094] The memory Z04 is configured to store various types of data to support operations on the electronic device Z00. Examples of such data include instructions for any application or method operating on the electronic device Z00, contact data, phone book data, messages, pictures, videos, etc. The memory Z04 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, or graphene memory.

[0095] The power supply assembly Z06 provides power to various components of the electronic device Z00. The power supply assembly Z06 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device Z00.

[0096] The multimedia component Z08 includes a screen that provides an output interface between the electronic device Z00 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component Z08 includes a front camera and / or a rear camera. When the electronic device Z00 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0097] The audio component Z10 is configured to output and / or input audio signals. For example, the audio component Z10 includes a microphone (MIC), and when the electronic device Z00 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory Z04 or sent via the communication component Z16. In some embodiments, the audio component Z10 also includes a speaker for outputting an audio signal.

[0098] I / O interface Z12 provides an interface between processing component Z02 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0099] The sensor assembly Z14 includes one or more sensors for providing various aspects of status assessment for the electronic device Z00. For example, the sensor assembly Z14 can detect the open / closed state of the electronic device Z00, the relative positioning of the components, such as the display and keypad of the electronic device Z00, and the sensor assembly Z14 can also detect the position change of the electronic device Z00 or the components of the electronic device Z00, the presence or absence of contact between the user and the electronic device Z00, the orientation or acceleration / deceleration of the device Z00 and the temperature change of the electronic device Z00. The sensor assembly Z14 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly Z14 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly Z14 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0100] The communication component Z16 is configured to facilitate wired or wireless communication between the electronic device Z00 and other devices. The electronic device Z00 can access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component Z16 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component Z16 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0101] In an exemplary embodiment, the electronic device Z00 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0102] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory Z04 including instructions, and the above instructions can be executed by a processor Z20 of the electronic device Z00 to complete the above method. For example, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0103] In an exemplary embodiment, a computer program product is further provided. The computer program product includes instructions. The instructions can be executed by the processor Z20 of the electronic device Z00 to implement the above method.

[0104] Figure 8 is a block diagram of an electronic device S00 for service update according to an exemplary embodiment. For example, the electronic device S00 may be a server. Figure 8 The electronic device S00 includes a processing component S20, which further includes one or more processors, and a memory resource represented by a memory S22 for storing instructions executable by the processing component S20, such as an application. The application stored in the memory S22 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component S20 is configured to execute the instructions to perform the above method.

[0105] The electronic device S00 may further include: a power supply component S24 configured to perform power management of the electronic device S00, a wired or wireless network interface S26 configured to connect the electronic device S00 to a network, and an input / output (I / O) interface S28. The electronic device S00 may operate based on an operating system stored in the memory S22, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD or the like.

[0106] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory S22 including instructions, and the above instructions can be executed by a processor of the electronic device S00 to complete the above method. The storage medium can be a computer-readable storage medium, for example, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0107] In an exemplary embodiment, a computer program product is further provided. The computer program product includes instructions. The instructions can be executed by a processor of the electronic device S00 to complete the above method.

[0108] It should be noted that the above-mentioned devices, electronic devices, computer-readable storage media, computer program products, etc. may also include other implementation methods according to the description of the method embodiments. The specific implementation methods can refer to the description of the relevant method embodiments, which will not be described one by one here.

[0109] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

[0110] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A service update method, characterized in that: The method comprises: When receiving an update instruction for the original service, obtaining a configuration file of the original service, wherein the original service is an online service in the open platform, and the configuration file is computer-executable related parameters and initial settings configured for the original service; Create a service to be updated according to the configuration file of the original service; In response to the update instruction, the service to be updated is updated to obtain a target service; When receiving a publishing instruction for the target service, setting the state of the target service to an online state, and updating the state of the original service to an invalid state; There are multiple original services and target services, and each has a corresponding version identifier; the method also includes: when receiving an offline instruction for any service that is already online, the offline instruction carries the version identifier of the service, and the service is any original service or target service that is already online; updating the status of the service corresponding to the version identifier to an invalid state.

2. The method according to claim 1, characterized in that The method further comprises: Receiving a rollback request for a historical service, wherein the rollback request carries a version identifier of the historical service; Obtaining a configuration file of a historical service corresponding to the version identifier, and generating a rollback service corresponding to the historical service according to the configuration file of the historical service; The rollback request is executed, and the status of the rollback service is updated to an online status.

3. The method according to claim 2, characterized in that The method further comprises: In response to a request from an account to view historical services corresponding to any service, acquiring iterative services corresponding to the any service, the iterative services including historical services with different version identifiers generated by the any service during an iteration process; The iterative service is displayed to the account, and the iterative service is used to instruct the account to determine a historical service to be rolled back from the iterative service.

4. The method according to claim 3, characterized in that After updating the status of the rollback service to an online status, the method further includes: Obtaining the status of the iterative service corresponding to the historical service; When the status of the iterative service is an online status, the status of the iterative service is updated to an invalid status.

5. The method according to claim 1, characterized in that The original service has a corresponding version identifier; after creating the service to be updated according to the configuration file of the original service, the method further includes: The version identifier of the target service is generated based on the version identifier of the original service.

6. A service updating device, characterized in that: include: A service configuration acquisition module, configured to acquire a configuration file of the original service when receiving an update instruction for the original service, wherein the original service is a service that has been online in the open platform, and the configuration file is a computer-executable related parameter and initial setting configured for the original service; A service creation module, configured to create a service to be updated according to a configuration file of the original service; A service update module, configured to execute in response to the update instruction, update the service to be updated, and obtain a target service; The service publishing module is configured to execute, when receiving a publishing instruction for the target service, setting the state of the target service to an online state and updating the state of the original service to an invalid state; There are multiple original services and target services, and each has a corresponding version identifier; the device also includes a status update module, which is configured to execute: when an offline instruction for any service that is already online is received, the offline instruction carries the version identifier of the service, and the service is any original service or target service that is already online; the status of the service corresponding to the version identifier is updated to an invalid state.

7. The device according to claim 6, characterized in that The device also includes a service rollback processing module, which is configured to execute: Receiving a rollback request for a historical service, wherein the rollback request carries a version identifier of the historical service; Obtaining a configuration file of a historical service corresponding to the version identifier, and generating a rollback service corresponding to the historical service according to the configuration file of the historical service; The rollback request is executed, and the status of the rollback service is updated to an online status.

8. The device according to claim 7, characterized in that The device also includes a historical service display module, which is configured to execute: In response to an account's request to view historical services corresponding to any service, acquiring iterative services corresponding to the any service, the iterative services including historical services with different version identifiers generated by the any service during an iteration process; The iterative service is displayed to the account, and the iterative service is used to instruct the account to determine a historical service to be rolled back from the iterative service.

9. The device according to claim 8, characterized in that The service rollback processing module is further configured to execute: Obtaining the status of the iterative service corresponding to the historical service; When the status of the iterative service is an online status, the status of the iterative service is updated to an invalid status.

10. The device according to claim 6, characterized in that The original service has a corresponding version identifier; the device also includes: The version identification generation module is configured to generate the version identification of the target service based on the version identification of the original service.

11. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the service update method according to any one of claims 1 to 5.

12. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the service updating method according to any one of claims 1 to 5.

13. A computer program product, comprising instructions, characterized in that: When the instruction is executed by a processor of an electronic device, the electronic device is enabled to execute the service updating method as described in any one of claims 1 to 5.

Images