# US 2017/0288957 A1 · Input method engine management for edge services

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

- Number: US 2017/0288957 A1
- Document ID: US20170288957A1
- Status: Published application
- Kind: A1
- Application number: 15/084,611
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Su Liu; Eric J. Rozner; Chin Ngai Sze; Yaoguang Wei
- Web page: https://patentgrep.com/patent/US20170288957A1

## CPC

- G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)}
- H04L 41/0803: Configuration setting
- G06F 11/30: Monitoring
- G06F 11/302: {where the computing system component is a software system}
- H04L 43/16: Threshold monitoring
- G06F 2201/81: Threshold
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for managing deployment of input method engines (IMEs) to computing devices in proximate relation to endpoint devices within a data communication network includes receiving software logic data indicating deployment rules for deploying an IME executing on a first computing device in the data communication network to a second computing device in the data communication network. The method further includes receiving a software data structure identifying configuration preferences of a user of an endpoint device. The method further includes monitoring the usage of the IME. Monitoring may include obtaining usage data associated with the user's access to the IME through the second computing device. The method additionally includes determining, based on the monitoring and the software logic data and the software data structure, whether the threshold condition is satisfied and deploying the IME to the second computing device in when that the threshold condition is satisfied.

## Claims

### Claim 1

A method for managing deployment of input method engines (IMEs) to computing devices in proximate relation to endpoint devices within a data communication network, the method comprising:
receiving software logic data indicating deployment rules for deploying a first IME executing on a first computing device in the data communication network to a second computing device in the data communication network, the deployment rules indicating a threshold condition for deploying the first IME to the second computing device;
receiving software data structure identifying configuration preferences of a user of an endpoint device, the configuration preferences associating the user with a configuration of the first IME, wherein the user's accesses the first IME is routed in the data communication network through the endpoint device and second computing device;
monitoring the usage of the first IME, wherein the monitoring includes obtaining usage data associated with the user's access to the first IME through the second computing device;
determining, based on the monitoring and the software logic data and the software data structure, whether the threshold condition is satisfied; and
deploying the first IME to the second computing device when the threshold condition is satisfied.

### Claim 2 (depends on 1)

The method of claim 1, wherein communication latency between the first computing device and the endpoint computing device is greater than communication latency between the second computing device and the endpoint computing device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the first computing device is separated from the end point computing device by a first number of intermediate computing devices, and the second computing device is separated from the endpoint computing device by a second number of computing devices, wherein the second number is smaller than the first number.

### Claim 4 (depends on 1)

The method of claim 1, wherein the threshold condition is satisfied when a threshold number of users access the first IME though the second computing device.

### Claim 5 (depends on 1)

The method of claim 1, wherein the receiving the software data structure comprises:
receiving configuration preferences associated with two or more users of the first IME; and
merging the configuration preferences to generate the software data structure.

### Claim 6 (depends on 1)

The method of claim 1, wherein the threshold condition is at least one of a number of users accessing the IME through the second computing system, a volume of data exchanged between the IME and a user of the IME, the frequency with which a user accesses the IME through the second computing system, and a span of time since the IME was last accessed.

### Claim 7 (depends on 1)

The method of claim 1, wherein the second computing device is an edge server.

### Claim 8 (depends on 1)

The method of claim 1, wherein the second computing device and is an access point.

### Claim 9 (depends on 1)

The method of claim 1, wherein deployment rules further indicate a criteria for removing a second IME executing on the second computing device from the second computing device before deploying the first IME to the second computing device.

### Claim 10

A system for managing deployment of input method engines (IMEs) to a computing device in proximate relation to an endpoint device within a data communication network, the system comprising:
a mediator component to configured to receive a software data structure, wherein the software data structure identifies configuration preferences of a user of the endpoint device, the configuration preferences associating the user with a configuration a first IME executing on a first computing device in the data communication network, wherein the user accesses the first IME through a communication channel routed through the endpoint device and the second computing device;
a usage monitor component configured to monitor the usage of the first IME, wherein the usage includes usage data associated with the user's access to the first IME through the second computing device; and
a service manager component coupled to the mediator component and the usage monitor component, the service manager component configured to:
receive software logic data, wherein the software logic data indicates deployment rules for deploying the first IME to the second computing device in the network environment, the deployment rules indicating a threshold condition for deploying the first IME to the second computing device;
determine, based on the monitoring and the software logic data and the software data structure, whether the threshold condition device is satisfied; and
deploy the first IME to the second computing device when the threshold condition is satisfied.

### Claim 11 (depends on 10)

The system of claim 10, wherein communication latency between the first computing device and the endpoint computing device is greater than communication latency between the second computing device and the endpoint computing device.

### Claim 12 (depends on 10)

The system of claim 10, wherein the first computing device is separated from the end point computing device by a first number of intermediate computing devices, and the second computing device is separated from the endpoint computing device by a second number of computing devices, wherein the second number is smaller than the first number.

### Claim 13 (depends on 10)

The system of claim 10, wherein the threshold condition is satisfied when a threshold number of users access the first IME though the second computing device.

### Claim 14 (depends on 10)

The system of claim 10, wherein the mediator component is further configured to:
receive configuration preferences associated with two or more users of the first IME; and
merge the configuration preferences to generate the software data structure.

### Claim 15 (depends on 10)

The system of claim 10, wherein the threshold condition is at least one of a number of users accessing the IME through the second computing system, a volume of data exchanged between the IME and a user of the IME, the frequency with which a user accesses the IME through the second computing system, and a span of time since the IME was last accessed.

### Claim 16 (depends on 10)

The system of claim 10, wherein the second computing device is an edge server.

### Claim 17 (depends on 10)

The system of claim 10, wherein the second computing device and is an access point.

### Claim 18

A computer program product for managing deployment of input method engines (IMEs) to computing devices in proximate relation to endpoint devices within a data communication network, the computer program product including a computer readable storage medium having program instructions embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program instructions executable by a processing circuit to cause the processing circuit to perform a method comprising:
receiving software logic data indicating deployment rules for deploying a first IME executing on a first computing device in the data communication network to a second computing device in the data communication network, the deployment rules indicating a threshold condition for deploying the first IME to the second computing device;
receiving software data structure identifying configuration preferences of a user of an endpoint device, the configuration preferences associating the user with a configuration of the first IME, wherein the user's accesses the first IME is routed in the data communication network through the endpoint device and second computing device;
monitoring the usage of the first IME, wherein the monitoring includes obtaining usage data associated with the user's access to the first IME through the second computing device;
determining, based on the monitoring and the software logic data and the software data structure, whether the threshold condition is satisfied; and
deploying the first IME to the second computing device when the threshold condition is satisfied.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the threshold condition is satisfied when a threshold number of users access the first IME though the second computing device.

### Claim 20 (depends on 18)

The computer program product of claim 18, wherein communication latency between the first computing device and the endpoint computing device is greater than communication latency between the second computing device and the endpoint computing device.
