Skip to content

Commit 0d3c562

Browse files
author
James Green
committed
Tweaks to wording and formatting
1 parent d9133cc commit 0d3c562

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/private-5g-core/private-5g-core-overview.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -150,15 +150,16 @@ In the context of private mobile networks, a single RAN can connect to both a pr
150150

151151
### Maximum Transmission Unit (MTU)
152152

153-
The Maximum Transmission Unit (MTU) is a property of an IP link, and it is configured on the interfaces at each end of the link. Packets that exceed an interface's configured MTU are split into smaller packets via IPv4 fragmentation prior to sending and are then reassembled at their destination. If an interface's configured MTU is higher than the link's supported MTU, then the packet will fail to be transmitted correctly.
153+
The Maximum Transmission Unit (MTU) is a property of an IP link, and it is configured on the interfaces at each end of the link. Packets that exceed an interface's configured MTU are split into smaller packets via IPv4 fragmentation prior to sending and are then reassembled at their destination. However, if an interface's configured MTU is higher than the link's supported MTU, the packet will fail to be transmitted correctly.
154154

155155
To avoid transmission issues caused by IPv4 fragmentation, a 4G or 5G packet core instructs UEs what MTU they should use. However, UEs do not always respect the MTU signalled by the packet core.
156156

157-
IP packets from the UE are tunnelled through from the RAN, which adds overhead from encapsulation. As a result of this the MTU value for the UE should be smaller than the MTU value used between the RAN and the Packet Core to avoid transmission issues. RANs typically come pre-configured with an MTU of 1500. The Packet Core’s default UE MTU is 1300 bytes to allow for encapsulation overhead.
157+
IP packets from UEs are tunnelled through from the RAN, which adds overhead from encapsulation. Due to this, the MTU value for the UE should be smaller than the MTU value used between the RAN and the Packet Core to avoid transmission issues.
158158

159-
This default value maximizes RAN interoperability but risks that certain UEs will not observe the default MTU and will generate larger packets that require IPv4 fragmentation and might be dropped by the network.
159+
RANs typically come pre-configured with an MTU of 1500. The Packet Core’s default UE MTU is 1300 bytes to allow for encapsulation overhead. These values maximize RAN interoperability, but risk that certain UEs will not observe the default MTU due to generating larger packets that require IPv4 fragmentation that may be dropped by the network.
160+
161+
If you are affected by this issue, it is strongly recommended to configure the RAN to use an MTU of 1560 or higher which allows a sufficient overhead for the encapsulation and avoid fragmentation with a UE using a standard MTU of 1500.
160162

161-
If you are affected by this issue, it is strongly recommended to configure the RAN to use an MTU of 1560 or higher which allows for sufficient overhead for the encapsulation to avoid fragmentation when the UE uses a standard MTU of 1500.
162163
## Flexible integration with Azure private multi-access edge compute (MEC) partners
163164

164165
Each packet core instance is standards-compliant and compatible with several radio access network (RAN) partners in the Azure private MEC ecosystem.

0 commit comments

Comments
 (0)