# US 2026/0089220 A1 · Native edge management protocol for edge devices on layer 2 communication

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

- Number: US 2026/0089220 A1
- Document ID: US20260089220A1
- Status: Published application
- Kind: A1
- Application number: 18/897,116
- Filed: 2024-09-26
- Published: 2026-03-26
- Earliest claimed: 2024-09-26
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Veerabhadra Swamy Dummi Kubendrappa; Ajith George
- Web page: https://patentgrep.com/patent/US20260089220A1

## CPC

- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/145: avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
- H04L 67/147: Signalling methods or messages providing extensions to protocols defined by standardisation
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system for session management between a client device and an edge device includes issuing, by the client device and via a native edge management protocol (NEMP) protocol data unit (PDU), a session create request to an edge device, the NEMP PDU being a portion of a L2 data packet, and the session create request including a session identifier, obtaining, via the NEMP, a session create response from the edge device. The session create response includes the session identifier, a state of the edge device, and software information. The method further includes executing a session, via the NEMP, using the session identifier, the state of the edge device, and the software information, and performing, after the executing and via the NEMP, a session end.

## Claims

### Claim 1

A method for session management, the method comprising:
issuing, by a client device and via a native edge management protocol (NEMP) protocol data unit (PDU), a session create request to an edge device,
wherein the NEMP PDU is a portion of a L2 data packet, and
wherein the session create request comprises a session identifier;
obtaining, via the NEMP, a session create response from the edge device,
wherein the session create response comprises the session identifier, a state of the edge device, and software information;
executing a session, via the NEMP, using the session identifier, the state of the edge device, and the software information; and
performing, after the executing and via the NEMP, a session end.

### Claim 2 (depends on 1)

The method of claim 1, wherein the NEMP PDU comprises: a version of the NEMP, a time to live (TTL) type, a TTL value, a check sum, the session identifier, a sequence number, and a message, wherein the message is in a type, length, and value (TLV) format.

### Claim 3 (depends on 1)

The method of claim 1, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates troubleshooting the edge device; and
obtaining, from the edge device and via the NEMP, a session management response, wherein the session management response comprises a device identifier, the session identifier, and a message associated with the troubleshooting.

### Claim 4 (depends on 1)

The method of claim 1, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates a high volume of data transmission from the edge device to the client device; and
obtaining, from the edge device and via the NEMP, a plurality of session management responses, wherein each of the plurality of session management responses comprises a device identifier, the session identifier, and a message associated with the high volume of data transmission.

### Claim 5 (depends on 1)

The method of claim 1, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a heartbeat request, wherein the heartbeat request indicates a heartbeat monitoring, and wherein the heartbeat request comprises the session identifier; and
obtaining, from the edge device and via the NEMP, a heartbeat response, wherein the heartbeat response comprises the session identifier and a second state of the edge device, wherein the second state of the edge device is based on a second point in time after a first point in time of the state of the edge device.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
prior to issuing the session create request, performing device discovery of the edge device via the NEMP,
wherein the edge device is unprovisioned prior to performing the device discovery, and
wherein the session create request specifies obtaining a device identifier and operating system details from the edge device;
obtaining, via the NEMP, the device identifier and operating system details from the edge device;
performing, via the NEMP, an authentication mechanism with the edge device using the device identifier and the operating system details; and
based on the authentication mechanism, enabling session creation with the edge device by the client device.

### Claim 7 (depends on 1)

The method of claim 1, wherein the session end is initiated by the client device.

### Claim 8 (depends on 1)

The method of claim 1, wherein the session end is initiated by the edge device.

### Claim 9

A system, comprising:
an edge device; and
a client device comprising a processor and memory comprising instructions, which when executed by the processor, cause the processor to perform a method, the method comprising:
issuing, via a native edge management protocol (NEMP) protocol data unit (PDU), a session create request to an edge device,
wherein the session create request is transmitted using layer 2 (L2) communication,
wherein the NEMP PDU is a portion of a L2 data packet, and
wherein the session create request comprises a session identifier;
obtaining, via the NEMP, a session create response from the edge device,
wherein the session create response comprises the session identifier, a state of the edge device, and software information;
executing a session, via the NEMP, using the session identifier, the state of the edge device, and the software information; and
performing, after the executing and via the NEMP, a session end.

### Claim 10 (depends on 9)

The system of claim 9, wherein the NEMP PDU comprises: a version of the NEMP, a time to live (TTL) type, a TTL value, a check sum, the session identifier, a sequence number, and a message, wherein the message is in a type, length, and value (TLV) format.

### Claim 11 (depends on 9)

The system of claim 9, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates troubleshooting the edge device; and
obtaining, from the edge device and via the NEMP, a session management response, wherein the session management response comprises a device identifier, the session identifier, and a message associated with the troubleshooting.

### Claim 12 (depends on 9)

The system of claim 9, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates a high volume of data transmission from the edge device to the client device; and
obtaining, from the edge device and via the NEMP, a plurality of session management responses, wherein each of the plurality of session management responses comprises a device identifier, the session identifier, and a message associated with the high volume of data transmission.

### Claim 13 (depends on 9)

The system of claim 9, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a heartbeat request, wherein the heartbeat request indicates a heartbeat monitoring, wherein the heartbeat request comprises the session identifier; and
obtaining, from the edge device and via the NEMP, a heartbeat response, wherein the heartbeat response comprises the session identifier and a second state of the edge device, wherein the second state of the edge device is based on a second point in time after a first point in time of the state of the edge device.

### Claim 14 (depends on 9)

The system of claim 9, further comprising:
prior to issuing the session create request, performing device discovery on the edge device via the NEMP,
wherein the edge device is unprovisioned prior to performing the device discovery, and
wherein the session create request specifies obtaining a device identifier, and operating system details from the edge device, and
wherein performing the device discovery comprises obtaining, via the NEMP, the device identifier and operating system details from the edge device;
performing, via the NEMP, an authentication mechanism with the edge device using the device identifier and the operating system details; and
based on the authentication mechanism, enabling session creation with the edge device by the client device.

### Claim 15 (depends on 14)

The system of claim 14, further comprising:
a plurality of edge devices comprising at least the edge device; and
a network device providing operative connection between the client device and each of the plurality of edge devices,
wherein the device discovery and authentication mechanism are performed on each of the plurality of edge devices via the NEMP.

### Claim 16

A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing data access, the method comprising:
issuing, by a client device and via a native edge management protocol (NEMP) protocol data unit (PDU), a session create request to an edge device,
wherein the NEMP PDU comprises: a version of the NEMP, a time to live (TTL) type, a TTL value, a check sum, a session identifier, a sequence number, and a message,
wherein the message is in a type, length, and value (TLV) format,
wherein the NEMP PDU is a portion of a L2 data packet, and
wherein the session create request comprises the session identifier;
obtaining, via the NEMP, a session create response from the edge device,
wherein the session create response comprises the session identifier, a state of the edge device, and software information;
executing a session, via the NEMP, using the session identifier, the state of the edge device, and the software information; and
performing, after the executing and via the NEMP, a session end.

### Claim 17 (depends on 16)

The non-transitory computer readable medium of claim 16, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates troubleshooting the edge device; and
obtaining, from the edge device and via the NEMP, a session management response, wherein the session management response comprises a device identifier, the session identifier, and a message associated with the troubleshooting.

### Claim 18 (depends on 16)

The non-transitory computer readable medium of claim 16, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a session management request, wherein the session management request indicates a high volume of data transmission from the edge device to the client device; and
obtaining, from the edge device and via the NEMP, a plurality of session management responses, wherein each of the plurality of session management responses comprises a device identifier, the session identifier, and a message associated with the high volume of data transmission.

### Claim 19 (depends on 16)

The non-transitory computer readable medium of claim 16, wherein executing the session comprises:
issuing, by the client device and via the NEMP, a heartbeat request, wherein the heartbeat request indicates a heartbeat monitoring, wherein the heartbeat request comprises the session identifier; and
obtaining, from the edge device and via the NEMP, a heartbeat response, wherein the heartbeat response comprises the session identifier and a second state of the edge device, wherein the second state of the edge device is based on a second point in time after a first point in time of the state of the edge device.

### Claim 20 (depends on 16)

The non-transitory computer readable medium of claim 16, further comprising:
prior to issuing the session create request, performing device discovery of the edge device via the NEMP,
wherein the edge device is unprovisioned prior to performing the device discovery, and
wherein the session create request specifies obtaining a device identifier, and operating system details from the edge device;
obtaining, via the NEMP, the device identifier and operating system details from the edge device;
performing, via the NEMP, an authentication mechanism with the edge device using the device identifier and the operating system details; and
based on the authentication mechanism, enable session creation with the edge device by the client device.
