CN114265652A

CN114265652A - UI (user interface) display method and device, cloud server and storage medium

Info

Publication number: CN114265652A
Application number: CN202111531854.9A
Authority: CN
Inventors: 陈剑; 徐庆贺
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2021-12-14
Filing date: 2021-12-14
Publication date: 2022-04-01
Anticipated expiration: 2041-12-14
Also published as: CN114265652B

Abstract

The application provides a UI (user interface) display method and device, a cloud server and a storage medium, wherein the cloud server is provided with a cloud service product comprising a plurality of service modules and UI services, the UI services are provided with a plurality of UI interfaces shared by the service modules, and processes in which the UI services operate are different from processes in which the service modules operate respectively. And the target service module is used for sending a calling request for calling the target UI to the UI service, wherein the calling request comprises input configuration parameters corresponding to the target UI. The UI service is used for displaying a target UI interface according to the input configuration parameters and feeding back output result information of the target UI interface to the target service module. The UI display function required by a plurality of service modules is provided through a single UI service, all the service modules reuse the UI interface provided by the UI service, and the UI development cost is reduced.

Description

UI (user interface) display method and device, cloud server and storage medium

Technical Field

The invention relates to the technical field of cloud computing, in particular to a UI (user interface) display method and device, a cloud server and a storage medium.

Background

With the continuous development of cloud computing technology, more and more users choose to deploy their own services using resources provided by cloud computing vendors or directly purchase services provided by cloud computing vendors, such as cloud desktops and some cloud application products.

The current cloud desktop and cloud application products are often operated in a virtual machine environment, and can relate to the development of the interior of an operating system in a virtual machine on the cloud. Generally, most of the cloud desktops and cloud applications run in the background in a system service mode, but some functions or some scenes need to pop up some UI prompts on an interface, such as a file selection dialog box, a download progress bar, a service exception prompt and the like. In practical application, the display of the UI interfaces is often performed by different processes, and if each process develops the UI display code of the process, the workload is large. Moreover, the display of the UI interface and the corresponding service are all operated in the same process, and if the display code of the UI interface is abnormal, the corresponding service cannot be operated normally.

Disclosure of Invention

The embodiment of the invention provides a UI (user interface) display method and device, a cloud server and a storage medium, which are used for reducing the UI development cost of different service modules in a cloud service product and ensuring the operation reliability of the service modules.

In a first aspect, an embodiment of the present invention provides a UI interface display method, which is applied to a UI service of a cloud service product, and the method includes:

receiving a calling request for calling a target UI (user interface) by a target service module in the cloud service product, wherein the calling request comprises input configuration parameters corresponding to the target UI; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the processes in which the UI service operates are different from the processes in which the plurality of service modules operate respectively;

displaying the target UI according to the input configuration parameters;

and feeding back the output result information of the target UI to the target service module.

In a second aspect, an embodiment of the present invention provides a UI interface display device, which is located in a UI service of a cloud service product, and includes:

the receiving module is used for receiving a calling request of a target UI (user interface) called by a target service module in the cloud service product, wherein the calling request comprises input configuration parameters corresponding to the target UI; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the processes in which the UI service operates are different from the processes in which the plurality of service modules operate respectively;

the display module is used for displaying the target UI according to the input configuration parameters;

and the sending module is used for feeding back the output result information of the target UI to the target service module.

In a third aspect, an embodiment of the present invention provides a cloud server, including:

the cloud service product comprises a plurality of service modules and UI services, wherein the UI services provide a plurality of UI interfaces shared by the service modules, and the processes in which the UI services operate are different from the processes in which the service modules operate respectively;

a target service module in the plurality of service modules is used for sending a calling request for calling a target UI (user interface) to the UI service, wherein the calling request comprises input configuration parameters corresponding to the target UI interface; receiving output result information of the target UI interface fed back by the UI service; wherein the target UI interface is one of the plurality of UI interfaces, and the target service module is any one of a plurality of service modules contained in the cloud service product;

and the UI service is used for displaying the target UI interface according to the input configuration parameters and feeding back the output result information of the target UI interface to the target service module.

In a fourth aspect, an embodiment of the present invention provides a non-transitory machine-readable storage medium having stored thereon executable code, which, when executed by a processor of a cloud server, causes the processor to implement at least the UI interface display method according to the first aspect.

In the embodiment of the present invention, a shared UI service is set in the cloud service product, all service modules share the UI service, and the process in which the UI service runs is different from the process in which each service module runs. In the UI service, various UI interfaces for multiplexing all service modules are provided. When a certain target service module needs to display a certain UI (user interface) called as a target UI, triggering a corresponding calling request to the UI service, wherein the calling request carries related configuration parameters required to be input for calling the target UI, so that the UI service completes rendering display of the target UI based on the input configuration parameters, and feeds output result information (such as whether successful display is performed or not and interaction behaviors of a user on the interface) of the target UI back to the target service module.

By combining the UI display requirements of each service module, various UI interfaces with higher use requirements of a plurality of service modules are pre-configured in the UI service, part of interface elements in the UI interfaces are fixed and unchanged, and only part of interface elements can change along with the input configuration parameters of the service modules, so that the difference of the overall visual effect is small when different service modules use the same UI interface, and the consistency of the UI interface style is maintained. The UI display requirements of different service modules are independently provided in another single UI service, all the service modules reuse UI interfaces provided by the UI service in an independent UI service mode, the UI development cost is reduced, the UI display logic is separated from the service logic of the service modules, and the problem that the service modules cannot normally operate due to abnormal UI display can be solved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a schematic composition diagram of a cloud service product according to an embodiment of the present invention;

fig. 2 is a schematic diagram of function distribution of a cloud service product according to an embodiment of the present invention;

fig. 3a is a schematic diagram of a call logic of a file selection dialog type interface according to an embodiment of the present invention;

FIG. 3b is a diagram of a file selection dialog interface according to an embodiment of the present invention;

FIG. 3c is a diagram of another file selection dialog interface provided by an embodiment of the present invention;

fig. 4a is a schematic diagram of a call logic of a dialog interface for uploading and downloading files according to an embodiment of the present invention;

fig. 4b is a schematic diagram of a file upload and download dialog interface according to an embodiment of the present invention;

fig. 5a is a schematic diagram of a call logic of a message prompt dialog type interface according to an embodiment of the present invention;

FIG. 5b is a diagram of a message prompt dialog interface according to an embodiment of the present invention;

FIG. 6a is a schematic diagram of a calling logic of a custom UI interface according to an embodiment of the present invention;

FIG. 6b is a diagram illustrating a custom UI interface according to an embodiment of the invention;

FIG. 6c is a schematic view of an interaction behavior corresponding to the UI interface shown in FIG. 6 b;

FIG. 7 is a diagram illustrating a UI display process according to an embodiment of the invention;

fig. 8 is a schematic structural diagram of a UI interface display device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Some embodiments of the invention are described in detail below with reference to the accompanying drawings. The features of the embodiments and examples described below may be combined with each other without conflict between the embodiments. In addition, the sequence of steps in each method embodiment described below is only an example and is not strictly limited.

Cloud computing providers have provided a variety of cloud service products for users, such as cloud desktops and other cloud applications (applications). Each cloud service product may actually include several service modules, or called function modules, such as an agent (agent) module, a session (session) management module, an Over-The-Air (Firmware Over-The-Air, Fota for short) module, and so on. The service modules are responsible for realizing different service logics in corresponding cloud service products, and UI display requirements are often met in the operation process.

At present, a common UI development logic is to put a service module (i.e. its service logic) and its required UI display function in the same process, and this process is responsible for running the service module and executing the corresponding UI display logic. If this process is abnormally exited due to the UI display, the corresponding service module may also be affected and become unavailable. Moreover, if other service modules of a cloud service product also need the UI display function, development and design of the corresponding service module and the UI display logic needed by the service module need to be performed in other processes, and in fact, if each process develops its own UI display code, development workload is large and much work is repeated.

In order to reduce the development cost of the UI and ensure the reliable operation of the service module, the embodiment of the invention provides a new UI construction and use framework. In summary, in the scheme provided by the embodiment of the present invention, an independent UI service is constructed in a cloud service product, and the UI display function is decoupled from each service module in the cloud service product, that is, any problem of the UI service does not affect each normal service module. In addition, the UI service can provide UI display functions for all service modules in the cloud service product, and each service module does not need to be separately developed with the corresponding UI display function, so that the development cost is reduced.

Fig. 1 is a schematic composition diagram of a cloud service product provided in an embodiment of the present invention, and as shown in fig. 1, the cloud service product includes: a plurality of service modules, and a UI service. In practical applications, the cloud service product may run in a certain cloud server in the cloud, for example, run in a certain virtual machine in the cloud server.

In fig. 1, the UI Service is represented as a GUI-Service, which is responsible for all UI-related display functions, supporting the display requirements of various UI interfaces from multiple clients.

In fig. 1, the plurality of service modules are represented as n service modules as follows: Biz-Service-1, Biz-Service-2, …, Biz-Service-n. The plurality of clients are a plurality of service modules. The Service modules are mainly responsible for realizing different Service functions of the whole cloud Service product, and when the UI needs to be displayed, the GUI-Service is called to display a corresponding UI interface.

As shown in fig. 1, different Service modules run in different processes, such as process 1, process 2, …, process n, illustrated in the figure, and the GUI-Service runs in another independent process, such as process Z illustrated in fig. 1.

In an alternative embodiment, as shown in fig. 1, the Service module may interact with the GUI-Service by means of a communication such as a Remote Procedure Call (gRPC). gRPC communication, gRPC is an efficient communication framework, the data transmission quantity is small, the delay is low, and the delay of UI display caused by cross-process communication can be reduced through the gRPC communication framework.

Of course, in practical application, other communication modes may also be adopted to implement communication between the service module and the UI service according to requirements, such as a pipe, socket communication, shared memory, and the like.

In addition, in practical applications, most of the Service modules included in a cloud Service product may operate in a system Service manner, that is, most of the Service modules provide system (operating system) -level services, and may operate in a kernel state in a system authority, because the Service modules need the system authority to complete corresponding functions, for security, as shown in fig. 2, the UI Service (i.e., GUI-Service in the figure) may operate in a user state, so that it may be avoided that a user performs some operations that may harm the safe operation of the system through the system authority on the UI interface.

In the embodiment of the present invention, since the UI service running independently provides a uniform UI display function for each service module in the cloud service product, that is, each service module multiplexes the UI display function provided by the UI service, the UI display function commonly used by a plurality of service modules can be abstracted, and some UI interfaces with higher abstract usage rates can be configured in the UI service for each service module to call.

As shown in fig. 1, a plurality of common UI interfaces can be obtained by abstracting common UI functions of a plurality of service modules, which mainly include the following three types: a file selection dialog box type interface, a file uploading and downloading dialog box interface, and a message prompt dialog box type interface. The three types of UI interfaces can basically satisfy more than 90% of UI display functions required by cloud product services. In order to deal with the situation that some service modules have special UI display requirements which cannot be met by the three types of UI interfaces, one special type of UI interface can be included in the multiple types of UI interfaces provided by the UI service, which is called a custom UI interface.

In practical application, because various types of UI interfaces provided by the UI service in the cloud service product are used by each service module in the cloud service product, the unified design and development are carried out on each UI interface multiplexed by a plurality of service modules at the UI service side, the consistent overall style of the same type of UI interfaces used by the plurality of service modules can be ensured, and meanwhile, the style consistency among different types of UI interfaces can be considered, so that the style of the UI interfaces and the style of the service modules are kept consistent. The style of the UI interface reflects the overall layout and visual characteristics of the interface.

It will be appreciated that the three types of UI interfaces illustrated above will include many interface elements, such as text, buttons, selection boxes, text boxes, and the like. Interface elements can be divided into two categories in terms of their stability or variability: fixed elements and variable elements. The fixed elements reflect the overall layout and style characteristics of the interface, such as the color, length and width of the text box, the background color of the entire interface, the color, length and width of the progress bar, and the like. The change elements are basically related to different service modules, that is, when different service modules call the same type of interface, some interface elements in the interface can be adjusted according to requirements to match with the call requirements triggered when the service modules execute certain service functions, for example, some text contents displayed in the interface are changed.

Therefore, after various UI interfaces are designed in the UI service, in order to enable each service module to use the UI interfaces, the service modules need to be informed of the existence of the UI interfaces and what types of parameters need to be input when being called. As can be seen from the above descriptions of the fixed elements and the variable elements, in fact, when the service module calls the UI interface, the parameters that need to be input often correspond to the variable elements, and of course, some parameters related to control management and interface selection also need to be input. The UI service can abstract corresponding call interface parameters (i.e., parameter types that need to be input) for each UI interface, and inform each service module, so that when a certain type of UI interface is called, the service module inputs corresponding configuration parameters according to the corresponding parameter types.

The parameters that need to be entered for the different types of interfaces will be exemplified below. Here, it is assumed that the service module already knows the parameter type that needs to be input when each UI interface is called, and then, for a target service module (any one of the plurality of service modules), when a target UI interface (one of the plurality of UI interfaces) needs to be called, a call request including an input configuration parameter corresponding to the target UI interface is triggered to the UI service, where the input configuration parameter is determined according to the known parameter type that needs to be input when the target UI interface is called. After receiving the calling request, the UI service displays a corresponding target UI interface based on the input configuration parameters carried in the calling request, and further feeds back the output result information of the target UI interface to the target service module. Wherein, the output result information may include status information for reflecting whether the target UI interface can be successfully displayed. In addition, if the user triggers some interactive behaviors in the displayed target UI interface, the UI service also responds to the interactive behaviors and feeds back the interactive behavior information triggered by the user on the target UI interface to the target service module.

In summary, three common dialog box interfaces can be provided in the UI service, abstraction of calling input parameters and output information can be performed, for the UI service, basic function display of dialog box interfaces of corresponding types can be satisfied by introducing some basic and important parameters, so that the UI service does not need to expose all UI capabilities of the UI interface to each service module, that is, the service module does not need to care about related information of some interface elements in the UI interface, interaction between the service module and the UI service is simplified, and data transmission amount between the service module and the UI service is reduced.

The three dialog box interfaces are simply introduced, and for the three dialog box interfaces, the three dialog box interfaces are actually equivalent to the three dialog box interfaces already constructed in the UI service, and the service module only needs to call as required and fine-tune part of interface elements therein. However, when the UI functions required to be used by the service module are beyond the coverage of the three dialog interfaces, the service module may also customize the private UI functions based on the custom UI interface provided by the UI service. Briefly, when a service module needs to display a UI, if it is found that there is no UI interface needed by the service module in multiple dialog box interfaces that the UI service can provide, the user-defined UI interface is called, multiple locally configured UI controls are sent to the UI service, so that the UI service displays the multiple UI controls in the user-defined UI interface according to respective corresponding configuration information, receives an interaction behavior of a user, and feeds back the interaction behavior to the service module.

While various UI interfaces that can be provided by the UI service and the process of the service module invoking the UI interfaces are briefly described above, the functions of the various UI interfaces and the types of parameters that need to be input are exemplarily described below with reference to the following embodiments.

Fig. 3a is a schematic diagram of a call logic of a file selection dialog box type interface according to an embodiment of the present invention, and as shown in fig. 3a, when a target service module wants to call a file selection dialog box type UI interface, parameters (params) to be input include: request identification (id), file operation type (type), interface title (title). And the output results (returns) that the UI service needs to feed back to the service module may include: the interface displays the status (status), file-path (file-path).

When a certain UI interface (called a target UI interface) provided by the UI service is called, the target service module triggers a calling request corresponding to the target UI interface to the UI service. Assuming that the target service module calls a file selection dialog box type interface, it will be appreciated that the identification of the interface type may be sent to the UI service in association with the call request, which may be the inclusion of the interface type identification in the call request. As shown in fig. 3a, the file selection dialog box type interface needs to input a parameter type, and the call request further needs to include an input configuration parameter determined by the target service module according to the input parameter type, that is, the input configuration parameter includes a request identifier corresponding to the call request, interface header information, and a target file operation type selected from a plurality of known file operation types.

The request identifier is used for identifying which service module triggers the calling request and which UI interface is called. Since the UI service is shared by multiple service modules, and different service modules may trigger a call request of the UI interface to the UI service, in order to identify a call request sent by each service module each time, the service module needs to generate the request identifier to be carried in the call request.

The file operation type refers to that in an interface such as a file selection dialog box, a file selection dialog box interface (i.e., each specific UI interface included in one type) corresponding to different file operation types can be provided according to a common file operation type. Common file operation types include two types of operations, namely file selection and file saving, so that two types of file selection dialog box interfaces can be set: a file selection dialog interface a and a file save dialog interface B. The two file operation types are notified to each service module in advance, so that the target service module can select the required file operation type according to the requirements of the currently executed service logic, for example, if a certain file is required to be selected currently, the file selection operation is selected; if a file is currently needed to be saved, a file save operation is selected.

The interface title means that the target service module can self-define an interface title information based on the operation type of the target file selected by the target service module.

When the UI service receives a call request containing the input configuration parameters, knowing that the target service module needs to use a target file selection dialog box interface corresponding to the target file operation type (for example, a file selection dialog box interface A or a file storage dialog box interface B), displaying the target file selection dialog box interface, and displaying the interface title information customized by the target service module at the title information position of the interface.

Based on the successful display of the target file selection dialog interface, the user may perform a corresponding file selection or file save operation in the target file selection dialog interface. Regardless of which operation is performed, a corresponding file operation path (e.g., a file selection path, a file saving path) is actually displayed in the target file selection dialog interface, and when the user confirms that the operation is completed, the UI service may know that output result information needs to be fed back to the target service module based on the request identifier, where the output result information may include the file operation path and may also include a display state (e.g., successful display) of the target file selection dialog interface. It can be understood that if the target file selection dialog interface is not successfully displayed, there is no subsequent action of the user for inputting the file operation path, and at this time, only the display status information of the failure of the interface display is fed back.

Fig. 3B and 3c illustrate two specific file selection dialog type interfaces, referred to as file selection dialog interface a and file saving dialog interface B, respectively.

In fig. 3b, it is assumed that the interface title information input by the target service module is: and (4) opening. Assume that the file selection dialog interface a includes a text box 301 for displaying a file selection path, and a text box 302 for displaying a finally selected file name. Based on the user's file selection behavior, the corresponding file selection path is displayed in text box 301, and the file name of the finally selected file is displayed in text box 302. When the user clicks the "open" button in the diagram, the UI service feeds back output result information including the file selection path, the file name, and the like to the target service module.

In fig. 3c, it is assumed that the interface title information input by the target service module is: and stored as follows. It is assumed that the file saving dialog interface B includes a text box 303 for displaying a file saving path, a text box 304 for displaying a file name of a saved file, and a selection box 305 for selecting a file saving type. Based on the user's file save behavior, the corresponding file save path is displayed in text box 303, the finally named file name is displayed in text box 304, and the selected file save type is displayed in selection box 305. When the user clicks the "save" button in the graph, the UI service feeds back output result information including the file save path, file name, and file save type to the target service module.

Fig. 4a is a schematic diagram of a call logic of a file upload and download dialog interface according to an embodiment of the present invention, and as shown in fig. 4a, when a target service module wants to call the file upload and download dialog interface, types of parameters (params) to be input include: request identification (id), interface title (title), file description information (content), transmission progress information (fraction). And the output results (returns) that the UI service needs to feed back to the service module may include: the interface displays the status. Optionally, a subtitle (subtitle) may be included in the input parameter type. The file description information is used for describing the name of the file being uploaded or downloaded.

The meaning of the different parameter types described above is exemplified in connection with fig. 4 b.

In fig. 4b, it is assumed that the interface title information input by the target service module is: the file description information is (file name): rar, the transmission progress information is: 60%, the subtitle information is: the 1 st file is being uploaded, for a total of 1.

Based on the above assumptions, as shown in fig. 4b, in the file upload and download dialog interface, the text content for displaying interface title information may become: has been completed by 60%; the text content for displaying the subtitle becomes: 1 file is being uploaded, and the total number is 1; the text content for displaying the file description information becomes: rar; a color area in the progress bar representing that progress has been completed is rendered to an effect matching 60% progress. When a user clicks a 'pause' button in a graph in the file downloading or uploading process, the UI service feeds back output result information including a pause downloading or uploading instruction to the target service module, and certainly, when the interface is successfully displayed or cannot be displayed, the UI service also feeds back corresponding display state information to the target service module.

Fig. 5a is a schematic diagram of a call logic of a message prompt dialog type interface according to an embodiment of the present invention, and as shown in fig. 5a, when a target service module wants to call the message prompt dialog type interface, types of parameters (params) to be input include: request identification (id), message prompt type (type), interface title (title), and prompt message content (content). And the output results (returns) that the UI service needs to feed back to the service module may include: the interface displays the status.

The preset message prompt type may include, for example, the following types illustrated in the drawing: error prompt type (error), alarm prompt type (warning), general prompt type (tip).

Fig. 5b illustrates the display effect of the interface when the user selects the error prompt type. In fig. 5b, it is assumed that the target service module is transmitting a certain file, and an abnormal error occurs during the transmission process, and at this time, a corresponding message prompt interface needs to be called for error prompt. Assume that the input interface title information is: file transmission, the input prompting message content is: this file exceeds the upper limit of the file size allowed for transmission. Then in the message alert interface corresponding to the error type, "file transfer" is displayed at the text position for displaying the interface title, and "this file exceeds the upper limit of the file size allowed for transfer" is displayed at the text position for displaying the alert message content.

Fig. 6a is a schematic diagram of a calling logic of a custom UI interface according to an embodiment of the present invention, and as shown in fig. 6a, when a target service module wants to call the custom UI interface, types of parameters (params) to be input include: a request identification (id) and a custom UI control List (List < common control >). And the output results (returns) that the UI service needs to feed back to the service module may include: list indicating UI control states in the UI control list: (List < common control status >).

In this embodiment of the present invention, two interface functions may be defined, which are respectively referred to as a first interface function (such as common control described above) and a second interface function (such as common control status described above), and both the two interface functions are supported in each service module and UI service, wherein the first interface function is used for transmitting the relevant configuration information of a plurality of UI controls customized by the service module between the service module and the UI service, the second interface function is used for transmitting the display result states of the plurality of UI controls and the modified configuration information between the UI service and the service module, the modification of the configuration information of one UI control mainly refers to a result of a change of the UI control by a user interaction behavior, for example, in a text box which is not originally filled with content or is filled with initial default content, a user inputs new text content, and then the configuration information of the text box corresponding to the filled content is modified to: new text content entered by the user.

In the first interface function, several UI controls and configuration functions of the controls are supported, such as supporting configuration functions of multiple UI controls, such as Text (Text), a CheckBox (CheckBox), a picture (Image), a Text box (TextEdit), a Button (Button), and the like, where the configuration functions are simply attributes of each UI control and configuration of attribute values, and the attributes include Text content, color, width, length, height, background color, display position, and the like.

In practical application, in the process of customizing a UI interface, the service module may have a plurality of UI controls of the same kind in the UI interface and may include a plurality of different UI controls, and in order to distinguish the UI controls, when the service module configures the UI controls by user, the service module may assign an index identifier (index) to each configured UI control, so as to uniquely identify a UI control in the UI interface. Based on this, for the target service module, according to actual service requirements, each required UI control can be selected, configuration of relevant attribute values can be performed as required, a unique index identifier can be allocated to the UI control, after the configuration operations are completed, the configuration result is packaged through the first interface function, so that a call request corresponding to the user-defined UI interface is triggered to the UI service through the first interface function, and the call request includes configuration information from the UI controls of the first interface function and the index identifier of each UI control.

And after receiving the calling request, the UI service analyzes the configuration information of each UI control and performs rendering display in the user-defined UI according to the configuration information of each UI control.

The display results of the custom UI interface are illustrated in connection with FIG. 6 b. In FIG. 6b, it is assumed that the target service module is configured with several UI controls: the text content is "user name: "601; a text box 602 for entering a user name, the text box initially configured being empty; the text content is' password: "603; a text box 604 for entering a login password, the content of the text box initially configured is empty; and a confirmation button 605. And as shown in fig. 6b, assume that the index identifications of the above 5 UI controls are in turn: index1, index2, index3, index4, and index 5.

After displaying the customized UI interface as shown in fig. 6b, optionally, at this time, the UI service may feed back the status information that the customized UI interface is successfully displayed to the target service module, and then, the user may perform an input operation of a user name and a login password in the interface.

As shown in fig. 6c, assume that the user input the user name "lie somewhere" and the login password is "123456". Based on the user's input behavior, some attribute values of the

text boxes

602 and 604 are changed, i.e., the text content therein is changed from the original blank content to the content input by the user. Based on this, after the user clicks the confirm button 605, the UI service may feed back to the target service module the index identification of the UI control whose property value has changed and the changed property value.

In the above example, the UI service may feed back, to the target service module, result information of the following interaction behaviors: [ index2, something Lei; index4,123456 ]. After receiving the feedback information, the target service module learns that the user name input by the user is 'Lisomewhat' and the login password is '123456' based on the two index identifications, and then can perform subsequent login verification processing.

The UI service can call a second interface function, package the index identifiers of the UI controls and the modified attribute values of the UI controls, feed back a list containing the index identifiers of the modified UI controls and the modified attribute values of the UI controls to the target service module through the second interface function, and the target service module analyzes the index identifiers and the modified attribute values.

In summary, by constructing a UI service independently running in a process in a cloud service product, decoupling UI display from each service module in the cloud service product, and configuring each service module to reuse multiple common UI interfaces provided by the UI service, development cost of the UI interfaces can be reduced, and normal running of the service modules can be guaranteed.

Fig. 7 is a flowchart of a UI interface display method provided in an embodiment of the present invention, where the method may be performed by a UI service of a cloud service product, as shown in fig. 7, and the method includes the following steps:

701. receiving a calling request of a target UI (user interface) called by a target service module in a cloud service product, wherein the calling request comprises input configuration parameters corresponding to the target UI.

The target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the processes in which the UI service operates are different from the processes in which the plurality of service modules operate respectively.

702. And displaying a target UI interface according to the input configuration parameters.

703. And feeding back the output result information of the target UI interface to the target service module.

For the specific implementation process of the scheme provided in this embodiment, reference may be made to the relevant descriptions in the foregoing embodiments, which are not described herein again.

A UI interface display device of one or more embodiments of the present invention will be described in detail below. Those skilled in the art will appreciate that these means can each be constructed using commercially available hardware components and by performing the steps taught in this disclosure.

Fig. 8 is a schematic structural diagram of a UI interface display device according to an embodiment of the present invention, where the UI interface display device corresponds to a UI service in a cloud service product, and as shown in fig. 8, the UI interface display device includes: a receiving module 11, a display module 12 and a sending module 13.

A receiving module 11, configured to receive a call request for a target service module in the cloud service product to call a target UI interface, where the call request includes an input configuration parameter corresponding to the target UI interface; the target service module is any one of a plurality of service modules included in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and processes in which the UI service operates are different from processes in which the plurality of service modules operate respectively.

And the display module 12 is configured to display the target UI interface according to the input configuration parameters.

And the sending module 13 is configured to feed back the output result information of the target UI interface to the target service module.

Optionally, the UI service operates in a user mode.

Optionally, the sending module 13 is further configured to: and informing the service modules of the parameter types which need to be input respectively by using the UI interfaces so as to ensure that the target service module determines the input configuration parameters according to the parameter types corresponding to the target UI interfaces.

Optionally, the target UI interface is a file selection dialog box type interface, and the input configuration parameter includes a request identifier corresponding to the call request, interface header information, and a target file operation type selected from known multiple file operation types. At this time, the display module 12 is specifically configured to: and displaying the interface title information in a target file selection dialog box interface corresponding to the target file operation type, wherein the target file selection dialog box interface comprises a file path operation box corresponding to the target file operation type. The sending module is further configured to: and receiving a file operation path input by a user in the file path operation frame. The sending module is specifically configured to: and feeding back the file operation path to the target service module according to the request identifier.

Optionally, the target UI interface is a file upload and download dialog interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, file description information of upload or download, and transmission progress information. At this time, the display module 12 is specifically configured to: and displaying the interface title information, the file description information and the transmission progress information in the file uploading and downloading dialog box interface. The sending module is specifically configured to: and feeding back the display state of the file uploading and downloading dialog box interface to the target service module according to the request identifier.

Optionally, the target UI interface is a message prompt dialog box type interface, and the input configuration parameter includes a request identifier corresponding to the invocation request, interface title information, prompt message content, and a target message prompt type selected from a plurality of known message prompt types. At this time, the display module 12 is specifically configured to: in a target message prompt interface corresponding to the target message prompt type, displaying the interface title information and the prompt message content, where the sending module is specifically configured to: and feeding back the display state of the target message prompt interface to the target service module according to the request identifier.

Optionally, the target UI interface is a custom UI interface, and the input configuration parameter includes a request identifier corresponding to the invocation request, multiple UI controls configured by the target service module in a custom manner, and index identifiers corresponding to the multiple UI controls. At this time, the display module 12 is specifically configured to: and displaying the plurality of UI controls according to the index identifications corresponding to the plurality of UI controls in the user-defined UI interface. The receiving module 11 is further configured to: and receiving the interaction behavior information of the user on the target UI control in the plurality of UI controls. The sending module 13 is further configured to: and feeding back the display state of the user-defined UI interface, the index identification corresponding to the target UI control and the interaction behavior information to the target service module according to the request identification.

The apparatus shown in fig. 8 may perform the steps performed by the UI service in the foregoing embodiment, and the detailed performing process and technical effect refer to the description in the foregoing embodiment, which are not described herein again.

In addition, the present invention provides a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of a cloud server, causes the processor to implement at least the steps performed by the UI service as in the foregoing embodiments.

The above described embodiments of the apparatus are merely illustrative, wherein the network elements illustrated as separate components may or may not be physically separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course, can also be implemented by a combination of hardware and software. With this understanding in mind, the above-described aspects and portions of the present technology which contribute substantially or in part to the prior art may be embodied in the form of a computer program product, which may be embodied on one or more computer-usable storage media having computer-usable program code embodied therein, including without limitation disk storage, CD-ROM, optical storage, and the like.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A UI interface display method is applied to a UI service of a cloud service product and comprises the following steps:

displaying the target UI according to the input configuration parameters;

2. The method of claim 1, wherein the UI service operates in a user mode.

3. The method of claim 1, further comprising:

and informing the service modules of the parameter types which need to be input respectively by using the UI interfaces so as to ensure that the target service module determines the input configuration parameters according to the parameter types corresponding to the target UI interfaces.

4. The method of claim 1, wherein receiving a call request for a target service module in the cloud service product to call a target UI interface comprises:

and receiving a calling request for calling the target UI interface, which is triggered by the target service module through a remote procedure calling mode.

5. The method according to any one of claims 1 to 4, wherein the target UI interface is a file selection dialog box type interface, and the input configuration parameters include a request identifier corresponding to the call request, interface header information, and a target file operation type selected from a plurality of known file operation types;

the displaying the target UI interface according to the input configuration parameters comprises:

displaying the interface title information in a target file selection dialog box interface corresponding to the target file operation type, wherein the target file selection dialog box interface comprises a file path operation box corresponding to the target file operation type;

the feeding back the output result information of the target UI interface to the target service module comprises the following steps:

receiving a file operation path input by a user in the file path operation frame;

and feeding back the file operation path to the target service module according to the request identifier.

6. The method according to any one of claims 1 to 4, wherein the target UI interface is a file upload and download dialog box interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, file description information for upload or download, and transmission progress information;

displaying the interface title information, the file description information and the transmission progress information in the file uploading and downloading dialog box interface;

and feeding back the display state of the file uploading and downloading dialog box interface to the target service module according to the request identifier.

7. The method according to any one of claims 1 to 4, wherein the target UI interface is a message prompt dialog type interface, and the input configuration parameters include a request identifier corresponding to the invocation request, interface title information, prompt message content, and a target message prompt type selected from a plurality of known message prompt types;

displaying the interface title information and the prompt message content in a target message prompt interface corresponding to the target message prompt type;

and feeding back the display state of the target message prompt interface to the target service module according to the request identifier.

8. The method according to any one of claims 1 to 4, wherein the target UI interface is a custom UI interface, and the input configuration parameters include a request identifier corresponding to the invocation request, a plurality of UI controls configured by the target service module in a custom manner, and index identifiers corresponding to the plurality of UI controls;

displaying the plurality of UI controls according to the index identifications corresponding to the plurality of UI controls in the user-defined UI interface;

receiving interaction behavior information of a user on a target UI control in the plurality of UI controls;

and feeding back the display state of the user-defined UI interface, the index identification corresponding to the target UI control and the interaction behavior information to the target service module according to the request identification.

9. A UI interface display apparatus, provided in a UI service of a cloud service product, the apparatus comprising:

10. A cloud server, comprising:

11. The cloud server of claim 10, wherein the UI service operates in a user mode.

12. The cloud server of claim 10, wherein the plurality of UI interfaces comprises at least one of: a file selection dialog box type interface, a file uploading and downloading dialog box interface, a message prompt dialog box type interface and a user-defined UI interface.

13. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of a cloud server, causes the processor to perform the UI interface display method of any one of claims 1 to 8.