# US 2017/0302747 A1 · Card-type desktop implementation method, apparatus, and system

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

- Number: US 2017/0302747 A1
- Document ID: US20170302747A1
- Status: Published application
- Kind: A1
- Application number: 15/639,677
- Filed: 2017-06-30
- Published: 2017-10-19
- Earliest claimed: 2014-12-31
- Assignees: Alibaba Group Holding Limited
- Applicants: Alibaba Group Holding Limited
- Inventors: Zirong LUO; Xueshu QIAN; Yang YANG
- Web page: https://patentgrep.com/patent/US20170302747A1

## CPC

- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F 3/0481: based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F 8/38: for implementing user interfaces
- G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57)
- G06F 9/451: Execution arrangements for user interfaces
- G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06)
- G06F 16/986: {Document structures and storage, e.g. HTML extensions}
- G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- G06F 8/61: Installation
- 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

The present invention provides card-type desktop implementation methods, apparatuses and systems. Some embodiments comprise: a service management module sending a resource address of a service card from a server terminal to a desktop module; the desktop module creating a view area on a desktop, the view area being used to display the service card corresponding to the resource address, creating a view corresponding to the service card in the view area, and sending view information and the resource address to a rendering module; and the rendering module acquiring a resource file corresponding to the resource address from the server terminal, and rendering the resource file to the view according to the view information. The embodiments of the present invention can get rid of template restrictions, reduce system consumption, and improve stability of the desktop.

## Claims

### Claim 1

A card-type desktop implementation method, comprising:
acquiring a resource address of a service card from a server terminal;
creating, by a desktop module, a view area on a desktop, the view area being used to display the service card corresponding to the resource address;
creating, by the desktop module, a view corresponding to the service card in the view area;
acquiring, by a rendering module, a resource file corresponding to the resource address from the server terminal; and
rendering, by the rendering module, the resource file to the view according to view information.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
storing, related information of the service card in a database, the related information of the service card comprising the resource address and the view information.

### Claim 3 (depends on 2)

The method according to claim 2, further comprising:
reading, the related information of the service card in the database.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
receiving a content update message comprising the resource address; and
re-acquiring, by the rendering module, a resource file corresponding to the resource address from the server terminal.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising:
acquiring an event of deleting the service card by a user; and
deleting the view corresponding to the service card,
wherein a view area occupied by the view is restored to be available.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising:
acquiring an operational event of a user on the service card; and
responding, to the operational event,
wherein the operational event is captured by one of a JavaScript code on the service card and the rendering module.

### Claim 7 (depends on 6)

The method according to claim 6, wherein responding to the operational event is performed by the rendering module, the method further comprising:
acquiring, from the server terminal, a second resource file corresponding to a resource address requested by the operational event; and
rendering the second resource file to either the view corresponding to the service card, or to a created window on the desktop created by the desktop module.

### Claim 8 (depends on 6)

The method according to claim 6, wherein responding to the operational event is performed by the desktop module, the method further comprising:
sending, by the desktop module, a resource address requested by the operational event and the view information corresponding to the service card to the rendering module; and
rendering a second resource file to the corresponding view, wherein the second resource file corresponds with the resource address requested by the operational event.

### Claim 9 (depends on 7)

The method according to claim 7, wherein the created window covers either at least a part of the view, or an area not conflicting with the view on the desktop.

### Claim 10

(canceled)

### Claim 11 (depends on 1)

The method according to claim 1, wherein the desktop module and the rendering module exchange information by means of inter-process communication.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the rendering module calls a web engine to perform the operation of rendering.

### Claim 13

A card-type desktop implementation apparatus, comprising:
a desktop module configured to:
create a view area on a desktop after receiving a resource address of a service card, the view area being used to display the service card corresponding to the resource address; and
create a view corresponding to the service card in the view area; and
a rendering module, configured to:
acquire a resource file corresponding to the resource address from a server terminal; and
render the resource file to the view according to view information.

### Claim 14 (depends on 13)

The apparatus according to claim 13, wherein the desktop module is further configured to:
store related information of the service card in a database, the related information of the service card comprising the resource address and the view information.

### Claim 15 (depends on 14)

The apparatus according to claim 14, wherein the desktop module is further configured to:
read the related information of the service card in the database.

### Claim 16 (depends on 13)

The apparatus according to claim 13, wherein
the desktop module is further configured to, send an content update message comprising the resource address to the rendering module; and
the rendering module is further configured to, re-acquire a resource file corresponding to the resource address from the server terminal.

### Claim 17 (depends on 13)

The apparatus according to claim 13, wherein the desktop module is further configured to:
acquire an event of deleting the service card by a user; and
delete the view corresponding to the service card
wherein a view area occupied by the view is restored to be available.

### Claim 18 (depends on 13)

The apparatus according to claim 13, wherein
at least one of the rendering module and the desktop module is further configured to,
acquire an operational event of a user on the service card; and
respond to the operational event,
wherein the operational event is captured by one of a JavaScript code on the service card and the rendering module.

### Claim 19 (depends on 18)

The apparatus according to claim 18, wherein
the rendering module, when responding to the operational event, is further configured to:
acquire, from the server terminal, a second resource file corresponding to a resource address requested by the operational event; and
render the second resource file to either the view corresponding to the service card, or to a created window on the desktop.

### Claim 20 (depends on 18)

The apparatus according to claim 18, wherein
the desktop module, when responding to the operational event, is further configured to:
send a resource address requested by the operational event and the view information corresponding to the service card to the rendering module; or,
create a window on the desktop, and send the resource address requested by the operational event and information of the created window to the rendering module, wherein the rendering module renders a second resource file to the created window, the second resource file corresponding to the resource address requested by the operational event.

### Claim 21 (depends on 19)

The apparatus according to claim 19, wherein the window created by the desktop module covers either at least a part of the view, or an area not conflicting with the view on the desktop.

### Claim 22 (depends on 20)

The apparatus according to claim 20, wherein the desktop module is further configured to:
receive, the operational event and at least one of size and position information of the window, from the JavaScript code; and
create the window according to the at least one of size and the position information of the window.

### Claim 23 (depends on 13)

The apparatus according to claim 13, wherein the desktop module and the rendering module exchange information by means of inter-process communication.

### Claim 24 (depends on 13)

The apparatus according to claim 13, wherein the rendering module calls a web engine to perform the operation of rendering.

### Claim 25

(canceled)

### Claim 26

(canceled)

### Claim 27

A card-type desktop implementation method, comprising:
receiving a resource address of a service card from a server terminal;
creating a view area on a desktop, the view area being used to display the service card corresponding to the resource address;
creating a view corresponding to the service card in the view area;
acquiring a resource file corresponding to the resource address from the server terminal; and
rendering the resource file to the view according to view information.

### Claim 28 (depends on 27)

The method according to claim 27, further comprising:
receiving a content update message comprising the resource address; and
re-acquiring a resource file corresponding to the resource address from the server terminal.

### Claim 29 (depends on 27)

The method according to claim 27, further comprising:
acquiring an event of deleting the service card by a user; and
deleting the view corresponding to the service card,
wherein a view area occupied by the view is restored to be available.

### Claim 30 (depends on 27)

The method according to claim 27, further comprising:
acquiring an operational event of a user on the service card;
acquiring, from the server terminal, a second resource file corresponding to a resource address requested by the operational event; and
rendering the second resource file to either the view, or a created window on the desktop.

### Claim 31 (depends on 6)

The method according to claim 6, wherein responding to the operational event is performed by the desktop module, the method further comprising:
sending, by the desktop module, a resource address requested by the operational event and the view information corresponding to the service card to the rendering module;
creating, by the desktop module, a window on the desktop;
sending the resource address requested by the operational event and information of the created window to the rendering module; and
rendering the second resource file to the created window.

### Claim 32 (depends on 31)

The method according to claim 31, further comprising:
reporting, the operational event and at least one of size and position information of the window to the desktop module; and
creating, by the desktop module, the window based on the at least one of size and position information of the window.

### Claim 33 (depends on 31)

The method according to claim 31, wherein the created window covers either at least a part of the view, or an area not conflicting with the view on the desktop.

### Claim 34 (depends on 30)

The method according to claim 30, wherein the created window covers either at least a part of the view, or an area not conflicting with the view on the desktop.

### Claim 35

A non-transitory computer readable medium that stores a set of instructions that are executable by at least one processor of a card-type desktop implementation apparatus to perform a card-type desktop implementation method, the method comprising:
receiving a resource address of a service card from a server terminal;
creating a view area on a desktop, the view area being used to display the service card corresponding to the resource address;
creating a view corresponding to the service card in the view area;
acquiring a resource file corresponding to the resource address from the server terminal; and
rendering the resource file to the view according to information of the view.
