CN117424828A

CN117424828A - Micro-service interface generation method, device, equipment and storage medium

Info

Publication number: CN117424828A
Application number: CN202311310840.3A
Authority: CN
Inventors: 梁飞; 张旭东; 毛宏
Original assignee: Beijing Vision World Technology Co ltd
Current assignee: Beijing Vision World Technology Co ltd
Priority date: 2023-10-10
Filing date: 2023-10-10
Publication date: 2024-01-19

Abstract

The invention belongs to the technical field of computers, and discloses a method, a device, equipment and a storage medium for generating a micro-service interface; the method comprises the following steps: acquiring and displaying a micro-service list associated with the SaaS platform, wherein the micro-service list comprises a plurality of micro-services supported by the SaaS platform; responding to a business demand instruction input by a target user based on a micro-service list, and determining at least one corresponding target micro-service according to the business demand instruction; constructing a micro-service personalized interface of a target user according to the target micro-service; according to the invention, various service functions are disassembled to be independent micro-services, corresponding micro-service contents can be selected according to the service demands of users, a more concise and effective service use interface is constructed, meanwhile, the micro-services can be added and deleted according to the service demand changes, more flexible, convenient and comprehensive service functions are provided for the users, and the problems that the functions are not targeted and inconvenient and comprehensive in the use process of the users due to the integrated use of various service functions of the current SaaS platform are solved.

Description

Micro-service interface generation method, device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for generating a micro service interface.

Background

The software operation service is (Software as a Service, abbreviated as SaaS) to enable users to connect and use cloud-based application programs through the internet and provide complete software solutions, and provide various service functions, namely various applications for the users; the user may connect to various applications via the internet. The service provider is responsible for managing the hardware and software and ensuring the availability and security of the applications and data according to the appropriate service protocols.

Most of SaaS platforms are SaaS platforms specially developed for a certain type of users, and services possibly used by the users are preset in the platforms, so that the users can conduct business development directly through the SaaS platforms. Meanwhile, unavoidable services which are not used by users exist in the SaaS platform, so that the use is inconvenient, the development of industry or the expansion of user service are possible, and the services in the existing SaaS platform cannot meet the service use requirements of users.

Disclosure of Invention

The invention mainly aims to provide a method, a device, equipment and a storage medium for generating a micro-service interface, which aim to solve the technical problems that functions are not targeted and are inconvenient to use in the process of a user due to the integrated use of various service functions of a current SaaS platform in the prior art.

In order to achieve the above object, the present invention provides a method for generating a microservice interface, the method comprising the steps of:

acquiring and displaying a micro-service list associated with the SaaS platform, wherein the micro-service list comprises a plurality of micro-services supported by the SaaS platform;

responding to a business demand instruction input by a target user based on the micro-service list, and determining at least one corresponding target micro-service according to the business demand instruction;

and constructing a micro-service personalized interface of the target user according to the target micro-service.

Optionally, the determining the corresponding at least one target micro-service according to the business requirement instruction includes:

acquiring and displaying a reference service type according to the service demand instruction;

responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference service type based on the target service type instruction;

responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference micro-service based on the target service type instruction;

and responding to a reference micro-service instruction input by a target user based on the reference micro-service, and determining at least one corresponding target micro-service according to the reference micro-service instruction.

Optionally, after determining the corresponding at least one target micro-service, the method includes:

searching a first related micro-service used by the user with the same type as the target service and searching a second related micro-service used by the user with the same type as the target service;

displaying and recommending the first related micro-service and the second related micro-service;

and responding to an extended micro-service instruction input by a target user based on the first related micro-service and the second related micro-service, and taking the extended micro-service as a target micro-service.

Optionally, the constructing a micro-service personalized interface of the target user according to the target micro-service includes:

displaying the target micro-service on a preset original interface to obtain an initial interface;

responding to a target position instruction input by a target user based on the initial interface, and obtaining a target position of each target micro-service according to the target position instruction;

and migrating each target micro-service to a corresponding target position to obtain a micro-service personalized interface.

Optionally, after the migrating the initial interface target micro-service according to the target position to obtain the micro-service personalized interface, the method further includes:

Responding to a deleting instruction input by a target user based on the initial interface or the micro-service personalized interface, and determining a target micro-service to be deleted according to the deleting instruction;

deleting the micro-service to be deleted from the initial interface or the micro-service personalized interface, wherein the micro-service to be deleted is any one or more target micro-services in the micro-service personalized interface;

responding to a newly added micro-service instruction input by a target user based on the initial interface or the micro-service personalized interface, and determining a newly added target micro-service according to the newly added micro-service instruction;

displaying the newly added target micro-service on the initial interface or the micro-service personalized interface, wherein the newly added target micro-service is any one or more micro-services in the micro-service list.

Optionally, after the micro service personalized interface of the target user is constructed according to the target micro service, the method further includes:

acquiring a SaaS platform account number of a target user;

binding the SaaS platform account with the micro-service personalized interface to obtain a micro-service personalized interface corresponding to the SaaS platform account;

responding to a login instruction input by a user based on the SaaS platform, and obtaining a SaaS platform account of a target user according to the login instruction;

And determining and displaying a corresponding micro-service personalized interface according to the SaaS platform account number.

acquiring micro-service requirements of each reference user, and acquiring use feedback of each target user on a micro-service personalized interface, wherein the reference users comprise target users and non-target users;

responding to the micro-service expansion signal input based on the service requirement and the use feedback, and obtaining expansion micro-service information according to the micro-service expansion signal;

and updating the micro service list associated with the SaaS platform according to the extended micro service information.

Optionally, the acquiring the micro-service requirement of each reference user and acquiring the use feedback of each target user to the micro-service personalized interface, where the reference users include target users and non-target users, includes:

acquiring service types of all reference users and service types required by all reference users;

taking the service type and the service type as requirement labels of all reference users, and obtaining micro-service requirements of all reference users according to the requirement labels;

And responding to a state instruction input by the target user based on the micro-service personalized interface, and obtaining the use feedback of each target user on the micro-service personalized interface according to the state instruction.

Optionally, after updating the micro service list associated with the SaaS platform according to the extended micro service information, the method further includes:

obtaining a reference demand label of the extended micro service according to the extended micro service information;

obtaining a reference service type and a reference service type according to the reference demand label;

matching the reference service type with the service type of each target client to obtain a first matching object, and matching the reference service type with the service type of each target client to obtain a second matching object;

removing repeated target clients in the first matching object and the second matching object to obtain a target matching object;

pushing the extended micro-service to the target matching object.

Optionally, before the acquiring and displaying the micro service list associated with the SaaS platform, the method further includes:

acquiring the name, service type and service type of the micro service associated with the SaaS platform;

taking the service type and the service type of the micro service as labels of the micro service;

And creating a micro-service list associated with the SaaS platform according to the name and the label of the micro-service.

In addition, in order to achieve the above object, the present invention also provides a micro service interface generating device, including:

the information acquisition module is used for acquiring and displaying a micro-service list associated with the SaaS platform, wherein the micro-service list comprises a plurality of micro-services supported by the SaaS platform;

the micro-service confirmation module is used for responding to a business demand instruction input by a target user based on the micro-service list and determining at least one corresponding target micro-service according to the business demand instruction;

and the construction module is used for constructing a micro-service personalized interface of the target user according to the target micro-service.

Optionally, the micro service confirmation module is further configured to acquire and display a reference service type according to the service requirement instruction; responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference service type based on the target service type instruction;

Optionally, the micro-service confirmation module is further configured to search for a first related micro-service used by the user with the same type of the target service;

searching for a second related micro-service used by the user of the same type as the target service;

Optionally, the building module is further configured to display the target micro-service on a preset original interface to obtain an initial interface;

Optionally, the construction module is further configured to determine, according to a deletion instruction input by a target user based on the initial interface or the micro-service personalized interface, a target micro-service to be deleted;

Optionally, the construction module is further configured to obtain micro-service requirements of each reference user, and obtain usage feedback of each target user on the micro-service personalized interface, where the reference users include target users and non-target users;

Optionally, the construction module is further configured to obtain a service type of each reference user and a service type required by each reference user;

Optionally, the construction module is further configured to obtain a reference requirement label of the extended micro service according to the extended micro service information;

pushing the extended micro-service to the target matching object.

In addition, to achieve the above object, the present invention also proposes a micro service interface generation apparatus including: a memory, a processor, and a micro-service interface generation program stored on the memory and executable on the processor, the micro-service interface generation program configured to implement the steps of the micro-service interface generation method as described above.

In addition, in order to achieve the above object, the present invention also proposes a storage medium having stored thereon a micro service interface generation program which, when executed by a processor, implements the steps of the micro service interface generation method as described above.

According to the invention, various service functions are disassembled to be independent micro-services, corresponding micro-service contents can be selected according to the service demands of users, a more concise and effective service use interface is constructed, meanwhile, the micro-services can be added and deleted according to the service demand changes, more flexible, convenient and comprehensive service functions are provided for the users, and the problems that the functions are not targeted and inconvenient and comprehensive in the use process of the users due to the integrated use of various service functions of the current SaaS platform are solved.

Drawings

FIG. 1 is a schematic diagram of a micro service interface generating device of a hardware running environment according to an embodiment of the present invention;

FIG. 2 is a flowchart of a first embodiment of a method for generating a micro-service interface according to the present invention;

FIG. 3 is a schematic diagram of a micro service list of a SaaS platform according to an embodiment of the method for generating a micro service interface of the present invention;

FIG. 4 is a flowchart of a second embodiment of a method for generating a micro service interface according to the present invention;

FIG. 5 is a schematic diagram of a default original interface of a SaaS platform according to an embodiment of the method for generating a micro-service interface of the present invention;

FIG. 6 is a schematic diagram of an initial interface of a SaaS platform according to an embodiment of the method for generating a micro-service interface of the present invention;

FIG. 7 is a schematic diagram illustrating migration of a target micro service in a micro service personalized interface of a SaaS platform according to an embodiment of the method for generating a micro service interface of the present invention;

FIG. 8 is a flowchart of a third embodiment of a method for generating a micro service interface according to the present invention;

fig. 9 is a block diagram of a micro service interface generating device according to a first embodiment of the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a micro service interface generating device of a hardware running environment according to an embodiment of the present invention.

As shown in fig. 1, the micro service interface generation apparatus may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (Wi-Fi) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.

Those skilled in the art will appreciate that the structure shown in fig. 1 does not constitute a limitation of the micro-service interface generating device, and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.

As shown in fig. 1, an operating system, a network communication module, a user interface module, and a micro service interface generation program may be included in the memory 1005 as one type of storage medium.

In the micro service interface generating device shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the micro service interface generating device of the present invention may be provided in the micro service interface generating device, where the micro service interface generating device invokes the micro service interface generating program stored in the memory 1005 through the processor 1001, and executes the micro service interface generating method provided by the embodiment of the present invention.

An embodiment of the present invention provides a method for generating a micro service interface, and referring to fig. 2, fig. 2 is a schematic flow chart of a first embodiment of a method for generating a micro service interface according to the present invention.

In this embodiment, the method for generating a micro service interface includes the following steps:

Step S10: and acquiring and displaying a micro-service list associated with the SaaS platform, wherein the micro-service list comprises a plurality of micro-services supported by the SaaS platform.

It can be understood that the micro-service list may be a list of various micro-services that the SaaS platform can provide for users of the SaaS platform to use, and the list may also be updated or added or deleted according to the real-time development situation of the various micro-services.

It should be understood that when the user uses the SaaS platform described in this embodiment, a micro service list that has been established in advance is obtained and displayed to the user, so that the user can intuitively understand the micro services that can be provided by the SaaS platform, so as to further determine that the user determines the micro services that are required from the service list.

It should be noted that the micro service list may include a name of each micro service, a service type and a service type applicable to each micro service.

In a specific implementation, the construction of the micro-service list may be to obtain the name, the service type and the service type of the micro-service associated with the SaaS platform; taking the service type and the service type of the micro service as labels of the micro service; and creating a micro-service list associated with the SaaS platform according to the name and the label of the micro-service.

Wherein, it can be understood that each micro service has a corresponding label, and the label includes a service type and a service type applicable to the micro service; it is further described that each user may also have a corresponding tag, the service type of the user and the desired service type, and each micro service may have one or more tags, where the tags of each micro service may be pre-calibrated when the micro service is developed, or calibrated after development during use by a subsequent user.

The business types can comprise various types of factories, shops, enterprises, individuals and the like; the service type may include various types of personnel management, device management, department management, AI management, rights management, personnel management, and the like.

It should be noted that, the execution body of the embodiment is a micro service interface generating device, where the micro service interface generating device has functions of data processing, data communication, program running, and the like, and the micro service interface generating device may be an integrated controller, a control computer, and other devices with similar functions, and the embodiment is not limited to this.

Step S20: and responding to a business demand instruction input by a target user based on the micro-service list, and determining at least one corresponding target micro-service according to the business demand instruction.

It can be appreciated that the service requirement instruction may be an instruction generated when the user operates based on the micro service list when using the SaaS platform in the present embodiment.

In a specific implementation summary, when a list of micro services is presented to a user, the user may now select one or more business types, such as businesses; selecting one or more service types, such as personnel management, based on the enterprise; based on the person management, there may be a plurality of micro-services including enterprise and/or person management in the tags presented to the user, see in detail fig. 3.

It should be understood that the instruction generated by the user's operation in selecting the service type and the service type may be understood as a service demand instruction; the instructions generated by the user's operations in selecting a micro-service may also be understood as business need instructions.

It is understood that the target micro-service may be one or more user-selected micro-services in a list of micro-services.

It should be noted that, determining at least one corresponding target micro-service according to the service demand instruction may be obtaining and displaying a reference service type according to the service demand instruction; responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference service type based on the target service type instruction; responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference micro-service based on the target service type instruction; and responding to a reference micro-service instruction input by a target user based on the reference micro-service, and determining at least one corresponding target micro-service according to the reference micro-service instruction.

In specific implementation, after a user enters the SaaS platform, a use instruction of the user is obtained, a micro service list is obtained, and service types in the micro service list are displayed to the user: factories, stores, businesses, individuals; the user selects two business types of enterprises and stores, and service types related to the two business types of the enterprises and the stores are displayed according to the two business types of the enterprises and the stores selected by the user: personnel management, equipment management, department management and authority management; the user selects two service types of personnel management and authority management according to the service requirement of the user; based on two service types of personnel management and authority management selected by a user, the reference micro-service related to personnel management and authority management which can be provided by the current SaaS platform is displayed, and the user can select one or more target micro-services which are used by the user from a plurality of reference micro-services related to personnel management and authority management.

It is further emphasized that after the determining of the corresponding at least one target micro-service, a first related micro-service used by the user with the same type as the target service may be searched and a second related micro-service used by the user with the same type as the target service may be searched; displaying and recommending the first related micro-service and the second related micro-service; and responding to an extended micro-service instruction input by a target user based on the first related micro-service and the second related micro-service, and taking the extended micro-service as the target micro-service.

Wherein, it can be understood that each user can synchronously take the service type and the service type as the labels of the user when the service type and the service type required by the user are selected at the beginning, and the user can also modify the personal labels within the range of the given service type and service type.

It should be understood that, in the process of selecting the target micro-service by the target user or after determining the target micro-service, the service type of the target user and the service types of other users may be matched, the users with the same service type are used as the first relevant users, and the micro-service used by the first relevant users is used as the first relevant micro-service; and matching the service type of the target user with the service types of other users, taking the users with the same service type as second related users, and taking the micro-services used by the second related users as second related micro-services.

Further, the first related micro-service and the second related micro-service can be displayed and recommended to the target user, and meanwhile, the same micro-service in the first micro-service and the second micro-service is used as a first-level recommended micro-service, and other micro-services are used as second-level recommended micro-services.

It should be noted that, when recommending the first related micro-service and the second related micro-service to the target user, the target user may select one or more of the first related micro-service and the second related micro-service as the newly added micro-service, and the instruction generated by the operation of selecting the newly added micro-service from the first related micro-service and the second related micro-service by the user may be understood as an extended micro-service instruction. If the newly added micro service is not selected, an extended micro service instruction is not generated, and the display of the first related micro service and the second related micro service is canceled after the preset time, or the user actively exits the display and recommendation of the first related micro service and the second related micro service.

Step S30: and constructing a micro-service personalized interface of the target user according to the target micro-service.

It is understood that the micro-service personalized interface herein may be an interface that is more in line with the needs of the target user, as set by the personal business needs and the service needs of the target user.

It should be appreciated that based on the micro-service personalization interface, a user may adjust the target micro-services therein at any time, such as adding or deleting one or more of the target micro-services, moving the location of one or more of the target micro-services, etc.

It should be noted that, when the user initially uses the SaaS platform described in this embodiment, a blank interface will appear in advance, after the user determines that the target micro-service is well, the target micro-service is displayed in the blank interface, so as to complete the construction of the micro-service personalized interface of the target user.

According to the embodiment, various service functions are disassembled to serve as independent micro services, corresponding micro service contents can be selected according to service demands of users, a more concise and effective service use interface is constructed, meanwhile, the micro services can be added and deleted according to service demand changes, more flexible, convenient and comprehensive service functions are provided for the users, and the problems that functions are not targeted, and the users are inconvenient and comprehensive in the use process due to the fact that various service functions of the current SaaS platform are integrated and used are solved.

Referring to fig. 4, fig. 4 is a flowchart illustrating a second embodiment of a micro service interface generating method according to the present invention.

Based on the above first embodiment, the method for generating a micro service interface in this embodiment includes, at step S30:

step S31: and displaying the target micro-service on a preset original interface to obtain an initial interface.

It is understood that the preset original interface may be understood as a blank interface when the target user uses the SaaS platform described in the present specification for the first time, and the interface may not have a micro service already set.

It should be understood that the SaaS platform screens the corresponding micro services from the micro service list according to the service type and the service type provided by the target user, and the user can determine the required target micro services based on the screened micro services.

It should be noted that after determining the target micro-services, each target may be set as a service at a preset position in the preset original interface based on a certain preset initial rule.

It should be further noted that, the preset initial rule may be to display the target micro-service at each preset position according to the order in which the target user selects the target micro-service, or may be to display the target micro-service at each preset position according to the order in which the number of times of using the target micro-service in the micro-service list is selected by the user; the preset position may be a position preset in advance in the preset original interface, where each target micro service may be displayed, and reference is made to fig. 5 in detail.

Step S32: and responding to a target position instruction input by a target user based on the initial interface, and obtaining the target position of each target micro-service according to the target position instruction.

It is understood that the target location instruction may be an instruction issued by the user when moving one or more target micro-services in the initial interface.

It should be appreciated that the target locations may be where the user wants the target microservices to be, and that the target location of each target microservice may be adjusted according to the individual usage habits of the target user or the frequency of usage of the individual target user by the user.

In a specific implementation, if the personal habit of the target user is biased to use the left hand, the user can bias the display position of the micro-service in the SaaS platform to the left side according to the personal habit; if the initial interface of the target user includes the micro service a, the micro service B, the micro service C and the micro service D, where the micro service a belongs to a frequently used micro service and the micro service B belongs to a less frequently used micro service, the user may move the micro service a to a more convenient and obvious position such as the middle or the top of the initial interface, and refer to fig. 6 in detail.

Step S33: and migrating each target micro-service to a corresponding target position to obtain a micro-service personalized interface.

It can be understood that the target user completes the migration of the target service according to the personal use habit or the use probability of each micro service; meanwhile, the user can not adjust the positions of all the target micro services in the initial interface. Reference is made in detail to fig. 7.

It should be understood that if the user migrates each target micro-service, each micro-service and the corresponding location form the final micro-service personalized interface; if no migration occurs, the initial interface is directly used as a final micro-service personalized interface.

It should be noted that, after determining the micro-service personalized interface of the target user, or when the user wants to use the SaaS platform for the first time, the target user may register on the SaaS platform according to personal information (for example, a mobile phone number, a micro-signal, a QQ number, etc.).

It should be emphasized that after the target user completes registration, the target user is already bound with the interface displayed by the current SaaS platform, and if the user only registers, the interface may be a preset original interface; if the user selects the micro-service, the interface is a micro-service personalized interface.

In specific implementation, acquiring a SaaS platform account number of a target user; binding the SaaS platform account with the micro-service personalized interface to obtain a micro-service personalized interface corresponding to the SaaS platform account; responding to a login instruction input by a user based on the SaaS platform, and obtaining a SaaS platform account number of a target user according to the login instruction (the SaaS platform account number password verification can be synchronously performed here); and determining and displaying a corresponding micro-service personalized interface according to the SaaS platform account number.

It is emphasized that an account may include multiple micro-service personalization interfaces, and that the same manager may have different business products.

It can be understood that the login instruction may be an instruction generated when the user performs the login operation according to the SaaS platform account.

It should be emphasized that the target user may further add or delete the target micro service in the micro service personalized interface during the setting of the micro service personalized interface and during the use of the micro service personalized interface.

It is further emphasized that the adding and deleting of the target micro-service may be in response to a deleting instruction input by the target user based on the initial interface or the micro-service personalized interface, and determining the target micro-service to be deleted according to the deleting instruction; deleting the micro-service to be deleted from the initial interface or the micro-service personalized interface, wherein the micro-service to be deleted is any one or more target micro-services in the micro-service personalized interface; responding to a newly added micro-service instruction input by a target user based on the initial interface or the micro-service personalized interface, and determining a newly added target micro-service according to the newly added micro-service instruction; displaying the newly added target micro-service on the initial interface or the micro-service personalized interface, wherein the newly added target micro-service is any one or more micro-services in the micro-service list.

Wherein, it can be understood that the deleting instruction can be an instruction generated when the target user selects the target micro-service to be deleted on the initial interface or the micro-service personalized interface; the newly added micro service instruction may be an instruction that the target user selects the newly added micro service in the micro service list to be generated.

Wherein it should be understood that one or more micro services may be deleted or added; for example, 3 target micro services in the micro service personalized interface may be deleted at the same time, or 3 micro services may be selected from the micro service list as new micro services at the same time.

It should be noted that, while the target user uses each micro service, the service of the target user also develops along with the time, so that new micro services may appear, and the eliminated micro services inevitably exist, so that the target user can adjust the service in the micro service personalized interface according to the requirements of the service of the target user, and the service application requirements of the target user in different services and at each time are fully satisfied.

According to the method, the initial interface is generated according to the selected target micro-service of the user, the target positions of the target micro-services are flexibly set according to the micro-service use habit or the micro-service use frequency of the target user, the target micro-services in the initial interface are moved, the final micro-service personalized interface is obtained, a more flexible and convenient use method is provided for the user, and the user experience is improved.

Referring to fig. 8, fig. 8 is a flowchart illustrating a micro service interface generating method according to a second embodiment of the present invention.

Based on the above-mentioned first embodiment, the micro service interface generating method of the present embodiment further includes, after the step S30:

step S40: and acquiring micro-service requirements of each reference user, and acquiring use feedback of each target user on a micro-service personalized interface, wherein the reference users comprise target users and non-target users.

It is understood that the reference users include target users and non-target users, wherein the target users may be users who have used but are not currently used or are using the micro-service personalized interface provided by the SaaS platform in the present invention; the non-target user may be a user who has not used the micro-service personalized interface provided by the SaaS platform in the present invention.

It should be understood that the micro service requirement of each reference user can be simply understood as the use requirement of the reference user for the application and various service functions; the usage feedback of the respective target user may be a problem that the target user finds during the use of the personalized interface for the service, or a newly proposed suggestion, which may be an improved direction or a new service requirement.

It should be appreciated that the feedback of usage of applications, various service functions, and target users with reference to the user is time-efficient; and continuously acquiring micro-service requirements of the reference user and use feedback of the target user according to regular time intervals, and correspondingly optimizing each micro-service and the SaaS platform.

It should be noted that, the obtaining the micro service requirement of each reference user, and the obtaining the usage feedback of each target user to the micro service personalized interface may be obtaining the service type of each reference user and the service type required by each reference user; taking the service type and the service type as requirement labels of all reference users, and obtaining micro-service requirements of all reference users according to the requirement labels; and responding to a state instruction input by the target user based on the micro-service personalized interface, and obtaining the use feedback of each target user on the micro-service personalized interface according to the state instruction.

It can be understood that the acquisition of the micro-service requirement can be obtained by performing a method such as questionnaire investigation, interview or opinion collection on the reference users, and the service type and the required service type of each reference user can be obtained in the acquisition process, so that each reference user is labeled.

It can be understood that the obtaining of the feedback used by the target user may be according to the evaluation of the user on each micro service in the use process, or may be that a questionnaire is performed through the SaaS platform, and the operation performed by the target user in the feedback process may be used as a status instruction, where the feedback used may include like, dislike, update direction, and specific feedback content.

Step S50: and responding to the micro-service extension signal input based on the service requirement and the use feedback, and obtaining extension micro-service information according to the micro-service extension signal.

It can be understood that after the service requirement of the reference user and the use feedback of the target user are collected, the corresponding update or addition/deletion of each micro service can be further performed. For example, the feedback of the user to the use of a certain micro-service is inconvenient without labeling function, and the micro-service can be optimized based on the feedback to add the labeling function.

It should be understood that, if the micro service needs to be updated or added or deleted, a corresponding upgrade package may be generated on the SaaS platform, and a micro service extension signal may be generated corresponding to the generation/reception/obtaining of the upgrade package.

It is understood that the micro-service extension signal can be simply understood as which micro-service is to be upgraded, what micro-service is extended, the reminding signal of that micro-service is deleted, and the upgraded micro-service information, the deleted micro-service information and the extended micro-service information can be obtained based on the signal.

It should be noted that the extended micro service information may include the name and tag of the (extended, deleted, upgraded) micro service; if the service is the extended micro service, the label is a preset service type and service type; if the micro service is deleted or the micro service is updated, the label corresponding to the micro service is obtained.

Step S60: and updating the micro service list associated with the SaaS platform according to the extended micro service information.

It is appreciated that the extended micro-service information is populated into the micro-service list so that the target user can find the extended micro-service when looking into the service list.

It should be understood that the service list is updated continuously according to the feedback of the user, and the target user can adjust the micro-service personalized interface of the individual according to the use requirement of the individual according to the updated service list, so as to obtain the micro-service personalized interface which is more convenient for the user to use.

It should be noted that, after the micro service list associated with the SaaS platform is updated according to the extended micro service information, a reference requirement label of the extended micro service may also be obtained according to the extended micro service information; obtaining a reference service type and a reference service type according to the reference demand label; matching the reference service type with the service type of each target client to obtain a first matching object, and matching the reference service type with the service type of each target client to obtain a second matching object; removing repeated target clients in the first matching object and the second matching object to obtain a target matching object; pushing the extended micro-service to the target matching object.

It is understood that the reference requirement label is a service type and a service type set in advance for the extended micro service.

It should be understood that, by matching the service type and service type of the extended micro service with the service type and service type of each target user, the target user who may use, need and fit the extended micro service can be quickly found.

The recommendation informs the target user of the new micro service, so that the target user can conveniently select the new micro service.

According to the method and the system, the micro-service of the current SaaS platform is optimized and updated by collecting the use feedback of the user using the SaaS platform micro-service personalized interface and collecting the unused service requirements, so that the micro-service related to the SaaS platform can be changed continuously according to time and service requirements, the user can obtain the micro-service which meets the requirements better from the micro-service related to the SaaS platform, the service can be provided for the user better, and the user experience is improved.

In addition, the embodiment of the invention also provides a storage medium, wherein the storage medium is stored with a micro service interface generation program, and the micro service interface generation program realizes the steps of the micro service interface generation method when being executed by a processor.

Referring to fig. 9, fig. 9 is a block diagram showing the structure of a first embodiment of the micro service interface generating apparatus according to the present invention.

As shown in fig. 9, the micro service interface generating device according to the embodiment of the present invention includes:

In an embodiment, the micro service confirmation module is further configured to acquire and display a reference service type according to the service requirement instruction; responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference service type based on the target service type instruction;

In an embodiment, the micro service confirmation module is further configured to search for a first related micro service used by the user with the same type of the target service;

In an embodiment, the building module is further configured to display the target micro service on a preset original interface to obtain an initial interface;

In an embodiment, the construction module is further configured to determine, according to a deletion instruction input by a target user based on the initial interface or the micro-service personalized interface, a target micro-service to be deleted;

In an embodiment, the building module is further configured to obtain a micro service requirement of each reference user, and obtain a usage feedback of each target user on the micro service personalized interface, where the reference users include a target user and a non-target user;

In an embodiment, the construction module is further configured to obtain a service type of each reference user and a service type required by each reference user;

In an embodiment, the building module is further configured to obtain a reference requirement label of the extended micro service according to the extended micro service information;

pushing the extended micro-service to the target matching object.

It should be understood that the foregoing is illustrative only and is not limiting, and that in specific applications, those skilled in the art may set the invention as desired, and the invention is not limited thereto.

It should be noted that the above-described working procedure is merely illustrative, and does not limit the scope of the present invention, and in practical application, a person skilled in the art may select part or all of them according to actual needs to achieve the purpose of the embodiment, which is not limited herein.

Furthermore, it should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. Read Only Memory)/RAM, magnetic disk, optical disk) and including several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.

It should be understood that, although the steps in the flowcharts in the embodiments of the present application are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily occurring in sequence, but may be performed alternately or alternately with other steps or at least a portion of the other steps or stages.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

The invention discloses A1, a micro-service interface generation method, which comprises the following steps:

A2, the micro-service interface generating method according to A1, wherein the determining at least one corresponding target micro-service according to the service demand instruction includes:

A3, the micro service interface generating method according to A1, after determining at least one corresponding target micro service, includes:

A4, the micro-service interface generation method of A1, wherein the constructing the micro-service personalized interface of the target user according to the target micro-service comprises the following steps:

A5, the micro-service interface generation method according to A4, wherein the migration of the initial interface target micro-service according to the target position, after obtaining the micro-service personalized interface, further comprises:

A6, the micro service interface generation method according to any one of A1 to A5, after the micro service personalized interface of the target user is constructed according to the target micro service, further comprises:

acquiring a SaaS platform account number of a target user;

A7, the micro service interface generation method according to any one of A1 to A5, after the micro service personalized interface of the target user is constructed according to the target micro service, further comprises:

A8, the micro service interface generating method according to A7, wherein the obtaining the micro service requirement of each reference user and obtaining the use feedback of each target user to the micro service personalized interface, the reference user including target users and non-target users includes:

A9, after updating the micro service list associated with the SaaS platform according to the extended micro service information, the micro service interface generation method as described in A7 further includes:

Pushing the extended micro-service to the target matching object.

A10, the method for generating a micro service interface according to A1, before the step of acquiring and displaying the micro service list associated with the SaaS platform, further comprises:

B11, a micro service interface generating device, comprising:

B12, the micro service interface generating device as described in B11, wherein the micro service confirmation module is further configured to acquire and display a reference service type according to the service requirement instruction; responding to a target service type instruction input by a target user based on the reference service type, and acquiring and displaying a reference service type based on the target service type instruction;

B13, the micro service interface generating device as described in B11, wherein the micro service confirmation module is further configured to search a first related micro service used by the user with the same type of the target service;

B14, the micro-service interface generating device as described in B11, wherein the construction module is further configured to display the target micro-service on a preset original interface to obtain an initial interface;

B15, the micro-service interface generating device as described in B14, wherein the construction module is further configured to respond to a deletion instruction input by a target user based on the initial interface or the micro-service personalized interface, and determine a target micro-service to be deleted according to the deletion instruction;

The micro service interface generating device according to any one of B11-B15, wherein the building module is further configured to obtain micro service requirements of each reference user, and obtain usage feedback of each target user on the micro service personalized interface, where the reference user includes a target user and a non-target user;

B17, the micro service interface generating device as described in B16, wherein the construction module is further configured to obtain a service type of each reference user and a service type required by each reference user;

B18, the micro service interface generating device as described in B16, wherein the construction module is further configured to obtain a reference requirement label of the extended micro service according to the extended micro service information;

pushing the extended micro-service to the target matching object.

C19, a micro service interface generation apparatus, the apparatus comprising: the micro service interface generation system comprises a memory, a processor and a micro service interface generation program stored on the memory and capable of running on the processor, wherein the micro service interface generation program is configured to realize the micro service interface generation method.

D20, a storage medium, on which a micro service interface generation program is stored, which when executed by a processor, implements the micro service interface generation method as described above.

Claims

1. The micro service interface generation method is characterized by comprising the following steps of:

2. The method for generating a micro service interface according to claim 1, wherein determining the corresponding at least one target micro service according to the service requirement instruction comprises:

3. The method for generating a micro service interface according to claim 1, wherein after determining the corresponding at least one target micro service, the method comprises:

4. The method for generating a micro service interface according to claim 1, wherein the constructing a micro service personalized interface of the target user according to the target micro service comprises:

5. The method for generating a micro-service interface according to claim 4, wherein after the migration of the initial interface target micro-service according to the target position to obtain a micro-service personalized interface, further comprises:

6. The method for generating a micro service interface according to any one of claims 1 to 4, wherein after the micro service personalized interface of the target user is constructed according to the target micro service, the method further comprises:

7. The method for generating a micro service interface according to claim 6, wherein the step of obtaining the micro service requirement of each reference user, obtaining the usage feedback of each target user on the micro service personalized interface, the reference users including target users and non-target users, comprises:

8. A micro service interface generation apparatus, characterized in that the micro service interface generation apparatus comprises:

9. A micro service interface generation apparatus, the apparatus comprising: a memory, a processor, and a micro-service interface generation program stored on the memory and executable on the processor, the micro-service interface generation program configured to implement the micro-service interface generation method of any one of claims 1 to 7.

10. A storage medium, wherein a micro service interface generation program is stored on the storage medium, and when executed by a processor, the micro service interface generation program implements the micro service interface generation method according to any one of claims 1 to 7.