# US 2020/0403887 A1 · Method for managing software service, and server

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

- Number: US 2020/0403887 A1
- Document ID: US20200403887A1
- Status: Published application
- Kind: A1
- Application number: 16/833,716
- Filed: 2020-03-30
- Published: 2020-12-24
- Earliest claimed: 2019-06-19
- Assignees: Pegatron Corporation
- Applicants: Pegatron Corporation
- Inventors: WEN-YEN KAO; SHEN-HAU CHANG
- Web page: https://patentgrep.com/patent/US20200403887A1

## CPC

- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- H04L 41/0813: characterised by the conditions triggering a change of settings
- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- 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

A method for managing a software service, and a server are provided in the present disclosure. The method is suitable for operating in a software service system including a service manager. The service manager manages an existing software service in the software service system. The method includes: obtaining a first service deployment descriptor of a new software service by using the service manager, where a format of the first service deployment descriptor is the same as a format of a second service deployment descriptor of the existing software service; defining a data exchange mechanism between the new software service and the existing software service according to the first service deployment descriptor of the new software service by using the service manager; and exchanging data with the new software service according to the data exchange mechanism by the existing software service.

## Claims

### Claim 1

A method for managing a software service, suitable for operating in a software service system comprising a service manager, the service manager managing an existing software service in the software service system, and the method comprising:
obtaining a first service deployment descriptor of a new software service by the service manager, wherein a format of the first service deployment descriptor is the same as a format of a second service deployment descriptor of the existing software service;
defining a data exchange mechanism between the new software service and the existing software service according to the first service deployment descriptor of the new software service by the service manager; and
exchanging data with the new software service according to the data exchange mechanism by the existing software service.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the first service deployment descriptor of the new software service comprises at least one of a name and an identity of the new software service.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the first service deployment descriptor of the new software service comprises an output port of the new software service and an operation resource requirement of the new software service.

### Claim 4 (depends on 3)

The method according to claim 3, further comprising:
calling a hardware resource corresponding to the operation resource requirement of the new software service by the service manager from at least one server for use by the new software service.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the first service deployment descriptor of the new software service comprises a first service description of a first service application programming interface (API) of the new software service.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the first service description of the first service API comprises a first data type of a first version of the first service API.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the first data type comprises input parameter information and output parameter information of the first version of the first service API.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the data exchange mechanism comprises:
providing an input parameter to the first version of the first service API according to the input parameter information of the first data type by the existing software service when the existing software service intends to access the first version of the first service API; and
returning an output parameter corresponding to the output parameter information by the first version of the first service API to the existing software service according to the input parameter provided by the existing software service.

### Claim 9 (depends on 6)

The method according to claim 6, wherein the service description of the first service API further comprises a second data type of a second version of the first service API.

### Claim 10 (depends on 5)

The method according to claim 5, wherein the first service deployment descriptor of the new software service comprises a second service description of a second API of the new software service.

### Claim 11 (depends on 1)

The method according to claim 1, wherein the first service deployment descriptor of the new software service comprises a call description used for calling the existing software service.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the invocation description of the new software service comprises a name of the existing software service and a specific version of a specific service API, wherein the specific version is provided by the existing software service and to be accessed by the new software service.

### Claim 13 (depends on 12)

The method according to claim 12, wherein the data exchange mechanism comprises:
accessing the specific version of the specific service API of the existing software service according to the call description by the new software service.

### Claim 14

A server, on which a service manager is operated, the service manager managing an existing software service in a software service system, and the server comprising:
a storage circuit, comprising a plurality of modules; and
a processor, coupled to the storage circuit, and accessing the plurality of modules to perform the following steps:
operating the service manager to obtain a first service deployment descriptor of a new software service, wherein a format of the first service deployment descriptor is the same as a format of a second service deployment descriptor of the existing software service;
operating the service manager to define a data exchange mechanism between the new software service and the existing software service according to the first service deployment descriptor of the new software service; and
controlling the existing software service to exchange data with the new software service according to the data exchange mechanism.
