Ambient IoT — a tag with no battery

Easy to get wrong

One from each chapter that has one. The course carries 16 in all.

• 1.5 A tag with no battery, and the gap it was meant to fill

  "Battery-less" does not mean "no energy storage". Both the founding definition and the radio scope allow a capacitor. The device stores a tiny amount of energy and spends it; what it does not do is carry a chemical battery somebody has to replace.

• 2.3 Study first, then build, then do it again

  A pCR and a CR look the same and mean different things. A pCR edits a draft report that will be published once and then closed. A CR edits live binding text that products are already built against, so it carries a category, a release and a version number. Never quote a pCR as though it changed a specification.

• 3.3 Seventeen groups, and where the weight sat

  The "work item names led" column counts names, not items. Four separate CT work items share the one name AmbientIoT-CT, so a group that leads one of the four still shows the name once. Adding this column down the table gives a number that means nothing.

• 4.3 RAN1 and the radio problem

  Neither device in that scope is "a battery-less phone". The first one does not transmit in the ordinary sense at all — it reflects a wave somebody else provides. If you read the radio specifications expecting a small version of NR, nothing will make sense.

• 5.4 RAN2, RAN3, RAN4 and RAN5 — protocols, interfaces, performance, tests

  TS 38.195 tests the network end — the base station and the carrier-wave node. The device end is tested by RAN5's TS 38.591-1 and TS 38.591-2, a different pair of documents owned by a different group. Reaching for TS 38.195 to test a tag is reaching for the wrong document.

• 6.2 SA1 and the requirements nobody designed against yet

  A requirement is not a design and cannot be read as one. When TS 22.369 says something must be possible, that is a constraint on the architecture, not a description of it. The architecture is TS 23.369, and it is a different document by a different group TS 23.369.

• 7.7 SA2 and the specification that did not exist

  Phase 1 covered Topology 1 and phase 2 studies Topology 2. It is tempting to guess what those two arrangements are. Do not: the definitions live in TS 38.300 and this school does not hold them, so any explanation here would be invention.

• 8.3 SA3, and why a device with no battery is a hard security problem

  "Security for isolated private networks" is a scope, not a caveat somebody forgot to remove. Reading TS 33.369 as though it secured battery-less devices on a public network is reading it for a job it does not claim to do.

• 9.2 CT1, CT3, CT4 and CT6 — one work item description, four groups

  Every one of those four rows shows 959 documents, and it is the same 959 counted four times. Document counts in this register are per short name, not per work item. Add the four together and you get a number four times too large, describing nothing at all. The same trap sits under FS_AmbientIoT and under AmbientIoT AmbientIoT-CT AmbientIoT-CT FS_AmbientIoT AmbientIoT.

• 10.2.2 SA5 and SA6 — running it, billing it, and building on top of it

  There is no objective sentence to quote for this work item. Its description jumps straight from section 3 to section 5, so the section every other work item in this course is quoted from does not exist in it AmbientIoT_Ph2-OAM. That is a fact about the document, not a judgement on the work — and the fix, if you need its scope, is to open SP-260311 itself SP-260311.

• 11.3 The fifty-three specifications, and what this work put in each

  A TR is not a weaker TS. It is a different kind of document with a different life: written, published, closed. Quoting a solution out of TR 23.700-13 as though it were the design is wrong even when the solution was the one chosen — the design is in TS 23.369, and the two can differ TS 23.369.

• 12.4 Where the work stands, and what a percentage is worth

  Every date in the right-hand column is a target held in the work plan, not a recorded outcome. Nothing in this data says whether phase 2 is finished, and it is not finished. No chapter here says it is complete, and none says it has failed either AmbientIoT_Ph2-ARC Ambient_IoT_Solutions_Ph2-Perf.

• 13.2 How to follow this area yourself

  Rows that share a name share a number. The four AmbientIoT-CT rows all say 959, and it is one set of 959 documents seen four times. The same holds for the two FS_AmbientIoT rows, the two AmbientIoT rows and the five AmbientIoT_Ph2-CT rows. Adding the documents column down all 37 rows ^[2] counts the same paper several times over, so never do it.

• 14.3 What the record cannot tell you

  The temptation with an unexplained term is to guess from context. "Topology 2" plainly means some second arrangement — but which, and with what in it, decides whether a sentence about phase 2 is right or wrong. The definitions are in TS 38.300 and TS 23.369, and this school holds neither TS 38.300 TS 23.369.