Patent · US11307787B2 · B2 · US

Technologies for providing manifest-based asset representation

(11) Publication number

US11307787B2

(21) Application number

15/826,051

(22) Filing date

2017-11-29

(30) Priority date

2016-11-29

(43) Publication date

2022-04-19

(45) Date of grant

2022-04-19

(51) IPC

G06F 11/30; G06F 3/06; H04L 47/20; G06F 11/07; G06F 11/34; G06F 12/02; G06F 12/06; G06F 13/16; G06F 15/173; G06F 16/174; G06F 21/57; G06F 21/62; G06F 21/73; G06F 21/76; G06F 7/06; G06F 8/65; G06F 8/654; G06F 8/656; G06F 8/658; G06F 9/38; G06F 9/4401; G06F 9/455; G06F 9/48; G06F 9/50; G06F 9/54; G06T 1/20; G06T 1/60; G06T 9/00; H01R 13/453; H01R 13/631; H03K 19/173; H03M 7/30; H03M 7/40; H03M 7/42; H04L 12/28; H04L 12/46; H04L 41/044; H04L 41/0816; H04L 41/0853; H04L 41/12; H04L 43/04; H04L 43/06; H04L 43/08; H04L 43/0894; H04L 47/2441; H04L 49/104; H04L 61/5007; H04L 67/10; H04L 67/1014; H04L 67/63; H04L 67/75; H04L 9/08; H05K 7/14

(52) CPC

G06F Electric digital data processing: 9/5005, 11/0709, 11/0751, 11/079, 11/1453, 11/3006, 11/3034, 11/3055, 11/3079, 11/3409, 12/023, 12/0284, 12/0692, 13/1652, 13/4022, 13/4027, 15/161, 15/80, 16/1744, 21/44, 21/57, 21/6218, 21/70, 21/73, 21/76, 2212/401, 2212/402, 2221/2107, 3/0604, 3/0608, 3/0611, 3/0613, 3/0617, 3/0641, 3/0647, 3/065, 3/0653, 3/067, 7/06, 8/65, 8/654, 8/656, 8/658, 9/3851, 9/3891, 9/4401, 9/45533, 9/4843, 9/4881, 9/5038, 9/5044, 9/505, 9/5083, 9/544
G06T Image data processing or generation, in general: 1/20, 1/60, 9/005
H01R Electrically-conductive connections; structural associations of a plurality of mutually-insulated electrical connecting elements; coupling devices; current collectors: 13/453, 13/4536, 13/4538, 13/631
H03K Pulse technique: 19/1731
H03M Coding; decoding; code conversion in general: 7/3084, 7/40, 7/42, 7/60, 7/6011, 7/6017, 7/6029
H04L Transmission of digital information, e.g. telegraphic communication: 12/2881, 12/4633, 41/044, 41/046, 41/0816, 41/0853, 41/0895, 41/0896, 41/12, 41/142, 41/40, 43/04, 43/06, 43/08, 43/0894, 47/20, 47/2441, 47/78, 47/83, 49/104, 61/2007, 63/1425, 67/10, 67/1014, 67/327, 67/36, 9/0822
H05K Printed circuits; casings or constructional details of electric apparatus; manufacture of assemblages of electrical components: 7/1452, 7/1487, 7/1492

(73) Assignee

Intel Corp

(72) Inventors

Murugasamy K. Nachimuthu; Mohan J. Kumar; Alberto J. Munoz

(54) Title

Technologies for providing manifest-based asset representation

(57) Abstract

Technologies for generating manifest data for a sled include a sled to generate manifest data indicative of one or more characteristics of the sled (e.g., hardware resources, firmware resources, a configuration of the sled, or a health of sled components). The sled is also to associate an identifier with the manifest data. The identifier uniquely identifies the sled from other sleds. Additionally, the sled is to send the manifest data and the associated identifier to a server. The sled may also detect a change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also generate an update of the manifest data based on the detected change, where the update specifies the detected change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also send the update of the manifest data to the server.

Full text

View on Google Patents

Claims (24)

An apparatus, comprising: a compute circuitry to: generate manifest data indicative of one or more characteristics of multiple devices coupled to a circuit board, wherein the manifest data comprises configuration information indicative of firmware configurations of individual devices of the multiple devices and wherein the configuration information indicative of firmware configurations of individual devices of the multiple devices is to indicate one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the apparatus from among a plurality of apparatuses; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more characteristics of at least one device among the multiple devices; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the at least one device; and send the update of the manifest data to the orchestrator server.
The apparatus of claim 1, wherein to update the manifest data comprises to: determine which of the manifest data to update based on the change; and modify the manifest data based on the change.
The apparatus of claim 1, wherein the change is at least one of an addition of a first resource or a removal of a second resource.
The apparatus of claim 1, wherein the update sent to the orchestrator server comprises an indication of the change to the manifest data.
The apparatus of claim 1, wherein the manifest data includes at least one hardware manifest, firmware manifest, configuration manifest, or health manifest.
The apparatus of claim 5, wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices.
The apparatus of claim 6, wherein the configuration manifest comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order.
The apparatus of claim 6, wherein to generate the manifest data indicative of the one or more characteristics of multiple devices coupled to a circuit board comprises to: determine present hardware resources and firmware resources; determine a configuration of the multiple devices; determine a health of the hardware resources; and create the hardware manifest based on the present hardware resources, the firmware manifest based on the present firmware resources, the configuration manifest based on the determined configuration of the multiple devices, and the health manifest based on the health of the hardware resources.
The apparatus of claim 6, wherein to associate the identifier with the manifest data comprises to: determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.
The apparatus of claim 1, wherein to send the manifest data and the associated identifier comprises to send the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.
The apparatus of claim 1, wherein a node comprises at least the apparatus, wherein the node is composed based, in part, on the manifest data and wherein the compute circuitry is further to generate the manifest data for a composed node.
One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause one or more devices to: generate manifest data indicative of one or more characteristics of multiple devices of a system, wherein the manifest data comprises configuration information indicative of a firmware utilized by individual devices of the multiple devices and wherein the configuration information indicative of a firmware utilized by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the system from among a plurality of systems; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more of the characteristics of the system; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the system; and send the update of the manifest data to the orchestrator server.
The one of more non-transitory machine-readable storage media of claim 12, wherein the update sent to the orchestrator server is an indication of the change to the manifest data.
The one of more non-transitory machine-readable storage media of claim 12, wherein the manifest data includes at least one hardware manifest, a firmware manifest, configuration manifest, or health manifest.
The one of more non-transitory machine-readable storage media of claim 14, wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices, wherein the firmware manifest specifies at least one of a BIOS version, baseboard management controller (BMC) version, DIMM firmware version, or solid state drive (SSD) version, and wherein the configuration manifest of the system comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order.
The one of more non-transitory machine-readable storage media of claim 14, wherein to generate the manifest data indicative of the one or more characteristics of the system comprises to: determine hardware resources and firmware resources present in the system; determine a configuration of the system; and create the at least one hardware manifest based on the hardware resources present, the firmware manifest based on the firmware resources present, and the configuration manifest based on the determined configuration.
The one of more non-transitory machine-readable storage media of claim 14, wherein to associate the identifier with the manifest data comprises to: determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.
The one of more non-transitory machine-readable storage media of claim 12, wherein to send the manifest data and the associated identifier comprises to send the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.
The one of more non-transitory machine-readable storage media of claim 18, wherein a node comprises at least the system, wherein the node is composed based, in part, on the manifest data.
A system comprising: one or more processors; and a memory to store a plurality of instructions, which, when executed by the one or more processors, causes at least one circuitry to: generate manifest data indicative of one or more characteristics of multiple devices in the system, wherein the manifest data comprises configuration information indicative of a firmware applied by individual devices of the multiple devices and wherein the configuration information indicative of a firmware applied by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the system from among a plurality of systems; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more of the characteristics of the system; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the system; and send the update of the manifest data to the orchestrator server.
A method comprising: generating, by circuitry, manifest data indicative of one or more characteristics of multiple devices coupled to a system, wherein the manifest data comprises configuration information indicative of a firmware applied by individual devices of the multiple devices and wherein the configuration information indicative of a firmware applied by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version and wherein the system is one of a plurality of systems; associating, by the circuitry, an identifier with the manifest data, wherein the identifier identifies the system from among the plurality of systems; sending, by the circuitry, the manifest data and the associated identifier to an orchestrator server; detecting, by the circuitry, a change in at least one of hardware resources, firmware resources, or the configuration of the system; generating, by the circuitry, an update of the manifest data based on the detected change, wherein the update specifies the detected change in the at least one of the hardware resources, firmware resources, or the configuration of the system; and sending, by the circuitry, the update of the manifest data to the orchestrator server.
The method of claim 21, wherein sending the manifest data and the associated identifier comprises sending the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.
The method of claim 21, wherein a node comprises at least the system, wherein the node is composed based, in part, on the manifest data.
The method of claim 21, wherein generating the manifest data indicative of the one or more characteristics of the system comprises: determining hardware resources and firmware resources present in the system; determining a configuration of the system; and creating a hardware manifest based on the hardware resources present, a firmware manifest based on the firmware resources present, and a configuration manifest based on the determined configuration.

Description

In systems that distribute workloads among multiple compute devices (e.g., in a data center), a centralized server may compose nodes of compute devices to process the workloads. Each node represents a logical aggregation of resources (e.g., compute, storage, acceleration, and the like) provided by each compute device. Based on the resource requirements of the workload, the centralized server determines a composition of compute devices that satisfies such requirements. For instance, for compute-intensive workloads, the centralized server may include, in the node, a compute device that has a relatively large processor count, wherein each processor exceeds a given core frequency. Typically, prior to composing a node, the centralized server performs an asset discovery process on the compute devices in the system to determine resources provided by each compute device. During the asset discovery process, the centralized server queries a given compute device and receives information about the resources on that device. The centralized system may then evaluate the information to determine which compute devices satisfy resource requirements for a given workload.

Further, the centralized server composes nodes in a variety of situations after initial configuration of the system. For example, following an outage, the centralized server must bring nodes back online. However, doing so requires the centralized server to again conduct the asset discovery process to determine which resources are present in each compute device.

Citations (6)

US9250956B2
US20130125107A1
US9378461B1
US20160356639A1
US20170235613A1
US20170286087A1

Record as JSON

{
  "publication_number": "US11307787B2",
  "country": "US",
  "kind": "B2",
  "title": "Technologies for providing manifest-based asset representation",
  "abstract": "Technologies for generating manifest data for a sled include a sled to generate manifest data indicative of one or more characteristics of the sled (e.g., hardware resources, firmware resources, a configuration of the sled, or a health of sled components). The sled is also to associate an identifier with the manifest data. The identifier uniquely identifies the sled from other sleds. Additionally, the sled is to send the manifest data and the associated identifier to a server. The sled may also detect a change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also generate an update of the manifest data based on the detected change, where the update specifies the detected change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also send the update of the manifest data to the server.",
  "claims": [
    "1. An apparatus, comprising: a compute circuitry to: generate manifest data indicative of one or more characteristics of multiple devices coupled to a circuit board, wherein the manifest data comprises configuration information indicative of firmware configurations of individual devices of the multiple devices and wherein the configuration information indicative of firmware configurations of individual devices of the multiple devices is to indicate one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the apparatus from among a plurality of apparatuses; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more characteristics of at least one device among the multiple devices; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the at least one device; and send the update of the manifest data to the orchestrator server.",
    "2. The apparatus of claim 1, wherein to update the manifest data comprises to: determine which of the manifest data to update based on the change; and modify the manifest data based on the change.",
    "3. The apparatus of claim 1, wherein the change is at least one of an addition of a first resource or a removal of a second resource.",
    "4. The apparatus of claim 1, wherein the update sent to the orchestrator server comprises an indication of the change to the manifest data.",
    "5. The apparatus of claim 1, wherein the manifest data includes at least one hardware manifest, firmware manifest, configuration manifest, or health manifest.",
    "6. The apparatus of claim 5, wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices.",
    "7. The apparatus of claim 6, wherein the configuration manifest comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order.",
    "8. The apparatus of claim 6, wherein to generate the manifest data indicative of the one or more characteristics of multiple devices coupled to a circuit board comprises to: determine present hardware resources and firmware resources; determine a configuration of the multiple devices; determine a health of the hardware resources; and create the hardware manifest based on the present hardware resources, the firmware manifest based on the present firmware resources, the configuration manifest based on the determined configuration of the multiple devices, and the health manifest based on the health of the hardware resources.",
    "9. The apparatus of claim 6, wherein to associate the identifier with the manifest data comprises to: determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.",
    "10. The apparatus of claim 1, wherein to send the manifest data and the associated identifier comprises to send the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.",
    "11. The apparatus of claim 1, wherein a node comprises at least the apparatus, wherein the node is composed based, in part, on the manifest data and wherein the compute circuitry is further to generate the manifest data for a composed node.",
    "12. One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause one or more devices to: generate manifest data indicative of one or more characteristics of multiple devices of a system, wherein the manifest data comprises configuration information indicative of a firmware utilized by individual devices of the multiple devices and wherein the configuration information indicative of a firmware utilized by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the system from among a plurality of systems; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more of the characteristics of the system; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the system; and send the update of the manifest data to the orchestrator server.",
    "13. The one of more non-transitory machine-readable storage media of claim 12, wherein the update sent to the orchestrator server is an indication of the change to the manifest data.",
    "14. The one of more non-transitory machine-readable storage media of claim 12, wherein the manifest data includes at least one hardware manifest, a firmware manifest, configuration manifest, or health manifest.",
    "15. The one of more non-transitory machine-readable storage media of claim 14, wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices, wherein the firmware manifest specifies at least one of a BIOS version, baseboard management controller (BMC) version, DIMM firmware version, or solid state drive (SSD) version, and wherein the configuration manifest of the system comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order.",
    "16. The one of more non-transitory machine-readable storage media of claim 14, wherein to generate the manifest data indicative of the one or more characteristics of the system comprises to: determine hardware resources and firmware resources present in the system; determine a configuration of the system; and create the at least one hardware manifest based on the hardware resources present, the firmware manifest based on the firmware resources present, and the configuration manifest based on the determined configuration.",
    "17. The one of more non-transitory machine-readable storage media of claim 14, wherein to associate the identifier with the manifest data comprises to: determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.",
    "18. The one of more non-transitory machine-readable storage media of claim 12, wherein to send the manifest data and the associated identifier comprises to send the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.",
    "19. The one of more non-transitory machine-readable storage media of claim 18, wherein a node comprises at least the system, wherein the node is composed based, in part, on the manifest data.",
    "20. A system comprising: one or more processors; and a memory to store a plurality of instructions, which, when executed by the one or more processors, causes at least one circuitry to: generate manifest data indicative of one or more characteristics of multiple devices in the system, wherein the manifest data comprises configuration information indicative of a firmware applied by individual devices of the multiple devices and wherein the configuration information indicative of a firmware applied by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version; associate an identifier with the manifest data, wherein the identifier identifies the system from among a plurality of systems; send the manifest data and the associated identifier to an orchestrator server; detect a change in at least one or more of the characteristics of the system; update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the system; and send the update of the manifest data to the orchestrator server.",
    "21. A method comprising: generating, by circuitry, manifest data indicative of one or more characteristics of multiple devices coupled to a system, wherein the manifest data comprises configuration information indicative of a firmware applied by individual devices of the multiple devices and wherein the configuration information indicative of a firmware applied by individual devices of the multiple devices specifies one or more of: a BIOS version, baseboard management controller (BMC) firmware version, DIMM firmware version, and/or solid state drive (SSD) firmware version and wherein the system is one of a plurality of systems; associating, by the circuitry, an identifier with the manifest data, wherein the identifier identifies the system from among the plurality of systems; sending, by the circuitry, the manifest data and the associated identifier to an orchestrator server; detecting, by the circuitry, a change in at least one of hardware resources, firmware resources, or the configuration of the system; generating, by the circuitry, an update of the manifest data based on the detected change, wherein the update specifies the detected change in the at least one of the hardware resources, firmware resources, or the configuration of the system; and sending, by the circuitry, the update of the manifest data to the orchestrator server.",
    "22. The method of claim 21, wherein sending the manifest data and the associated identifier comprises sending the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data.",
    "23. The method of claim 21, wherein a node comprises at least the system, wherein the node is composed based, in part, on the manifest data.",
    "24. The method of claim 21, wherein generating the manifest data indicative of the one or more characteristics of the system comprises: determining hardware resources and firmware resources present in the system; determining a configuration of the system; and creating a hardware manifest based on the hardware resources present, a firmware manifest based on the firmware resources present, and a configuration manifest based on the determined configuration."
  ],
  "description_excerpt": "In systems that distribute workloads among multiple compute devices (e.g., in a data center), a centralized server may compose nodes of compute devices to process the workloads. Each node represents a logical aggregation of resources (e.g., compute, storage, acceleration, and the like) provided by each compute device. Based on the resource requirements of the workload, the centralized server determines a composition of compute devices that satisfies such requirements. For instance, for compute-intensive workloads, the centralized server may include, in the node, a compute device that has a relatively large processor count, wherein each processor exceeds a given core frequency. Typically, prior to composing a node, the centralized server performs an asset discovery process on the compute devices in the system to determine resources provided by each compute device. During the asset discovery process, the centralized server queries a given compute device and receives information about the resources on that device. The centralized system may then evaluate the information to determine which compute devices satisfy resource requirements for a given workload.\n\nFurther, the centralized server composes nodes in a variety of situations after initial configuration of the system. For example, following an outage, the centralized server must bring nodes back online. However, doing so requires the centralized server to again conduct the asset discovery process to determine which resources are present in each compute device.",
  "cpc": [
    "G06F 9/5005",
    "G06F 11/0709",
    "G06F 11/0751",
    "G06F 11/079",
    "G06F 11/1453",
    "G06F 11/3006",
    "G06F 11/3034",
    "G06F 11/3055",
    "G06F 11/3079",
    "G06F 11/3409",
    "G06F 12/023",
    "G06F 12/0284",
    "G06F 12/0692",
    "G06F 13/1652",
    "G06F 13/4022",
    "G06F 13/4027",
    "G06F 15/161",
    "G06F 15/80",
    "G06F 16/1744",
    "G06F 21/44",
    "G06F 21/57",
    "G06F 21/6218",
    "G06F 21/70",
    "G06F 21/73",
    "G06F 21/76",
    "G06F 2212/401",
    "G06F 2212/402",
    "G06F 2221/2107",
    "G06F 3/0604",
    "G06F 3/0608",
    "G06F 3/0611",
    "G06F 3/0613",
    "G06F 3/0617",
    "G06F 3/0641",
    "G06F 3/0647",
    "G06F 3/065",
    "G06F 3/0653",
    "G06F 3/067",
    "G06F 7/06",
    "G06F 8/65",
    "G06F 8/654",
    "G06F 8/656",
    "G06F 8/658",
    "G06F 9/3851",
    "G06F 9/3891",
    "G06F 9/4401",
    "G06F 9/45533",
    "G06F 9/4843",
    "G06F 9/4881",
    "G06F 9/5038",
    "G06F 9/5044",
    "G06F 9/505",
    "G06F 9/5083",
    "G06F 9/544",
    "G06T 1/20",
    "G06T 1/60",
    "G06T 9/005",
    "H01R 13/453",
    "H01R 13/4536",
    "H01R 13/4538",
    "H01R 13/631",
    "H03K 19/1731",
    "H03M 7/3084",
    "H03M 7/40",
    "H03M 7/42",
    "H03M 7/60",
    "H03M 7/6011",
    "H03M 7/6017",
    "H03M 7/6029",
    "H04L 12/2881",
    "H04L 12/4633",
    "H04L 41/044",
    "H04L 41/046",
    "H04L 41/0816",
    "H04L 41/0853",
    "H04L 41/0895",
    "H04L 41/0896",
    "H04L 41/12",
    "H04L 41/142",
    "H04L 41/40",
    "H04L 43/04",
    "H04L 43/06",
    "H04L 43/08",
    "H04L 43/0894",
    "H04L 47/20",
    "H04L 47/2441",
    "H04L 47/78",
    "H04L 47/83",
    "H04L 49/104",
    "H04L 61/2007",
    "H04L 63/1425",
    "H04L 67/10",
    "H04L 67/1014",
    "H04L 67/327",
    "H04L 67/36",
    "H04L 9/0822",
    "H05K 7/1452",
    "H05K 7/1487",
    "H05K 7/1492"
  ],
  "ipc": [
    "G06F 11/30",
    "G06F 3/06",
    "H04L 47/20",
    "G06F 11/07",
    "G06F 11/34",
    "G06F 12/02",
    "G06F 12/06",
    "G06F 13/16",
    "G06F 15/173",
    "G06F 16/174",
    "G06F 21/57",
    "G06F 21/62",
    "G06F 21/73",
    "G06F 21/76",
    "G06F 7/06",
    "G06F 8/65",
    "G06F 8/654",
    "G06F 8/656",
    "G06F 8/658",
    "G06F 9/38",
    "G06F 9/4401",
    "G06F 9/455",
    "G06F 9/48",
    "G06F 9/50",
    "G06F 9/54",
    "G06T 1/20",
    "G06T 1/60",
    "G06T 9/00",
    "H01R 13/453",
    "H01R 13/631",
    "H03K 19/173",
    "H03M 7/30",
    "H03M 7/40",
    "H03M 7/42",
    "H04L 12/28",
    "H04L 12/46",
    "H04L 41/044",
    "H04L 41/0816",
    "H04L 41/0853",
    "H04L 41/12",
    "H04L 43/04",
    "H04L 43/06",
    "H04L 43/08",
    "H04L 43/0894",
    "H04L 47/2441",
    "H04L 49/104",
    "H04L 61/5007",
    "H04L 67/10",
    "H04L 67/1014",
    "H04L 67/63",
    "H04L 67/75",
    "H04L 9/08",
    "H05K 7/14"
  ],
  "assignees": [
    "Intel Corp"
  ],
  "inventors": [
    "Murugasamy K. Nachimuthu",
    "Mohan J. Kumar",
    "Alberto J. Munoz"
  ],
  "filing_date": "2017-11-29",
  "publication_date": "2022-04-19",
  "grant_date": "2022-04-19",
  "priority_date": "2016-11-29",
  "application_number": "US-201715826051-A",
  "family_id": "62190163",
  "cited_by_count": 2,
  "citations": [
    "US9250956B2",
    "US20130125107A1",
    "US9378461B1",
    "US20160356639A1",
    "US20170235613A1",
    "US20170286087A1"
  ]
}

Record 1,192 of 8,000 in Patents full text (MLC-0201). Request the full dataset.