A 4G camera is useful where a fixed internet connection is impractical, provided its carrier, recording mode and power system fit the site. Specify what must be recorded locally, what must reach a remote viewer, and how long the site must operate unattended. Cellular connectivity alone promises neither continuous recording nor recovery of missed alerts.
Choose the connection path before the camera
An integrated cellular camera contains its own modem and usually has its own SIM. A separate LTE router can instead provide the internet uplink for a local camera network. In that layout, PoE cameras can send video to a local recorder over Ethernet while the router carries remote access traffic. Include the router, switch and recorder in the power budget; an internet router supplies neither camera power nor recording by itself.
| Path | Useful when | Confirm before buying |
|---|---|---|
| Cellular camera → supported app/service | One isolated view, minimal local network | Supported region, account ownership, subscription, local storage and recording mode |
| Cameras → local NVR → LTE router → remote viewer | Several views need a local timeline | Recorder remote access, router coverage, upload capacity and full-system power |
| Camera/router → managed network → remote recorder | An organisation requires off-site recording | Routing, supported video protocol, security, upload allowance and outage recording |
A camera that works through its manufacturer's app may not expose a stream usable by an NVR. Obtain the supported protocol and connection method for the exact camera/recorder combination. Carrier private addressing or carrier-grade NAT can prevent unsolicited inbound connections: a local IP address or an app connection is not proof of a remotely reachable camera. Ask the carrier and installer whether a supported outbound service, managed VPN, or appropriate private/public addressing service is required. Do not solve an unverified access problem by exposing camera administration ports.
Confirm the SIM, bands and coverage at the real position
- Identify the regional hardware. Match the camera/modem's documented LTE bands against the destination carrier's service. A country name or “4G compatible” label is insufficient. Confirm whether the supplier locks the SIM or service and whether moving the equipment changes support.
- Check the plan. Ask about device restrictions, SIM size, activation, available balance, PIN handling, roaming, expiry, overage and throttling. A SIM that works in a phone is an initial clue, not acceptance of camera compatibility. Assign renewal to a named site owner.
- Get APN details from the carrier. APN means access point name: the modem's connection setting for that mobile service. Authentication may also be needed. Use the device's documented configuration process; do not assume a phone's automatic settings or another brand's import procedure apply.
- Test the assembled equipment. Use the actual SIM, camera/router and supported antenna at the planned mounting height. Test live view, alert delivery and playback during working hours and an evening busy period. Record failures and reconnect times; signal bars alone do not demonstrate usable upload.
Reolink's SIM guide checks carrier, plan and device restrictions for its listed models. Its APN guide illustrates a model-specific configuration method. These are examples of why compatibility needs checking, not installation instructions or specifications for QuarkView equipment.
If metal containers or new buildings obstruct reception, retest before relocating an antenna. An external antenna requires a supported connector, mounting and cable arrangement; greater height is not an unconditional improvement. If adequate uploads cannot be achieved, consider a different carrier, a supported alternative network path, or a local-only recording requirement with scheduled collection.
Build a data budget from activities, not resolution alone
For transmitted video, decimal GB ≈ average bitrate in Mbps × seconds transmitted ÷ 8,000. Use the combined bitrate if audio or multiple streams are included; variable bitrate makes this an estimate. Count every session or upload the camera actually sends. Users watching concurrently may create separate transmissions, depending on the service.
| Activity and assumption | Calculation | Video traffic |
|---|---|---|
| Live view: 10 min/day | 1 × 600 × 30 ÷ 8,000 | 2.25 GB |
| Uploaded events: 20 clips/day, 30 s each | 1 × 20 × 30 × 30 ÷ 8,000 | 2.25 GB |
| Remote playback: 60 min/month | 1 × 3,600 ÷ 8,000 | 0.45 GB |
| Subtotal | 2.25 + 2.25 + 0.45 | 4.95 GB |
| Continuous off-site video instead: 24 h/day | 1 × 86,400 × 30 ÷ 8,000 | 324 GB |
These are arithmetic examples, not measured usage or a recommended SIM package. The subtotal excludes still images, notifications, service keepalives, firmware downloads, protocol overhead and retransmissions. For a separate assumption of 50 uploaded images/day at 200 kB each, add 0.30 GB/month. Notification overhead is service dependent; measure it rather than assuming alerts are free. A low-bandwidth live-view stream can save traffic, but retain sufficient recorded detail for the evidence task.
Recording entirely to local storage does not itself upload that video. Viewing it remotely later does. Reolink's data-use guidance makes this distinction and lists other network activities for its cameras; its default bitrates and plan figures are not QuarkView specifications. Use carrier counters over representative active and quiet days, reconcile them with viewing and upload logs, and allow headroom for the site's busiest period. Exceeding a plan can stop or slow remote services even while local recording remains available.
Verify what happens when the network disappears
Separate loss of mobile service from loss of power. Local recording during a network outage requires an enabled, supported recording mode, working media and enough power. Backfilling old clips to the cloud after reconnection is a separate feature; a restored live view does not prove it happened.
- On a test unit, set the required recording schedule and create a recognisable timed event. Retrieve its start and end from saved footage.
- With power maintained, use the manufacturer's supported method to interrupt the test data connection. Create further timed events during the outage. Do not remove a SIM from powered equipment unless the manual permits it.
- Restore service. Record reconnect time; compare local clips, remote playback and any delayed uploads. Check whether alerts were queued, lost, or delivered late. Agree how late alerts should be handled.
- Test the separate power-recovery procedure. Confirm time, schedule and account access survive restart; verify a new event and clip export rather than just an online icon.
- Check the oldest retained footage and overwrite behaviour. Export essential evidence before media reuse; a stolen or damaged camera can take its local recordings with it.
Leave a serviceable remote installation
For an illustrative remote gate requiring event review rather than a full timeline, start with one tested cellular view, local event storage and selective uploads. Accept it only if fast and slow approaches at night are recorded from the required point; a wake-up camera may miss a brief crossing. If a complete delivery timeline is required, choose verified continuous recording and size power and storage for it. Changing an alert setting does not convert unsupported hardware into continuous recording equipment.
Give the site owner the camera ID, mounting view, authorised users, SIM account, renewal date, storage target, power reserve and fault contact. Use individual authorised accounts where supported, strong passwords and the documented firmware-update process. Set the required privacy masks and audio permissions before commissioning. Keep passwords and APN credentials in secure administration records. Agree checks for remaining data, recent recordings, battery/charging and blocked views, plus who visits when remote access fails. Use the solar energy budget for off-grid power and the jobsite relocation checklist when the scene will change.