# US 2023/0057487 A1 · Data packet format to communicate across different networks

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

- Number: US 2023/0057487 A1
- Document ID: US20230057487A1
- Status: Published application
- Kind: A1
- Application number: 17/970,944
- Filed: 2022-10-21
- Published: 2023-02-23
- Earliest claimed: 2020-05-06
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Renwei Li; Kiran Makhijani; Lijun Dong
- Web page: https://patentgrep.com/patent/US20230057487A1

## CPC

- H04L 45/566: {Routing instructions carried by the data packet, e.g. active networks}
- H04L 45/741: Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
- H04W 40/24: Connectivity information management, e.g. connectivity discovery or connectivity update
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present technology discloses data communication in a network. A node in the network receives an internet protocol (IP) data packet. The IP data packet has a header and a payload. The node performs actions on the IP data packet based on specifications in the header of the IP data packet. The node then forwards the IP data packet based on the specifications in the header of the IP data packet to a next hop node in the network.

## Claims

### Claim 1

A method for data communication in a network, comprising:
receiving, by a node in the network, an internet protocol (IP) data packet, the IP data packet having a header and a payload;
performing, by the node, an action on the IP data packet based on specifications in the header of the IP data packet; and
forwarding, by the node, the IP data packet based on the specifications in the header of the IP data packet to a next hop node in the network.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data packet has a format including a header field and the specifications, and
the specifications include a shipping specification field, a contract specification field and a payload specification field.

### Claim 3 (depends on 2)

The method of claim 2, wherein each of the shipping specification field, the contract specification field and the payload specification field are independently variable in length.

### Claim 4 (depends on 2)

The method of claim 2, wherein the header field specifies an offset of the shipping specification field, an offset of the contract specification field, an offset of the payload specification field, and a length of the payload.

### Claim 5 (depends on 2)

The method of claim 2, wherein the shipping specification field specifies one or more address format types, a source address (SA) field and a destination address (DA) field, wherein the SA and DA fields specify at least one of a length of the address, a type of communication and the SA and DA.

### Claim 6 (depends on 5)

The method of claim 5, wherein the length of the address of the SA and DA is variable.

### Claim 7 (depends on 2)

The method of claim 2, wherein
each contract specification field includes one or more contract clauses, and
each contract clause includes at least one of an event and a condition, and an action.

### Claim 8 (depends on 7)

The method of claim 7, further comprising executing the action in the contract upon occurrence of the event specified in the contract clause and when the condition specified in the contract clause is satisfied.

### Claim 9 (depends on 8)

The method of claim 8, wherein
the contract clause includes the event, the condition and the action;
the event indicates the occurrence or state of a node in the network that impacts behavior of the network;
the condition indicates one or more logical operators to perform a conditional check upon occurrence of the event; and
the action indicates a delivery time of the IP data packet communicated between a source and a destination.

### Claim 10 (depends on 9)

The method of claim 9, wherein the payload specification field specifies a differentiated value or property corresponding to portions of the payload.

### Claim 11 (depends on 10)

The method of claim 10, wherein the action corresponds to an operation performed on the payload based on the differentiated value or property in the payload specification.

### Claim 12 (depends on 11)

The method of claim 11, wherein the property specifies a relationship between different portions of the payload.

### Claim 13 (depends on 12)

The method of claim 12, further comprising performing the action on portions of the payload according to the condition and the action and the property corresponding to portions of the payload in the contract clause.

### Claim 14 (depends on 10)

The method of claim 10, wherein
the property specifies the differentiated value corresponding to the portions of the payload, and
the property includes a flag that indicates that the action has been performed on one or more of the portions of the payload.

### Claim 15

A node for communicating data in a network, comprising:
a non-transitory memory storage comprising instructions; and
one or more processors in communication with the memory, wherein the one or more processors cause the node to execute the instructions to:
receive an internet protocol (IP) data packet, the IP data packet having a header and a payload;
perform an action on the IP data packet based on specifications in the header of the IP data packet; and
forward the IP data packet based on the specifications in the header of the IP data packet to a next hop node in the network.

### Claim 16 (depends on 15)

The node of claim 15, wherein the data packet has a format including a header field and the specifications, and
the specifications include a shipping specification field, a contract specification field and a payload specification field.

### Claim 17 (depends on 16)

The node of claim 16, wherein the header field specifies an offset of the shipping specification field, an offset of the contract specification field, an offset of the payload specification field, and a length of the payload.

### Claim 18 (depends on 16)

The node of claim 16, wherein the shipping specification field specifies one or more address format types, a source address (SA) field and a destination address (DA) field, wherein the SA and DA fields specify at least one of a length of the address, a type of communication and the SA and DA.

### Claim 19 (depends on 18)

The node of claim 18, wherein
each contract specification field includes one or more contract clauses, and
each contract clause includes at least one of an event and a condition, and an action.

### Claim 20

A non-transitory computer-readable medium storing computer instructions for data communications in a network, that when executed by one or more processors, cause the one or more processors to perform the steps of:
receiving, by a node in the network, an internet protocol (IP) data packet, the IP data packet having a header and a payload;
performing, by the node, an action on the IP data packet based on specifications in the header of the IP data packet; and
forwarding, by the node, the IP data packet based on the specifications in the header of the IP data packet to a next hop node in the network.
