KR20200047491A - Unnecessary resource recognition and release plan in application hot deploy on distributed system - Google Patents

Abstract

According to an embodiment of the present disclosure, disclosed is a method for managing a non-stop version of an application in a system including a plurality of application servers. The operations stored in a computer program to perform the method comprise: an operation of recording service performing relation information by each of a plurality of versions of an application stored in the application server; an operation of transmitting at least one of retention version information, the service performing relation information by version, version information of an application performing a service to an application management server; an operation of transmitting unused version information including version information of an application having no service to be performed to the application management service when there is no service which an application of a version other than a newest version among applications of a plurality of versions based on the service performing relation information by version; and an operation of receiving an unused version removal command from the application management server.

Description

Unnecessary resource recognition and release plan for non-disruptive deployment of applications in distributed environment systems {UNNECESSARY RESOURCE RECOGNITION AND RELEASE PLAN IN APPLICATION HOT DEPLOY ON DISTRIBUTED SYSTEM}

The present invention relates to a method for conforming application versions during nondisruptive distribution of applications and a computer program stored in a computer-readable medium, and more particularly, to a method for conforming application versions in a distributed environment.

Nondisruptive distribution distributes the updated version of the application to the server without stopping the server, so that the user can apply the updated version of the application to the application server processing the service without interrupting the service of users. In a distributed environment, multiple servers can be operated, and service processing can be performed on multiple servers.

Depending on the order of the servers in which the updated version of the application is distributed, the application time of each application may vary for each server. When a service is requested with the latest version to a server that has not yet applied the updated version of the application, an error occurs or an incorrect result is returned.

There was a problem in that if an older version of the application remains after the updated version of the application is distributed, the memory becomes insufficient.

Accordingly, there is a need in the art for a method of matching application consistency with an updated version in a distributed environment and a method of removing application resources of an updated version.

Korean Registered Patent KR20027000225 discloses a method of loading a class related to an application program.

The present disclosure has been devised in response to the background art described above, and aims to provide a method for non-disruptive version management of an application.

A computer program stored in a computer-readable storage medium according to an embodiment of the present disclosure for realizing the above-described problems, wherein the computer program includes a plurality of application servers when executed in one or more processors of the application server In order to perform the following operations for non-disruptive version management in the application, the operations include: transmitting the retained application version information to the application management server; Receiving an updated version of the application file and version information corresponding to the application file from the application management server; Loading an application file of an updated version and determining that a service using the updated version of the application is available; When it is determined that a service using the updated version of the application can be performed, transmitting the application update preparation complete information to the application management server; It may include an operation of receiving an application command of the updated version from the application management server.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, the application command of the updated version includes a system comprising the plurality of application servers When the application update preparation completion information is received from all application servers of the application management server, the application management server may generate the information.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, when the application of the updated version fails, the updated version is applied to the application management server. Transmitting failure information of the application; Receiving an update version application cancellation command from the application management server; And performing a service by using the updated version of the application prior to the application.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, when receiving an update version applying command from the application management server, the update Determining the version of the application as the latest version; And the service after receiving the application command of the updated version may further include an operation performed by using the updated version of the application.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, receiving a service from another application server; If version information exists in the service, perform the service with the identified version of the application based on the version information of the service, or if version information does not exist in the service, perform the service with the latest version of the application It may further include the operation.

A method for non-disruptive version management of an application in a system including a plurality of application servers according to an embodiment of the present disclosure for realizing the above-described problems, the method comprising: transmitting retained application version information to an application management server; Receiving an updated version of the application file and version information corresponding to the application file from the application management server; Determining that it is possible to perform a service using the updated version of the application by loading the updated version of the application file; When it is determined that a service using the updated version of the application is available, transmitting application ready preparation information to the application management server; And receiving an application command of an updated version from the application management server.

An application server for non-disruptive version management of an application in a system including a plurality of application servers according to an embodiment of the present disclosure for realizing the above-described problems, comprising: a processor including one or more cores; And a memory, wherein the processor transmits retained application version information to an application management server, receives an updated version of the application file and version information corresponding to the application file from the application management server, and the updated version of the application. When it is determined that the service using the updated version of the application can be performed by loading a file, and when it is determined that the service using the updated version of the application can be performed, the application management server receives application preparation preparation information from the application management server. It is possible to transmit and receive an update version application command from the application management server.

A computer program stored in a computer-readable storage medium according to an embodiment of the present disclosure for realizing the above-described problems, wherein the computer program includes a plurality of application servers when executed in one or more processors of the application server In order to perform the following operations for non-disruptive version management in the application, the operations include: recording service performance related information for each version of a plurality of versions of applications stored in the application server; Transmitting at least one of version information of a retained application, information related to service execution for each version, and version information of an application executing the service to an application management server; If there is no service being executed by an application of a version other than the latest version among the plurality of versions of the application based on the service execution related information for each version, version information of the application for which the service being executed does not exist in the application management server Transmitting unused version information including; And receiving an unused version removal command from the application management server.

In an alternative embodiment of computer program operations to perform the following operations for application uninterrupted version management in a system including a plurality of application servers, when receiving the unused version removal command, based on the unused version removal command It may further include an operation of determining the version of the application identified by the removal standby state.

In an alternative embodiment of computer program operations to perform the following operations for application uninterrupted version management in a system including a plurality of application servers, when receiving the unused version removal command, based on the unused version removal command The method may further include transmitting unused version removal preparation completion information for the identified version of the application to the application management server.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system comprising a plurality of application servers, the command to remove unused versions comprises: When unused version information for an application of the same version is received from the application management server from all application servers, the application management server may generate the unused version information based on the unused version information.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system comprising a plurality of application servers, terminate an instance for the identified version of the application based on the unused version information. And recovering the allocated main memory.

In an alternative embodiment of computer program operations to perform the following operations for application uninterrupted version management in a system including a plurality of application servers, when receiving the unused version removal command, based on the unused version removal command The method may further include an operation of terminating the instance for the identified version of the application and retrieving the allocated main memory.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, receiving an unused version removal confirmation command from the application management server; And when an unused version removal confirmation command is received from the application management server, terminating an instance of the identified version of the application based on the unused version removal confirmation command and recovering the allocated main memory. And deleting the identified version of the application from the storage medium based on the removal confirmation command of the unused version.

In an alternative embodiment of computer program operations to perform the following operations for non-disruptive version management of an application in a system including a plurality of application servers, the removal confirmation command of an unused version includes a system comprising the plurality of application servers. When unused version removal preparation information for an application of the same version is received from all application servers of the application management server, the application management server may generate the unused version removal preparation information.

In an alternative embodiment of computer program operations to perform the following operations for application uninterrupted version management in a system including a plurality of application servers, when receiving the unused version removal command, based on the unused version removal command Determining whether a service performed by the identified version of the application is delivered to another application server; And when a service performed by the application of the version identified based on the unused version removal command is delivered to another application server, the application management server may not receive version removal information of the version of the application identified based on the unused version removal command. It may further include the operation of transmitting.

As a method for non-disruptive version management of an application in a system including a plurality of application servers according to an embodiment of the present disclosure for realizing the above-described problems, for each version of each of a plurality of versions of applications stored in the application server Recording service related information; Transmitting at least one of version information of a retained application, information related to service execution for each version, and version information of an application executing the service to an application management server; If there is no service being executed by an application of a version other than the latest version among the plurality of versions of the application based on the service execution related information for each version, version information of the application for which the service being executed does not exist in the application management server Transmitting unused version information including; And receiving an unused version removal command from the application management server.

An application server for non-disruptive version management of an application in a system including a plurality of application servers according to an embodiment of the present disclosure for realizing the above-described problems, comprising: a processor including one or more cores; And a memory, wherein the processor records service execution related information for each version of a plurality of versions of applications stored in the application server, version information of the application held in the application management server, service related information for each version, and the If at least one of version information of an application performing a service is transmitted, and a service of an application of a version other than the latest version among the plurality of versions of the application is not performed based on the service performance related information for each version, the It is possible to transmit unused version information including version information of an application for which the service being executed does not exist to the application management server, and receive an unused version removal command from the application management server.

The present disclosure may provide a method for non-disruptive version management of an application.

1 is a schematic diagram illustrating a system for performing an operation for non-disruptive version management of an application according to an embodiment of the present disclosure.
2 is a block diagram of an application management server according to an embodiment of the present disclosure.
3 is a block diagram of an application server according to an embodiment of the present disclosure.
4 is a flowchart for non-disruptive version management of an application in one embodiment of the present disclosure.
5 is a flowchart for application non-disruptive version management according to another embodiment of the present disclosure.
6 is a block diagram illustrating logic for non-disruptive version management of an application according to an embodiment of the present disclosure.
7 is a block diagram illustrating a module for non-disruptive version management of an application according to an embodiment of the present disclosure.
8 is a block diagram illustrating a circuit for non-disruptive version management of an application according to an embodiment of the present disclosure.
9 is a block diagram showing a means for non-disruptive version management of an application according to an embodiment of the present disclosure.
10 is a block diagram illustrating logic for non-disruptive version management of an application according to another embodiment of the present disclosure.
11 is a block diagram illustrating a module for non-disruptive version management of an application according to another embodiment of the present disclosure.
12 is a block diagram illustrating a circuit for non-disruptive version management of an application according to another embodiment of the present disclosure.
13 is a block diagram illustrating a means for non-disruptive version management of an application according to another embodiment of the present disclosure.
14 is a block diagram of a computing device according to an embodiment of the present disclosure.

Various embodiments are now described with reference to the drawings. In this specification, various descriptions are presented to provide an understanding of the present disclosure. However, it is apparent that these embodiments can be practiced without these specific details.

As used herein, the terms “component”, “module”, “system” and the like refer to computer-related entities, hardware, firmware, software, combinations of software and hardware, or execution of software. For example, a component can be, but is not limited to, a process executed on a processor, a processor, an object, a thread of execution, a program, and / or a computer. For example, both the application and the computing device running on the computing device can be components. One or more components can reside within a processor and / or thread of execution. One component can be localized in one computer. One component can be distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored therein. Components are, for example, signals having one or more data packets (e.g., data and / or signals from one component interacting with other components in a local system, distributed system, etc.) through other systems and networks such as the Internet (Transmitted data) may be communicated through local and / or remote processes.

In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or unclear in context, "X uses A or B" is intended to mean one of the natural inclusive substitutions. That is, X uses A; X uses B; Or, if X uses both A and B, "X uses A or B" can be applied in either of these cases. It should also be understood that the term “and / or” as used herein refers to and includes all possible combinations of one or more of the listed related items.

In addition, the terms “comprises” and / or “comprising” should be understood as meaning that the corresponding feature and / or component is present. It should be understood, however, that the terms “comprises” and / or “comprising” do not exclude the presence or addition of one or more other features, elements, and / or groups thereof. In addition, unless otherwise specified or contextually unclear as indicating a singular form, the singular in the specification and claims should generally be construed to mean "one or more."

Those skilled in the art additionally describe various exemplary logical blocks, configurations, modules, circuits, means, logics, and algorithm steps described in connection with the embodiments disclosed herein in electronic hardware, computer software, or a combination of both. It should be recognized that it can be implemented as To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, configurations, means, logics, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented in hardware or as software depends on the specific application and design limitations imposed on the overall system. Skilled technicians can implement the functionality described in various ways for each particular application. However, such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Descriptions of the presented embodiments are provided so that those skilled in the art of the present disclosure may use or practice the present invention. Various modifications to these embodiments will be apparent to those skilled in the art of the present disclosure. The general principles defined herein can be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present invention is not limited to the embodiments presented herein. The invention should be interpreted in its broadest scope consistent with the principles and novel features presented herein.

In one embodiment of the present disclosure, the server may include other configurations for performing the server environment of the server. The server can include any type of device. The server is a digital device, and may be a digital device equipped with a processor and having computing power, such as a laptop computer, a notebook computer, a desktop computer, a web pad, and a mobile phone. The server may be a web server that processes services. The above-mentioned types of servers are only examples, and the present disclosure is not limited thereto.

1 is a schematic diagram illustrating a system for performing an operation for non-disruptive version management of an application according to an embodiment of the present disclosure. In the present specification, the application management server 100 may perform operations for managing a version of an application installed in each of the plurality of application server 200 and used for a service. The application management server 100 may distribute an updated version of the application to each of the plurality of application servers 200 and instruct the application server 200 to remove the unused version of each application. The application server 200 is a server that processes requests for services. The application server 200 can process one service alone. In a distributed environment, multiple servers can be operated. In a distributed environment, resources may be distributed among multiple applications and distributed. In a distributed environment, a plurality of application servers 200 may process one service together.

The configuration of the system 10 shown in FIG. 1 is only an example simplified. In FIG. 1, three application servers are shown, but this is only an example, and the number of application servers and the number of application management servers are not limited thereto.

The system 10 provides processing of services using servers included in the system. The service may be performed using an application held by the application server 200. The system 10 may include one or more application servers 200 that perform services using an application and an application management server 100 that manages versions of applications of both the application servers 200.

The application server 200 may transmit the retained application version information to the application management server 100. The retained application may include all applications stored in the application server 200, installed, or installed and capable of processing a service, and the retained application version information may include version information of each application in each state.

When receiving an uninterrupted distribution command from the management system (not shown), the application management server 100 may transmit the updated version of the application file and version information corresponding to the application file to each of the plurality of application servers 200. The version information is information for identifying the version of the application, and may be configured with values unique to each version. The version information may be issued one by one from the application management server 100 whenever the application management server 100 performs an uninterrupted distribution of transmitting the updated version of the application file to each of the plurality of application servers 200. The version information issued by the application management server 100 does not overlap with other version information. The application management server 100 and the application server 200 may distinguish application files of various versions through version information. For example, if the updated version of the application file is the interest rate calculation logic for the loan interest, the application management server 100 is a new version whenever the application file for the interest rate calculation logic for the loan interest is transmitted to the application server 200 Information can be issued. In the application management server 100 and the plurality of application servers 200, the interest rate calculation logic for yesterday's loan interest is version information 1, and the interest rate calculation logic for today's loan interest is version information when version information is 2. Through this, it is possible to distinguish which date is the interest rate calculation logic for the loan interest.

The updated version of the application file that the application management server 100 delivers to each of the plurality of application servers 200 may include all information of the new version of the application to be distributed, and the application management server 100 may include multiple applications. The updated version of the application file delivered to each of the servers 200 may include information reflecting only the difference between the new version of the application to be distributed and the previously distributed version.

The application server 200 may store the updated version of the application file received from the application management server 100 and version information corresponding to the application file in a separate storage for each version. The application server 200 may load the updated version of the application file to enable processing of the service with the updated version when a service is requested with the updated version. When the application server 200 is loaded to enable processing of a service with the received update version of the application file, the application management server 100 may transmit the application update preparation completion information to the application management server 100.

The application management server 100 may transmit an application application command of the updated version to each of the plurality of application servers 200 when receiving the same version of the application update preparation complete information from all of the plurality of application servers 200.

When receiving the application command of the updated version from the application management server 100, the application server 200 may determine the updated version of the application as the latest version. The application server 200 may then perform using the latest version of the application that updated the received service. When receiving the service, the application server 200 may provide version information of an application to be performed. The service may be performed with a version of the application initially received from the application server 200 until the service is completed. That is, one service may be processed as one version of the application for consistency of service processing. When receiving a service from the application server 2 (201), the application server 1 (200) may determine whether version information exists in the received service. When the version information exists in the service received from the application server 2 201, the application server 1 200 may perform the service with the corresponding version. If the version information does not exist in the service received from the application server 2 201, the application server 1 200 may perform the service with the latest version of the application.

If the application server 200 fails to apply due to a problem in the process of determining the updated version of the application as the latest version, it may be determined that the application of the updated version has failed. When the application of the updated version fails, the application server 200 may transmit information regarding the failure to apply the updated version to the application management server 100.

The application management server 100 may generate a command for canceling the application of the updated version when receiving information about a failure to apply the updated version from at least one of the plurality of application servers 200. The application management server 100 may transmit an application version cancel command to each of the plurality of application servers 200.

When the application server 200 receives a command to cancel the application of the updated version from the application management server 100, the application server 200 may cancel the determination of the updated version of the application as the latest version. The application server 200 may then perform the received service using an application of a version prior to the update.

The application management server 100 may store whether the application distribution of the updated version is successful. Among the application servers 200, the server that is stopped due to a problem in determining an updated version of the application as the latest version may check whether the latest version of the application and the delivered applications are used to the application management server 100 when restarting. Among the application servers 200, a server that is stopped due to a problem in determining an updated version of an application as the latest version may apply or cancel the application file of the updated version. The application server 200 restarted after the interruption may request version information and application files of an application currently available to the application management server 100.

A version control method for a plurality of application servers 200 according to an embodiment of the present disclosure may maintain version consistency of applications processing services in the plurality of application servers 200. The application server 200 maintains version consistency of applications that process services, thereby preventing errors that may occur when a plurality of application servers 200 process services, thereby processing services of a plurality of application servers 200 Performance can be improved. Reliability of service processing of the plurality of application servers 200 can be prevented by preventing errors that may occur when a plurality of application servers process services by maintaining version consistency of applications that process services in the application server 200 Improve it.

The application server 200 may record information about a plurality of versions of applications that are stored and managed in separate storages. The application server 200 may record information on which service is being performed for each version of each application that is stored and managed in a separate storage. The application server 200 may transmit the retained application version information to the application management server 100. For example, the application server 200 may transmit version information indicating that version 1, version 2, and version 3 of application A are transmitted to the application management server 100. The application server 200 may transmit information about what service is being performed for each version to the application management server 100. For example, the application server 200 does not have a service running in version 1, and service 1 and service 2 are running in version 2, and service 3 is running in version 3 to the application management server 100. Can transmit. The application server 200 may transmit version information of an application performing a service to the application management server 100. For example, information indicating that the service is being performed in version 2 and version 3 may be transmitted to the application management server 100. The application server 200 may determine whether there is a service being executed as an application of a version other than the latest version of the plurality of versions of the application, based on information related to service execution for each version. The application management server 100 may identify a version that is not performing a service in a plurality of application servers 200 based on service performance information for each version. The application server 200 may determine the corresponding version as an unused version for an application of a version in which the service being performed does not exist. The application server 200 may transmit unused version information to the application management server 100. The application server 200 may terminate the instance of the identified version of the application based on the unused version information and recover the allocated main memory. The instance may be running an application file in order to process a service in a corresponding version on the application server. The application server 200 may remove a version of the application identified from the unused version information from the main memory. The application server 200 may maintain the installation and storage on the hard disk, which is the auxiliary storage device, for the version of the application identified based on the unused version information without ending installation and storage.

The application management server 100 is based on the unused version information in the application management server 100 when unused version information for the same version of the application is received from the application management server 100 from all the application servers 200. An unused version removal command can be generated. The application management server 100 may transmit an unused version removal command to each of all application servers 200.

The application server 200 may receive an unused version removal command from the application management server 100. The application server 200 may determine an application of the identified version as a standby for removal based on the received unused version removal command. The version-determined application determined to be removed may be deleted from the storage medium when an unused removal confirmation command is received from the application management server 100. The application server 200 may terminate the instance of the identified version of the application based on the received unused version removal command and recover the allocated main memory. The instance may be running an application file in order to process a service in a corresponding version on the application server. The application server 200 may remove the main memory allocated for the identified version of the application based on the unused version removal command. The application server 200 may maintain the installation and storage on the hard disk, which is the auxiliary storage device, for the version of the application identified based on the unused version removal command, without ending installation and storage. The application server 200 may determine that the unused version is ready to be removed, if the application of the identified version is determined to be in the standby state for removal based on the uninstall command of the version identified based on the unused version removal command. The application server 200 may transmit unused version removal preparation completion information for the identified version of the application to the application management server 100 based on the unused version removal command.

The application management server 100 receives unused version removal preparation completion information for an application of the same version from all application servers 200 to the application management server 100 based on the unused version removal preparation completion information. You can generate an order to confirm the removal. The application management server 100 may transmit an unused version removal confirmation command to each of the application servers 200.

When the application server 200 receives a confirmation command to remove an unused version from the application management server 100, the application server 200 terminates an instance for the identified version of the application based on the removal confirmation command to remove the unused version, and allocates the allocated main memory. Can be recovered. The instance may be running an application file in order to process a service in a corresponding version on the application server. The application server 200 may remove the identified version of the application from the main memory based on the unused version removal confirmation command. The application server 200 may remove the application of the identified version from the storage medium based on the unused version removal confirmation command. The application server 200 may end the installation and storage on the hard disk that is the auxiliary storage device for the identified version of the application based on the unused version removal confirmation command.

When the updated version of the application includes all the information of the new version of the application to be distributed, the application server 200 hardly uses the entire file as an auxiliary storage device for the identified version of the application based on the unused version removal confirmation command. It can be removed from the disc. When the updated version of the application includes information that reflects only the difference between the new version of the application to be distributed and the previously distributed version, the application server 200 relates to the identified version of the application based on the unused version removal confirmation command. Rather than removing the entire file, the updated version can be merged with the unused version to keep the installation and storage on the secondary storage hard disk.

Each service can be processed by calling another application or calling another application server in a synchronous or asynchronous connection method. The synchronous interworking method refers to a method in which one application server waits until a result is received with respect to the called service when the application server makes a call to the service. The asynchronous interworking method means a method in which one application server performs another service regardless of whether or not a result is received in relation to the called service when the application server makes a call to the service.

In the application server 200, a service may be performed in a synchronous interlocking manner. The application server 1 200 may request a service from the application server 2 201. The application server 1 200 may not determine an unused version of the application version on which the service is performed until the service server 2 201 requesting the service receives the processing completion for the service.

In the application server 200, a service may be performed in an asynchronous interlocking manner. The application server 1 200 may request a service from the application server 2 201. When receiving the unused version removal command, the application server 1 200 may determine whether a service performed with the identified version of the application is delivered to another application server based on the unused version removal command. If the service performed by the application of the identified version is transmitted to the application server 2 201 based on the unused version removal command, the application server 1 200 may generate version removal information of the corresponding version. The application server 1 may transmit version non-removal information to the application management server 100.

When receiving version non-removal information from at least one of the plurality of application servers 200, the application management server 100 may generate an unused version removal cancel command for the identified version of the application based on the version non-removal information. have. The application management server 100 may transmit an unused version removal cancel command to all of the plurality of application servers 200.

When the application server 200 receives a command for canceling an unused version removal from the application management server 100, it is possible to cancel the removal standby state for the identified version of the application based on the unused version removal cancel command. When the application server 200 receives a command for canceling an unused version removal from the application management server 100, it is possible to cancel the instance termination and main memory recovery for the identified version of the application based on the unused version removal cancel command. .

By using a version management method for a plurality of application servers 200 according to another embodiment of the present disclosure, unnecessary versions in which a service being performed by the plurality of application servers 200 does not exist may be removed. By removing unnecessary versions from the application server 200, as the memory 230 of the plurality of application servers 200 is efficiently used, service processing performance of the application server 200 can be improved.

2 is a block diagram of an application management server according to an embodiment of the present disclosure.

The application management server 100 may include a network unit 110, a processor 120, and a memory 130. The processor 120 may read a computer program stored in the memory 130 to perform application non-disruptive version distribution management according to an embodiment of the present disclosure.

The network unit 110 may include a transmitter and a receiver. The network unit may include a wired / wireless Internet module for network access. Wireless Internet technology (Wireless LAN) (Wi-Fi), Wibro (Wireless broadband), Wimax (World Interoperability for Microwave Access), HSDPA (High Speed Downlink Packet Access) may be used. As a wired Internet technology, digital subscriber line (XDSL), fibers to the home (FTTH), and power line communication (PLC) may be used.

The network unit 110 includes a short-range communication module, and is located at a relatively short distance from the service processing device and transmits and receives data to and from an electronic device including the short-range communication module. Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, etc. may be used as short range communication technology. In one embodiment of the present disclosure, the network unit may detect a connection state of the network and a transmission / reception speed of the network. Data received through the network unit may be stored through a memory or may be transmitted to other electronic devices at a short distance through a short range communication module.

The network unit 110 may receive the updated version of the application file from the external computing device. The network unit 110 may receive the updated version of the application file from the external computing device and transmit it to the processor 120. The network unit 110 may transmit the updated version of the application file and version information corresponding to the application file to each of the network units 210 of the plurality of application servers 200.

The network unit 110 may receive information about the application update preparation completion of the same version from all of the network units 210 of the plurality of application servers 200. The processor 120 may generate an application application command of the updated version when receiving the same version of the application update preparation complete information from all of the network units 210 of the plurality of application servers 200. The network unit 110 may transmit an update version application application command to each of the network units 210 of the plurality of application servers 200.

The network unit 110 may receive information on the failure to apply the updated version from at least one of the network units 210 of the plurality of application servers 200. When receiving information about a failure to apply the updated version from at least one of the plurality of application servers 200, the processor 120 may generate a command to cancel the application of the updated version. The network unit 110 may transmit an application version cancellation command to each of the plurality of applications.

The memory 130 may store whether the application distribution of the updated version is successful. The memory 130 may store retained application version information transmitted from the application server.

The processor 120 may be composed of one or more cores, threads, a central processing unit (CPU) of a computing device, a general purpose graphics processing unit (GPGPU), and a tensor processing unit (TPU: tensor processing unit), and a processor for data analysis and service processing. The processor 120 may read a computer program stored in the memory 130 to perform a service processing method according to an embodiment of the present disclosure. Further, the computer program executed in the computing device according to an embodiment of the present disclosure may be a CPU, GPGPU, or TPU executable program.

The processor 120 may read a computer program stored in the memory 130 to perform application non-disruptive version management according to an embodiment of the present disclosure.

The network unit 110 may receive unused version information for an application of the same version from the network unit 210 of all application servers 200 to the application management server 100. The processor 120 may generate an unused version removal command based on the unused version information. The network unit 110 may transmit an unused version removal command to each of the network units 210 of all application servers 200.

The network unit 110 may receive unused version removal preparation completion information for the same version of the application from the network unit 210 of all application servers 200. The processor 120 may generate an unused version removal confirmation command based on the unused version removal preparation completion information. The network unit 110 may transmit an unused version removal confirmation command to each of the network units 210 of all application servers 200.

3 is a block diagram of an application server according to an embodiment of the present disclosure.

The application server 200 may include a network unit 210, a processor 220, and a memory 230. The processor 220 may read a computer program stored in the memory 230 to perform application non-disruptive version distribution according to an embodiment of the present disclosure.

The network unit 210 may include a transmitter and a receiver. The network unit may include a wired / wireless Internet module for network access. Wireless Internet technology (Wireless LAN) (Wi-Fi), Wibro (Wireless broadband), Wimax (World Interoperability for Microwave Access), HSDPA (High Speed Downlink Packet Access) may be used. As a wired Internet technology, digital subscriber line (XDSL), fibers to the home (FTTH), and power line communication (PLC) may be used.

The processor 220 may be composed of one or more cores, threads, a central processing unit (CPU) of a computing device, a general purpose graphics processing unit (GPGPU), and a tensor processing unit (TPU: tensor processing unit), and a processor for data analysis and service processing. The processor 220 may read a computer program stored in the memory 230 to perform a service processing method according to an embodiment of the present disclosure. Further, the computer program executed in the computing device according to an embodiment of the present disclosure may be a CPU, GPGPU, or TPU executable program.

The network unit 210 includes a short-range communication module, and is located at a relatively short distance from the service processing device, and may transmit and receive data to and from an electronic device including the short-range communication module. Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, etc. may be used as short range communication technology. In one embodiment of the present disclosure, the network unit may detect a connection state of the network and a transmission / reception speed of the network. Data received through the network unit may be stored through a memory or may be transmitted to other electronic devices at a short distance through a short range communication module.

The network unit 210 may receive an updated version of the application file and version information corresponding to the application file from the network unit 110 of the application management server 100. The memory 230 may store an updated version of the application file and version information corresponding to the application file. When the service is requested in the corresponding version, the memory 230 may load the updated version of the application file to enable processing of the service in the corresponding version. The processor 220 may generate application update preparation completion information when it is loaded to enable processing of a service with the received update version application file. The network unit 210 may transmit update ready information to the network unit 110 of the application management server 100.

The network unit 210 may receive an application command of an updated version from the network unit 110 of the application management server 100. The processor 210 may determine the updated version of the application as the latest version. The processor 220 may then perform using the latest version of the application that updated the received service.

The processor 220 may determine that the application of the updated version has failed when the determination fails due to a problem in the process of determining the updated version of the application as the latest version. When the application of the updated version fails, the network unit 210 may transmit information regarding the failure to apply the updated version to the network unit 110 of the application management server 100.

The network unit 210 may receive an application version cancel command from the network unit 110 of the application management server 100. The processor 220 may cancel the determination of the updated version of the application to the latest version. The processor 220 may then perform the received service using an application of a version prior to the update.

The memory 230 may record information on a plurality of versions of applications. The memory 230 may record information on which service is being performed for each version of the application.

The processor 220 may read a computer program stored in the memory 230 to perform application uninterrupted version management according to an embodiment of the present disclosure.

The network unit 220 may transmit at least one of the version information of the retained application, information on which service is being performed for each version, and version information of the application performing the service to the network unit 120 of the application management server 100. have.

The processor 220 may determine whether there is a service being executed as an application of a version other than the latest version among the plurality of versions of the application. The processor 220 may determine the corresponding version as an unused version with respect to an application for which the service being performed does not exist. The network unit 220 may transmit unused version information to the network unit 120 of the application management server 100. The processor 220 may terminate the instance of the identified version of the application based on the unused version information and recover the allocated main memory.

The network unit 210 may receive an unused version removal command from the network unit 110 of the application management server 100. The processor 220 may determine an application of the identified version as a standby for removal based on the received unused version removal command. The processor 220 may terminate the instance of the identified version of the application based on the received unused version removal command and recover the allocated main memory. The processor 220 may determine that the unused version is ready to be removed, if the application of the identified version is determined to be in the standby state for removal based on the uninstall command of the version identified based on the unused version removal command. The network unit 210 may transmit unused version removal preparation completion information to the network unit 110 of the application management server 100.

The network unit 210 may receive an unused version removal confirmation command from the network unit 110 of the application management server 100. The processor 220 may terminate the instance for the identified version of the application based on the removal confirmation command of the unused version and recover the allocated main memory. The memory 230 may delete the identified version of the application from the memory 230 based on the unused version removal confirmation command.

4 is a flowchart for non-disruptive version management of an application in one embodiment of the present disclosure.

The application server 200 receives the updated version of the application file and version information corresponding to the application file from the application management server 100 (410).

The application server 200 loads an updated version of the application file and determines 420 that a service using the updated version of the application is available.

The application server 200 transmits the application update preparation completion information to the application management server 100 (430).

When the application update preparation completion information is received from the application management server 100 from all application servers, the application server 200 receives an application command of an update version generated by the application management server 100 from the application management server 100 (440).

The application server 200 determines 450 the updated version of the application as the latest version.

5 is a flowchart for removing an uninterrupted version of an application according to an embodiment of the present disclosure.

As a system 10 for non-disruptive version management of an application, the application server 200 is based on information related to service execution for each version, and when a service of a version other than the latest version of the plurality of applications does not exist In operation 510, unused version information including version information of an application for which a service being executed does not exist is transmitted to the application management server 100.

The application server 200 terminates the instance for the identified version of the application based on the unused version information and recovers the allocated main memory (520).

The application server 200 removes the unused version generated based on the unused version information from the application management server 100 when unused version information for the same version of the application is received from the application management server 100 from the all application servers. The command is received 530 from the application management server 100.

The application server 200 determines 540 an application of the identified version to be in a standby state for removal based on an unused version removal command.

The application server 200 transmits 550 the unused version removal preparation completion information for the identified version of the application to the application management server 100 based on the unused version removal command.

The application server 200 is based on the unused version removal preparation completion information from the application management server 100 when the unused version removal preparation information for the same version of the application is received from the application management server 100 from all application servers. The generated unused version removal confirmation command is received from the application management server 100 (560).

The application server 200 deletes (570) the identified version of the application from the storage medium based on the removal confirmation command of the unused version.

6 is a block diagram illustrating logic for non-disruptive version management of an application according to an embodiment of the present disclosure.

The method for non-disruptive version management of an application according to an embodiment of the present disclosure may be implemented by the following logic.

A method for non-disruptive version management of an application according to an embodiment of the present disclosure includes: a logic 610 for an application server to transmit retained application version information to an application management server; Logic (620) for the application server to receive an updated version of the application file and version information corresponding to the application file from the application management server; Logic (630) for determining that the application server is capable of performing a service using the updated version of the application by loading the updated version of the application file; Logic (640) for transmitting application update preparation completion information to the application management server when it is determined that the application server can perform a service using the updated version of the application; The application server may include logic 650 for receiving an update version application command from the application management server.

7 is a block diagram illustrating a module for non-disruptive version management of an application according to an embodiment of the present disclosure. A method for non-disruptive version management of an application according to an embodiment of the present disclosure may be implemented by the following module.

A method for non-disruptive version management of an application according to an embodiment of the present disclosure includes: a module 710 for an application server to transmit retained application version information to an application management server; A module 720 for the application server to receive an updated version of the application file and version information corresponding to the application file from the application management server; A module 730 for determining that the application server is capable of performing a service using the updated version of the application by loading the updated version of the application file; A module 740 for transmitting application update preparation completion information to the application management server when it is determined that the application server can perform a service using the updated version of the application; The application server may include a module 750 for receiving an update version application command from the application management server.

8 is a block diagram illustrating a circuit for non-disruptive version management of an application according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, a method for non-disruptive version management of an application may be implemented by the following circuit.

A method for non-disruptive version management of an application according to an embodiment of the present disclosure includes: a circuit 810 for an application server to transmit retained application version information to an application management server; A circuit 820 for the application server to receive an updated version of the application file and version information corresponding to the application file from the application management server; A circuit 830 for determining, by the application server, that the application file of the updated version is capable of performing a service using the updated version of the application; A circuit 840 for transmitting application update preparation completion information to the application management server when it is determined that the application server can perform a service using the updated version of the application; The application server may include circuitry 850 for receiving an update version application command from the application management server.

9 is a block diagram showing a means for non-disruptive version management of an application according to an embodiment of the present disclosure.

A method for non-disruptive version management of an application according to an embodiment of the present disclosure may be implemented by the following means.

According to an embodiment of the present disclosure, a method for non-disruptive version management of an application includes means (910) for an application server to transmit retained application version information to an application management server; Means (920) for the application server to receive an updated version of the application file and version information corresponding to the application file from the application management server; Means (930) for determining that the application server is capable of performing a service using the updated version of the application by loading the updated version of the application file; Means (940) for transmitting the application update preparation completion information to the application management server when it is determined that the application server can perform a service using the updated version of the application; The application server may include means 950 for receiving an update version application command from the application management server.

10 is a block diagram illustrating logic for non-disruptive version management of an application according to another embodiment of the present disclosure.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application may be implemented by the following logic.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application includes logic 1010 for an application server to record service execution related information for each version of a plurality of versions of applications stored in the application server; A logic 1020 for the application server to transmit at least one of application version information held by the application management server, service performance related information for each version, and version information of an application executing the service; If a service in which an application of a version other than the latest version of the plurality of versions of the application does not exist is performed by the application server based on the service execution related information for each version, an application in which the service running in the application management server does not exist A logic 1030 for transmitting unused version information including version information of; The application server may include logic 1040 for receiving an unused version removal command from the application management server.

11 is a block diagram illustrating a module for non-disruptive version management of an application according to another embodiment of the present disclosure.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application may be implemented by the following module.

According to an embodiment of the present disclosure, a method for non-disruptive version management of an application includes a module 1410 for an application server to record service execution related information for each version of a plurality of versions of applications stored in the application server; A module 1420 for the application server to transmit at least one of application version information, application-related service information for each version, and version information of an application executing the service to the application management server; If a service in which an application of a version other than the latest version of the plurality of versions of the application does not exist is performed by the application server based on the service execution related information for each version, an application in which the service running in the application management server does not exist A module 1430 for transmitting unused version information including version information of; The application server may include a module 1440 for receiving an unused version removal command from the application management server.

12 is a block diagram illustrating a circuit for non-disruptive version management of an application according to another embodiment of the present disclosure.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application may be implemented by the following circuit.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application includes a circuit 1210 for an application server to record service performance related information for each version of a plurality of versions of applications stored in the application server; A circuit 1220 for the application server to transmit at least one of application version information held by the application management server, service related information for each version, and version information of an application executing the service; If a service in which an application of a version other than the latest version of the plurality of versions of the application does not exist is performed by the application server based on the service execution related information for each version, an application in which the service running in the application management server does not exist A circuit 1230 for transmitting unused version information including version information of; The application server may include circuitry 1240 for receiving an unused version removal command from the application management server.

13 is a block diagram illustrating a means for non-disruptive version management of an application according to another embodiment of the present disclosure.

According to another embodiment of the present disclosure, a means for non-disruptive version management of an application may be implemented by the following module.

According to another embodiment of the present disclosure, a method for non-disruptive version management of an application includes: means (1310) for an application server to record service performance-related information for each version of a plurality of versions of applications stored in the application server; Means (1320) for the application server to transmit at least one of the version information of the application held by the application management server, the service performance related information for each version, and the version information of the application performing the service; If a service in which an application of a version other than the latest version of the plurality of versions of the application does not exist is performed by the application server based on the service execution related information for each version, an application in which the service running in the application management server does not exist Means (1330) for transmitting unused version information including version information of; The application server may include means 1340 for receiving an unused version removal command from the application management server.

14 is a block diagram of a computing device according to an embodiment of the present disclosure.

14 shows a simplified and general schematic diagram of an exemplary computing environment in which embodiments of the present disclosure can be implemented.

Although the present disclosure has been described above in general with respect to computer-executable instructions that may be executed on one or more computers, those skilled in the art will appreciate that the present disclosure may be implemented in combination with other program modules and / or as a combination of hardware and software. will be.

Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In addition, those of ordinary skill in the art may appreciate that the methods of the present disclosure may include single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc. It will be appreciated that it may be implemented in other computer system configurations, including one that may operate in conjunction with one or more associated devices.

The described embodiments of the present disclosure may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Computers typically include a variety of computer readable media. Any computer-accessible medium can be a computer-readable medium. Computer-readable media includes volatile and non-volatile media, transitory and non-transitory media, removable and non-removable media. By way of example, and not limitation, computer readable media may include computer readable storage media and computer readable transmission media. Computer-readable storage media are volatile and non-volatile media, temporary and non-transitory media, removable and non-removable, implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules or other data Includes media. Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital video disk (DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, Or any other medium that can be accessed by a computer and used to store desired information.

Computer readable transmission media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and Includes all information delivery media. The term modulated data signal means a signal in which one or more of the characteristics of the signal are set or changed to encode information in the signal. By way of example, and not limitation, computer readable transmission media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above-described media are also intended to be included within the scope of computer-readable transmission media.

An exemplary environment 1100 is shown that implements various aspects of the present disclosure, including a computer 1102, and the computer 1102 includes a processing device 1104, a system memory 1106, and a system bus 1108. do. System bus 1108 connects system components, including, but not limited to, system memory 1106 to processing device 1104. The processing device 1104 can be any of a variety of commercial processors. Dual processor and other multiprocessor architectures may also be used as the processing unit 1104.

The system bus 1108 can be any of several types of bus structures that can be further interconnected to a memory bus, peripheral bus, and local bus using any of a variety of commercial bus architectures. System memory 1106 includes read-only memory (ROM) 1110 and random access memory (RAM) 1112. The basic input / output system (BIOS) is stored in a non-volatile memory 1110 such as ROM, EPROM, EEPROM, etc., and this BIOS is basic to help transfer information between components in the computer 1102 at the same time as during startup. Contains routines. The RAM 1112 may also include high-speed RAM, such as static RAM for caching data.

Computer 1102 is also an internal hard disk drive (HDD) 1114 (eg, EIDE, SATA)-this internal hard disk drive 1114 can also be configured for external use within a suitable chassis (not shown). Yes, magnetic floppy disk drive (FDD) 1116 (e.g., for reading from or writing to removable diskette 1118), and optical disk drive 1120 (e.g., CD-ROM Disc 1122, or for reading from or writing to other high-capacity optical media such as a DVD). The hard disk drive 1114, the magnetic disk drive 1116, and the optical disk drive 1120 are respectively connected to the system bus 1108 by the hard disk drive interface 1124, the magnetic disk drive interface 1126, and the optical drive interface 1128. ). The interface 1124 for implementing an external drive includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

These drives and their associated computer-readable media provide non-volatile storage of data, data structures, computer-executable instructions, and the like. In the case of computer 1102, drives and media correspond to storing any data in a suitable digital format. Although the above description of computer readable media refers to HDDs, removable magnetic disks, and removable optical media such as CDs or DVDs, zip drives, magnetic cassettes, flash memory cards, cartridges, etc. It will be appreciated that other types of media readable by a computer, etc., may also be used in the exemplary operating environment and any such media may include computer-executable instructions for performing the methods of the present disclosure.

A number of program modules may be stored in the drive and RAM 1112, including the operating system 1130, one or more application programs 1132, other program modules 1134, and program data 1136. All or part of the operating system, applications, modules and / or data may also be cached in RAM 1112. It will be appreciated that the present disclosure can be implemented in various commercially available operating systems or combinations of operating systems.

The user may input commands and information to the computer 1102 through one or more wired / wireless input devices, for example, pointing devices such as a keyboard 1138 and a mouse 1140. Other input devices (not shown) may include a microphone, IR remote control, joystick, game pad, stylus pen, touch screen, etc. These and other input devices are often connected to the processing unit 1104 through an input device interface 1142 connected to the system bus 1108, but the parallel port, IEEE 1394 serial port, game port, USB port, IR interface, And other interfaces.

The monitor 1144 or other type of display device is also connected to the system bus 1108 through an interface such as a video adapter 1146. In addition to the monitor 1144, the computer generally includes other peripheral output devices (not shown) such as speakers, printers, and the like.

The computer 1102 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer (s) 1148 via wired and / or wireless communication. The remote computer (s) 1148 may be a workstation, computing device computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other conventional network node, typically in computer 1102. It includes many or all of the components described with respect to, but for simplicity, only the memory storage device 1150 is shown. The illustrated logical connections include wired / wireless connections to a local area network (LAN) 1152 and / or a larger network, such as a wide area network (WAN) 1154. Such LAN and WAN networking environments are common in offices and companies, and facilitate enterprise-wide computer networks such as intranets, all of which can be connected to computer networks around the world, for example, the Internet.

When used in a LAN networking environment, the computer 1102 is connected to the local network 1152 via a wired and / or wireless communication network interface or adapter 1156. The adapter 1156 may facilitate wired or wireless communication to the LAN 1152, which also includes a wireless access point installed therein to communicate with the wireless adapter 1156. When used in a WAN networking environment, the computer 1102 may include a modem 1158, or connect to a communication computing device on the WAN 1154, or establish communication over the WAN 1154, such as through the Internet. Have other means. The modem 1158, which may be an internal or external and wired or wireless device, is connected to the system bus 1108 through a serial port interface 1142. In a networked environment, program modules described for the computer 1102 or portions thereof may be stored in the remote memory / storage device 1150. It will be appreciated that the network connections shown are exemplary and other means of establishing a communication link between computers can be used.

The computer 1102 is associated with any wireless device or object that is deployed and operates in wireless communication, such as a printer, scanner, desktop and / or portable computer, a portable data assistant (PDA), communication satellite, or wireless detectable tag. It operates to communicate with any equipment or place and telephone. This includes at least Wi-Fi and Bluetooth wireless technology. Accordingly, the communication may be a predefined structure as in a conventional network or simply ad hoc communication between at least two devices.

Wi-Fi (Wireless Fidelity) enables a connection to the Internet or the like without a wired connection. Wi-Fi is a wireless technology such as a cell phone that allows a device, for example, a computer to transmit and receive data indoors and outdoors, ie anywhere within the base station's coverage area. Wi-Fi networks use a wireless technology called IEEE 802.11 (a, b, g, etc.) to provide a secure, reliable and high-speed wireless connection. Wi-Fi can be used to connect computers to each other, to the Internet, and to a wired network (using IEEE 802.3 or Ethernet). Wi-Fi networks can operate in unlicensed 2.4 and 5 GHz radio bands, for example, at 11 Mbps (802.11a) or 54 Mbps (802.11 b) data rates, or in products that include both bands (dual band). have.

One of ordinary skill in the art of the present disclosure will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, instructions, information, signals, bits, symbols and chips that can be referenced in the above description are voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields Or particles, or any combination thereof.

Those of ordinary skill in the art of the present disclosure may use various examples of logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the embodiments disclosed herein in electronic hardware, (convenience For the sake of understanding, it may be implemented by various forms of program or design code (referred to herein as “software”) or a combination of both. To clearly illustrate this interoperability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art of the present disclosure may implement the functions described in various ways for each particular application, but such implementation decisions should not be interpreted as being outside the scope of the present disclosure.

Various embodiments presented herein may be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "manufactured article" includes a computer program, carrier, or media accessible from any computer-readable device. For example, computer-readable media include magnetic storage devices (eg, hard disks, floppy disks, magnetic strips, etc.), optical disks (eg, CDs, DVDs, etc.), smart cards, and flash memory Devices (eg, EEPROMs, cards, sticks, key drives, etc.), but are not limited to these. Also, various storage media presented herein include one or more devices and / or other machine-readable media for storing information.

It is understood that the specific order or hierarchy of steps in the processes presented is an example of exemplary approaches. Based on design priorities, it is understood that within the scope of the present disclosure, a specific order or hierarchy of steps in the processes may be rearranged. The accompanying method claims provide elements of the various steps in a sample order, but are not meant to be limited to the specific order or hierarchy presented.

Descriptions of the presented embodiments are provided to enable any person of ordinary skill in the art to use or practice the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art of the present disclosure. The general principles defined herein can be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure should not be limited to the embodiments presented herein, but should be interpreted in the broadest scope consistent with the principles and novel features presented herein.

Claims (1)

A computer program stored on a computer readable storage medium.

Images