Definition
EPS (Evolved Packet System) bearers are the packet data channels established between the LTE core network and the radio access network for user devices. They are divided into default bearers and dedicated bearers. When IoT SIM cards attach for the first time and successfully establish a packet data network connection, they typically first receive a default bearer associated with the default APN, responsible for general Internet or private network access. When the service requires priority differentiation, bandwidth assurance, or billing isolation, the network side can initiate the establishment of a dedicated bearer bound to different QoS parameters. In 4G, the QoS identifier commonly used is QCI (QoS Class Identifier), while in 5G it corresponds to 5QI (5G QoS Identifier), and together with parameters such as ARP (Allocation and Retention Priority) and GBR/MBR, describes the expected service.
For IoT SIM card user data, bearers are "invisible" channels, but their QCI/5QI directly affects the base station scheduling order, whether the minimum rate is guaranteed, and whether dropping is allowed during congestion. If video backhaul, vehicle telemetry, industrial control messages, and small metering packets share the same default bearer, they may mutually affect each other during congestion periods. Therefore, industry private networks often achieve a sliced experience through dedicated bearers and policy charging control (PCC) rules.
NB-IoT and other standards have limited support for dedicated bearers, and QoS representation is more in terms of core network rate limiting, APN-AMBR, and wireless resource priority. The feasible set of parameters needs to be confirmed with operators during the planning stage.
Technical key points
Default bearers are always associated with the terminal, while dedicated bearers can be dynamically established and released. The creation of dedicated bearers depends on the policies issued by the PCRF/PCF and the response from the P-GW/SMF; if IoT SIM cards are not authorized for a certain QCI, the network will either reject or downgrade it to the default level. ARP is used to determine preemption relationships when resources are scarce. High-priority IoT services (such as emergency broadcast terminals) may be assigned higher ARP, but abuse can result in ordinary devices being preempted, so caution is needed.
QCI defines the latency and packet loss targets for typical services; for example, certain classes are suitable for voice, while others are suitable for background traffic. IoT platforms should map their own business SLA to an allowed subset of QCI/5QI rather than directly using the default policies of consumer broadband data plans. In multi-APN scenarios, different APNs can be bound to different default QCI to achieve separation of the 'management plane and business plane.'
From 4G interoperation to 5G, QoS Flow replaces part of the EPS bearer semantics. If an IoT module is dual-registered, it needs to understand the merging behavior of sessions and QoS rules to avoid sudden RTT jitter observed by the application layer.
IoT SIM cards and platform configuration
The SIM card template should specify the target QCI/5QI, whether GBR is allowed, and uplink/downlink APN-AMBR. The connection management platform can display the currently active bearer list (if the operator interface is open) to verify deviations where 'card subscription ≠ live network effect.' For customers using VPDN, private network firewall policies should align with wireless QoS objectives to prevent bottlenecks in the private network from negating high QCI.
Platform applications should maintain compatibility with different bearer MTUs, IPv6 prefix changes, and DSCP markings; some operators implement more aggressive buffer management for low-priority bearers, so application timeout thresholds need to be handled differently. After an eUICC switches to another operator's Profile, the QoS template may change overall, requiring business pressure testing again.
When upgrading firmware on devices in bulk, avoid streaming simultaneously to high-priority bearer devices and non-critical devices during congestion periods. Group scheduling and window period control can reduce mutual impact.
Operation and Troubleshooting
The phenomenon of "some device SIMs in the same area are frozen while others are normal" may be related to failures in establishing dedicated bearers, causing a fallback to default low priority. Capturing SMF/PGW logs (with operator cooperation) can reveal error codes for policy issuance. If there have been recent changes to the card data plan or enterprise contracts, the PCC rules should be checked for synchronization first.
Latency complaints need to distinguish among air interface, bearer, and internet gateway segments. A hotspot comparison using the same type of SIM card phone can quickly determine if it's caused by IoT-specific policies. For sporadic disconnections, check whether GBR resource shortage triggered bearer release.
It is recommended to perform QoS end-to-end testing on key SIM numbers before major event support and retain baseline reports for accountability afterward.
Compliance and Security
High-priority bearers may involve network resource fairness policies; the purpose should be stated in the contract to avoid being regarded as improper use of wireless resources. QoS configuration changes involving critical services should be included in change management and double review. If QCI and service type are recorded in logs, attention should be paid to commercial confidentiality and the classification and storage of customer data.
During cross-border roaming, QoS may be downgraded due to the visited network's policy, and SLA commitments should specify a "roaming exception clause."
Use Cases
Scenarios sensitive to latency and jitter, such as connected vehicle video monitoring, remote surgical assistance devices, power differential protection communication, and financial transaction terminals, are often supported through dedicated bearers and clear QCI/5QI guarantees. Massive metering is more suitable for low-priority, aggregated scheduling strategies to save wireless and core network costs. In mixed scenarios, multiple applications coexisting on the same terminal can achieve traffic splitting through OS or module multi-PDN connections.
SimtoLink assists customers in aligning QoS objectives in three areas: IoT SIM card subscription, policy orchestration, and platform monitoring, turning EPS/5GS bearer capability into verifiable business metrics.