Method, device and electronic device for starting personalized service instance
By pre-deploying personalized service instances and establishing a user list, the problem of high development costs for customized personalized services is solved. This allows multiple users' personalized needs to be met without affecting other users' usage, thus improving development efficiency and user experience.
Patent Information
- Application Number
- CN202210994010.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-18
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-08-18
AI Technical Summary
In the current technology, the development of personalized services is costly and time-consuming, and cannot meet user needs in a timely manner.
Pre-deploy personalized service instances and establish corresponding user lists. Determine whether to start the personalized service instance based on the user identifier in the user request to avoid affecting the normal use of other users.
Reduce development costs, improve development efficiency, meet the personalized needs of multiple users, and enhance user experience.
Smart Images

Figure CN115361436B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of financial technology and other related technical fields, and specifically, to a method, device and electronic device for starting a personalized service instance. Background Art
[0002] SaaS (Software-as-a-Service) is a technical method for providing software services through the Internet. Among them, SaaS platform suppliers will deploy application software on their own servers, and then customers can purchase the required software services from suppliers through the Internet according to actual work needs, and obtain the services provided by SaaS platform suppliers through the Internet. In other words, in the application scenario of SaaS, multiple customers will use the same set of SaaS services at the same time.
[0003] With the development of enterprise informatization, the general SaaS platform can no longer meet the personalized needs of enterprises. Since SaaS products use a multi-tenant architecture, how to better meet the personalized needs of each customer has become the key to affecting the user experience. In the prior art, when users put forward personalized needs, customized development is usually provided to users based on the personalized needs. However, this solution will lead to high development costs. At the same time, due to the long time cycle of customized development, it will also lead to the problem of not being able to meet the personalized needs of users in a timely manner.
[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention
[0005] The embodiments of the present application provide a method, device and electronic device for starting a personalized service instance, so as to at least solve the technical problem in the prior art of high cost of customized development of personalized services.
[0006] According to one aspect of an embodiment of the present application, a method for starting a personalized service instance is provided, comprising: obtaining a user request, wherein the user request includes at least a user identifier and a main service instance identifier, and the main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; running the main service instance, and determining a personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-general service instance; obtaining a user list corresponding to the personalized service instance, wherein the user list includes multiple target user identifiers; detecting whether the user identifier is included in the multiple target user identifiers in the user list; and starting and running the personalized service instance when the user identifier is included in the user list.
[0007] Furthermore, the personalized service instance startup method further includes: after detecting whether the multiple target user identifiers in the user list include the user identifier, if the user identifier is not included in the user list, prohibiting the startup of the personalized service instance and continuing to execute the main service instance.
[0008] Furthermore, the method for starting a personalized service instance also includes: receiving a configuration request before running the main service instance and determining a personalized service instance associated with the main service instance during the running of the main service instance, wherein the configuration request is used to configure the personalized service instance based on the main service instance; obtaining the program code of the main service instance according to the configuration request, and determining the interface location in the program code, wherein the interface location is the location where the personalized service instance interacts with the main service instance for information.
[0009] Furthermore, the method for starting a personalized service instance also includes: parsing the business logic of the program code; decoupling the program code into multiple sub-program codes according to the business logic, wherein each sub-program code corresponds to a sub-business logic in the business logic; determining a target sub-program code from the multiple sub-program codes according to business scenario information and the sub-business logic corresponding to each sub-program code; and determining an interface location according to the location of the target sub-program code in the program code.
[0010] Furthermore, the method for starting the personalized service instance also includes: after determining the interface position according to the position of the target subprogram code in the program code, generating a calling interface at the interface position, wherein the calling interface is used to associate the personalized service instance with the main service instance.
[0011] Furthermore, the method for starting a personalized service instance also includes: before obtaining a user list corresponding to the personalized service instance, obtaining an interface identifier of a calling interface and a service identifier of the personalized service instance; generating an initial user list based on the interface identifier and the service identifier; receiving a user adding request, wherein the user adding request includes at least a service identifier, a target user identifier and an interface identifier; adding the target user identifier to the initial user list based on the user adding request to obtain a user list, wherein the user corresponding to the target user identifier has the authority to use the personalized service instance.
[0012] Furthermore, the method for starting a personalized service instance also includes: obtaining update information of the main service instance; detecting whether there is conflicting information between the update information and the personalized service instance; if there is no conflicting information between the update information and the personalized service instance, updating the main service instance according to the update information; if there is conflicting information between the update information and the personalized service instance, identifying target information in the update information, wherein the target information is information in the update information other than the conflicting information; and updating the main service instance according to the target information.
[0013] Furthermore, the method for starting a personalized service instance also includes: after updating the main service instance according to the target information, generating prompt information according to the conflict information and the target information, and sending the prompt information to the target account, wherein the target account is an account for managing the main service instance.
[0014] According to another aspect of an embodiment of the present application, a device for starting a personalized service instance is also provided, including: a first acquisition module, used to obtain a user request, wherein the user request includes at least a user identifier and a main service instance identifier, and the main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; a determination module, used to run the main service instance, and determine the personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-general service instance; a second acquisition module, used to obtain a user list corresponding to the personalized service instance, wherein the user list contains multiple target user identifiers; a detection module, used to detect whether the user identifier is included in the multiple target user identifiers in the user list; and a startup module, used to start and run the personalized service instance when the user identifier is included in the user list.
[0015] According to another aspect of an embodiment of the present application, a computer-readable storage medium is further provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned method for starting a personalized service instance when running.
[0016] According to another aspect of the example of the present application, an electronic device is also provided, which includes one or more processors; a memory for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors are implemented to run the programs, wherein the program is configured to execute the above-mentioned startup method of the personalized service instance at runtime.
[0017] In the present application, a personalized service instance is pre-deployed, and a corresponding user list is established for the personalized service instance. After obtaining a user request, the main service instance is run, and the personalized service instance associated with the main service instance is determined during the running of the main service instance. Then, the user list corresponding to the personalized service instance is obtained, and it is detected whether the user identifier is included in the multiple target user identifiers in the user list. When the user identifier is included in the user list, the personalized service instance is started and run. Among them, the user request includes at least a user identifier and a main service instance identifier. The main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; the personalized service instance is a pre-deployed non-general service instance; and the user list contains multiple target user identifiers.
[0018] As can be seen from the above content, in this application, a personalized service instance can be pre-deployed, and a corresponding user list can be established for the personalized service instance. As long as the user ID in the user request exists in the user list, it means that the user corresponding to the user ID has the authority to use the personalized service instance, thereby starting the personalized service instance. If the user ID in the user request does not exist in the user list, starting the personalized service instance is prohibited, thereby achieving the purpose of satisfying the personalized call needs of multiple users through one personalized service instance while ensuring that the normal use of the main service instance by other users is not affected, which not only reduces development costs, but also saves development time and achieves the effect of improving development efficiency.
[0019] It can be seen that through the technical solution of the present application, the purpose of using the same personalized service instance to meet the different personalized needs of multiple users is achieved, thereby achieving the effect of improving the user experience and further solving the technical problem of high customized development cost of personalized services in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0021] Figure 1 is a flowchart of an optional method for starting a personalized service instance according to an embodiment of the present application;
[0022] Figure 2 is a schematic diagram of an optional service instance management system according to an embodiment of the present application;
[0023] Figure 3 is a schematic diagram of a user adding request according to an embodiment of the present application;
[0024] Figure 4 is a flow chart of an optional method for starting a personalized service instance according to an embodiment of the present application;
[0025] Figure 5 is a schematic diagram of an optional starting device for a personalized service instance according to an embodiment of the present application;
[0026] Figure 6 is a schematic diagram of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0027] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.
[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application 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 interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0029] In addition, it should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data 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. For example, an interface is set between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.
[0030] Example 1
[0031] According to an embodiment of the present application, an embodiment of a method for starting a personalized service instance is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0032] Figure 1 is a flowchart of an optional method for starting a personalized service instance according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:
[0033] Step S101, obtaining a user request.
[0034] In step S101, the user request includes at least a user identifier and a primary service instance identifier, and the primary service instance corresponding to the primary service instance identifier is a pre-deployed general service instance.
[0035] In an optional embodiment, a service instance management system can be used as the execution subject of the method for starting the personalized service instance in the embodiment of the present application. Figure 2 A schematic diagram of an optional service instance management system according to an embodiment of the present application is shown. Figure 2 As shown, the technical solution of the present application is used to solve the problem of dynamic personalized configuration of tenants based on the SaaS multi-tenant model. In the SaaS multi-tenant model, the service instance management system in the present application includes both the platform side and the tenant side, wherein the platform side project is independently deployed to provide tenant management, customized configuration management and other functions, and the tenant side can be divided into main service instances and personalized service instances according to the functional division. It should be noted that the number of main service instances can be multiple, and the number of personalized service instances can also be multiple. As Figure 2 As shown, the main service instance is a general service instance, that is, each user has the authority to use the main service instance, and the personalized service instance is opened separately for individual users.
[0036] Optionally, since there can be multiple primary service instances, in order to accurately start the primary service instance, the user request includes not only the user identifier but also the primary service instance identifier, where the primary service instance identifier is a unique identifier of the primary service instance, and different primary service instances can be distinguished by this identifier.
[0037] Step S102: running the main service instance, and determining a personalized service instance associated with the main service instance during the running of the main service instance.
[0038] In step S102, the personalized service instance is a pre-deployed non-universal service instance. Specifically, there is an association relationship between the personalized service instance and the main service instance in the present application, and the personalized service instance can be started during the operation of the main service instance. For example, personalized service instance 1 and personalized service instance 2 are associated with main service instance A. When main service instance A runs to the first node, personalized service instance 1 can be called to start, and when main service instance A runs to the second node, personalized service instance 2 can be called to start, wherein the first node and the second node are different nodes.
[0039] In addition, it should be noted that multiple personalized service instances can call each other, thereby further reducing development costs and improving development efficiency. For example, the main service instance A is a transfer service instance. In the early stage, in order to meet the personalized needs of user A, the developer pre-deployed personalized service instance 1, where personalized service instance 1 is a service instance for decrypting encrypted information. On this basis, user B proposed a personalized demand for security detection of financial information. Since the premise of financial information security detection is to decrypt encrypted information, in order to improve development efficiency, the developer can combine personalized service instance 1 and only develop a personalized service instance 2 that performs security detection based on the decrypted information. By calling personalized service instance 1 and personalized service instance 2 in the operation process of the main service instance A, the personalized needs of user B can be met, which not only saves development costs, but also improves the reusability of personalized service instances.
[0040] Step S103: Obtain a user list corresponding to the personalized service instance.
[0041] In step S103, the user list includes multiple target user identifiers. Specifically, for each personalized service instance, there is a corresponding user list, wherein the user corresponding to the target user identifier in the user list is a user who has the authority to use the personalized service instance. It should be noted that the user list can be accessed through the tenant management function in the service instance management system.
[0042] Step S104, detecting whether the user identifier is included in the multiple target user identifiers in the user list;
[0043] Step S105: when the user list contains the user identification, start and run the personalized service instance.
[0044] Optionally, the user identifier can be understood as the user ID. Assuming that the user identifier in the user request is user ID1, and the main service instance identifier is main service instance A, when the main service instance A runs to the first node, the service instance management system will obtain the user list 1 corresponding to the personalized service instance 1. If the user list 1 contains user ID1, the service instance management system will start the personalized service instance 1, so that the user corresponding to user ID1 can use the services provided by the personalized service instance 1.
[0045] It should be noted that with the development of enterprise informatization, the general SaaS platform can no longer meet the personalized needs of enterprises. Since SaaS products use a multi-tenant architecture, how to better meet the personalized needs of each customer has become the key to affecting the user experience. Traditional software usually adopts a customized method to meet the personalized needs of users, which can of course also be adopted for SaaS software. However, compared with traditional software, SaaS needs to be updated and customized according to changes in needs during the use of the software, and the customization should not affect the use of other users, and the SaaS customization process must be simple and easy so that users can complete it by themselves. Therefore, these differences from traditional software make SaaS applications more complex in technical design, and the development cost is also higher than that of traditional software.
[0046] The present application establishes a corresponding user list for the personalized service instance. As long as the user ID is in the user list, the user corresponding to the user ID can use the personalized service instance, thereby achieving the purpose of one personalized service instance simultaneously meeting the personalized calling needs of multiple users, which not only reduces development costs but also shortens the development cycle.
[0047] Based on the contents of the above steps S101 to S105, it can be known that in this application, a personalized service instance is pre-deployed, and a corresponding user list is established for the personalized service instance. After obtaining the user request, the main service instance is run, and the personalized service instance associated with the main service instance is determined during the running of the main service instance, and then the user list corresponding to the personalized service instance is obtained, and it is detected whether the user identifier is included in the multiple target user identifiers in the user list. When the user identifier is included in the user list, the personalized service instance is started and run. Among them, the user request includes at least the user identifier and the main service instance identifier, and the main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; the personalized service instance is a pre-deployed non-general service instance; and the user list contains multiple target user identifiers.
[0048] As can be seen from the above content, in this application, a personalized service instance can be pre-deployed, and a corresponding user list can be established for the personalized service instance. As long as the user ID in the user request exists in the user list, it means that the user corresponding to the user ID has the authority to use the personalized service instance, thereby starting the personalized service instance. If the user ID in the user request does not exist in the user list, starting the personalized service instance is prohibited, thereby achieving the purpose of satisfying the personalized call needs of multiple users through one personalized service instance while ensuring that the normal use of the main service instance by other users is not affected, which not only reduces development costs, but also saves development time and achieves the effect of improving development efficiency.
[0049] It can be seen that through the technical solution of the present application, the purpose of using the same personalized service instance to meet the different personalized needs of multiple users is achieved, thereby achieving the effect of improving the user experience and further solving the technical problem of high customized development cost of personalized services in the prior art.
[0050] In an optional embodiment, when the user list does not contain the user identifier, the service instance management system prohibits starting the personalized service instance and continues to execute the main service instance.
[0051] Optionally, still taking the main service instance as main service instance A, the user identifier in the user request is user ID1. When the main service instance A runs to the second node, the service instance management system will obtain the user list 2 corresponding to the personalized service instance 2. If the user list 2 does not contain user ID1, the service instance management system will prohibit the startup of personalized service instance 2 and continue to execute the subsequent processes of the main service instance.
[0052] It is easy to notice that user list 2 does not include user ID 1, which means that the user corresponding to user ID 1 has not activated personalized service instance 2. Therefore, prohibiting the startup of personalized service instance 2 at the second node can make the user corresponding to user ID 1 unaware of the existence of personalized service instance 2, thereby ensuring that it will not affect the user's normal use of main service instance A.
[0053] In an optional embodiment, before running the main service instance and determining the personalized service instance associated with the main service instance during the running of the main service instance, the service instance management system first receives a configuration request, wherein the configuration request is used to configure the personalized service instance based on the main service instance. Then, the service instance management system obtains the program code of the main service instance according to the configuration request, and determines the interface position in the program code, wherein the interface position is the position where the personalized service instance interacts with the main service instance.
[0054] Optionally, before calling the personalized service instance, it is necessary to pre-deploy the personalized service instance and determine the association relationship between the personalized service instance and the main service instance. Specifically, the service instance management system will first receive a configuration request, wherein the configuration request contains at least the main service instance identifier and the service identifier of the personalized service instance, and determines which personalized service instance the configuration request is based on based on which main service instance to configure through the main service instance identifier and the service identifier. Assuming that the configuration request is to associate the main service instance B with the personalized service instance 4, the service instance management system needs to first analyze the program code of the main service instance B and determine the interface location associated with the personalized service instance 4.
[0055] In an optional embodiment, the configuration request includes at least business scenario information corresponding to the personalized service instance, and the service instance management system analyzes the business logic of the program code, and then decouples the program code into multiple sub-program codes according to the business logic, wherein each sub-program code corresponds to a sub-business logic in the business logic. Finally, the service instance management system determines the target sub-program code from the multiple sub-program codes according to the business scenario information and the sub-business logic corresponding to each sub-program code, and determines the interface position according to the position of the target sub-program code in the program code.
[0056] Optionally, still taking the main service instance B as an example, after obtaining the program code of the main service instance B, the service instance management system can parse the business logic of the program code. For example, the business logic of the main program instance B is the business logic for implementing transaction transfers. On this basis, the service instance management system decouples the program code into multiple sub-program codes according to the business logic, and each sub-program code corresponds to a sub-business logic in the business logic. For example, the program code is decoupled into three sub-program codes. The sub-business logic of the first sub-program code is to verify the payment object and payment funds, the sub-business logic of the second sub-program code is to verify the payment object information, and the sub-business logic of the third sub-program code is to perform a security check on the fund transaction.
[0057] Further, assuming that the business scenario information of personalized service instance 4 is to encrypt the payment object information and payment funds information in the transaction transfer, then based on the business scenario information, the service instance management system can determine that the first subroutine code is the target subroutine code, and determine that the end of the first subroutine code is the interface position.
[0058] In an optional embodiment, after determining the interface position according to the position of the target subprogram code in the program code, the service instance management system generates a calling interface at the interface position, wherein the calling interface is used to associate the personalized service instance with the main service instance.
[0059] Optionally, the present application utilizes a calling interface to realize the association between the main service instance and the personalized service instance. It should be noted that in order to ensure that no changes are made to the code of the main service instance, although the calling interface is generated at the interface location, the relevant code of the calling interface is deployed in the personalized service instance and will not affect the program code of the main service instance. The specific method can be to use the aspect-oriented programming principle to set an entry point (i.e., a calling interface) in the service layer of the personalized service instance.
[0060] In an optional embodiment, before obtaining the user list corresponding to the personalized service instance, the service instance management system obtains the interface identifier of the calling interface and the service identifier of the personalized service instance, and generates an initial user list according to the interface identifier and the service identifier, and then after receiving the user adding request, adds the target user identifier to the initial user list according to the user adding request to obtain the user list. The user adding request includes at least the service identifier, the target user identifier and the interface identifier; the user corresponding to the target user identifier has the authority to use the personalized service instance.
[0061] Optional, Figure 3 A schematic diagram of a user adding request according to an embodiment of the present application is shown, such as Figure 3 As shown, when it is necessary to grant a user the permission to use a personalized service instance, the administrator can submit a user addition request in the service instance management system, wherein the user addition request includes at least the service identifier of the personalized service instance, the main service instance identifier of the main service instance, and the target user identifier used to represent the user. After the service instance management system receives the user addition request, the service instance management system will add the target user identifier to the user list corresponding to the personalized service instance, so that the user has the permission to use the personalized service instance.
[0062] In addition, it should be noted that the service instance management system in this application also supports the function of batch adding, that is, multiple target user identifiers can be included in the user adding request, so that multiple target user identifiers are added to the user list corresponding to a personalized service instance at the same time, or multiple service identifiers are included in the user adding request, so that a target user identifier is added to multiple user lists at the same time, where each user list corresponds to a service identifier. Remarks can also be filled in the user adding request, such as the reason for adding, the period of use, etc.
[0063] In an optional embodiment, the service instance management system may also obtain update information of the main service instance, and detect whether there is conflicting information between the update information and the personalized service instance. If there is no conflicting information between the update information and the personalized service instance, the service instance management system updates the main service instance according to the update information. If there is conflicting information between the update information and the personalized service instance, the service instance management system identifies target information in the update information and updates the main service instance according to the target information. The target information is information in the update information other than the conflicting information.
[0064] Optionally, since a main service instance may be associated with multiple personalized service instances, and the main service instance, as a general service instance of SaaS, will be updated in stages, in order to avoid the update content of the main service from affecting the personalized service instance, the service instance management system in this application will actively obtain the update information of the main service instance, and before formally updating the main service instance, detect whether there is conflicting information between the updated information of the main service instance and the personalized service instance. If there is no conflicting information, the main service instance can be updated directly. If there is conflicting information, the target information in the update information is identified. Since the target information is the information in the update information other than the conflicting information, the update of the main service instance can be updated according to the target information first, thereby ensuring that the updated content will not affect the use of the personalized service instance and improving the user experience.
[0065] In addition, after updating the main service instance according to the target information, the service instance management system will also generate prompt information according to the conflict information and the target information, and send the prompt information to the target account, wherein the target account is the account that manages the main service instance.
[0066] It should be noted that the process of detecting conflict information is equivalent to a detection of the main service instance. When conflict information exists, it means that there are defects in the update of the main service instance. Therefore, the service instance management system promptly reminds the managers of the main service instance to adjust the update content by generating prompt information, thereby improving the update efficiency of the main service instance while ensuring the stable operation of the personalized service instance.
[0067] In an optional embodiment, Figure 4 A flowchart of a method for starting a personalized service instance according to an embodiment of the present application is shown. Figure 4 As shown, taking the personalized service instance as an example of sending a verification message during the payment process, when user A enters the payment stage, the service instance management system calls the main service instance that implements the payment function. During the operation of the main service instance, the service instance management system calls the calling interface associated with the personalized service instance and passes the user ID to the personalized service instance. The personalized service instance queries the user list stored in the database based on the user ID. If the user ID exists in the user list, the personalized service instance is executed to implement the function of sending the verification message. If the user ID does not exist in the user list, the personalized service instance is not executed, and the subsequent payment process continues.
[0068] It can be seen that through the technical solution of the present application, the purpose of using the same personalized service instance to meet the different personalized needs of multiple users is achieved, thereby achieving the effect of improving the user experience and further solving the technical problem of high customized development cost of personalized services in the prior art.
[0069] Example 2
[0070] According to an embodiment of the present application, a device for starting a personalized service instance is also provided, wherein: Figure 5 is a schematic diagram of a starting device for an optional personalized service instance according to an embodiment of the present application, such as Figure 5 As shown, the device includes: a first acquisition module 501, used to obtain a user request, wherein the user request includes at least a user identifier and a main service instance identifier, and the main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; a determination module 502, used to run the main service instance, and determine a personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-general service instance; a second acquisition module 503, used to obtain a user list corresponding to the personalized service instance, wherein the user list contains multiple target user identifiers; a detection module 504, used to detect whether the user identifier is included in the multiple target user identifiers in the user list; a start module 505, used to start and run the personalized service instance when the user identifier is included in the user list.
[0071] It should be noted that the above-mentioned first acquisition module 501, determination module 502, second acquisition module 503, detection module 504 and startup module 505 correspond to steps S101 to S105 in the above-mentioned embodiment, and the examples and application scenarios implemented by the five modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned embodiment 1.
[0072] Optionally, the personalized service instance startup device further includes: a startup prohibition module, which is used to prohibit the startup of the personalized service instance and continue to execute the main service instance when the user identifier is not included in the user list.
[0073] Optionally, the startup device of the personalized service instance further includes: a first receiving module and a first determining module. The first receiving module is used to receive a configuration request, wherein the configuration request is used to configure the personalized service instance based on the main service instance; the first determining module is used to obtain the program code of the main service instance according to the configuration request, and determine the interface position in the program code, wherein the interface position is the position where the personalized service instance interacts with the main service instance.
[0074] Optionally, the first determination module further includes: a parsing unit, a decoupling unit, a first determination unit, and a second determination unit. The parsing unit is used to parse the business logic of the program code; the decoupling unit is used to decouple the program code into multiple sub-program codes according to the business logic, wherein each sub-program code corresponds to a sub-business logic in the business logic; the first determination unit is used to determine the target sub-program code from the multiple sub-program codes according to the business scenario information and the sub-business logic corresponding to each sub-program code; the second determination unit is used to determine the interface position according to the position of the target sub-program code in the program code.
[0075] Optionally, the starting device for the personalized service instance further includes: a first generating module, configured to generate a calling interface at the interface position, wherein the calling interface is used to associate the personalized service instance with the main service instance.
[0076] Optionally, the startup device of the personalized service instance further includes: a third acquisition module, a second generation module, a second receiving module and an adding module. The third acquisition module is used to acquire the interface identifier of the calling interface and the service identifier of the personalized service instance; the second generation module is used to generate an initial user list according to the interface identifier and the service identifier; the second receiving module is used to receive a user adding request, wherein the user adding request includes at least a service identifier, a target user identifier and an interface identifier; the adding module is used to add the target user identifier to the initial user list according to the user adding request to obtain a user list, wherein the user corresponding to the target user identifier has the authority to use the personalized service instance.
[0077] Optionally, the startup device of the personalized service instance also includes: a fourth acquisition module, a first detection module, a first update module, an identification module, and a second update module. Among them, the fourth acquisition module is used to obtain the update information of the main service instance; the first detection module is used to detect whether there is conflicting information between the update information and the personalized service instance; the first update module is used to update the main service instance according to the update information when there is no conflicting information between the update information and the personalized service instance; the identification module is used to identify the target information in the update information when there is conflicting information between the update information and the personalized service instance, wherein the target information is the information in the update information other than the conflicting information; the second update module is used to update the main service instance according to the target information.
[0078] Optionally, the starting device for the personalized service instance further includes: a sending module, configured to generate prompt information according to the conflict information and the target information, and send the prompt information to the target account, wherein the target account is an account for managing the main service instance.
[0079] Example 3
[0080] According to an embodiment of the present application, a computer-readable storage medium is further provided, in which a computer program is stored, wherein the computer program is configured to execute the method for starting the personalized service instance in the above-mentioned embodiment 1 when running.
[0081] Example 4
[0082] According to an embodiment of the present application, an electronic device embodiment is also provided, wherein: Figure 6 is a schematic diagram of an optional electronic device according to an embodiment of the present application, such as Figure 6 As shown, the electronic device includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented:
[0083] Obtain a user request, wherein the user request includes at least a user identifier and a main service instance identifier, and the main service instance corresponding to the main service instance identifier is a pre-deployed general service instance; run the main service instance, and determine a personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-general service instance; obtain a user list corresponding to the personalized service instance, wherein the user list includes multiple target user identifiers; detect whether the user identifier is included in the multiple target user identifiers in the user list; and when the user identifier is included in the user list, start and run the personalized service instance.
[0084] Optionally, when executing the program, the processor further implements the following steps: after detecting whether the multiple target user identifiers in the user list include the user identifier, if the user identifier is not included in the user list, prohibiting the start of the personalized service instance and continuing to execute the main service instance.
[0085] Optionally, the processor also implements the following steps when executing the program: receiving a configuration request before running the main service instance and determining a personalized service instance associated with the main service instance during the running of the main service instance, wherein the configuration request is used to configure the personalized service instance based on the main service instance; obtaining the program code of the main service instance according to the configuration request, and determining the interface location in the program code, wherein the interface location is the location where the personalized service instance interacts with the main service instance for information.
[0086] Optionally, the processor also implements the following steps when executing the program: parsing the business logic of the program code; decoupling the program code into multiple sub-program codes according to the business logic, wherein each sub-program code corresponds to a sub-business logic in the business logic; determining the target sub-program code from the multiple sub-program codes according to the business scenario information and the sub-business logic corresponding to each sub-program code; and determining the interface location according to the location of the target sub-program code in the program code.
[0087] Optionally, when executing the program, the processor further implements the following steps: after determining the interface position according to the position of the target subroutine code in the program code, generating a calling interface at the interface position, wherein the calling interface is used to associate the personalized service instance with the main service instance.
[0088] Optionally, the processor also implements the following steps when executing the program: before obtaining the user list corresponding to the personalized service instance, obtain the interface identifier of the calling interface and the service identifier of the personalized service instance; generate an initial user list based on the interface identifier and the service identifier; receive a user adding request, wherein the user adding request includes at least the service identifier, the target user identifier and the interface identifier; add the target user identifier to the initial user list according to the user adding request to obtain a user list, wherein the user corresponding to the target user identifier has the authority to use the personalized service instance.
[0089] Optionally, when the processor executes the program, the following steps are also implemented: obtaining update information of the main service instance; detecting whether there is conflicting information between the update information and the personalized service instance; if there is no conflicting information between the update information and the personalized service instance, updating the main service instance according to the update information; if there is conflicting information between the update information and the personalized service instance, identifying target information in the update information, wherein the target information is information in the update information other than the conflicting information; and updating the main service instance according to the target information.
[0090] Optionally, the processor further implements the following steps when executing the program: after updating the main service instance according to the target information, generating prompt information according to the conflict information and the target information, and sending the prompt information to the target account, wherein the target account is the account that manages the main service instance.
[0091] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0092] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.
[0093] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
[0094] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0095] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0096] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.
[0097] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A method for starting a personalized service instance, characterized in that: include: Obtaining a user request, wherein the user request includes at least a user identifier and a primary service instance identifier, and the primary service instance corresponding to the primary service instance identifier is a pre-deployed general service instance; Running the main service instance, and determining a personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-general service instance; Obtaining a user list corresponding to the personalized service instance, wherein the user list includes multiple target user identifiers; Detecting whether the user identifier is included in the plurality of target user identifiers in the user list; When the user identifier is included in the user list, starting and running the personalized service instance; Among them, the startup method of the personalized service instance also includes: obtaining update information of the main service instance; detecting whether there is conflicting information between the update information and the personalized service instance; if there is no conflicting information between the update information and the personalized service instance, updating the main service instance according to the update information; if there is conflicting information between the update information and the personalized service instance, identifying target information in the update information, wherein the target information is information in the update information other than the conflicting information; and updating the main service instance according to the target information.
2. The method according to claim 1, characterized in that: After detecting whether the user identifier is included in the plurality of target user identifiers in the user list, the method further includes: When the user list does not contain the user identifier, starting the personalized service instance is prohibited, and the main service instance continues to be executed.
3. The method according to claim 1, characterized in that Before running the main service instance and determining a personalized service instance associated with the main service instance during the running of the main service instance, the method further includes: receiving a configuration request, wherein the configuration request is used to configure the personalized service instance based on the main service instance; The program code of the main service instance is obtained according to the configuration request, and an interface position is determined in the program code, wherein the interface position is a position where the personalized service instance and the main service instance perform information interaction.
4. The method according to claim 3, characterized in that The configuration request at least includes business scenario information corresponding to the personalized service instance, and the program code of the main service instance is obtained according to the configuration request, and the interface position is determined in the program code, including: Parsing the business logic of the program code; Decoupling the program code into a plurality of sub-program codes according to the business logic, wherein each sub-program code corresponds to a sub-business logic in the business logic; Determine a target subprogram code from a plurality of subprogram codes according to the business scenario information and the sub-business logic corresponding to each subprogram code; The interface position is determined according to the position of the target subprogram code in the program code.
5. The method according to claim 4, characterized in that After determining the interface position according to the position of the target subprogram code in the program code, the method further comprises: A calling interface is generated at the interface position, wherein the calling interface is used to associate the personalized service instance with the main service instance.
6. The method according to claim 5, characterized in that Before obtaining the user list corresponding to the personalized service instance, the method further includes: Obtaining an interface identifier of the calling interface and a service identifier of the personalized service instance; Generate an initial user list according to the interface identifier and the service identifier; receiving a user adding request, wherein the user adding request at least includes the service identifier, the target user identifier and the interface identifier; The target user identifier is added to the initial user list according to the user adding request to obtain the user list, wherein the user corresponding to the target user identifier has the authority to use the personalized service instance.
7. The method according to claim 1, characterized in that After updating the primary service instance according to the target information, the method further includes: Prompt information is generated according to the conflict information and the target information, and the prompt information is sent to a target account, wherein the target account is an account that manages the primary service instance.
8. A device for starting a personalized service instance, characterized in that: include: A first acquisition module is used to acquire a user request, wherein the user request includes at least a user identifier and a primary service instance identifier, and the primary service instance corresponding to the primary service instance identifier is a pre-deployed general service instance; A determination module, configured to run the main service instance and determine a personalized service instance associated with the main service instance during the running of the main service instance, wherein the personalized service instance is a pre-deployed non-universal service instance; A second acquisition module is used to acquire a user list corresponding to the personalized service instance, wherein the user list includes multiple target user identifiers; A detection module, used for detecting whether the user identifier is included in the multiple target user identifiers in the user list; A starting module, used for starting and running the personalized service instance when the user identifier is included in the user list; Among them, the starting device of the personalized service instance also includes: a fourth acquisition module, used to obtain the update information of the main service instance; a first detection module, used to detect whether there is conflict information between the update information and the personalized service instance; a first update module, used to update the main service instance according to the update information when there is no conflict information between the update information and the personalized service instance; an identification module, used to identify target information in the update information when there is conflict information between the update information and the personalized service instance, wherein the target information is information in the update information other than the conflict information; a second update module, used to update the main service instance according to the target information.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method for starting a personalized service instance as described in any one of claims 1 to 7 when running.
10. An electronic device, characterized in that: The electronic device includes one or more processors; A memory for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the operation of the programs, wherein the programs are configured to execute the method for starting the personalized service instance described in any one of claims 1 to 7 when running.
