English:
[0001] Ubiquitous remote access to service instances has become commonplace as a result of the growth and availability of broadband and wireless network access. As such, users are accessing service instances using an ever-growing variety of client devices (e.g., mobile devices, tablet computing devices, laptop/notebook/desktop computers, etc.). The service instances may be accessed over a remote server that may communicate messages that contain data or other information between service instances and client devices over a variety of networks including, 3G and 4G mobile data networks, wireless networks such as WiFi and WiMax, wired networks, etc.
[0002] There may be a limited number of service instances available at any given time due to resource or physical constraints. As such, clients attempting to connect to service instances may be unable to do so. This may cause a problem for a client that needs to access a service that is in-use by another client or in an idle waiting state after a client has established communications.
[0003] Disclosed herein are systems and methods for requesting termination of a service instance that is owned by a client computing device when, for example, there is limited availability of such service instances. In accordance with an aspect of the disclosure, a method for requesting termination of a service instance executing on a remote application server, the service instance being owned by a first client device, is described. The method may include receiving, at a second client device, a list of service instances to which a request may be made, the list of service instances including the service instance; requesting, by the second client device, termination of the service instance; forwarding a request to the first client device to terminate the service instance; and creating a new service instance if the service instance owned by the first client device is terminated whereafter the second client device becomes the owner of the new service instance.
[0004] Other systems, methods, features and/or advantages will be or may become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features and/or advantages be included within this description and be protected by the accompanying claims.
[0005] The components in the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding parts throughout the several views.
[0006] FIG. 1 is a simplified block diagram illustrating an environment for providing access to limited service instances;
[0007] FIG. 2 is an example operational flow for providing and requesting access to limited service instances;
[0008] FIGS. 3A-3B are simplified block diagrams illustrating an example of providing access to limited service instances in accordance with the operational flow of FIG. 2 within the environment of FIG. 1;
[0009] FIGS 4-6 illustrate example user interfaces associated with the operational flow of FIG. 2;
[0010] FIG. 7 is a simplified block diagram illustrating another example environment for providing access to limited service instances; and
[0011] FIG. 8 illustrates an exemplary computing device.
[0013] FIG. 1 is a simplified block diagram illustrating an environment 100 for providing access to limited service instances. In accordance with some implementations, one or more service instances 1/2 may be provided, which may be, applications, data providers, etc. that are remotely accessed by client devices 108A/108B/108C. The service instances 1/2 may be executed on application servers (not shown) that each may run multiple service instances as resources permit. Users of the client devices 108A/108B/108C may enter a predetermined connection Uniform Resource Locator (URL) in a client user interface (Ul) 109 A/109 B/109C to connect to the service instances 1/2 through a resource manager 106 over a communications network 112. The network 112 may be any type of network, for example, the Internet, Ethernet, Wi-Fi (IEEE 802.11x), WiMax (IEEE 802.16), Ethernet, 3G, 4G, LTE, etc.
[0015] The resource manager 106 is provided with a mechanism to enable a client device 108A/108B/108C to request termination of a service instance when no service instances are available. The resource manager 106 may maintain a list of service instances 107 that are registered therewith (as described below). The list may include information about each of the service instances, such as, but is not limited to, the token associated with the service instance, host information (e.g. username, full name, department, etc.), and post-session information (e.g., status of session, idle/non-idle state, etc.). The idle time is a period of time when a user does not interact with the service instance. Further details of the resource manager 106 will be described below with reference to FIG. 2.
[0016] The resource manager 106 may be executing on a same or different server than the service instances 1/2. The service instances 1/2 may connect to the resource manager 106 at a predetermined Internet Protocol (IP) address and/or socket or using a URL associated with the resource manager 106 to register itself with the resource manager 106. In some instances, the service instances 1/2 may connect to the resource manager 106 over the network 112 to register with the resource manager 106. Once registered, the service instance 1/2 is queued such that a client device may connect therewith. Queued service instances may be referenced by a unique instanceld. The client device may connect to the service instance by connecting to the resource manager 106 and may either connect to a specific service instance of the queued service by using the application instanceld or connect to the first available queued service instance of a particular type using the application name.
[0017] The service instance 1/2 may be an "unmanaged service," which is a service that may reside on a same or different server (node) than a server (node) of the resource manager 106. In unmanaged services, the application/process life cycle is not managed by the resource manager 106.
[0018] The servers and client devices 108A/108B/108C described above may be implemented using hardware such as that shown in the general purpose computing device of FIG. 8. Software, applications (e.g., the service instance 1/2, the resource manager 106, and the client Ul 109 A/109 B/109C) operating systems, etc. may be executed in memory and on the processer of the general purpose computing device of FIG. 8.
[0019] FIG. 2 is an example operational flow 200 for providing and requesting access to limited service instances that may be implemented in environment 100. FIGS. 3A- 3B illustrate connectivities and data flow in the environment 100 in accordance with the operational flow 200. Initially, as shown in FIG. 3A, the client device 108A is Owner 1, which owns Service Instance 1 in Slot 1. Service Instance 1 is displayed in the client Ul 109A (see, connection 302). Therefore, Owner 1 is provided with Token 1. Client device 108B is Owner 2 and owns Service Instance 2 in Slot 2. Service Instance 2 is displayed in the client Ul 109B (see, connection 303). As such, Owner 2 is provided with Token 2.
[0020] At 202, an "intruder" may request access to a new service instance; however, the intruder is denied access. As used herein, the client device (e.g., 108C) requesting termination of one or more service instances is called an "intruder." For example, the intruder— client device 108C - may make a request to the resource manager 106 to access a new service instance, but is denied as there may be no resource available for a new service instance (see, reference numeral 304a).
[0021] At 204, the intruder is presented with a list of service instances. For example, the intruder may be authenticated by the resource manager 106 and presented a table or the list of service instances 107 to which the intruder may request termination of (see, reference numeral 306). An example user interface showing the list of services is shown in FIG. 4.
[0022] The list of service instances may be sorted or prioritized in accordance with a level access or authority assigned to the intruder, an importance of the particular service instance, resources available at the application server on which the service instance executes, or other criteria. The information provided to the intruder at 204 may also be sorted according to pre-configured rules, e.g., the access/authority level (e.g., a user will not see instances associated with other users having higher levels of authority or access), idle time, department, position, user preferences, etc., or manually sorted by the intruder. The list of service instances may include service instances and their respective tokens (e.g., Token 1, Token 2, etc.).
[0023] At 205, the intruder selects a service instance (or instances) from the list of service instances 107. As shown in FIG. 4, the intruder may request termination of Service Instance 2 by clicking a checkbox. A limited access connection may be established that connects the intruder to the session, however the intruder does not collaboratively participate in the session, nor is the intruder visible to other client devices in the session. The resource manager 106 may also hold Slot 2 for the intruder so no other intruder or user may connect to a service instance ahead of the intruder.
[0024] At 206, the intruder may request termination of one or more service instances. For example, in the dialog box of FIG. 4, the user at the intruder has selected a service instance to request termination (e.g., Service Instance 2 owned by Owner 2). Using an inter-client communication mechanism provided by the environment 100, the intruder contacts the client devices of sessions associated with the service instances to which the intruder is requesting termination. At 207, it is determined if the requested service instance(s) for termination is idle or active. If the service instance is idle (i.e., one where a user is not actively interacting therewith), then at 208, the idle service instance and/or client device may listen for an intruder and a timer is started (at 210) to provide an option for the client device (or a user interacting with the client device) to cancel the termination request. For example, the user interface of FIG. 5 may be presented in the client Ul displaying the idle service instance to provide a warning and option for a user at the client device to cancel the request. In some implementations, a one minute timer may be set to enable the client device or user to cancel the request. Alternatively, the user interface of FIG. 5 may display the user name of the intruder. At 212, it is determined if the client device or user at the client device has canceled the termination request.
[0025] If the client device or user did not cancel the termination, then at 214 the intruder becomes the owner of a new service instance created in the place of the terminated service instance. For example, as shown in FIG. 3B, when Service Instance 2 in Slot 2 owned by Owner 2 terminates, the connection 303 is terminated, and a new Service Instance 3 is created in Slot 2. A new connection 308 is created between the intruder and
[0026] However, if at 212, the host cancels the termination, then at 222 it is determined if another service instance is terminated. If so, then at 214 the intruder becomes owner of the new service instance created in place of the recently terminated service instance, as noted above. Again, optionally at 216, any outstanding termination requests associated with the intruder are canceled. However, if at 222, no other service instances have terminated, then at 224 it is determined if the request should be repeated. If so, the process returns to 206. If not, then the process proceeds to 226 where a request may be made to Information Technology (IT) support for more assistance, the process may end, or the intruder may wait for a session to become available.
[0027] Returning to 207, if it is determined that the intruder has requested termination of an active service instance (at 218), then at 219, a user at the client device is asked to terminate. For example, if Owner 2 was associated with the active service request, a user at Owner 2 would be presented a user interface in client Ul 109B, such as shown in FIG. 6. Alternatively, the user interface of FIG. 6 may display the user name of the intruder. Next, at 220, it is determined if the user at the client device has in-fact terminated in response to the request. In accordance with aspects of the disclosure, an active service instance must be explicitly terminated in response to the intruder's request. If the service instance has terminated, then the flow continues at 214, as described above. However, if at 220 the service instance has not terminated, then at 222 it is determined if another service instance has terminated. If so, then at 214 the flow continues as described above. However, if at 222 no other service instance has terminated then the process at 224 and 226 are performed as discussed above.
[0028] FIG. 7 is a simplified block diagram illustrating another environment 700 for providing access to limited service instances. The environment 700 may be provided as a scalable, fault tolerant remote access architecture in, e.g., a cloud infrastructure such as Amazon Web Services (AWS) or other entities. While the environment 700 is intended to scale to accommodate potentially large numbers of service instances and Hosts, there may be other limitations on scalability, such as licensing constraints, physical capacity, network capacity, etc. As such, the techniques of the present disclosure may be implemented to provide access to service instances to intruders.
[0029] In FIG. 7, remote access and application servers 103A/103B may be provided to host service instance 1 and service instance 2, respectively. Although only one service instance is shown on each of the remote access and application servers 103A/103B, there may be more than one service instance executing on each of the remote access and application servers 103A/103B. The remote access and application servers 103A/103B may be cloud-based instances that are created from images. For example, there may be a pre- built image associated with each service instance such that the image can be loaded onto a remote access and application server 103A/103B when instantiated in a cloud environment.
[0030] Each remote access and application server 103 A/103 B may include a service manager 111A/111B and an application server 114A/114B. The service manager 111A/111B is responsible for stopping and starting service instances on a particular remote access and application server 103A/103B. The application server 114A/114B provides for connection marshalling and may include a server SDK (not shown) that provides display information to the service instances 1/2 from the client device 108A/10SB/108C and vice versa. An example of the remote access and application server 103A/103B is PUREWEB, available from Calgary Scientific, Inc. of Calgary, Alberta, Canada.
[0031] Proxy servers 113A/113B may be an HTTP server and reverse proxy server capable of handling a relatively large number of simultaneous requests. As shown, the proxy server 113A/113B executes on a node (e.g., a server computing device) separate from the remote access and application server(s) 103A/103B. An example proxy server 113A/113B is nginx, available from Nginx Inc., San Francisco, California.
[0032] The resource manager 106 may be provided as a functionality of a scheduler (not shown) that may manage the utilization of resources, such as remote access and application servers 103A/103B or other nodes within a cluster 120. In addition to the functions of the resource manager 106, the scheduler may implement one or more selection heuristics to determine which application server 103A/103B to service a remote access connection request, as described in U.S. Patent Application No. 15/011,183.
[0033] The example operational flow 200 of FIG. 2 for providing and requesting access to limited service instances that may also be implemented in environment 700. However, due to the nature of the environment 700, a difference in the connectivities and data flow of FIGS. 3A-3B is that the Hosts (i.e., client devices 108A/108B/108C) connect to the proxy servers 113A/113B, which provide connections to service instance 1/2, respectively.
[0034] In accordance with aspects of the present disclosure, there may be multiple intruders requesting access to service instances. Each of the requests made by the multiple intruders may be prioritized based on a first-in-first-out basis, an urgency of the need of the request, a level of authority of the requester, etc. Further, it is noted that the above may mitigate limited service instance availability that results from an enterprise system with limited resources, e.g., limited number of licenses, limited CPU/GPU capability, etc. The techniques described herein may also be used in cloud-based environments.
[0035] As an example, the above techniques may be used by an emergency room physician that requires immediate access to a medical imaging application. In another example, a high ranking military office may have precedence over lower ranking personnel to access to a logistical application showing troop or equipment deployments. In yet another example, a manager may be provided precedence over a subordinate to gain access to a business application. Thus, the techniques disclosed herein may be used in many different environments to provide access to a service where instances are limited by constraints such as physical capacity, logical capacity, licensing, etc.
[0036] FIG. 8 shows an exemplary computing environment in which example embodiments and aspects may be implemented. The computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality.
[0037] Numerous other general purpose or special purpose computing system environments or configurations may be used. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network personal computers (PCs), minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.
[0039] With reference to FIG. 8, an exemplary system for implementing aspects described herein includes a computing device, such as computing device 800. In its most basic configuration, computing device 800 typically includes at least one processing unit 802 and memory 804. Depending on the exact configuration and type of computing device, memory 804 may be volatile (such as random access memory (RAM)), non-volatile (such as read-only memory (ROM), flash memory, etc.), or some combination of the two. This most basic configuration is illustrated in FIG. 8 by dashed line 806.
[0040] Computing device 800 may have additional features/functionality. For example, computing device 800 may include additional storage (removable and/or nonremovable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in FIG. 8 by removable storage 808 and non-removable storage 810.
[0041] Computing device 800 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by device 800 and includes both volatile and non-volatile media, removable and nonremovable media.
[0042] Computer storage media include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Memory 804, removable storage 808, and non-removable storage 810 are all examples of computer storage media. Computer storage media include, but are not limited to, RAM, ROM, electrically erasable program read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 800. Any such computer storage media may be part of computing device 800.
[0043] Computing device 800 may contain communications connection(s) 812 that allow the device to communicate with other devices. Computing device 800 may also have input device(s) 814 such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 816 such as a display, speakers, printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here.
[0044] It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the presently disclosed subject matter. In the case of program code execution on programmable computers, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. One or more programs may implement or utilize the processes described in connection with the presently disclosed subject matter, e.g., through the use of an application programming interface (API), reusable controls, or the like. Such programs may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language and it may be combined with hardware implementations.

中文:
[0001]由于宽带和无线网络接入的增长和可用性,对服务实例的无所不在的远程访问已变得很普遍。因此,用户正在使用种类日益增长的客户端设备(例如,移动设备、平板计算设备、膝上型计算机/笔记本/台式计算机等)来访问服务实例。服务实例可以通过远程服务器访问,该服务器可以通过多种网络在服务实例和客户端设备之间传递包含数据或其它信息的消息,所述网络包括3G和4G移动数据网络、诸如WiFi和WiMax的无线网络、有线网络等。
[0002]由于资源或物理约束,在任何给定的时间可能存在有限数量的可用服务实例。因此,尝试连接到服务实例的客户端可能无法连接。在客户端已建立通信之后,对于需要访问正由另一个客户端使用或处于空闲的等待状态的服务的客户端来说,这可能引起麻烦。
[0003]本文所公开的是当例如这样的服务实例的可用性有限时用于请求由客户端计算设备拥有的服务实例的终止的系统和方法。根据本公开的一个方面,描述了一种请求终止在远程应用服务器上执行的服务实例的方法,该服务实例由第一客户端设备拥有。该方法可包括:在第二客户端设备处接收可以对其做出请求的服务实例的列表,服务实例的列表包括所述服务实例;由第二客户端设备请求终止所述服务实例;将请求转发至第一客户端设备以终止所述服务实例;以及如果由第一客户端设备拥有的服务实例被终止,则创建新服务实例,然后,第二客户端设备变成新服务实例的所有者。
[0004]在详尽研究以下附图和详细描述后,其它系统、方法、特征和/或优点对于本领域的技术人员将会或可能变得显而易见。所有这样的附加系统、方法、特征和/或优点旨在包括在本说明书内并由所附权利要求保护。
[0005]附图中的部件未必相对于彼此按比例绘制。贯穿若干视图,类似的附图标记标示对应的零件。
[0006]图1是简化框图,示出了用于提供对有限的服务实例的访问的环境;
[0007]图2是用于提供并请求对有限的服务实例的访问的示例性操作流程;
[0008]图3A-3B是简化框图,示出了在图1的环境内根据图2的操作流程提供对有限的服务实例的访问的示例;
[0009]图4-6示出了与图2的操作流程相关联的示例性用户接口;
[0010]图7是简化框图,示出了用于提供对有限的服务实例的访问的另一个示例性环境;以及
[0011]图8示出了示例性的计算设备。
[0013]图1是简化框图,示出了用于提供对有限的服务实例的访问的环境100。根据一些实施,可以提供一个或多个服务实例1/2,其可以是由客户端设备108A/108B/108C远程访问的应用程序、数据提供方等。服务实例1/2可以在应用服务器(未示出)上执行,当资源允许时,每个应用服务器可以运行多个服务实例。客户端设备108A/108B/108C的用户可以在客户端用户接口(UI)109A/109B/109C中输入预定的连接统一资源定位符(URL)以经由通信网络112通过资源管理器106连接到服务实例1/2。网络112可以是任何类型的网络,例如,因特网、以太网、Wi-Fi(IEEE 802.11x)、WiMax(IEEE 802.16)、以太网、3G、4G、LTE等。
[0015]资源管理器106具有一机构,当没有服务实例可用时,该机构允许客户端设备108A/108B/108C请求终止服务实例。资源管理器106可以保持与向其注册的服务实例的列表107(如下所述)。该列表可包括关于每一个服务实例的信息,例如但不限于与服务实例相关联的令牌、主机信息(例如,用户名、全名、部门等)、以及后会话信息(例如,会话的状况、空闲/非空闲状态等)。空闲时间是当用户不与服务实例交互时的一段时间。下面将参照图2描述资源管理器106的另外的细节。
[0016]资源管理器106可以在与服务实例1/2相同或不同的服务器上执行。服务实例1/2可以在预定的因特网协议(IP)地址和/或套接口处或使用与资源管理器106相关联的URL连接到资源管理器106以将其自身向资源管理器106注册。在某些情况下,服务实例1/2可以通过网络112连接到资源管理器106以向资源管理器106注册。一旦注册,服务实例1/2就被排队,使得客户端设备可以与其连接。排队的服务实例可以通过唯一的实例Id来被引用。客户端设备可以通过连接到资源管理器106而连接到服务实例,并且可以或者通过使用应用程序实例Id连接到排队的服务的具体的服务实例,或者使用应用程序名称连接到特定类型的第一可用排队服务实例。
[0017]服务实例1/2可以是“非管理服务”,其为可驻留在与资源管理器106的服务器(节点)相同或不同的服务器(节点)上的服务。在非管理服务中,应用程序/过程生命周期不受资源管理器106管理。
[0018]上述服务器和客户端设备108A/108B/108C可以使用诸如在图8的通用计算设备中所示那些的硬件来实现。软件、应用程序(例如,服务实例1/2、资源管理器106和客户端UI109A/109B/109C)操作系统等可以在存储器中和图8的通用计算设备的处理器上执行。
[0019]图2是可以在环境100中实现的用于提供并请求对有限的服务实例的访问的示例性操作流程200。图3A-3B示出了根据操作流程200在环境100中的连通性和数据流。首先,如图3A所示,客户端设备108A为所有者1,其拥有在槽1中的服务实例1。服务实例1在客户端UI109A中被显示(参见连接302)。因此,所有者1具有令牌1。客户端设备108B为所有者2并且拥有在槽2中的服务实例2。服务实例2在客户端UI 109B中被显示(参见连接303)。因此,所有者2具有令牌2。
[0020]在202中,“入侵者”可以请求访问新服务实例;然而,入侵者被拒绝访问。如本文所用,请求终止一个或多个服务实例的客户端设备(例如,108C)被称为“入侵者”。例如,入侵者--客户端设备108C--可以向资源管理器106提出访问新服务实例的请求,但被拒绝,因为可能没有资源可用于新服务实例(参见附图标记304a)。
[0021]在204中,向入侵者呈现服务实例的列表。例如,入侵者可以被资源管理器106认证并呈现入侵者可能请求终止的服务实例的表或列表107(参见附图标记306)。图4中显示了示出服务列表的示例性用户接口。
[0022]服务实例的列表可以根据分配给入侵者的访问或授权的级别、特定服务实例的重要性、在执行服务实例的应用服务器处可用的资源或其它标准来分类或优先化。在204中提供给入侵者的信息也可以根据预先配置的规则分类,例如,访问/授权级别(例如,用户不会看到与具有更高授权或访问级别的其他用户相关联的实例)、空闲时间、部门、职位、用户偏好等,或者由入侵者手动分类。服务实例的列表可包括服务实例及其相应的令牌(例如,令牌1、令牌2等)。
[0023]在205中,入侵者从服务实例的列表107选择一个(或多个)服务实例。如图4所示,入侵者可以通过单击复选框来请求终止服务实例2。将入侵者连接到会话的有限访问连接可以建立,但入侵者不能协作地参与会话,并且入侵者也看不到该会话中的其它客户端设备。资源管理器106也可以为入侵者保留槽2,从而使其他入侵者或用户不可以在该入侵者之前连接到服务实例。
[0024]在206中,入侵者可以请求终止一个或多个服务实例。例如,在图4的对话框中,在入侵者处的用户已选择了要请求终止的服务实例(例如,由所有者2拥有的服务实例2)。利用由环境100提供的客户端间通信机构,入侵者联系与入侵者正请求终止的服务实例相关联的会话的客户端设备。在207中,确定请求终止的(多个)服务实例是否为空闲的或活动的。如果服务实例为空闲的(即,其中用户未与其主动地交互的服务实例),那么在208中,空闲的服务实例和/或客户端设备可以监听入侵者,并且定时器启动(在210中),以便为客户端设备(或与客户端设备交互的用户)提供取消终止请求的选项。例如,图5的用户接口可以呈现在显示空闲的服务实例的客户端UI中,以便为在客户端设备处的用户提供取消请求的警告和选项。在一些实施中,可以设定一分钟的定时器以允许客户端设备或用户取消请求。备选地,图5的用户接口可以显示入侵者的用户名。在212中,确定客户端设备或在客户端设备处的用户是否已取消终止请求。
[0025]如果客户端设备或用户未取消终止,那么在214中入侵者变成代替终止的服务实例而创建的新服务实例的所有者。例如,如图3B所示,当由所有者2拥有的槽2中的服务实例2终止时,连接303被终止,并且在槽2中创建新服务实例3。在入侵者和目前正在槽2中执行的服务实例3之间创建新连接308。入侵者此时变成服务实例3的所有者,并且令牌2被传递给入侵者(参见流310)。可选地,在216中,与入侵者相关联的任何未完成的终止请求都被取消,因为入侵者在206中可能请求终止多于一个服务实例。
[0026]然而,如果在212中主机取消终止,那么在222中确定是否另一个服务实例被终止。如果是这样,那么在214中入侵者变成代替最近终止的服务实例而创建的新服务实例的所有者,如上文所提及的。同样,可选地,在216中,与入侵者相关联的任何未完成的终止请求都被取消。然而,如果在222中没有其它服务实例被终止,那么在224中确定请求是否应被重复。如果是这样,则过程返回至206。如果不是,那么过程前进至226,其中可以向信息技术(IT)支持发出请求以获得更多辅助,该过程可以结束,或者入侵者可以等待会话变得可用。
[0027]返回到207,如果确定入侵者已请求终止活动的服务实例(在218中),那么在219中,在客户端设备处的用户被要求终止。例如,如果所有者2与活动的服务请求相关联,则在所有者2处的用户将被呈现在客户端UI 109B中的用户接口,例如图6所示那样。备选地,图6的用户接口可以显示入侵者的用户名。接下来,在220中,确定在客户端设备处的用户是否事实上已响应于请求而终止。根据本公开的方面,活动的服务实例必须响应于入侵者的请求而被明确地终止。如果服务实例已终止,那么流程在214中如上文所述那样继续。然而,如果在220中服务实例未被终止,那么在222中确定是否另一个服务实例已被终止。如果是这样,那么在214中流程如上文所述那样继续。然而,如果在222中没有其它服务实例被终止,那么过程在224和226中如上文所讨论那样执行。
[0028]图7是简化框图,示出了用于提供对有限的服务实例的访问的另一个环境700。环境700可以提供为在例如诸如亚马逊网络服务(AWS)或其它实体的云基础设施中的可扩展的容错远程访问架构。虽然环境700旨在扩展以适应潜在地较大数量的服务实例和主机,但可能存在对可扩展性的其它限制,例如,许可证约束、物理容量、网络容量等。因此,本公开的技术可以实现以向入侵者提供对服务实例的访问。
[0029]在图7中,远程访问和应用服务器103A/103B可以提供用于分别托管服务实例1和服务实例2。虽然在每一个远程访问和应用服务器103A/103B上仅示出一个服务实例,但可以存在在每一个远程访问和应用服务器103A/103B上执行的多于一个服务实例。远程访问和应用服务器103A/103B可以是从图像创建的基于云的实例。例如,可以存在与每个服务实例相关联的预构建的图像,使得当在云环境中实例化时该图像可被加载到远程访问和应用服务器103A/103B上。
[0030]每个远程访问和应用服务器103A/103B可包括服务管理器111A/111B和应用服务器114A/114B。服务管理器111A/111B负责停止和启动在特定的远程访问和应用服务器103A/103B上的服务实例。应用服务器114A/114B提供用于连接编组,并且可包括服务器SDK(未示出),该服务器SDK将显示信息从客户端设备108A/108B/108C提供至服务实例1/2或从服务实例1/2提供至客户端设备108A/108B/108C。远程访问和应用服务器103A/103B的示例为可得自加拿大阿尔伯塔省卡尔加里市的Calgary Scientific,Inc.的PUREWEB。
[0031]代理服务器113A/113B可以是HTTP服务器和反向代理服务器,其能够处理相对大量的同时请求。如图所示,代理服务器113A/113B在与(多个)远程访问和应用服务器103A/103B分开的节点(例如,服务器计算设备)上执行。示例性代理服务器113A/113B为可得自加利福尼亚州旧金山市的Nginx Inc.的nginx。
[0032]资源管理器106可以提供为调度器(未示出)的功能,该调度器可以管理诸如远程访问和应用服务器103A/103B或簇120内的其它节点的资源的使用。除了资源管理器106的功能之外,调度器可以实现一个或多个选择启发,以确定哪个应用服务器103A/103B来服务于远程访问连接请求,如在美国专利申请第15/011,183号中所述。
[0033]用于提供并请求对有限的服务实例的访问的图2的示例性操作流程200也可以在环境700中实现。然而,由于环境700的性质,在图3A-3B的连通性和数据流中的差别在于,主机(即,客户端设备108A/108B/108C)分别连接到提供到服务实例1/2的连接的代理服务器113A/113B。
[0034]根据本公开的方面,可以存在请求访问服务实例的多个入侵者。由多个入侵者发出的每个请求可以基于先进先出原则、请求的需求紧迫性、请求者的授权级别等优先化。此外,应当指出,上述方法可以缓解由具有有限的资源的企业系统导致的有限的服务实例可用性,有限的资源为例如有限数量的许可证、有限的CPU/GPU能力等。本文所述技术也可以在基于云的环境中使用。
[0035]作为示例,上述技术可以由需要立即访问医学成像应用的急诊室医师使用。在另一示例中,高级别的军官可以优先于较低级别的工作人员访问显示军队或装备部署的后勤应用。在又一示例中,可以向经理提供相比下属的优先级以获得对商业应用的访问。因此,本文所公开的技术可以在许多不同的环境中使用,以提供对其中实例受到诸如物理容量、逻辑容量、许可证等的约束限制的服务的访问。
[0036]图8示出了可以在其中实现示例性实施例和方面的示例性的计算环境。该计算系统环境仅是合适的计算环境的一个示例,而并非意图暗示对使用或功能的范围的任何限制。
[0037]可以使用多种通用或专用计算系统环境或配置。可能适合使用的熟知的计算系统、环境和/或配置的示例包括但不限于个人计算机、服务器计算机、手持设备或膝上型设备、多处理器系统、基于微处理器的系统、网络个人计算机(PC)、小型计算机、大型计算机、嵌入式系统、包括上述系统或设备中任一个的分布式计算环境,等等。
[0039]参照图8,用于实现本文所述方面的示例性系统包括计算设备,例如计算设备800。在其最基本的配置中,计算设备800通常包括至少一个处理单元802和存储器804。根据计算设备的精确配置和类型,存储器804可以是易失性的(例如,随机存取存储器(RAM))、非易失性的(例如,只读存储器(ROM)、闪存等)或两者的一些组合。该最基本的配置在图8中由虚线806示出。
[0040]计算设备800可具有附加的特征/功能。例如,计算设备800可包括附加的存储(可移动和/或不可移动),包括但不限于磁性或光学的盘或带。这样的附加存储在图8中由可移动存储808和不可移动存储810示出。
[0041]计算设备800通常包括各种计算机可读介质。计算机可读介质可以是能由设备800访问的任何可用介质,并且包括易失性和非易失性介质、可移动和不可移动介质。
[0042]计算机存储介质包括以任何方法或技术实现的用于存储诸如计算机可读指令、数据结构、程序模块或其它数据的信息的易失性和非易失性以及可移动和不可移动介质。存储器804、可移动存储808和不可移动存储810是计算机存储介质的所有示例。计算机存储介质包括但不限于RAM、ROM、电可擦可编程只读存储器(EEPROM)、闪存或其它存储技术、CD-ROM、数字多用盘(DVD)或其它光学存储、磁卡带、磁带、磁盘存储或其它磁性存储设备,或任何其它可用于存储所需信息并可由计算设备800访问的介质。任何这样的计算机存储介质都可以是计算设备800的一部分。
[0043]计算设备800可以包含(多个)通信连接812,其允许计算设备与其它设备通信。计算设备800也可具有(多个)输入设备814,例如,键盘、鼠标、笔、语音输入设备、触摸输入设备等。也可包括诸如显示器、扬声器、打印机等的(多个)输出设备816。所有这些设备都是本领域熟知的,并且不需要在这里详细地讨论。
[0044]应当理解,本文所述各种技术可以结合硬件或软件或适当时两者的组合来实现。因此,本文所公开的主题或其某些方面或部分的方法和装置可以采取程序代码(即,指令)的形式,该程序代码嵌入诸如软盘、CD-ROM、硬盘驱动器或任何其它机器可读存储介质的有形介质中,其中,当程序代码被加载到诸如计算机的机器中并由机器执行时,该机器变成用于实践本文所公开的主题的装置。就程序代码在可编程计算机上的执行而言,计算设备大体包括处理器、可由处理器读取的存储介质(包括易失性和非易失性存储器和/或存储元件)、至少一个输入设备和至少一个输出设备。一个或多个程序可以实现或利用结合本文所公开的主题描述的过程,例如,通过使用应用程序编程接口(API)、可重复使用的控件等。这样的程序可以以高级别的过程性或面向对象的编程语言实现以与计算机系统通信。然而,如果需要,(多个)程序可以汇编或机器语言实现。在任何情况下,语言可以是编译型或解释型语言,并且可以与硬件实施结合。