Every question of this course

Q1.1 What can a sensing network do that the network's existing positioning cannot?

• Work out where a connected device is, more accurately
• Detect an object that is not connected to the network at all
• Carry more data on the same spectrum

The radio study says positioning based on the radio technology is already supported, and that what the specifications lack is a built-in way to detect objects that are not connected to the network. why FS_Sensing_NR was proposed

Q1.2 What is "3GPP sensing data", in the requirements document's own words?

• The location of a device, as the core network holds it
• Any measurement a base station reports about itself
• Data derived from 3GPP radio signals that an object or environment has reflected, refracted or diffracted

The definition is about what happened to the signal. Something in the world changed the radio on its way, and the data is derived from that change. "3GPP sensing data" as 22.137 defines it

Q1.3 What is a "sensing result"?

• Sensing data once it has been processed for whoever asked for it
• The raw measurement a base station takes
• A report that an object was not found

The requirements document keeps the two apart. Sensing data is the raw material, a sensing result is what a service consumer is given. "Sensing result" as 22.137 defines it

Q1.4 What does the stage 2 specification now being written actually cover?

• Every use case the original study collected
• Aerial objects such as drones, detected and tracked, and nothing else
• Cars, drones and factory robots, but not people

The scope of the stage 2 specification names aerial object detection and tracking and nothing else. It does not say who does the sensing — that the base station is the sensing entity is the security study's wording, not this one's. the scope of 23.137

Q1.5 How many pieces of work does the 3GPP work plan carry for this subject?

• 14, one per acronym
• 18 entries, under 14 different acronyms
• One study and one work item

Three entries share the acronym Sensing and three share Sensing-CT, so the entry count and the acronym count are different questions with different right answers. 18 Sensing entries in the work plan

Q2.1 What does TR 22.837 say it contains?

• Use cases and potential requirements for sensing services across several industries
• Radio measurements and their accuracy
• The architecture of a sensing network

Its scope names use cases and potential requirements for enhancing the 5G system to provide sensing services, and lists the industries it looked at. the scope of 22.837

Q2.2 Which document has received more change requests than any other in this area?

• TS 23.501, the 5G architecture, with 13
• TR 38.765, the radio study, with none
• TR 22.837, the use-case study, with 46

518 documents name TR 22.837 and 46 of those are change requests, more than any other document in this record has received. TR 22.837

Q2.3 Which single meeting handled more sensing documents than any other?

• SA2 meeting 175
• The SA plenary that opened the first study
• SA1 meeting 101, with 154 of them

S1-101 handled 154 sensing documents, more than any other meeting in the local record. The requirements group did its heaviest work early. S1-101 handled 154 Sensing documents, more than any other meeting

Q2.4 Which document opened the very first study on this subject?

• SP-260297, at an SA plenary
• RP-234069, at a RAN plenary
• SP-220084, at an SA plenary

SP-220084 is the new study item description that opened the SA1 study at SA#95-e, and it is the oldest opening document in this record. SP-220084

Q2.5 How much of the use-case study's ambition is in the stage 2 specification being written now?

• All of it, one clause per use case
• One slice — aerial objects such as drones, detected by base stations
• None of it; the study was abandoned

The stage 2 scope narrows to aerial object detection and tracking, while the study listed driving, V2X, drones, 3D maps, smart cities, smart homes, factories, healthcare and shipping. the scope of 23.137

Q3.1 What is a pCR, and why are there so many of them here?

• Proposed text for a study report, which is how a study is written
• A comment on somebody else's paper
• A change to a published specification, proposed by one company

2036 of the 3492 documents are pCRs. A study report is assembled out of proposed text, so an area still doing studies is mostly pCRs. 2036 Sensing documents of type pCR

Q3.2 How many of the area's documents are change requests to a live specification?

• 2036
• 968
• 136

136 of 3492. A change request is the only way a published specification is ever altered, and there are very few of them here. 136 Sensing documents of type CR

Q3.3 What does a version number below 1.0.0 tell you?

• The document is a draft, not a published report
• The document belongs to Release 1
• The document was rejected

TR 33.777 stands at 0.6.0, which means the security study is still being written. Approved reports in this area sit at 19.4.0, 20.0.0 or 20.1.0. TR 33.777

Q3.4 When a study item needs changing, what happens to it?

• It is closed and a new study item is opened
• It is revised, and the revision is the document the work plan points at
• It is merged into the specification it was going to produce

The second radio study was revised at RAN#109 and again at RAN#110, and RP-253246 is the revision the work plan now points at. RP-253246

Q3.5 What is a liaison statement in this record?

• A vote taken between two plenaries
• A summary of a meeting
• A document one group sends to another

38 documents are outgoing liaisons. SA2 sent one on what needed coordinating with RAN, and RAN3 replied with a document of its own. 38 Sensing documents of type LS out

Q4.1 Which group filed more sensing documents than any other?

• RAN1, the physical-layer group
• SA2, the architecture group, with 995
• SA1, the requirements group

SA2 filed 995 documents over 10 meetings, the largest count of any group in this record, ahead of RAN1's 872 and SA1's 640. SA2

Q4.2 Which group spent the most meetings on sensing?

• SA2, across 10
• SA1, across 11
• RAN1, across 16 meetings

RAN1 has documents at 16 meetings, from RAN1#116 to RAN1#126 — more meetings than any other group spent on the subject. RAN1

Q4.3 How many separate meetings have had a sensing document on the table?

• 14
• 79
• 3492

79 meetings across all the groups and plenaries. 3492 is the document count and 14 is the number of work item acronyms. 79 meetings have had Sensing documents on the table

Q4.4 RAN2 appears in this record with exactly one document. What is it?

• A liaison, not work of its own
• A study item description
• A change request to TS 38.300

RAN2's single document is at RAN2#133 and is a liaison. The group has no sensing work of its own in this record. RAN2

Q4.5 Which group is named as doing half a job but has no entry at all?

• CT3
• RAN4
• CT1

The CT work item names CT3 alongside CT4, but no document at a CT3 meeting carries a sensing acronym yet, so the register has no CT3 entry and no count for it. the objective of Sensing-CT

Q4.6 What does "OPPO filed 163 documents" tell you?

• OPPO wrote 163 of the specifications
• OPPO led the work
• OPPO filed more sensing documents than any other single source

It is a count of paper filed, nothing more. Nothing in this record measures influence, and a working group's own submission is often the collected work of many companies. OPPO filed 163 Sensing documents, more than anyone else

Q5.1 What was the first radio study actually about?

• Channel modelling, so that everybody's simulation of sensing starts from the same assumptions
• Choosing frequencies for sensing
• Building sensing into base stations

Its stated focus is to define channel modelling aspects supporting object detection and tracking, aiming at a common modelling framework. the objective of FS_Sensing_NR

Q5.2 What is TR 38.901?

• The sensing study report
• The radio channel model, the shared assumptions every 3GPP radio simulation starts from
• The specification of the 5G radio interface

TR 38.901 is the channel model. The Rel-19 sensing study added sensing to it, and 23 of the 26 sensing documents naming it are change requests. TR 38.901

Q5.3 What does "mono-static" mean, as the second radio study writes it?

• A single frequency band
• One base station, serving one drone
• A single radio point where the sensing transmitter and the receiver sit together

The objective spells it out in brackets — a single TRP with co-located sensing transmitter and receiver. the objective of FS_Sensing_NR_bis

Q5.4 What waveform does TR 38.765 take as its baseline?

• Whichever the operator chooses
• CP-OFDM
• A dedicated radar waveform

The report's own scope says CP-OFDM is considered as baseline waveform — the same waveform the network already uses to carry data. the scope of 38.765

Q5.5 Which document approved the second radio study's report?

• RP-251861, which opened it
• RP-261477, at RAN#112
• RP-253246, the last revision of the study item

RP-261477 put TR 38.765 to the RAN plenary at RAN#112, and the report now stands at version 20.0.0. RP-261477

Q6.1 Which group leads the radio rule-writing for sensing?

• RAN1, which led both studies
• RAN3, the group that owns the interfaces between radio nodes
• RAN2, the radio-protocol group

The work item that follows the studies is led by RAN3, and the three radio documents it changes are the overall description, the architecture and F1AP. NR_Sensing_bis

Q6.2 What does the radio work item promise about the phone?

• There will be no UE impacts
• Phones become the sensing receivers
• Phones will need a software update

The objective says so in one sentence — the work specifies gNB-based mono-static sensing for drone use cases and there will be no UE impacts. the objective of NR_Sensing_bis

Q6.3 Which specification is F1AP?

• TS 38.300
• TS 38.401
• TS 38.473

TS 38.473 is F1AP, the protocol between the two halves of a split base station. Five sensing documents name it and none of them is a change request yet. TS 38.473

Q6.4 Why does the work plan carry two entries for the same radio work item?

• It is filed once as the feature and once as its core part, both described by the same document
• One entry is a mistake
• Two groups are doing it in parallel

NR_Sensing_bis and NR_Sensing_bis-Core are both described by RP-261566, and only the core-part entry has a document against it so far. NR_Sensing_bis-Core

Q6.5 How many change requests have reached TS 38.300 and TS 38.401 for sensing?

• The work item does not touch them
• None yet, although both are listed as changed
• Thirteen between them

Both are named by the RAN work item as documents it will change, and neither has a sensing change request in this record. TS 38.300

Q7.1 What does the SA1 work item say it will introduce?

• A radio measurement procedure
• An architecture for sensing
• Numbers the service must hit, and 5G system functional requirements, including configuration and authorisation

The objective is to introduce KPIs and 5G system functional requirements for the wireless sensing service, covering configuration and authorization. the objective of Sensing

Q7.2 What did the requirements work item do to TS 22.261, the general 5G service requirements?

• Added a section pointing at the new document, in four change requests
• Nothing; TS 22.261 is untouched
• Rewrote its sensing clauses

TS 22.261 carries four sensing change requests, and the work item's stated change to it is adding a new section pointing out to the new TS. TS 22.261

Q7.3 What version does TS 22.137 stand at?

• 19.1.0, a Release 19 specification
• 20.0.0, a Release 20 specification
• 0.3.0, a draft

19.1.0. The stage 1 work is the only part of this area that is finished, and the version number is how you can tell. TS 22.137

Q7.4 Where does this record link sensing to 6G?

• In TR 22.870, the 6G use-case study, which carries three documents tagged with a sensing work item
• In the RAN work item
• Nowhere at all

TR 22.870 is the only specification in this record that links the two, and it does so with three documents. TR 22.870

Q7.5 Why does this course say nothing about the objective of the first SA1 study?

• The objective is secret
• The study had no objective
• There is no work item description for it on this machine, so no objective, leadership or target is recorded

FS_Sensing has a work plan entry and an approval document but no description in readable form here. Everything said about it comes from its documents and the report it produced. FS_Sensing

Q8.1 Which group carries the largest share of the sensing documents?

• RAN1, with 872 across sixteen
• SA1, with 640 across eleven
• SA2, with 995 across ten meetings

SA2 has the largest count of any group in this record, and it leads both the architecture study and the architecture rule-writing. SA2

Q8.2 What does the architecture study say it investigates?

• Charging for sensing services
• The radio measurements needed for sensing
• Function enhancement, end-to-end service operations and procedures, based on the requirements in TS 22.137

That is its scope, word for word, with a sub-set of use cases named as examples — commercial, automotive, public safety and emergency services. the scope of 23.700-14

Q8.3 What is a "Sensing Function"?

• A measurement report
• A new base station type
• The logical function involved to support the sensing service

TR 23.700-14 defines it in one line. It is a logical function, which means a responsibility in the architecture, not a box. "Sensing Function" as 23.700-14 defines it

Q8.4 What does the Sensing-ARC work item say it is specifying against?

• The use cases of TR 22.837
• The conclusions reached in clause 8 of TR 23.700-14
• The radio study, TR 38.765

The objective names clause 8 of the study report and then lists the key issues it will turn into specification text, starting with the system architecture to support the sensing service. the objective of Sensing-ARC

Q8.5 How many sensing change requests has TS 23.501 received?

• None yet
• 13
• 302

13 change requests, updating the architecture reference model and the network functions in it. TS 23.502 has 8, for the procedures. TS 23.501

Q8.6 What state is TS 23.137, the stage 2 specification, in?

• Approved at 20.0.0
• A draft at 0.3.0
• Not yet started

0.3.0 — below 1.0.0, so a draft. 262 documents name it, but it is not yet a rule anybody has to follow. TS 23.137

Q9.1 What state is the security study in?

• Approved, at 20.0.0
• Still running, at 0.6.0
• Not yet opened

TR 33.777 stands at 0.6.0, below 1.0.0, so it is a draft. Its documents run to SA3#128 and 226 of them name it. TR 33.777

Q9.2 What is SA6's work item for?

• Charging for sensing
• Developing the application enablement layer architecture and solutions concluded in the Rel-20 study
• Writing the radio measurements

That is the objective in its own words. SA6 works above the network, on the services applications use rather than on the network itself. the objective of Sensing-APP

Q9.3 Which existing SA6 specification has taken the most sensing change requests?

• TS 23.434, with none
• TS 23.286, for vehicles, with three
• TS 23.255, for drone systems, with 22

22 change requests, which fits the whole area narrowing onto drones. TS 23.437 for spatial maps has seven and TS 23.286 for vehicles three. TS 23.255

Q9.4 SA5 runs two separate studies here. What are they about?

• Charging, and managing the network once sensing is in it
• Security and privacy
• Radio and architecture

FS_Sensing_CH is charging, aimed at TR 28.893, and FS_Sensing_OAM is management, aimed at TR 28.895. Both were opened at SA#110. FS_Sensing_CH

Q9.5 What does the CT work add to TS 29.510?

• A new charging record
• Nothing; TS 29.510 is untouched
• Support in the directory every network function registers in, so the sensing function can be registered and found

TS 29.510 has three sensing change requests, updating the registry so that the Sensing Function can register itself and be discovered. TS 29.510

Q9.6 What is TS 29.545?

• The stage 2 architecture specification
• A study report on charging
• The stage 3 protocol specification for the sensing function's services, still at 0.1.0

It is the new protocol specification, created by this work, and one document in this record names it. Stage 3 has only just begun. TS 29.545

Q10.1 How many specifications does this work touch, and out of how many?

• 149 out of 3599
• 27 out of 3599 active 3GPP specifications
• 11 out of 27

27 specifications, against 3599 active ones altogether. It is a small footprint, and most of it is documents this work created itself. 27 specifications this work touches

Q10.2 Which document should somebody new to this subject read first?

• TR 23.700-14, the architecture study
• TS 22.137, the requirements
• TS 23.501, the 5G architecture

It is short and it defines the words every other document in the area uses. Everything else assumes you have read it. TS 22.137

Q10.3 What is TR 38.901 for, outside sensing?

• It is the shared radio channel model every 3GPP radio simulation starts from
• It is the 5G radio specification
• It is the sensing study report

It is the assumption set for radio simulation across all of 3GPP, which is why adding sensing to it had to happen before anything could be evaluated. TR 38.901

Q10.4 Two more specifications were left out of the register. Why?

• Exactly one document names each and no work item does, so a single mention is as likely a filing mistake as a real link
• They belong to another release
• They are secret

The rule was two documents or a work item listing. One document alone is not enough evidence of a link. 2 specifications are named by a single document only

Q10.5 Which specification is the stage 3 protocol for the new function?

• TS 23.137
• TS 29.510
• TS 29.545

TS 29.545, "Sensing Function Services; Stage 3", created by this work and standing at 0.1.0. TS 29.510 is the registry it registers in. TS 29.545

Q11.1 What does the ratio of pCRs to change requests say about this area?

• The change requests were rejected
• It is nearly finished
• It is still mostly writing study reports rather than altering live specifications

2036 documents are proposed text for study reports and 136 are changes to published specifications. The homework far outweighs the rule-writing. 2036 Sensing documents of type pCR

Q11.2 Which document has received the most sensing change requests?

• TS 23.501, the 5G architecture
• TR 22.837, the use-case study, with 46
• TS 23.137, the stage 2 specification

46. The next largest are TR 38.901 with 23 and TS 23.255 with 22. TS 23.501, the document that would matter most, has 13. TR 22.837

Q11.3 Why do the per-year document counts not add up to 3492?

• 78 documents carry no upload time at all
• The years overlap
• Some documents were deleted

The five per-year counts fall short of 3492 by exactly the 78 documents that carry no upload time. 78 Sensing documents carry no upload time

Q11.4 How many of the area's documents are marked Release 20?

• 2069
• 3492
• 1416

2069, against 1416 marked Release 19. Most of this work is still ahead of the record rather than behind it. 2069 Sensing documents marked Rel-20

Q11.5 What is the second largest kind of document here?

• Discussion papers, at 968
• Liaison statements
• Change requests

968 discussion papers — arguments with no text attached. The second largest kind here is somebody making a case rather than proposing words. 968 Sensing documents of type discussion

Q12.1 Which part of this area is completely finished?

• The stage 1 requirements, in Release 19
• The stage 2 architecture
• The protocol work

TS 22.137 stands at 19.1.0 and TR 22.837 at 19.4.0, both approved by the plenary, and no SA1 document on the subject has appeared since. TS 22.137

Q12.2 What state is the security study in?

• A draft at 0.6.0, with documents running to SA3#128
• Withdrawn
• Approved at 20.0.0

Below 1.0.0 means a draft. The security and privacy questions of sensing are not settled. TR 33.777

Q12.3 How many pieces of rule-writing are running at once?

• None; everything is still a study
• One, in SA2
• Four — SA2, SA6, RAN3 and CT4

SA2 writes stage 2, SA6 the application layer, RAN3 the radio side and CT4 stage 3. None of the four has finished. Sensing-ARC

Q12.4 Can this record tell you when Release 20 will be finished?

• No — it holds meeting codes and version numbers, and no date for anything
• Yes, from the work item descriptions

SP-260110 is recorded as approved at SA#111. That is a meeting code, not a date, and nothing here converts one into the other. SP-260110

Q12.5 TR 28.893 stands at 1.0.0 and TR 28.895 at 0.3.0. What is the difference?

• 1.0.0 has reached a version number that is no longer a draft; 0.3.0 is still below one
• 28.895 has been withdrawn
• They are the same state, written by different editors

The charging study has reached 1.0.0 and the management study is at 0.3.0. Both sets of documents run to SA5#167, so both are recent. TR 28.893

Q13.1 Why is searching for the word "sensing" the wrong way to find this work?

• The search is too slow
• The documents do not use the word
• 2053 documents say sensing and mean other work entirely

Sidelink partial sensing, listen-before-talk channel sensing and the separate 6G work all use the word. Everything in this course was found by work item acronym instead. 2053 documents say sensing but mean other work

Q13.2 What does searching by acronym miss?

• Only the oldest documents
• Nothing
• The 440 documents that carry no acronym, including every plenary approval document

A proposal filed before a work item existed has nothing to be tagged with, and plenary approval documents are not tagged either. Search by acronym and by title, and expect the two to disagree. 440 Sensing documents carry no work item acronym

Q13.3 Which acronym returns the most documents?

• Sensing-CT, with 9
• FS_Sensing_NR, with 776
• Sensing, with 128

The first radio study is the largest single acronym in this area, just ahead of the architecture study's 706. 776 documents carrying the work item FS_Sensing_NR

Q13.4 A document number starting RP- comes from where?

• The RAN plenary
• A RAN3 meeting
• RAN working group 1

RP- is the RAN plenary, SP- the SA plenary, CP- the CT plenary. Working groups use S1-, S2-, R1-, R3-, C4- and so on. RP-261566

Q13.5 What is the shortest document that says what a group has promised to do?

• The study report
• The work item description
• The meeting minutes

One document, approved by a plenary, carrying the objective and the list of specifications it will change. RP-261566 is the radio one. RP-261566

Q14.1 What does this record say about why a decision was taken?

• It carries a summary of the argument
• Nothing. A document's status says approved, revised, noted, endorsed, postponed or withdrawn, and stops there
• It carries the discussion for every document

SP-250809 is recorded as "revised" and nothing more. Why it was revised, who asked, and what changed are not in this data. SP-250809

Q14.2 Can this course tell you what the radio study concluded?

• No. The register holds titles, scopes, objectives and counts, and not one number out of the report
• Only the headline result
• Yes, its conclusions are in the register

No key issue, no candidate solution, no evaluation result. Anything you are told about sensing performance did not come from here and cannot be checked here. TR 38.765

Q14.3 Why is every count in this course a floor rather than a total?

• Documents were counted only when they carry a work item acronym, and 440 documents about this subject carry none
• Counting was done by hand
• The database is incomplete

Every plenary approval document is among those 440, as is everything filed before a work item existed to file it under. 440 Sensing documents carry no work item acronym

Q14.4 Which piece of work has no description on this machine at all?

• The CT work item
• The architecture study
• FS_Sensing, the oldest work item

It has a work plan entry and an approval document but no work item description, so no objective, no leadership line and no target document is recorded for it. FS_Sensing

Q14.5 Is sensing the largest or fastest-moving Release 20 topic?

• This record cannot say — nothing here measures any other area of work
• Yes, on the document counts

2069 documents are marked Release 20 for sensing, and nothing in this data counts positioning, or AI, or ambient IoT, so no comparison is possible. 2069 Sensing documents marked Rel-20

Q14.6 Does this record name the people who did the work?

• Yes, every rapporteur
• No. It carries the company or the role a document came from, never a human being's name

RP-234069 is recorded as coming from "Nokia (moderator)". The work item descriptions on this machine do name rapporteurs, and none of those names was put into the register. RP-234069