# US 2019/0379733 A1 · Method and device for managing data in internet of things, computer device and readable medium

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

- Number: US 2019/0379733 A1
- Document ID: US20190379733A1
- Status: Published application
- Kind: A1
- Application number: 16/353,807
- Filed: 2019-03-14
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Applicants: Beijing Baidu Netcom Science and Technology Co., Ltd.
- Inventors: Miao HUANG; Zhi WANG; Leding LI
- Web page: https://patentgrep.com/patent/US20190379733A1

## CPC

- H04L 41/0853: by actively collecting configuration information or by backing up configuration information
- G06F 16/23: Updating
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 43/16: Threshold monitoring
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1063: {Discovery through centralising entities}
- H04L 67/1065: {Discovery involving distributed pre-established resource-based relationships among peers, e.g. based on distributed hash tables [DHT] (pre-configuration of logical or physical connections H04L67/1053)}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- 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 disclosure provides a method and device for managing data in Internet of Things, a computer device and a readable medium. The method includes: receiving a relationship data query request carrying a target device identifier sent by a query device; acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database; and returning, to the query device, all the relationship data corresponding to the target device.

## Claims

### Claim 1

A method for managing data in an Internet of Things, the method comprising:
receiving a relationship data query request carrying a target device identifier sent by a query device;
acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database; and
returning, to the query device, all the relationship data corresponding to the target device.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the relationship data identifies a connection relationship, a hierarchical relationship, or a supply relationship between the target device and another device.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the target device is a physical object, and the other device is a physical object or a virtual object.

### Claim 4 (depends on 1)

The method according to claim 1, wherein before acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database, the method further comprises:
acquiring the relationship data between the target device and another device in the Internet of Things; and
storing the relationship data between the target device and the other device into the relationship database in a tag mode.

### Claim 5 (depends on 4)

The method according to claim 4, wherein the tag mode is represented by a key-value.

### Claim 6 (depends on 1)

The method according to claim 1, wherein, if the target device is a physical object, the method further comprises:
receiving data uploaded by the target device according to a preset attribute model; and
storing the data of the target device into a service database.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the preset attribute model comprises at least one attribute defined in advance.

### Claim 8 (depends on 6)

The method according to claim 6, wherein before storing the data of the target device into a service database, the method further comprises:
detecting and determining data of a target attribute that needs to be stored according to a pre-configured data storage strategy; and
the storing the data of the target device into a service database comprises: storing the data of the target attribute of the target device into the service database.

### Claim 9 (depends on 8)

The method according to claim 8, wherein the pre-configured data storage strategy comprises: storing all the data of the reported target attribute; when the data of the target attribute received this time changes compared with the data stored last time, storing the data this time; or if the data received this time is greater than a preset threshold, storing the data received this time.

### Claim 10

A cloud server device, the device comprising:
at least one processor; and
a memory storing instructions, wherein the instructions when executed by the at least one processor, cause the at least one processor to perform operations, the operations comprising:
receiving a relationship data query request carrying a target device identifier sent by a query device;
acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database; and
returning, to the query device, all the relationship data corresponding to the target device.

### Claim 11 (depends on 10)

The device according to claim 10, wherein the relationship data identifies a connection relationship, a hierarchical relationship, or a supply relationship between the target device and another device.

### Claim 12 (depends on 11)

The device according to claim 11, wherein the target device is a physical object, and the other device is a physical object or a virtual object.

### Claim 13 (depends on 10)

The device according to claim 10, wherein before acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database, the operations further comprise:
acquiring the relationship data between the target device and another device in the Internet of Things; and
storing the relationship data between the target device and the other device into the relationship database in a tag mode.

### Claim 14 (depends on 13)

The device according to claim 13, wherein the tag mode is represented by a key-value.

### Claim 15 (depends on 13)

The device according to claim 13, wherein:
if the target device is a physical object, the operations further comprise:
receiving data uploaded by the target device according to a preset attribute model; and
storing the data of the target device into a service database.

### Claim 16 (depends on 15)

The device according to claim 15, wherein the preset attribute model comprises at least one attribute defined in advance.

### Claim 17 (depends on 15)

The device according to claim 15, wherein before storing the data of the target device into a service database, the operations further comprise:
detecting and determining data of a target attribute that needs to be stored according to a pre-configured data storage strategy; and
the storing the data of the target device into a service database comprises: storing the data of the target attribute of the target device into the service database.

### Claim 18 (depends on 16)

The device according to claim 16, wherein the pre-configured data storage strategy comprises: storing all the data of the reported target attribute; when the data of the target attribute received this time changes compared with the data stored last time, storing the data this time; or if the data received this time is greater than a preset threshold, storing the data received this time.

### Claim 19

A non-transitory computer readable medium, storing a computer program thereon, wherein the computer program, when executed by a processor, causes the processor to perform operations, the operations comprising:
receiving a relationship data query request carrying a target device identifier sent by a query device;
acquiring, based on the target device identifier, all relationship data corresponding to the target device from a relationship database; and
returning, to the query device, all the relationship data corresponding to the target device.
