Software service deployment method, electronic device, and storage medium

Abstract

The application provides a software service deployment method, comprising: establishing a community service unit according to an agent unit, a flow engine and a plurality of software service units; receiving a service request from a client through the agent unit; sending the service request to a first software service unit in the plurality of software service units; sending a connection request to the flow engine based on a domain name system service through the first software service unit; connecting the first software service unit and at least one second software service unit in the plurality of software service units through the flow engine; and responding to the service request of the client through the first software service unit and the at least one second software service unit. The application also provides an electronic device and a storage medium. The application connects a plurality of software service units in the form of establishing a community service unit, so as to enhance the interactivity between software as a service.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software service, and particularly relates to a software service deployment method, an electronic device and a storage medium. BACKGROUND

[0002] Nowadays, a platform as a service (PaaS) provided by a cloud computing service can provide a hardware and software running environment for a software as a service (SaaS), so that a developer can conveniently deploy the SaaS into a cloud microservice. Since different Saas are independent and irrelevant to each other, each SaaS provides a microservice, and therefore when a connection between different Saas is established, connection information of another SaaS, such as a public address or a port, needs to be written in a program code in a development stage of the SaaS, or the port information of the other SaaS is disclosed in a wide area network (WAN), and a geographical location of the SaaS deployment also affects the connection with other Saas, so that it is inconvenient to combine multiple Saas to provide a software service, and the interactivity between Saas is weak. SUMMARY

[0003] In view of the above, it is necessary to provide a software service deployment method, an electronic device and a storage medium, which connect multiple software service units by establishing a community service unit, so as to enhance the interactivity between Saas.

[0004] A first aspect of the present application provides a software service deployment method, which comprises:

[0005] establishing a community service unit according to an agent unit, a flow engine and multiple software service units;

[0006] receiving a service request from a client through the agent unit;

[0007] sending the service request to a first software service unit in the multiple software service units;

[0008] sending a connection request to the flow engine through the first software service unit based on a domain name system service;

[0009] connecting the first software service unit and at least one second software service unit in the multiple software service units through the flow engine; and

[0010] responding to the service request of the client through the first software service unit and the at least one second software service unit.

[0011] Preferably, the method further comprises:

[0012] sending the service request to an authentication unit for authentication when the service request is received by the proxy unit;

[0013] sending the service request to the first software service unit when the service request is authenticated; or

[0014] sending a rejection message to the client when the service request information fails authentication.

[0015] Preferably, the sending the service request to the first software service unit comprises:

[0016] sending authentication information in the service request to the first software service unit according to a domain name of the first software service unit.

[0017] Preferably, the connecting the first software service unit and at least one second software service unit in the plurality of software service units through the flow engine comprises:

[0018] connecting the first software service unit and the at least one second software service unit through the flow engine according to a preset workflow and a name of each second software service unit.

[0019] Preferably, the connecting the first software service unit and the at least one second software service unit through the flow engine according to a preset workflow and a name of each second software service unit comprises:

[0020] sending the connection request to the second software service unit through the flow engine according to a preset workflow and a domain name corresponding to the name of the second software service unit;

[0021] determining whether there is a second software service unit responding to the connection request; and

[0022] connecting the first software service unit and the second software service unit responding to the connection request.

[0023] Preferably, the method further comprises:

[0024] establishing a connection with a software service repository, wherein the software service repository comprises a plurality of software service units, each software service unit comprises a plurality of copies and an application software composed of the copies.

[0025] Preferably, the method further comprises:

[0026] The plurality of software service units for establishing the community service unit are selected from the software service resource library according to a service type provided by the community service unit and a type of the application software.

[0027] Preferably, the establishing the community service unit according to the agent unit, the flow engine and the plurality of software service units comprises:

[0028] The plurality of community service units are established according to the agent unit, the flow engine and the plurality of software service units, wherein each community service unit corresponds to a service type.

[0029] The receiving the service request from the client by the agent unit comprises:

[0030] The receiving the service request matching the service type of the current community service unit by the agent unit.

[0031] A second aspect of the present application provides an electronic device, comprising:

[0032] a processor; and

[0033] a memory, the processor being configured to implement the software service deployment method when executing a computer program stored in the memory.

[0034] A third aspect of the present application provides a computer readable storage medium having a computer program stored thereon, the computer program being configured to implement the software service deployment method when executed by a processor.

[0035] The software service deployment method, the electronic device and the storage medium can establish a community service unit, and when receiving a service request from a client, connect a plurality of software service units through a domain name system service to provide software services with a theme function, thereby effectively enhancing the interactivity between software as a service. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor based on the provided drawings.

[0037] Figure 1 is a schematic diagram of an application environment architecture of the software service deployment method provided by the preferred embodiment of the present application.

[0038] Figure 2 is a flowchart of the software service deployment method provided by the preferred embodiment of the present application. is a schematic diagram of an application environment architecture of the software service deployment method provided by the preferred embodiment of the present application.

[0039] Figure 3 is a schematic diagram of a software service repository provided by a preferred embodiment of the present application.

[0040] Figure 4 is a schematic diagram of an application structure of a software service deployment system provided by a preferred embodiment of the present application.

[0041] Figure 5 is a schematic diagram of an electronic device provided by a preferred embodiment of the present application.

[0042] Explanation of main component symbols

[0043] Electronic device 1

[0044] Processor 10

[0045] Software service deployment system 100

[0046] Communication module 101

[0047] Selection module 102

[0048] Establishment module 103

[0049] Reception module 104

[0050] Authentication module 105

[0051] Sending module 106

[0052] Connection module 107

[0053] Response module 108

[0054] Memory 20

[0055] Computer program 30

[0056] Community service unit 40

[0057] Software service unit 41

[0058] Agent unit 42

[0059] Flow engine 43

[0060] Authentication unit 44

[0061] Server 2

[0062] Software service repository 201

[0063] Client 3

[0064] The following detailed description will further explain the present application in conjunction with the above-mentioned figures. DETAILED DESCRIPTION

[0065] In order to enable a more clear understanding of the above-mentioned objects, features and advantages of the present application, the present application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0066] In the following description, a large number of specific details are set forth in order to facilitate a thorough understanding of the present application. The described embodiments are merely some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0067] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application belongs. The terms used in the specification of the present application are only for the purpose of describing the specific embodiments and are not intended to limit the present application.

[0068] Please refer to Figure 1 Fig. 1 is a schematic diagram of an application environment architecture of a software service deployment method provided by a preferred embodiment of the present application.

[0069] The software service deployment method in the present application is applied in an electronic device 1, which establishes a communication connection with at least one server 2 and at least one client 3 through a network. The network can be a wired network or a wireless network, such as radio, wireless fidelity (WI-FI), cellular, satellite, broadcast, etc.

[0070] The electronic device 1 can be an electronic device running a software service deployment program, such as a personal computer, a server, etc., wherein the server can be a single server, a server cluster or a cloud server, etc.

[0071] The server 2 can be a single server, a server cluster or a cloud server, etc.

[0072] The client 3 can be various smart electronic devices, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, a server, etc.

[0073] Please refer to Figure 2 Fig. 2 is a flowchart of a software service deployment method provided by a preferred embodiment of the present application. The order of the steps in the flowchart can be changed, and some steps can be omitted according to different needs.

[0074] S201, a connection is established with a software service resource library 201.

[0075] In the embodiment, the software service repository 201 is stored in the server 2. The electronic device 1 is connected to the server 2 through a network, i.e. connected to the software service repository 201. Please refer to Figure 3 As shown in the figure, the software service repository 201 includes a plurality of software service units 41, each of which includes a plurality of copies and application software composed of the copies, such as Figure 3 news application software (news v1.0) in the figure. The types of the application software can include, but are not limited to, news, stock market, and food.

[0076] S202, the software service repository 201 selects a plurality of software service units 41 to establish the community service unit 40 according to the type of service provided by the community service unit 40 and the type of the application software.

[0077] It should be noted that the community service unit 40 at this time is a community service unit to be established. The type of service provided by the community service unit 40 can include, but is not limited to, news, stock market, and food.

[0078] S202 specifically includes: selecting the plurality of software service units 41 according to the type of application software matching the type of service provided by the community service unit 40 to be established. For example, when the type of service provided by the community service unit 40 to be established is news, a plurality of software service units 41 including news application software are selected. Among them, the plurality of software service units 41 matching the type of service provided by the community service unit 40 can be automatically selected according to type matching, or the plurality of software service units 41 matching the type of service provided by the community service unit 40 can be selected in response to the manual operation of the establisher of the community service unit 40.

[0079] S203, the community service unit 40 is established according to the agent unit 42, the flow engine 43 and the plurality of software service units 41.

[0080] In the embodiment, the community service unit 40 is established based on K8S Namespace (Kubernetes Namespace), and the agent unit 42, the flow engine 43 and the plurality of software service units 41 are all containers (POD) in the K8S Namespace.

[0081] In the embodiment, the proxy unit 42 is a TCP (Transmission Control Protocol) proxy module or a TCP proxy server, and the flow engine 43 is configured to provide a service flow management based on the selected software service units 41. The software service units 41 include at least one application software configured to provide a corresponding service. The community service units 40 are configured to provide software services with unique and thematic functions based on the application software of the software service units 41, such as news collection services, stock market query services, and food query services.

[0082] Further, S203 can include establishing the community service units 40 based on the proxy units 42, the flow engines 43, and the software service units 41. Each community service unit corresponds to a service type.

[0083] In other embodiments, S203 can include establishing the community service units 40 based on the proxy units 42, the flow engines 43, the authentication unit 44, and the software service units 41.

[0084] S204 receives a service request from the client 3 through the proxy unit 42.

[0085] In the embodiment, the service request includes a service name and authentication information. The service name is transmitted to the proxy unit 42 through a domain name sent by the client 3. For example, the domain name can be http: / / domain / service_name / index.html. The authentication information is a JWT (JSON Web Token) that includes the identity information of the user of the client 3.

[0086] S204 specifically includes determining the service name through the domain name sent by the client 3, so that the proxy unit 42 of the community service unit 40 with a service type matching the service name receives the service request. For example, when the service name in the service request is news, the proxy unit 42 of the community service unit 40 with a news service type receives the service request.

[0087] S205 sends the service request to a first software service unit in the software service units 41.

[0088] In the embodiment, the first software service unit runs in the electronic device 1, which is a preset target software service unit for responding to the service request. S205 specifically includes: sending the authentication information of the service request to the first software service unit by sending a domain name corresponding to the name of the first software service unit. For example, the domain name corresponding to the name of the first software service unit is http: / / Target-SaaS / index.html. Wherein, Target-SaaS is the name of the first software service unit.

[0089] In the embodiment, the authentication information is the header of JWT (JSON Web Token).

[0090] In other embodiments, the method further includes: when the proxy unit 42 receives the service request, sending the service request to the authentication unit 44 for authentication. Specifically, the authentication information (JWT) in the service request is sent to the authentication unit 44 for authentication, and when the authentication information is the same as the preset authentication information, it is determined that the service request is authenticated; when the authentication information is different from the preset authentication information, it is determined that the service request fails to authenticate. The method further includes: when the service request is authenticated, sending the service request to the first software service unit. When the service request information fails to authenticate, sending a rejection information to the client 3 to reject the service request. Wherein, the rejection information can be not responding to the service request, or the content can be a prompt information of "request failure", and the prompt information can be displayed in the form of a pop-up window on the client 3 to prompt the user of the client 3.

[0091] S206, based on the domain name system (DNS) service, sending a connection request to the flow engine 43 through the first software service unit.

[0092] In the embodiment, when the first software service unit of the community service unit 40 receives the service request, the community service unit 40 provides the client 3 sending the service request with a software service with a theme function, and the plurality of software service units 41 in the community service unit 40 need to cooperate to provide the client 3 with services through a plurality of application softwares in the plurality of software service units 41. Therefore, the first software service unit sends a connection request to other software service units through the flow engine 43 to connect other software service units, so as to establish the cooperative service among the plurality of software service units 41. The first software service unit sends the connection request to the flow engine 43 by sending the domain name of the flow engine 43 based on the domain name system service. The domain name is protocol: / / Flow-Engine, and Flow-Engine is the name of the flow engine 43. For example, the domain name is http: / / Flow-Engine / api.

[0093] S207, connecting the first software service unit and at least one second software service unit in the plurality of software service units 41 through the flow engine 43.

[0094] In the embodiment, the at least one second software service unit is a software service unit in the plurality of software service units 41 except the first software service unit. The at least one second software service unit can run in the electronic device 1 or in other servers, such as the server 2. In the embodiment, the preset workflow of the flow engine 43 is the order of connecting the at least one second software service unit.

[0095] S207 specifically includes: connecting the first software service unit and the at least one second software service unit through the flow engine 43 according to the preset workflow and the name of each second software service unit. Specifically, according to the preset workflow and the domain name corresponding to the name of the second software service unit, the flow engine 43 sends the connection request to the second software service unit, judges whether there is a second software service unit responding to the connection request, and connects the first software service unit and the second software service unit responding to the connection request. It should be noted that when the second software service unit is in a maintenance or fault state, it cannot normally provide services, and therefore cannot respond to the connection request.

[0096] The domain name is protocol: / / saas-name, and saas-name is the name of the second software service unit. For example, the domain name of the second software service unit with the name SaaS-A is http: / / SaaS-A / / api.

[0097] S208, responding to the service request of the client 3 by the first software service unit and the at least one second software service unit.

[0098] In the embodiment, when the first software service unit is connected with the at least one second software service unit, the application software in the first software service unit and the application software in the at least one second software service unit together provide the client 3 with the service corresponding to the service name in the service request, so as to realize the function of the community service unit 40 providing the service with the theme function. For example, the news application software in the first software service unit and the news application software in the at least one second software service unit together provide the client 3 with the news service, so as to realize the function of the community service unit 40 providing the news service with the news type.

[0099] When there is no second software service unit responding to the connection request sent by the stream engine 43, the stream engine 43 feeds back the result that there is no second software service unit responding to the connection request to the first software service unit, and the first software service unit responds to the service request and provides the client 3 with the software service by the application software in the first software service unit.

[0100] The software service deployment method provided by the application can establish a community service unit, and when receiving a service request from a client, connect multiple software service units through a domain name system service to provide software service with a theme function, thereby effectively enhancing the interactivity between software as a service.

[0101] The above Figure 2 The software service deployment method of the application is described in detail below, and the function modules of the software service deployment system and the hardware device architecture for implementing the software service deployment method are described below in combination with FIGS. 4-5.

[0102] It should be understood that the embodiments are only for illustration, and the scope of the patent application is not limited by the structure.

[0103] Please refer to Figure 4 FIG. 4 shows a structural diagram of a software service deployment system provided by a preferred embodiment of the application.

[0104] In some embodiments, the software service deployment system 100 is running in the electronic device 1. The electronic device 1 is connected with a server 2 and a client 3 through a network. The software service deployment system 100 can include a plurality of functional modules composed of program code segments. The program code of each program segment in the software service deployment system 100 can be stored in the memory of the electronic device 1 and executed by the at least one processor to realize the software service deployment function.

[0105] In the present embodiment, the software service deployment system 100 can be divided into a plurality of functional modules according to the functions it performs. Referring to Figure 3 As shown, the functional modules can include a communication module 101, a selection module 102, an establishment module 103, a receiving module 104, an authentication module 105, a sending module 106, a connection module 107, and a response module 108. The module referred to in the present application refers to a series of computer program segments that can be executed by at least one processor and can complete a fixed function, which are stored in the memory.

[0106] The communication module 101 is used to establish a connection with the software service repository 201.

[0107] The selection module 102 is used to select a plurality of software service units 41 from the software service repository according to the service type provided by the community service unit 40 and the type of the application software.

[0108] The establishment module 103 is used to establish the community service unit 40 according to the proxy unit 42, the flow engine 43, and the plurality of software service units 41.

[0109] The receiving module 104 is used to receive a service request from the client 3 through the proxy unit 42.

[0110] The authentication module 105 is used to send the service request to the authentication unit 44 for authentication when the proxy unit 42 receives the service request.

[0111] The sending module 106 is used to send the service request to a first software service unit in the plurality of software service units 41.

[0112] In other embodiments, the sending module 106 is used to send the service request to the first software service unit when the service request is authenticated; and send a rejection message to the client 3 when the service request information fails to be authenticated.

[0113] The sending module 106 is also used to send a connection request to the flow engine 43 through the first software service unit based on a domain name system service.

[0114] The connection module 107 is configured to connect the first software service unit and at least one second software service unit in the plurality of software service units 41 through the flow engine 43.

[0115] The response module 108 is configured to respond to the service request of the client 3 through the first software service unit and the at least one second software service unit.

[0116] The software service deployment system provided by the present application can establish a community service unit, and connect a plurality of software service units through a domain name system service when receiving a service request from a client, so as to provide software service with a theme function, and effectively enhance the interactivity between software as a service.

[0117] Please refer to Figure 5 Fig. 1 is a schematic diagram of an electronic device 1 provided by a preferred embodiment of the present application.

[0118] The electronic device 1 comprises a processor 10, a memory 20, a computer program 30 stored in the memory 20 and executable on the processor 10, and a community service unit 40. For example, the computer program is a software service deployment program. The processor 10 implements the steps in the above-mentioned software service deployment method embodiments when executing the computer program 30, for example Figure 2 Fig. 1 shows steps S201-S208. Alternatively, the processor 10 implements the functions of the modules / units in the above-mentioned software service deployment system 100 embodiments when executing the computer program 30, for example Figure 4 the modules 101-108 in Fig. 1.

[0119] For example, the computer program 30 can be divided into one or more modules / units, which are stored in the memory 20 and executed by the processor 10 to complete the present application. The one or more modules / units can be a series of computer program instruction segments capable of completing a specific function, which are used to describe the execution process of the computer program 30 in the electronic device 1. For example, the computer program 30 can be divided into Figure 3 the communication module 101, the selection module 102, the establishment module 103, the receiving module 104, the authentication module 105, the sending module 106, the connection module 107, and the response module 108 in Fig. 1.

[0120] Those skilled in the art can understand that the schematic diagram is only an example of the electronic device 1, and does not constitute a limitation on the electronic device 1, which can include more or fewer components than shown, or combine certain components, or different components, for example, the electronic device 1 can also include an input / output device, a network access device, a bus, etc.

[0121] The processor 10 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor 10 can also be any conventional processor. The processor 10 is a control center of the electronic device 1, and connects various parts of the electronic device 1 through various interfaces and lines.

[0122] The memory 20 can be used to store the computer program 30 and / or modules / units. The processor 10 realizes various functions of the electronic device 1 by running or executing the computer program and / or modules / units stored in the memory 20, and calling data stored in the memory 20. The memory 20 can mainly include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required for a function (such as a sound playing function, an image playing function, etc.), etc. The data storage area can store data created according to the use of the electronic device 1 (such as audio data, a phone book, etc.), etc. In addition, the memory 20 can include volatile and nonvolatile memories, such as a hard disk, a memory, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, at least one disk storage device, a flash memory device, or other memory devices.

[0123] The community service unit 40 is a running environment in platform as a service, and is used to provide unique software services with theme functions. The community service unit 40 includes a plurality of software service units 41, an agent unit 42, a flow engine 43, and an authentication unit 44.

[0124] The modules / units integrated in the electronic device 1 are stored in a computer readable storage medium if they are realized in the form of software function units and sold or used as independent products. Based on such understanding, all or part of the processes in the above-mentioned embodiment methods can also be completed by a computer program instructing related hardware. The computer program can be stored in a computer readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by a processor. The computer program includes computer program code, which can be in the form of source code, object code, executable files or some intermediate forms. The computer readable medium can include any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM) and the like.

[0125] The software service deployment method, electronic device and storage medium provided by the application can establish a community service unit, and when receiving a service request from a client, connect multiple software service units through a DNS service to provide software services with theme functions, thereby effectively enhancing the interactivity between software as a service.

[0126] In several embodiments provided by the application, the disclosed electronic device and method can be implemented by other ways. For example, the above-mentioned electronic device embodiments are only illustrative, and for example, the division of the units is only a logical function division, and another division mode can be used in actual implementation.

[0127] In addition, each function unit in each embodiment of the application can be integrated in the same processing unit, or each unit can exist physically, or two or more units can be integrated in the same unit. The integrated unit can be realized in the form of hardware or in the form of hardware plus software function module.

[0128] It is apparent to a person skilled in the art that the present application is not limited to the details of the above-described exemplary embodiments, but can be implemented in other concrete forms without departing from the spirit or essential characteristics of the present application. Therefore, the embodiments should be considered in all respects as illustrative and not restrictive, the scope of the present application being defined by the appended claims rather than the above description, and it is intended that all changes falling within the meaning and range of equivalency of the claims are embraced therein. Any reference signs in the claims should not be construed as limiting the claims to the figures in which the reference signs are used. Further, it is apparent that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. Multiple units or electronic devices recited in an electronic device claim can also be implemented by one unit or electronic device by means of software or hardware. The words first, second etc. are used to distinguish names only and do not necessarily indicate any particular order.

[0129] The above embodiments are only used to illustrate the technical solutions of the present application but not limit the present application, and although the present application is described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present application can be modified or equivalent replaced without departing from the spirit and scope of the present application.

Claims

1. A software service deployment method, characterized in that: The method comprises: Establishing a connection with a software service resource library, wherein the software service resource library includes a plurality of software service units, each software service unit includes a plurality of replicas and application software composed of the replicas; selecting, from the software service resource library, the plurality of software service units for establishing the community service unit according to the service type provided by the community service unit and the type of the application software, wherein the application software types of the plurality of software service units for establishing the community service unit match the service type provided by the community service unit; Establishing a plurality of community service units according to the proxy unit, the flow engine and the plurality of software service units, wherein each community service unit corresponds to a service type; Receiving, through the proxy unit, a service request from a client that matches a service type of the current community service unit; Sending the service request to a first software service unit among the multiple software service units of the current community service unit; Based on the domain name system service, sending the connection request to the stream engine through the first software service unit; Connecting the first software service unit and at least one second software service unit among the multiple software service units of the current community service unit through the flow engine includes: sending the connection request to the second software service unit through the flow engine according to a preset workflow and a domain name corresponding to the name of the second software service unit; determining whether there is a second software service unit that responds to the connection request; and connecting the first software service unit to the second software service unit that responds to the connection request; and The service request of the client is responded to through the first software service unit and the at least one second software service unit.

2. The software service deployment method according to claim 1, wherein: The method further comprises: When the proxy unit receives the service request, it sends the service request to the authentication unit for authentication; When the service request is authenticated, sending the service request to the first software service unit; or When the service request information authentication fails, a rejection message is sent to the client.

3. The software service deployment method according to claim 2, wherein: The sending the service request to the first software service unit includes: The authentication information in the service request is sent to the first software service unit according to the domain name of the first software service unit.

4. An electronic device, characterized in that: The electronic device comprises: processor; and The memory is configured to implement the software service deployment method according to any one of claims 1 to 3 when the processor is configured to execute the computer program stored in the memory.

5. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the software service deployment method according to any one of claims 1 to 3 is implemented.

Images