# US 2018/0321984 A1 · Virtual graph nodes

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

- Number: US 2018/0321984 A1
- Document ID: US20180321984A1
- Status: Published application
- Kind: A1
- Application number: 15/584,142
- Filed: 2017-05-02
- Published: 2018-11-08
- Earliest claimed: 2017-05-02
- Assignees: Home Box Office, Inc.
- Applicants: Home Box Office, Inc.
- Inventors: Sata Busayarat; Jack Song; Brandon C. Furtwangler; Jonathan David Lutz; Allen Arthur Gay; Steven N. Furtwangler
- Web page: https://patentgrep.com/patent/US20180321984A1

## CPC

- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 9/5005: {to service a request}
- G06F 16/2457: with adaptation to user needs
- G06F 16/285: {Clustering or classification}
- G06F 16/51: Indexing; Data structures therefor; Storage structures
- G06F 16/80: of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML (content-based retrieval of web data G06F16/95)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The described technology is directed towards returning less data than is available for a data item in response to a request to a data service. A virtual graph node is returned in response to client requests, in which the virtual node comprises a relatively lightweight set of information relative to the full set of information for the data item, e.g., maintained in a main (graph) node. A requesting client indicates that a virtual node is desired, and receives a response comprising the virtual node, generally processed from the main node's data into a reduced subset of the main node. The main node may be cached at the data service, and returned if and when requested.

## Claims

### Claim 1

A method comprising:
receiving a request for a data item, the data item identified by a data item identifier and an indication that the data item is requested to be returned as a virtual node;
determining from the data item identifier and the indication that the data item corresponds to a main node that has a corresponding virtual node;
obtaining the main node;
processing the main node into the virtual node, wherein the virtual node comprises modified data relative to the data of the main node; and
returning the virtual node in response to the request, in which the virtual node references the main node.

### Claim 2 (depends on 1)

The method of claim 1 wherein processing the main node into the virtual node comprises removing some of the data from the main node.

### Claim 3 (depends on 1)

The method of claim 1 wherein processing the main node into the virtual node comprises removing data from the main node, mutating data, or adding data to the virtual node from a source other than the main node, or any combination of removing data from the main node, mutating data, or adding data to the virtual node from a source other than the main node.

### Claim 4 (depends on 1)

The method of claim 1 wherein obtaining the main node comprises accessing the main node from a data service cache.

### Claim 5 (depends on 1)

The method of claim 1 wherein obtaining the main node comprises obtaining sub-parts from one or more backing data stores, and assembling the sub-parts into the main node.

### Claim 6 (depends on 1)

The method of claim 1 further comprising, caching the main node at a data service cache.

### Claim 7 (depends on 1)

The method of claim 1 wherein determining from the data item identifier and the indication that the data item corresponds to a main node that has a corresponding virtual node comprises, detecting node type information encoded in association with the data item identifier.

### Claim 8 (depends on 1)

The method of claim 1 further comprising, expanding the request for the virtual node into an expanded request that includes the virtual node and the main node.

### Claim 9 (depends on 1)

The method of claim 1 further comprising, receiving a request for another virtual node, and returning a main node instead of the other virtual node in response to the request.

### Claim 10 (depends on 1)

The method of claim 1 wherein processing the main node into the virtual node comprises locating a rule set corresponding to a device code and data item type, and applying the rule set.

### Claim 11 (depends on 10)

The method of claim 10 wherein locating the rule set comprises matching the identifier of the data item against a set of regular expressions.

### Claim 12 (depends on 10)

The method of claim 10 wherein the client request is associated with a token, and further comprising, obtaining the device code based upon information in the token.

### Claim 13 (depends on 1)

The method of claim 1 wherein the rule set is maintained as a file system rule set file, and wherein locating the rule set corresponding to the device code and the data item type comprises using information based upon the identifier of the data item to determine a filename, and using information based upon the device code to determine a set of one or more file system folders for locating the rule set file.

### Claim 14

A system comprising, a data service, including a request handler coupled to virtual node processing logic that processes a main node into a virtual node, the request handler configured to recognize a client request for a virtual node received at the data service, to obtain a main node corresponding to the request, to invoke the virtual node processing logic to generate the virtual node from the main node, and to return the virtual node in response to the request.

### Claim 15 (depends on 14)

The system of claim 14 further comprising a data service cache set, wherein the request handler obtains the main node from the cache set.

### Claim 16 (depends on 14)

The system of claim 14 wherein the data service comprises a front-end part and a back-end part, wherein the request handler is incorporated into the front-end part, and wherein the request handler obtains the main node from the back-end part

### Claim 17 (depends on 14)

The system of claim 14 wherein the request handler obtains a virtual node rule set based upon node type information and client device-specific information, and wherein the virtual node processing logic generates the virtual node from the main node based upon the virtual node rule set.

### Claim 18

One or more machine-readable storage media having machine-executable instructions, which when executed perform steps, comprising:
receiving a request for a node;
determining that the node has a corresponding virtual node;
obtaining the node;
processing the node into the virtual node, including applying a rule set to remove at least some data from the node; and
returning the virtual node in response to the request.

### Claim 19 (depends on 18)

The one or more machine-readable storage media of claim 18 wherein determining that the node has a corresponding virtual node comprises detecting an indicator associated with an identifier of the node.

### Claim 20 (depends on 18)

The one or more machine-readable storage media of claim 18 having further machine-executable instructions comprising, locating the rule set, including locating a rule set file based at least in part upon an identifier of the node.
