TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register

SIMCom SIM8200G 5G Sub-6 LGA

Article Number: 11167
Brand: SIMCom
Supplier number: S2-1096P

The SIM8200G is Multi‐Band 5G NR/LTE‐FDD/LTE‐TDD/HSPA+ module solution in a LGA type which supports R15 5g NSA/SA up to 4.0 Gbps data transfer.

It has strong extension capability with rich interfaces including UART,PCIe,USB3.1, GPIO etc. The module provides much flexibility and ease of integration for customer's application.

The package of SIM8200G is LGA form factor. This also minimize the investments of customers, and enables a short time‐to‐market.

It is designed for applications that need high throughput data communication in a variety of radio propagation conditions. Due to the unique combination of performance, security and flexibility, this module is ideally suited for many applications.

Dimensions: 41 mm x 43.6 mm x 2.8 mm
Weight: 11.17g

End-of-life

This product has reached
end-of-life and can not be
ordered any more.

Quantity Price

No prices available

For more information
please contact us at
sales-americas@techship.com

For larger quantities and complete pricing, please sign in or register

Subscribe to stay up to date with the latest about this product.

Subscribe to updates
UMTS Bands
B1 (2100)
B2 (1900)
B8 (900)
B4 (AWS)
B3 (1800)
B5 (850)
LTE Bands
B1 (FDD 2100)
B2 (FDD 1900)
B3 (FDD 1800)
B4 (FDD 1700 / AWS)
B7 (FDD 2600)
B8 (FDD 900)
B12 (FDD 700ac)
B13 (FDD 700c)
B14 (FDD 700PS)
B17 (FDD 700bc)
B18 (FDD 800lower)
B19 (FDD 800 upper)
B20 (FDD 800DD)
B5 (FDD 850)
B25 (FDD 1900)
B42 (TDD 3500)
B38 (TDD 2600)
B40 (TDD 2300)
B43 (TDD 3600)
B26 (FDD 850 Ext)
B28 (FDD 700 APAC)
B29 (US 700de Lower)
B34 (TDD 2000)
B39 (TDD 1900)
B41 (TDD 2500)
B30 (FDD 2300 WCS)
B66 (FDD 1700 / AWS-3)
B32 (SDL 1500)
B48 (TDD 3600)
B71 (FDD 600)
5G Sub6 Bands
n1 (2100)
n2 (1900)
n3 (1800)
n5 (850)
n7 (2600)
n12 (700)
n20 (800)
n28 (700)
n41 (TDD 2500)
n66 (AWS-3)
n71 (600)
n77 (TDD 3700)
n78 (TDD 3500)
n79 (TDD 4500)
n8 (900)
n38 (2600)
n40 (2300)
n66 (1700)
n48 (3600)
Form Factor
LGA
Technology
5G
GNSS
Yes
GNSS technology
GPS
GLONASS
BeiDou
Galileo
Max DL Speed
2400 Mbps
Max UL Speed
1000 Mbps
Chipset
Qualcomm
SDX55
Operating Temperature Range
-30 °C – 70 °C
Driver Support
Windows 7
Linux
Android
Windows 8
Windows 10
Data Interface
USB 2.0
GPIO
I2C
ADC
PCM
SDIO 3.0
SPI
USB 3.1
Certification
FCC
CE
CCC
RoHS
SRRC
CTA
REACH

SIMCom SIM8200G 5G Sub-6 LGA Datasheet

Download

Uploaded at
2020-12-08 17:00:37
Last updated
2021-04-07 16:26:32
Version
20210402
Related products
SIMCom SIM8200G 5G Sub-6 LGA

This guide describes the SIM8200 Series cellular modules AT control commands available and supported

Download

Uploaded at
2020-12-16 08:51:29
Last updated
2021-02-26 17:22:11
Version
V1.01
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8202G-M.2 5G
SIMCom SIM8202E-M.2 5G

The SIM8200 Series Linux USB User Guide.

Download

Uploaded at
2021-07-09 14:02:55
Last updated
2021-07-09 14:02:55
Version
1.00
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8202E-M.2 5G
SIMCom SIM8202G-M.2 5G

This application notes archive contains the following application notes:
FOTA v1.00
FTP(S) v1.00
HTTP(S) v1.00
Linux USB User Guide v1.00
MQTT(S) 1.00
Open Linux Sleep&Wakeup v1.00
SSL v1.00
TCPIP v1.00
TTS v1.00

Download

Uploaded at
2021-07-09 14:01:05
Last updated
2021-07-12 10:40:13
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8202E-M.2 5G
SIMCom SIM8202G-M.2 5G

This document describes the SIM8200G 5G module antenna port mapping and Antenna design guide to
customer to refer.

Download

Uploaded at
2021-01-29 11:36:28
Last updated
2021-01-29 11:36:28
Version
V1.02
Related products
SIMCom SIM8200G 5G Sub-6 LGA

This document describes SIM8200G hardware interface in great detail.

This document can help users understand both the interface specifications and the electrical and mechanical details of SIM8200G quickly. With the help of this document and other SIM8200G application notes or user guide, users can use SIM8200G to design various applications quickly.

Download

Uploaded at
2020-12-16 08:58:33
Last updated
2020-12-16 08:58:33
Version
V1.06
Related products
SIMCom SIM8200G 5G Sub-6 LGA

SIMCom Update Tool and User Guide for Simcom SIM7000 series, SIM7070 series, SIM7080 series, SIM7090 series, SIM7500 series, SIM7600 series, SIM79xx series, SIM820x series, SIM830x series.

Download

Uploaded at
2021-02-05 11:23:39
Last updated
2021-02-26 17:38:18
Version
R1.61
Requirements
Microsoft Windows 7 desktop system or later
Simcom Windows drivers installed
(Check during update that normal operational mode and firmware update mode drivers load properly in Windows device manager)
Simcom module firmware update file
Related products
SIMCom SIM7000E CAT-M1/NB1 SMT
SIMCom SIM7000G
SIMCom SIM7000E CAT-M1/NB1 mPCIe
SIMCom SIM7000G CAT-M/NB-IoT/GSM miniPCIe
SIMCom SIM7000A CAT-M SMT Verizon
SIMCom SIM7000A CAT-M SMT AT&T
SIMCom SIM7000A CAT-M mPCIe
SIMCom SIM7070E CAT-M/NB2
SIMCom SIM7070E CAT-M1/NB2 mPCIe
SIMCom SIM8202G-M.2 5G
SIMCom SIM8300G-M.2 5G mmWave
SIMCom SIM7070G CAT-M/NB2
SIMCom SIM7080G CAT-M/NB-IoT
Simcom SIM7600JC-H LTE CAT-4 mPCIe
SIMCom SIM7600SA LTE CAT-1 SMT
SIMCom SIM7600G R2 LTE CAT-1 SMT
SIMCom SIM7600G-H R2 LTE CAT-4 SMT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM7600NA-H mPCIe
SIMCom SIM7600G-H R2 mPCIe
SIMCom SIM7600V-H LTE CAT-4 M.2 Verizon
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM7600G-H LTE CAT-4 mPCIe
SIMCom SIM7600CE-T LTE CAT-4 mPCIe CN
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7500SA LTE mPCIe Audio
SIMCom SIM7500E LTE mPCIe EU
SIMCom SIM7500E LTE SMT EU
SIMCom EVB-Kit
SIMCom SIM7500A LTE SMT US

Simcom SIM820x / SIM830x Series 5G Module Windows USB Drivers V1.01

Download

Uploaded at
2021-02-26 17:19:30
Last updated
2021-02-26 17:19:30
Version
V1.01
Requirements
Microsoft Windows 10 Desktop systems
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8202G-M.2 5G
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8300G-M.2 5G mmWave
SIMCom SIM8202E-M.2 5G

Archive containing the Simcom SIM820x and SIM830x series Linux driver integration files, connection manager and guide

Download

Uploaded at
2021-02-26 17:09:54
Last updated
2021-02-26 17:09:54
Version
1
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8202G-M.2 5G
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8300G-M.2 5G mmWave
SIMCom SIM8202E-M.2 5G
Question

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using QMI Rmnet over USB interface

Solution

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using QMI Rmnet over USB interface

5G technology introduces new requirements on the interface links between the host systems and cellular modules.
The Linux community continuously commit necessary changes to the kernel drivers and interface management tools to improve the compatibility and performance.
Because of this, it is important that you base your Linux system builds on up-to-date kernel versions, avoiding many problems already solved.

Ensure that you have up-to-date firmware version in the cellular module. Check the dedicated product page here at Techship and the firmware downloads tab or open a technical support ticket.

Early devices and engineering samples came with a older baseline firmware version and need to be update in Windows systems.

This guide specifically only describes how to establish the QMUX data connection part of the QMI rmnet USB interface for the SIM8202x-M2 series modules.
The qmi_wwan kernel driver module and libqmi library is used.

Ensure that you have the module in QMI Rmnet usb mode and qmi_wwan network kernel driver and option usb-serial driver properly loaded to the module interfaces.
Can be checked e.g. through dmesg, usb-devices or lsusb -t commands.

usb-devices
T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1
P: Vendor=1e0e ProdID=9001 Rev=04.14
S: Manufacturer=QCOM
S: Product=SDXPRAIRIE-MTP _SN:
S: SerialNumber=
C: #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=techship_serial
I: If#=0x1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=60 Driver=techship_serial
I: If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=50 Driver=qmi_wwan
I: If#=0x6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs

If the qmi_wwan and option drivers do not get correctly loaded in your current system build and kernel version, please refer to the manufacturer Linux integration guide.

Alternatively you can try compile our modified out-of-kernel driver module variants: techship_qmi_wwan and techship_serial and load them in your system.
See the git readme files for details on pre-requirements, how to clone, compile and use the make file options to install the drivers.

They are available in the following git repository: https://bitbucket.org/storjor/techship_linux_drivers/

Once you have drivers correctly loaded, start by disabling the related qmi_wwan network interface name:
ip link set dev wwan0 down

Ensure RAW IP configuration is enabled:
sh -c "echo 'Y' > /sys/class/net/wwan0/qmi/raw_ip"
(observe the path name including the network interface name, update to match the interface name used in your system)

Create a virtual mux interface for the qmi network interface:
sh -c "echo '1' > /sys/class/net/wwan0/qmi/add_mux"
(observe the path name including the network interface name, update to match the interface name used in your system)

Configure the data format on module side:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wda-set-data-format=link-layer-protocol=raw-ip,ul-protocol=qmap,dl-protocol=qmap,dl-max-datagrams=32,dl-datagram-max-size=31744,ep-type=hsusb,ep-iface-number=5

Here in-between you should perform necessary operations to the module prior to having the cellular network data connection established.
Things like SIM state and PIN code entry, module device registration in the cellular network, APN profile management etc.

Refer to the qmicli manual pages for details on the control commands that can be supported by the libqmi library and qmicli command line interface. Note however that not all qmi commands are supported by all cellular module vendors and might be dependant on chipset families, firmware versions and additional vendor specific command etc.
https://www.freedesktop.org/wiki/Software/libqmi/

Once module is ready and registered in cellular network we can proceed to configure and set up the data connection.

Bind the virtual mux network interface we created earlier to the client ID (CID) that gets opened, the CID id is given back in the reply:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-bind-mux-data-port=mux-id=1,ep-iface-number=5 --client-no-release-cid

It is important to use the --client-no-release-cid attribute here to keep the tunnel open at all time while the data connection is established.
If the client id CID linked to the network connection is closed, then the data connection on the qmux virtual network interface will also be closed.

Start the cellular network data connection in the normal way now, include the --client-no-release-cid attribute and use the already open CID ID you got back from previous command reply. E.g. like this:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-start-network=apn=data.tre.se,ip-type=4 --client-no-release-cid --client-cid=##
Store the packet data handle id from the command reply, to re-use when stopping the network data connection.

Request the cellular data connection IP details from the module and network with command:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-get-current-settings --client-no-release-cid --client-cid=##

Bring up the main QMI RMNET network interface:
ip link set dev wwan0 up

Apply the IP address to the qmux interface that you acquired through qmicli --wds-get-current-settings above, e.g.:
ip addr add 2.64.116.145 dev qmimux0

Apply the given MTU size to the qmux interface that you acquired through qmicli --wds-get-current-settings above, e.g.:
ip link set mtu 1500 dev qmimux0

Bring up the QMUX virtual network interface:
ip link set dev qmimux0 up

You should now have a working cellular network data connection.

Test it e.g. by sending a ping over the qmux interface:
ping -I qmimux0 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) from 2.68.152.91 qmimux0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=31.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=29.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=36.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=36.0 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 29.821/33.494/36.690/2.911 ms

Apply appropriate network interface routing suitable for your use-case, e.g:
ip route add default dev qmimux0

the qmicli --wds-get-current-settings give back DNS server addresses also if they are defined by the cellular network.
Depending on how your Linux distribution handle DNS servers you can add them or instead use a public DNS server.

To stop the cellular data network connection:
Bring down the virtual mux interface:
ip link set qmimux0 down

Flush the ip addresses:
ip -4 -6 address flush dev qmimux0

Use the --wds-stop-network attribute to stop the data connection in module, include the packet data handle and the client ID from when establishing the connection.
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-stop-network=########## --client-cid=##
Note: by not adding the --client-no-release-cid attribute this client ID will be closed after command execution.

It is up to the host application to manage and poll the connection state of the cellular module.
E.g. it the connection is lost temporarily due to no network coverage in the current location, the host application should tear down and re-establish the data connection when cellular module is registered in network again.

If the data connection fails for some reason several times, ensure that the connect retry attempts do not take place continuously without some extended delays in-between. Depending on the cellular network operator, they can enforce lock-out on your subscription/device for certain time periods in order to protect the network.

Question

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using MBIM network interface over USB

Solution

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using MBIM network interface over USB

5G technology introduces new requirements on the interface links between the host systems and cellular modules.
The Linux community continuously commit necessary changes to the kernel drivers and interface management tools to improve the compatibility and performance.
Because of this, it is important that you base your Linux system builds on up-to-date kernel versions, avoiding many problems already solved.

Ensure that you have up-to-date firmware version in the cellular module. Check the dedicated product page here at Techship and the firmware downloads tab or open a technical support ticket.

Early devices and engineering samples came with a older baseline firmware version and typically need to be updated in a Windows system.

This guide describes how to establish a MBIM data connection in Linux using libmbim library and mbimcli command line interface for SIM8202x-M2 series modules when connected over USB to the host system.
The cdc_mbim kernel driver module and libmbim library is used.

Ensure that you have the Simcom module in MBIM usb mode and cdc_mbim network kernel driver and option usb-serial driver properly loaded to the module interfaces.
It can be checked e.g. through dmesg, usb-devices or lsusb -t commands.

usb-devices
T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 3 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 1
P: Vendor=1e0e ProdID=901e Rev=04.14
S: Manufacturer=QCOM
S: Product=SDXPRAIRIE-MTP _SN:
S: SerialNumber=
C: #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=techship_serial
I: If#=0x1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x2 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#=0x3 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=60 Driver=techship_serial
I: If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs

If the option serial drivers are not correctly loaded in your current system build and kernel version, you can try compile our modified option kernel driver module techship_serial from git link below and load them into your system build.
See the git readme files for details on pre-requirements, how to clone, compile and use the make file options to install the drivers.

They are available in the following git repository: https://bitbucket.org/storjor/techship_linux_drivers/

Refer to the mbimcli manual pages for details on the control commands that can be supported by the libmbim library and mbimcli command line interface. Note however that not all mbim commands are supported by all cellular module vendors and might be dependant on chipset families, firmware versions and additional vendor specific command etc.
https://www.freedesktop.org/wiki/Software/libmbim/

Example of how to set up a cellular data connection:
Note! A working MBIM network interface data connection requires that the MBIM control message tunnel is kept open at all time also.
To keep it open, start a new session with a mbimcli command, and keep the session open after the command execution by the --no-close attribute.
The Session ID / Transaction ID number (TRID) that is opened with the mbimcli command will be given back in the reply, save it for use in the next mbimcli command.
If the session ID linked to the network data connection is closed, then the data connection on the network interface will also be closed.

Check cellular RF radio status:
mbimcli -p -d /dev/cdc-wdm0 --query-radio-state --no-close
If not enabled, set it active:
mbimcli -p -d /dev/cdc-wdm0 --set-radio-state=on --no-close --no-open=##

Check SIM card subscriber state:
mbimcli -p -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --no-open=##
If pin is needed, enter it using --enter-pin command:
mbimcli -p -d /dev/cdc-wdm0 --enter-pin=#### --no-close --no-open=##

Check cellular network registration state:
mbimcli -p -d /dev/cdc-wdm0 --query-registration-state --no-close --no-open=##

If not registered already, try using register automatic:
mbimcli -p -d /dev/cdc-wdm0 --register-automatic --no-close --no-open=##

Check the packet data service state:
mbimcli -p -d /dev/cdc-wdm0 --query-packet-service-state --no-close --no-open=##

If packet service state is not attached, use attach command:
mbimcli -p -d /dev/cdc-wdm0 --attach-packet-service --no-close --no-open=##

To to start a data connection use the connect command, with the desired parameters for PDP APN, IP type, auth details, etc.
mbimcli -p -d /dev/cdc-wdm0 --connect=apn='data.tre.se',ip-type='ipv4v6' --no-close --no-open=##

Bring down the MBIM network interface:
ip link set dev wwan0 down

Clear any existing IP address and routes:
ip -4 -6 address flush dev wwan0
ip -4 -6 route flush dev wwan0

The mbimcli connect command returns the IP, gateway, DNS, and MTU details for the data connection if established successfully.
Enter the IPv4 details to the network interface in the Linux host system, e.g.:
ip address add 2.70.103.209/30 dev wwan0
ip link set mtu 1500 dev wwan0

Enter the IPv6 details to the network interface in the Linux host system, e.g.:
ip -6 addr add 2a02:aa1:1021:b9d1:4fb:e1c9:589c:d53f/64 dev wwan0
ip -6 link set mtu 1500 dev wwan0

Enable the network interface:
ip link set dev wwan0 up

Apply appropriate network interface routing suitable for your use-case, e.g:
ip route add default dev
ip -6 route add default dev wwan0

You should now have a working cellular network data connection.

Test it e.g. by sending ping requests over the interface:
ping -I wwan0 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) from 2.70.103.209 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=224 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=42.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=30.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=38.4 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 30.657/84.031/224.373/81.140 ms

ping -6 -I wwan0 2600:: -c 4
PING 2600::(2600::) from 2a02:aa1:1021:b9d1:8847:afd4:e35a:aa29 wwan0: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=52 time=173 ms
64 bytes from 2600::: icmp_seq=2 ttl=52 time=153 ms
64 bytes from 2600::: icmp_seq=3 ttl=52 time=152 ms
64 bytes from 2600::: icmp_seq=4 ttl=52 time=208 ms

--- 2600:: ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 152.108/171.523/208.073/22.623 ms

To stop the cellular data network connection use mbimcli disconnect command.
Use the Session ID from the previous mbimcli command reply in --no-open=## attribute, but do not include the --no-close attribute, doing so closes the session afterwards.
mbimcli -p -d /dev/cdc-wdm0 --disconnect --no-open=##


Bring down the interface:
ip link set dev wwan0 down

Clear any remaining IP address and routes:
ip -4 -6 address flush dev wwan0
ip -4 -6 route flush dev wwan0

It is up to the host application to manage and poll the connection state of the cellular module.
E.g. if the connection is lost temporarily due to no network coverage in the current location, the host application should tear down and re-establish the data connection when cellular module is registered in network again.

If the data connection fails for some reason several times, ensure that the connect retry attempts do not take place continuously without some extended delays in-between.
Depending on the cellular network operator, they can enforce lock-out on your subscription/device for certain time periods in order to protect the network from being flooded by requests.