Predictika · Cellular IoT module selection: LE910Cx ThreadX variants

An AI sales agent's cellular IoT module selection, checked before it goes out

An AI sales agent recommends a cellular IoT module for a customer's device: the module variant, the market and carrier it will run on, the LTE bands, voice and 3G/2G fallback it needs, the data rate and the operating conditions. Before the recommendation goes out, the agent sends it to Predictika, which checks it against a declarative model of the published variant table and returns a verdict, every reason and the figures it computed.

Scope: Telit Cinterion LE910Cx ThreadX modules: LE910C1-EUX, -SAX, -SAXD, -SVX, -WWX, -WWXD and LE910C4-WWX, -WWXD. See everything this validator covers

This validator models module selection for one product line, the Telit Cinterion LE910Cx cellular module family in the eight ThreadX variants listed below, not just the scenarios shown on this page.

  • Variants covered — LE910C1-EUX (Europe), LE910C1-SAX and -SAXD (North America, AT&T), LE910C1-SVX (North America, Verizon), and the worldwide LE910C1-WWX, -WWXD, LE910C4-WWX and -WWXD. A “D” variant is data only: voice is disabled.
  • Market and carrier — the deployment region must be one the variant is listed for, and the carrier (AT&T or Verizon) must be one the variant is listed for.
  • LTE bands, voice and fallback — each LTE band the deployment needs (1, 2, 3, 4, 5, 7, 8, 12, 13, 20 and 66) must be in the variant's band list; voice needs a voice variant; 3G and 2G fallback need a variant with 3G and 2G bands.
  • Data rate and operating conditions — LTE Cat.1 reaches 10 Mbps down and 5 Mbps up, Cat.4 reaches 150 and 50; the industrial temperature range is -40 to +85 degrees C and the supply range is 3.4 to 4.2 V; the downlink stated on the recommendation is compared with the computed one.
  • GNSS — GNSS is listed as optional without a per-variant list, so asking for it goes to a person.

Any deployment that uses these variants is in scope — not only the scenarios pictured here. Not covered: prices and connectivity plans (neither is public, so this validator produces no price build-up or line-item quote), the other LE910Cx variants and other Telit Cinterion module families, band 28 and the other bands not listed above, certifications by variant, footprint and mechanical details, and software or operating-system choices.

The AI sales agentBuilds the module recommendation from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
A module variant that must match the deployment region and carrierOnly with care
Each variant is sold for particular markets and carriers, so a rule is needed per variant and market and has to stay in step as the range changes.		Variant, region and carrier arrive together; each is checked against the variant on every call.
LTE bands the deployment needsOnly with workarounds
The needed bands come from the customer's carriers and each variant supports a different band list, so every band needs its own cross-check against the chosen variant.		Every needed band is checked against the variant's band list on every call, and each missing band is reported.
Voice and 3G/2G fallback that depend on the variantOnly with care
A data-only variant shares hardware with its voice twin and some variants have no 3G or 2G at all; a product rule can cover each case but each needs maintaining.		Voice and fallback needs are checked against the variant together with everything else.
Stated downlink that must match the module categoryOnly with care
A stated figure is free text on the quote; a rule can compare it with the category limit, but someone has to write and maintain that comparison.		The stated downlink travels with the recommendation and is compared with the computed one on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1The deployment is in North America, but the selected module variant is a Europe, Middle East and Africa variant.
2The deployment is in EMEA, but the selected module variant is a North America variant.
3The deployment is in Asia Pacific, but only the worldwide variants are listed for that market among the variants covered here.
4The deployment is in Latin America, but only the worldwide variants are listed for that market among the variants covered here.
5The deployment is on the AT&T network, but the selected module variant is not listed for AT&T.
6The deployment is on the Verizon network, but the selected module variant is not listed for Verizon.
7The deployment needs voice calls, but the selected module variant is data only.
8The deployment needs 3G fallback, but the selected module variant is LTE only.
9The deployment needs 2G fallback, but the selected module variant is LTE only.
10The deployment needs LTE band 13, which the selected module variant does not support.
11The deployment needs LTE band 66, which the selected module variant does not support.
12The deployment needs LTE band 2, which the selected module variant does not support.
13The deployment needs LTE band 12, which the selected module variant does not support.
14The deployment needs LTE band 5, which the selected module variant does not support.
15The deployment needs 11 Mbps downlink; the selected module reaches 10 Mbps.
16The deployment needs 151 Mbps downlink; the selected module reaches 150 Mbps.
17The quote states 150 Mbps downlink; the selected module gives 10 Mbps.
18The quote states 10 Mbps downlink; the selected module gives 150 Mbps.
19The deployment must work at 41 degrees C below zero; the module industrial range ends at 40 degrees C below zero.
20The deployment must work at 86 degrees C; the module industrial range ends at 85 degrees C.
21The host supplies 3,399 mV; the module supply range is 3,400 to 4,200 mV.
22The host supplies 4,201 mV; the module supply range is 3,400 to 4,200 mV.
23The module family lists GNSS as an optional capability, but the public documents do not say which variants offer it; a person should confirm.
24The quote states 50 Mbps downlink; the selected module gives 10 Mbps.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Region, carrier and bands: An LE910C1-EUX for a North America deployment on Verizon that needs LTE band 13

    
The agent's request. Please recommend the Telit Cinterion LE910C1-EUX module for a device deployed in North America on the Verizon network, needing 5 Mbps downlink, LTE band 13, working from -40 to 70 degrees C on a 3,800 mV supply. The recommendation states 10 Mbps downlink. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Module not sold for North America. The deployment is in North America, but the selected module variant is a Europe, Middle East and Africa variant.
    • 
      
  • Module not listed for Verizon. The deployment is on the Verizon network, but the selected module variant is not listed for Verizon.
    • 
      
  • LTE band 13 not supported. The deployment needs LTE band 13, which the selected module variant does not support.
    • 
    

    
2. Region, carrier and bands: The agent resubmits after fixing the errors

    
The agent's request. Please recommend the Telit Cinterion LE910C1-SVX module for a device deployed in North America on the Verizon network, needing 5 Mbps downlink, LTE band 13, working from -40 to 70 degrees C on a 3,800 mV supply. The recommendation states 10 Mbps downlink. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Module data rate. The selected module reaches 10 Mbps downlink and 5 Mbps uplink.
    • 
    

    
3. Voice, fallback and data rate: An LE910C1-SAXD for a North America AT&T deployment needing voice, 3G fallback and 20 Mbps downlink

    
The agent's request. Please recommend the Telit Cinterion LE910C1-SAXD module for a device deployed in North America on the AT&T network, needing 20 Mbps downlink, LTE band 4, voice calls and 3G fallback, working from -40 to 70 degrees C on a 3,800 mV supply. The recommendation states 150 Mbps downlink. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Voice not available on this variant. The deployment needs voice calls, but the selected module variant is data only.
    • 
      
  • No 3G fallback on this variant. The deployment needs 3G fallback, but the selected module variant is LTE only.
    • 
      
  • Required downlink above the module category. The deployment needs 20 Mbps downlink; the selected module reaches 10 Mbps.
    • 
      
  • Stated downlink does not match. The quote states 150 Mbps downlink; the selected module gives 10 Mbps.
    • 
    

    
4. Voice, fallback and data rate: The agent resubmits after fixing the errors

    
The agent's request. Please recommend the Telit Cinterion LE910C1-WWX module for a device deployed in North America on the AT&T network, needing 20 Mbps downlink, LTE band 4, voice calls and 3G fallback, working from -40 to 70 degrees C on a 3,800 mV supply. The recommendation states 150 Mbps downlink. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Required downlink above the module category. The deployment needs 20 Mbps downlink; the selected module reaches 10 Mbps.
    • 
      
  • Stated downlink does not match. The quote states 150 Mbps downlink; the selected module gives 10 Mbps.
    • 
    

    
5. Voice, fallback and data rate: The agent resubmits after fixing the errors

    
The agent's request. Please recommend the Telit Cinterion LE910C4-WWX module for a device deployed in North America on the AT&T network, needing 20 Mbps downlink, LTE band 4, voice calls and 3G fallback, working from -40 to 70 degrees C on a 3,800 mV supply. The recommendation states 150 Mbps downlink. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Module data rate. The selected module reaches 150 Mbps downlink and 50 Mbps uplink.
    • 
    

    
6. Operating conditions and GNSS: An LE910C4-WWX for an EMEA tracker needing GNSS, from 45 degrees C below zero to 90 degrees C on a 4,300 mV supply

    
The agent's request. Please recommend the Telit Cinterion LE910C4-WWX module for a device deployed in Europe, the Middle East and Africa, needing 40 Mbps downlink, GNSS, working from -45 to 90 degrees C on a 4,300 mV supply. The recommendation states 150 Mbps downlink. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Cold limit below the module range. The deployment must work at 45 degrees C below zero; the module industrial range ends at 40 degrees C below zero.
    • 
      
  • Hot limit above the module range. The deployment must work at 90 degrees C; the module industrial range ends at 85 degrees C.
    • 
      
  • Supply voltage outside the module range. The host supplies 4,300 mV; the module supply range is 3,400 to 4,200 mV.
    • 
      
  • GNSS option to confirm. The module family lists GNSS as an optional capability, but the public documents do not say which variants offer it; a person should confirm.
    • 
    

    
7. Operating conditions and GNSS: The agent resubmits after fixing the errors

    
The agent's request. Please recommend the Telit Cinterion LE910C4-WWX module for a device deployed in Europe, the Middle East and Africa, needing 40 Mbps downlink, GNSS, working from -40 to 85 degrees C on a 3,800 mV supply. The recommendation states 150 Mbps downlink. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • GNSS option to confirm. The module family lists GNSS as an optional capability, but the public documents do not say which variants offer it; a person should confirm.
    • 
      
  • Module data rate. The selected module reaches 150 Mbps downlink and 50 Mbps uplink.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent recommends a cellular IoT module for a customer's device: the module variant, the market and carrier it will run on, the LTE bands, and more. Before the recommendation goes out, the agent sends it to Predictika, which checks it against a declarative model of the published variant table and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please recommend the Telit Cinterion LE910C1-SAXD module for a device deployed in North America on the AT&T network, needing 20 Mbps downlink. The recommendation states 150 Mbps downlink. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. The deployment needs voice calls, but the selected module variant is data only. The deployment needs 3G fallback, but the selected module variant is LTE only. The deployment needs 20 Mbps downlink; the selected module reaches 10 Mbps. The other one is on screen.
    6. 
      
  6. The validator returned four blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for stated downlink that must match the module category, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the module variant to LE910C1-WWX.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with two findings, all in one answer. The deployment needs 20 Mbps downlink; the selected module reaches 10 Mbps. The quote states 150 Mbps downlink; the selected module gives 10 Mbps.
    12. 
      
  12. Two findings cleared. Still blocking: required downlink above the module category and stated downlink does not match.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the module variant to LE910C4-WWX.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. Both earlier findings are cleared, and the validator's figure matches the quote.
    18. 
      
  18. Four problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    19.