# US 2013/0297682 A1 · Client device, information processing system and associated methodology of accessing networked services

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

- Number: US 2013/0297682 A1
- Document ID: US20130297682A1
- Status: Published application
- Kind: A1
- Application number: 13/934,680
- Filed: 2013-07-03
- Published: 2013-11-07
- Earliest claimed: 2008-07-28
- Assignees: Sony Electronics Inc.; Sony Corporation
- Applicants: Sony Electronics Inc.; Sony Corporation
- Inventors: Hiroki TAKAKURA; Anna Gershnik; Brian Beaver; Charles Mccoy
- Web page: https://patentgrep.com/patent/US20130297682A1

## CPC

- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system makes it possible to use services offered by a plurality of servers different from one another is realized with the use of a common API. The system includes a plurality of service-offering servers, a client that uses services offered by the plurality of service-offering servers, and an interchange server that performs intermediary processing when the client uses a service. The client performs communication with the interchange server while using a common API when using any service among a plurality of services offered by the plurality of service-offering servers. The interchange server uses a unique API, which is unique to the service-offering server that offers the service selected by the client, to execute a processing sequence that is unique to the service-offering server. The client may use any service among services offered by the plurality of service-offering servers with the use of a common API without any need to use a unique API, which is unique to each of the plurality of service-offering servers.

## Claims

### Claim 1

A method of causing an interchange server to intermediate communication between a client device and a plurality of service-offering servers, the method comprising:
generating a uniform user interface at the client device in accordance with a common API, the common API being independent of a plurality of server-specific APIs, each of the plurality of server-specific APIs corresponding to a respective one of the plurality of service-offering servers, the plurality of server-specific APIs being stored in an electronic memory of the interchange server;
receiving, at the interchange server, input data entered into the uniform user interface, the input data including selection of a service corresponding to a desired service-offering server of the plurality of service offering servers;
translating the input data, at the interchange server, in accordance with a respective one of the server-specific APIs corresponding to the desired service-offering server; and
transmitting the translated input data from the interchange server to the desired service-offering server in accordance with the respective one of the plurality of server-specific APIs, a response from the desired service-offering server being translated and transmitted to the client device according to the common API.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising: determining, at the interchange server, new service-offering servers; and storing, in the electronic memory of the interchange server, server-specific APIs corresponding to the new service-offering servers.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising:
determining, at the interchange server, available services on the plurality of service-offering servers;
transmitting a list of the available services to the client device in accordance with the common API, the available services being incorporated into the uniform user interface; and
removing services corresponding to unavailable service-offering servers from the uniform user interface.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising: validating, at the interchange server, the input data using a machine-specific information corresponding to the client device, the machine-specific information being previously stored in the interchange server.

### Claim 5 (depends on 4)

The method according to claim 4, further comprising: generating a checksum at the client device using the machine specific information; appending the checksum to the input data at the client device; and verifying the checksum at the interchange server using the machine-specific information.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the common API includes a login function to log the client device onto the desired service-offering server, an albums function to return, via the interchange server to the client device, a listing of data groups stored on the desired service-offering server, the data groups being associated with the client device at the desired service-offering server, a new album function to generate, via the interchange server, a new data group in the desired service-offering server, an assets function to return, via the interchange server to the client device, a list of assets stored on the desired service-offering server, the list of assets being associated with the client device at the desired service-offering server, an image function to return selected data via the interchange server to the client device, the selected data being displayed on a display of the client device, and an upload function to upload the input data, via the interchange server, to the desired service-offering server.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the common API generates one of XML-formatted data and JSON-formatted data.

### Claim 8

An interchange server interposed between a client device and a plurality of service-offering servers, comprising:
a CPU coupled to a memory and including
a client interface unit to communicate with the client device according to a common API, data received from the client device via the client interface unit including selection of a service provided by a desired one of the service-offering servers;
a controller unit to translate the data received from the client device in accordance with a respective one of a plurality of server-specific APIs stored in an electronic memory of the interchange server, each of the server-specific APIs corresponding to one of the plurality of service-offering servers, the common API being independent from the plurality of server-specific APIs; and
a server interface unit to communicate, independently of the client interface unit, with the desired service-offering server in accordance with the respective one of the plurality of server-specific APIs, a response received from the desired service-offering server being translated and sent in accordance with the common API to the client device via the client interface unit, wherein the common API provides a uniform interface to access services offered by the plurality of service-offering servers via the plurality of server-specific APIs.

### Claim 9 (depends on 8)

The interchange server according to claim 8, wherein the controller unit dynamically updates the plurality of different server-specific APIs in response to updates by the plurality of service-offering servers.

### Claim 10 (depends on 8)

The interchange server according to claim 8, wherein the controller unit dynamically stores new server-specific APIs corresponding to newly detected service-offering servers and dynamically removes server-specific APIs corresponding to unavailable service-offering servers.

### Claim 11 (depends on 8)

The interchange server according to claim 8, further comprising: a validation unit to validate the data received from the client device in accordance with machine-specific information corresponding to the client device, the machine-specific information being previously stored in the interchange server.

### Claim 12 (depends on 11)

The interchange server according to claim 11, wherein the validation unit validates a checksum generated by the client device in accordance with the machine-specific information.

### Claim 13 (depends on 11)

The interchange server according to claim 11, wherein the controller unit includes a services unit to determine services provided by the plurality of service-offering servers, an album unit to determine groups of data stored on the desired service-offering server, a new album unit to generate a new group of data in the desired service-offering server, an image unit to request selected data via the respective one of the plurality of server-specific APIs, the selected data being supplied to the client device via the common API, the selected data being selected at the client device, and an upload unit to supply data received from the client to the desired service-offering server via the respective one of the plurality of server-specific APIs.

### Claim 14 (depends on 8)

The interchange server according to claim 8, wherein the common API is used to generate at least one of XML-formatted data and JSON-formatted data.

### Claim 15

A non-transitory computer-readable medium storing computer-readable instructions thereon, the computer-readable instructions when executed by a computer cause the computer to perform the method comprising:
generating a uniform user interface at a client device in accordance with a common API, the common API being independent of a plurality of server-specific APIs, each of the plurality of server-specific APIs corresponding to a respective one of a plurality of service-offering servers, the plurality of server-specific APIs being stored in an electronic memory of an interchange server; receiving, at the interchange server, input data entered into the uniform user interface, the input data including selection of a service corresponding to a desired service-offering server of the plurality of service offering servers;
translating the input data in accordance with a respective one of the server-specific APIs corresponding to the desired service-offering server; and
transmitting the translated input data from the interchange server to the desired service-offering server in accordance with the respective one of the plurality of server-specific APIs, a response from the desired service-offering server being translated and transmitted to the client device according to the common API.

### Claim 16

The non-transitory computer-readable medium according to 15, further comprising: determining new service-offering servers; and storing, in the electronic memory of the interchange server, server-specific APIs corresponding to the new service-offering servers.

### Claim 17

The non-transitory computer-readable medium according to 15, further comprising: determining available services on the plurality of service-offering servers; transmitting a list of the available services from the interchange server to the client device in accordance with the common API, the available services being incorporated into the uniform user interface; and removing services corresponding to unavailable service-offering servers from the uniform user interface.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium according to claim 15, further comprising: validating the input data using machine-specific information corresponding to the client device, the machine specific-information being previously stored in the interchange server.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium according to claim 18, further comprising: generating a checksum at the client device using the machine-specific information; appending the checksum to the input data at the client device; and verifying the checksum at the interchange server using the machine-specific information.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium according to claim 15, wherein the common API includes a login function to log the client device onto the desired service-offering server, an albums function to return, via the interchange server to the client device, a listing of data groups stored on the desired service-offering server, the data groups being associated with the client device at the desired service-offering server, a new album function to generate, via the interchange server, a new data group in the desired service-offering server, an assets function to return, via the interchange server to the client device, a list of assets stored on the desired service-offering server, the list of assets being associated with the client device at the desired service-offering server, an image function to return selected data via the interchange server to the client device, the selected data being displayed on a display of the client device, and an upload function to upload the input data, via the interchange server, to the desired service-offering server.

### Claim 21 (depends on 20)

The non-transitory computer-readable medium according to claim 20, wherein the common API generates one of XML-formatted data and JSON-formatted data.
