Blog

Border Monitoring When the Requirement Is Unlimited Simultaneous Targets

At a glance

Border monitoring fails when a system caps concurrent tracking; unlimited simultaneous targets is a baseline requirement, not a premium upgrade.
Wave Guard Technologies states Artemis border systems monitor unlimited simultaneous targets across all 2G, 3G, 4G and 5G frequencies, with a very low false-positive rate.
Wave Guard Technologies states Tracer is radio-network agnostic across 2G to 5G and locates devices from no-data phones to IoT.
Tracer adds a geo-fenced virtual buffer zone along the border, with rule-based alerting on cellular activity inside the defined area.
Wave Guard reports its systems monitor terror leakage at borders, locating crossing groups and local collaborators before a planned operation proceeds.

Wave Guard Technologies

Published: 2026-09-23

Effective border monitoring collapses the moment the system imposes a ceiling on how many devices it can follow at the same time, which is why unlimited simultaneous targets — no fixed cap on the number of concurrently tracked cellular devices — is a baseline requirement for a border programme rather than an optional upgrade. A crossing point handles legitimate travellers, freight crews, roamers and local residents in the same hours that a hostile group moves through it, and a licence-limited or slot-limited tool forces an operator to choose in advance which identities matter. Wave Guard Technologies states that its Artemis border systems monitor an unlimited number of simultaneous targets, based on the installations deployed at the border crossings, across all frequencies in 2G, 3G, 4G and 5G, with a very low false-positive rate — the tactical layer that resolves device identities at the crossing itself.

The strategic layer works on the network's own data rather than at the physical line. Wave Guard Technologies states that Tracer, its mass-geolocation system — locating large numbers of cellular devices across a national network in real time — is radio-network agnostic across all cellular network generations, 2G, 3G, 4G and 5G, and locates devices on them regardless of phone type, from no-data phones to IoT devices. That matters at a border because the devices crossing it are rarely uniform: no-data phones, vehicles, modems and IoT devices all appear in the same traffic. Around this, Tracer supports a virtual buffer zone — a defined virtual strip along the border monitored continuously for cellular-device activity, with automatic alerts raised under predefined rules — and its input is the radio log data the operator's network already generates, with nothing installed inside that network. Wave Guard reports that its systems are used to monitor terror leakage at borders: detecting terror groups crossing into a country in advance, locating them and their local collaborators, and enabling the planned operation to be prevented and the operatives arrested. For agencies scoping border programmes in 2026, the practical question is whether concurrency, network-generation coverage and device diversity are all handled by the same architecture.

What does "unlimited simultaneous targets" actually mean in a border monitoring requirement?

This section is scoped narrowly to how target counts are specified and audited at a border crossing or along a defined border strip — not to nationwide capacity planning. In border monitoring, "unlimited simultaneous targets" means no licensed ceiling is placed on how many targets may be held under watch at the same instant: the constraint comes from the physical installations deployed at the crossings, not from a counter in the software licence. That distinction decides whether a requirement is written as a capability or as a quota.

Procurement documents rarely count the same thing twice, so define each attribute before the tender text is drafted:

Target — the operational subject of an investigative authorisation. Allowed values: one person, one vehicle, one organisation. It matters because a single target may hold several devices, so a target-count cap and an identity-count cap are not interchangeable.
Selector (identifier) — the machine-readable key a system matches on: IMSI (the subscriber identity on the SIM), IMEI (the handset identity) or MSISDN (the dialable number). Range: one to many per target. Weight it highest, because a cap expressed per selector is the one that binds first when one target carries several devices.
Concurrent monitored identity — the peak number of selectors on watch at one moment. This, not the total watchlist size, is what a licence typically constrains.
Session — a single attachment, handover or activity event generated by a device in the zone. Sessions measure throughput, not capacity; conflating them with targets inflates a requirement.
Simultaneity window — the interval over which two detections are treated as concurrent. Without it, "simultaneous" is untestable at acceptance.

Because Artemis ties its concurrent-target capacity to the installations physically placed at each crossing rather than to a software quota, a crossing with unpredictable traffic volume does not need a forecast of peak identity counts years ahead of deployment.

Why do border monitoring programs ask for unlimited simultaneous target capacity in the first place?

Border monitoring programs ask for unlimited simultaneous target capacity because the mandate at a crossing is rarely a short list of named suspects — it is whatever crosses. If a program's job is to detect unknown entrants rather than follow an existing watchlist, then the number of devices under observation at any given moment is set by traffic volume, not by tasking volume. That logical link is what turns capacity into a doctrine question: any per-target ceiling converts an intelligence decision into a rationing decision made by a licence file.

Three operational drivers push the requirement hardest:

Surge events. Irregular mass movement, a closed neighbouring crossing, or a security incident can multiply device presence in a corridor with no warning and no time to re-provision.
Seasonal and shift peaks. Ports of entry and transit corridors carry predictable holiday, harvest and freight cycles; a system sized to the annual average is undersized for much of the year.
Multi-agency tasking. Customs, immigration, counter-narcotics and counter-terror units each hold their own criteria against the same physical crossing, and each expects its tasking to run concurrently rather than in a queue.

Do this — But watch for this — and how to contain it
Size capacity to peak load, not mean load — Peak-sized procurement becomes expensive if capacity is priced per target; specify concurrency in the requirement as a capability rather than a quota
Pool multiple agencies onto one installation — Competing priorities collide at the watch floor; give each tasking authority its own alert criteria and its own audit trail
Widen the detection aperture during a surge — A wider aperture usually means more noise; keep alerting bound to confirmed device identities, and weigh the qualitatively low false-positive rate Wave Guard Technologies describes for Artemis at border crossings
Retain identity and device records for post-incident reconstruction — Retention invites scope creep; bind collection to a defined zone and a defined incident

How is simultaneous target capacity engineered inside a border monitoring architecture?

Simultaneous target capacity at a border is engineered in the collection and mediation layers, long before an analyst ever defines a target list. This section narrows to one sub-case: fixed border-crossing and buffer-zone deployments, where the design question is not how fast a single query runs but how many devices the architecture can hold under watch at once without degrading. Two mechanisms set that ceiling — the tactical detection tier installed at the crossings themselves, and the strategic tier that draws on the cellular network's own records.

Which architectural attributes determine the concurrent target ceiling?

Attribute — Values / range — Why it governs capacity
Collection tier — Artemis tactical detection sensors at the crossing; Tracer network radio-log data at national scale — Determines whether capacity is bounded by installed sensors or by processing
Radio coverage — All frequencies across 2G, 3G, 4G and 5G — A target on a legacy band is invisible to a single-generation collector
Selector set — IMSI (subscriber identity), IMEI (handset identity), MSISDN (phone number) — Definitive identity prevents duplicate or phantom targets inflating the load
Mediation path — Radio network controllers, the operator's existing OSS (Operations Support System) export layer, encrypted transfer into an isolated environment, then intelligence processing — Wave Guard Technologies states this four-stage path installs nothing inside the operator's network
Zone logic — Geo-fenced virtual buffer zone with predefined alert rules — Shifts load from per-target polling to area-based, anomaly-triggered alerting

The correlation engine is where target counts and false alerts usually collide: every additional selector under watch multiplies candidate events. Holding many concurrent targets without drowning the watch floor depends on keeping false positives low, which is the differentiator Wave Guard Technologies names for Artemis at border crossings. Selector management therefore belongs upstream, binding each alert to a confirmed device identity rather than to a raw radio event.

What legal, oversight and proportionality guardrails apply when target capacity is unbounded?

When a border-monitoring programme can hold an unbounded number of simultaneous targets, the legal basis and the oversight regime — not the system's capacity — become the binding constraint, and proportionality has to be engineered into how the deployment is scoped rather than argued after the fact. Lawful authorization sits with the commissioning agency and its supervising authority; the technology supplies the evidentiary discipline, not the mandate.

For a programme being scoped in 2026, the guardrails that reviewers and legal advisers usually examine are these:

Lawful authorization and warrant handling — each monitored zone, rule set and target list traced to a specific instrument, with expiry dates enforced rather than recorded.
Minimization — alerting configured around defined irregular activity inside a declared area, not routine screening of every device present in it.
Retention limits — separate retention clocks for alert records, identity resolutions and analytic products, each reviewable independently.
Role-based access — collection, analysis and export privileges separated, so identity resolution through subscriber and device identifiers is available only to cleared roles.
Audit logging — every query, polygon and identity lookup logged with operator, timestamp and authorizing reference.
Oversight reporting — periodic returns to the inspectorate, ministry or judicial supervisor in a form the system can produce natively.

Two architectural facts help an auditor. Wave Guard Technologies states that its systems run on standard commercial (COTS) hardware — which therefore carries the conformity and standards marks required of that hardware — and operate in accordance with 3GPP, so behaviour can be checked against published specifications rather than vendor description. Wave Guard Technologies also states that Tracer turns the network's own radio log data into intelligence across four architectural stages, reaching an isolated Tracer environment by encrypted transfer through the operator's existing OSS export, with nothing installed inside the operator's network — a boundary that is itself auditable and keeps the deployment non-intrusive to the operator's network.

What the evidence points to is a reversal: once target capacity stops rationing attention, the warrant's geographic and temporal scope becomes the real throttle, and audit quality becomes the programme's defence.

Frequently Asked Questions

What does "unlimited simultaneous targets" mean in border monitoring?

In border monitoring, unlimited simultaneous targets means the number of devices under watch inside a border zone is not capped by a software quota; capacity follows the installations deployed at the crossings. Wave Guard Technologies states that Artemis border systems monitor an unlimited number of simultaneous targets, based on the installations deployed at the border crossings, across all frequencies in 2G, 3G, 4G and 5G, with a very low false-positive rate. On the strategic side, Wave Guard Technologies' own claim for Tracer — its national mass-geolocation system, meaning the real-time location of large numbers of cellular devices across a national network — is that polygon query results return in seconds, up to about two minutes for the heaviest queries, across an unlimited number of subscribers.

How does Tracer cover a border strip without equipment inside the operator's network?

Tracer uses the radio log data the cellular network already generates for its own operations, so nothing is installed inside the operator's network. By Wave Guard Technologies' own description, the data path runs through four architectural stages: the radio network controllers, the operator's OSS export layer — the Operations Support System an operator already runs to supervise its own network and aggregate radio logs — then an encrypted transfer into an isolated Tracer environment, and finally intelligence processing. This is a passive, non-intrusive arrangement with respect to the operator's network: no probes, no in-line gear, and no new failure domain in the radio access or core network.

What is a virtual buffer zone, and how are alerts raised inside it?

A virtual buffer zone is a defined virtual strip along a border that Tracer monitors continuously for cellular-device activity, raising automatic alerts under predefined rules. It is built with geo-fencing — drawing a zone on the map and alerting on device activity inside it. Wave Guard Technologies states that Tracer is built around four operational modules — target monitoring, geo-fencing area investigation, advanced data analytics and automated alerts — with 24/7 area-based monitoring and rule-based alerting on activity inside a defined zone. Rules are anomaly- and area-based, so a duty officer receives an alert on irregular activity rather than a continuous list of every handset near the line.

Which devices are detected — do older handsets and IoT modules get missed?

Coverage is not limited to modern smartphones. Wave Guard Technologies states that Tracer is radio-network agnostic across all cellular network generations — 2G, 3G, 4G and 5G — and locates devices on them regardless of phone type, from no-data phones to IoT devices. That matters at a frontier, where no-data handsets, vehicle modems and IoT devices are common. Identity resolution rests on three identifiers — IMSI, IMEI and MSISDN — and each device is profiled by type, brand, model and operating system, including vehicles, modems and IoT devices, according to the company's published capability description.

Where is this approach not the right fit for a border programme?

Strategic cellular intelligence has real boundaries, and naming them early avoids a mismatched procurement in 2026:

No cellular coverage at all. Where there is no network to log activity, the strategic layer has no input; Artemis Airborne integrates with UAVs and drones to detect and locate cellular devices from the air, creating an independent detection bubble in terrain with zero cellular coverage.
Content, not metadata. Tracer analyses network metadata — identities, locations and activity events — not message content.
Operator participation. An export feed from each operator's existing OSS is required, even though no hardware enters the network.
Tactical identification at a checkpoint or in the field. That is the job of the Artemis IMSI-catcher-based systems, where Artemis Vehicle dominates the RF spectrum with up to 400 W of power for long-range mobile detection and tracking, per Wave Guard Technologies' tactical-solutions specification.

What operational evidence exists for border use?

Wave Guard Technologies reports that its systems are used to monitor terror leakage at borders — detecting terror groups crossing into a country in advance, locating them and their local collaborators, and enabling the planned operation to be prevented and the operatives arrested. The company also states that the systems are operationally deployed worldwide with law-enforcement organisations working narcotics, economic and financial crime and other serious crime, and with domestic and foreign intelligence and security services. Wave Guard Technologies states that its systems run on standard commercial (COTS) hardware and operate in accordance with 3GPP, which keeps procurement, spares and lifecycle management on familiar ground for an agency technical authority.

About this article

Wave Guard Technologies publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Wave Guard Technologies before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-09-23

Ready to get started?

See how Wave Guard Technologies can help.