# US 2017/0257368 A1 · Application management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0257368 A1
- Document ID: US20170257368A1
- Status: Published application
- Kind: A1
- Application number: 15/057,677
- Filed: 2016-03-01
- Published: 2017-09-07
- Earliest claimed: 2016-03-01
- Inventors: Cay JEGLINSKI
- Web page: https://patentgrep.com/patent/US20170257368A1

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- H04L 9/0631: {Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)}
- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An application management system, especially a web application management system, for enabling different clients to access specific versions of an application, includes means for identifying at least one specific marker associated to the clients or to client requests, means for selecting a specific version of the application for a requesting client based on at least one identified marker, and means for delivering the selected specific version of the application to the requesting client.

## Claims

### Claim 1

An application management system, especially a web application management system, for enabling different clients to access specific versions of an application, the application management system comprising
means for identifying at least one specific marker associated to the clients or to client requests,
means for selecting a specific version of the application for a requesting client based on at least one identified marker, and
means for delivering the selected specific version of the application to the requesting client.

### Claim 2 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is an IP address marker.

### Claim 3 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is a DNS marker.

### Claim 4 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is a user marker or a user group marker.

### Claim 5 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is an application name html-header marker.

### Claim 6 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is a certificate marker.

### Claim 7 (depends on 1)

The application management system according to claim 1, wherein the at least one specific marker is an URI Marker.

### Claim 8 (depends on 1)

The application management system according to claim 1, wherein a version access rule base is associated to the application,

### Claim 9 (depends on 1)

The application management system according to claim 1, further comprising means for manipulating an URL request to the application based on the at least one identified marker.

### Claim 10 (depends on 1)

The application management system according to claim 1, further comprising means for applying a version rule base in case of failed version response by the application.

### Claim 11 (depends on 1)

The application management system according to claim 1, further comprising a life cycle management system for secure publication of applications without service interruption.

### Claim 12 (depends on 11)

The application management system according to claim 11, wherein the life cycle management system includes a production field with a server farm having a plurality of application servers sharing the same configuration and layout, the life cycle management system further including means for transitioning the servers to become different functional server groups through a life cycle, the functional server groups including
an active group processing requests to all applications,
a stand-by group, the life cycle management system being capable of appointing the stand-by group as the active group in case of malfunction of the active group, and
a staging group staging new transportation items and being used to quality assure new updates, services and/or versions to be applied to the server farm.

### Claim 13 (depends on 12)

The application management system according to claim 12, the functional server groups further including a reserve group that is assigned load in case response time thresholds are exceeded.

### Claim 14 (depends on 13)

The application management system according to claim 13, wherein the life cycle management system includes means for transporting a new service onto a Golden Master server.

### Claim 15 (depends on 14)

The application management system according to claim 14, wherein the life cycle management system includes means for staging the application servers of the staging group with the new service from the Golden Master server.

### Claim 16 (depends on 15)

The application management system according to claim 15, wherein the life cycle management system includes means for transitioning the application servers of the reserve group to become the application servers of the staging group and vice versa.

### Claim 17 (depends on 16)

The application management system according to claim 16, wherein the life cycle management system includes means for transitioning the application servers of the stand-by group to become the application servers of the staging group and vice versa.

### Claim 18 (depends on 17)

The application management system according to claim 17, wherein the life cycle management system includes means for transitioning the application servers of the stand-by group to become the application servers of the active group and vice versa.

### Claim 19 (depends on 1)

The application management system according to claim 1, further comprising a backend service which is used as a user authentication system.

### Claim 20 (depends on 19)

The application management system according to claim 19, wherein the user authentication system includes means for generating a unique ID in an html header cookie.

### Claim 21 (depends on 20)

The application management system according to claim 20, wherein a client includes means for generating an RSA key pair and transporting its public key to a backend server.

### Claim 22 (depends on 21)

The application management system according to claim 21, wherein the backend server includes means for generating its own RSA key pair.

### Claim 23 (depends on 22)

The application management system according to claim 22, wherein the backend server includes means for enciphering the public key with the client public key and transporting the enciphered public key to the client.

### Claim 24 (depends on 20)

The application management system according to claim 20, wherein the user authentication system includes means for generating an AES key that is used to encrypt the unique ID that is generated every time a client requests application data.
