# US 10,374,947 B2 · Method and apparatus for encapsulating / decapsulating data packets at a radio access node

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

- Number: US 10,374,947 B2
- Document ID: US10374947B2
- Status: Granted
- Kind: B2
- Application number: 15/715,454
- Filed: 2017-09-26
- Published: 2018-04-05
- Granted: 2019-08-06
- Earliest claimed: 2016-09-30
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Aaron James Callard
- Inventors: Aaron James Callard
- Web page: https://patentgrep.com/patent/US10374947B2

## CPC

- H04L 45/38: {Flow based routing}
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 45/42: Centralised routing
- H04L 2212/00: Encapsulation of packets
- H04W 88/08: Access point devices
- 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

A method and apparatus for handling a packet. The packet handling may include receiving the packet, associating the packet with configuration information, and performing packet handling operations on the packet according to packet handling instructions defined by the configuration information. A method and apparatus for encapsulating packets, decapsulating packets, or both, at a radio access node. The encapsulation and/or decapsulation operations are performed based on updateable configuration information specifying the operations to be performed without having to process the packet using the protocol with which it has been encoded.

## Claims

### Claim 1

A method for handling a packet by a radio access (RA) node, the method comprising the RA node:
receiving the packet as a bitstream of data;
associating the packet with configuration information based on data outside the bitstream; and,
performing packet handling operations on the packet, without the RA node using the protocol with which the packet has been encoded, according to packet handling instructions defined by the configuration information, wherein the packet handling instructions specify a packet handling operation to be performed on a portion of the bitstream, and specify an offset indicative of an offset bit located a count of bits from a predetermined starting bit position within the packet; and a length indicative of the bitstream as a count of bits from the offset bit.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the data outside the bitstream of the packet comprises a radio bearer associated with the packet.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the packet handling instructions comprise fixed rules, and wherein the packet handling operations apply the fixed rules to the bitstream.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the fixed rules indicate data in the bitstream and indicate the packet handling operations to be performed on that data.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising the RA node receiving the configuration information from a controller node.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising the RA node transmitting the packet as directed or modified by the packet handling instructions.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the packet handling operations comprise one or more encapsulation operations.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the packet comprises an uplink packet, and wherein the packet handling operations include the RA node appending or prepending an encapsulation header onto the uplink packet.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the one or more packet handling operations comprise one or more decapsulation operations.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the packet comprises a downlink packet intended for a user equipment (UE), and wherein the packet handling operations further comprise the RA node:
retrieving a payload from the packet; and,
transmitting at least payload contents based on the payload to the UE.

### Claim 11 (depends on 1)

The method according to claim 1, wherein the packet comprises a downlink packet, and wherein the packet handling operations performed by the RA node comprise:
reading a radio bearer identifier (RB-ID) located an offset number of bits within the downlink packet, the offset specified by the configuration information;
mapping the downlink packet to a radio bearer based at least in part on the RB-ID;
reading a payload from the downlink packet; and
transmitting the payload toward the radio bearer.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the predetermined starting bit position comprises a starting bit of the packet.

### Claim 13 (depends on 1)

The method according to claim 1, wherein performing the packet handling operations comprises performing one or more actions of a standardized set of actions on the packet.

### Claim 14 (depends on 1)

The method according to claim 1, wherein the portion of the bitstream on which the packet handling operation is to be performed is configurable by the RA node:
receiving updated configuration information, the updated configuration information specifying an updated portion of the bitstream; and,
replacing the configuration information with the updated configuration information.

### Claim 15

A network function comprising:
a network interface for receiving data from and transmitting data to network functions connected to a network;
a processor; and
a non-transient memory for storing instructions that when executed by the processor cause the network function to be configured to:
receive a packet as a bitstream of data;
associate the packet with configuration information based on data outside the bitstream of the packet; and,
perform packet handling operations on the packet, without the network function having to process the packet using the protocol with which the packet has been encoded, according to packet handling instructions defined by the updated configuration information, wherein the packet handling instructions specify a packet handling operation to be performed on a portion of the bitstream, and specify an offset indicative of an offset bit located a count of bits from a predetermined starting bit position within the packet; and a length indicative of the bitstream as a count of bits from the offset bit.

### Claim 16 (depends on 15)

The network function according to claim 15, wherein the data outside the bitstream of the packet comprises a radio bearer associated with the packet.

### Claim 17 (depends on 15)

The network function according to claim 15, wherein the packet handling instructions comprise fixed rules, and wherein the packet handling operations apply fixed rules to the bitstream.

### Claim 18 (depends on 17)

The network function according to claim 17, wherein the fixed rules indicate data in the bitstream and indicate the packet handling operations to be performed on that data.

### Claim 19 (depends on 15)

The network function according to claim 15, further operative to receive the configuration information from a controller node.

### Claim 20 (depends on 15)

The network function according to claim 15, further operative to transmit the packet as directed or modified by the packet handling instructions.

### Claim 21 (depends on 15)

The network function according to claim 15, wherein the packet handling operations comprise one or more encapsulation operations.

### Claim 22 (depends on 15)

The network function according to claim 15, wherein the packet comprises an uplink packet, and wherein the network function is further operative to append or prepend an encapsulation header onto the uplink packet.

### Claim 23 (depends on 15)

The network function according to claim 15, wherein the one or more packet handling operations comprise one or more decapsulation operations.

### Claim 24 (depends on 15)

The network function according to claim 15, wherein the packet comprises a downlink packet intended for a user equipment (UE), and wherein the network function is further operative to:
retrieve a payload from the packet; and,
transmit at least payload contents based on the payload to the UE.

### Claim 25 (depends on 15)

The network function according to claim 15, wherein the packet comprises a downlink packet, and wherein the packet handling operations performed by the network function further include the network function being operative to:
read a radio bearer identifier (RB-ID) located an offset number of bits within the downlink packet, the offset specified by the configuration information;
map the downlink packet to a radio bearer based at least in part on the RB-ID;
read a payload from the downlink packet; and
transmit the payload toward the radio bearer.

### Claim 26 (depends on 15)

The network function according to claim 15, wherein the predetermined starting bit position comprises a starting bit of the packet.

### Claim 27 (depends on 15)

The network function according to claim 15, wherein performing the packet handling operations comprises performing one or more actions of a standardized set of actions on the packet.

### Claim 28 (depends on 15)

The network function according to claim 15, wherein the portion of the bitstream on which the packet handling operation is to be performed is configurable by the network function being further operative to:
receive updated configuration information, the updated configuration information specifying an updated portion of the bitstream; and,
replace the configuration information with the updated configuration information.
