protocol_facts stringclasses 2
values | answer stringclasses 2
values | question stringclasses 2
values | reasoning stringclasses 2
values |
|---|---|---|---|
The UE sends a Registration Request, and the AMF completes the required authentication and security procedures successfully. The AMF then enters Registration Pending and sends a Registration Accept containing a new 5G-GUTI. In this trace's state rules, the UE sends Registration Complete after receiving an Accept that a... | The AMF remains in Registration Pending and may not yet mark the UE as Registered. It transitions to Registered when Registration Complete reaches it. | What is the AMF's current registration state, and may it already mark the UE as Registered? | The facts state that sending Registration Accept places the AMF in Registration Pending, and that receipt of Registration Complete is the required transition condition. Since that message has not reached the AMF, the condition for Registered has not been met. |
The UE is registered and sends a PDU Session Establishment Request for PDU Session ID 7 to the AMF. The AMF forwards the request to the SMF. The SMF returns a PDU Session Establishment Accept for ID 7, and the AMF delivers the corresponding NAS accept to the UE. The UE receives that accept. Under the state rules for th... | PDU Session 7 is established in the control plane. The facts do not establish that user-plane data forwarding is active. | What can be concluded about PDU Session 7, and can the facts establish that user-plane data forwarding is active? | The UE received an accept matching the pending PDU Session ID 7, satisfying the stated rule for control-plane establishment. The separate condition for active user-plane forwarding is not reported, so that conclusion is unsupported. |
5G SA Protocol Flow Deductive Reasoning QA Dataset
This dataset focuses on representative 5G SA procedures, including registration and PDU session establishment, and presents protocol messages, states, and explicit rules as premises. Models use these facts to infer reachable states, identify permitted procedure branches, or assess whether a conclusion is supported, with a rationale for each answer. It is suited to protocol understanding, procedure-state reasoning, and reasoning-oriented supervised fine-tuning.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| answer | string | The conclusion derived from the protocol facts, such as a reachable state, a permitted branch, or whether a claim is supported. |
| question | string | A question asking for a reachable state, an allowed procedure branch, or an assessment of a protocol conclusion based on the provided facts. |
| reasoning | string | A concise derivation linking the provided protocol facts and explicit rules to the answer. |
| protocol_facts | string | Messages, protocol states, and explicit rules provided as premises for deduction. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- 5