initial_state stringclasses 3
values | question stringclasses 3
values | process_rules stringclasses 3
values | reachable_state stringclasses 3
values | reasoning_basis stringclasses 3
values | scenario_context stringclasses 3
values | observed_messages stringclasses 3
values | blocking_condition stringclasses 2
values | derived_conclusion stringclasses 3
values | applicable_next_step stringclasses 3
values |
|---|---|---|---|---|---|---|---|---|---|
The UE is deregistered, and a registration attempt is in progress at the AMF. | What is the next applicable step, and what state is reachable immediately before that step? | For this scenario, receipt of Security Mode Complete establishes the security context. The AMF may send Registration Accept only after both the security context is established and the subscription profile states that registration is permitted. Sending Registration Accept changes the UE's registration state to REGISTERE... | Security context established; registration permitted; UE not yet REGISTERED. | Security Mode Complete satisfies the stated security-context condition, and the subscription response explicitly permits registration. The rules require both conditions for Registration Accept, and the observed sequence provides both. | A UE's registration attempt has passed authentication and security activation. Subscription authorization is also complete. Determine the next registration message and the state immediately before it is sent. | 1. UE → AMF: Registration Request. 2. Authentication completes successfully. 3. AMF → UE: Security Mode Command. 4. UE → AMF: Security Mode Complete. 5. AMF retrieves the UE subscription profile; the response states that registration is permitted. | Both prerequisites for Registration Accept are satisfied. The AMF may send Registration Accept; immediately before that message, the security context is established, but the UE has not yet entered REGISTERED. | AMF → UE: Registration Accept. | |
The UE is deregistered. The AMF has no authenticated UE context for this attempt. | What state has been reached, and what next step is permitted by the given rules? | For this scenario, an accepted Authentication Response moves the attempt to AUTHENTICATED. This state does not itself establish a security context. After AUTHENTICATED, and only then, the AMF may send Security Mode Command. The UE can enter REGISTERED only after the later steps specified by additional rules; none are s... | AUTHENTICATED; security context not established; not REGISTERED. | The observed Authentication Response was accepted, which satisfies the stated condition for entering AUTHENTICATED. The rules explicitly distinguish that state from having an established security context and authorize Security Mode Command as the next step. | A UE begins a registration attempt with an AMF. Determine the state reached after the messages listed below and identify the rule-authorized next action. | 1. UE → AMF: Registration Request. 2. AMF → UE: Identity Request. 3. UE → AMF: Identity Response. 4. AMF → UE: Authentication Request. 5. UE → AMF: Authentication Response, accepted by the AMF. | The attempt is AUTHENTICATED, but no security context is established yet. The AMF may send Security Mode Command next. | AMF → UE: Security Mode Command. | |
The UE is deregistered. The AMF has started a registration attempt but has not established a security context. | Can this attempt reach REGISTERED based on the observed messages and rules? Identify the blocking condition. | For this scenario, a rejected Authentication Response moves the attempt to AUTHENTICATION_FAILED. From AUTHENTICATION_FAILED, neither Security Mode Command nor Registration Accept is permitted. The attempt cannot enter REGISTERED unless authentication succeeds in a later attempt; no such attempt or success is present i... | AUTHENTICATION_FAILED; not REGISTERED. | The rejected response directly satisfies the stated condition for AUTHENTICATION_FAILED. The rules explicitly prohibit the steps needed to continue registration from that state, and provide no observed later successful attempt. | A registration attempt fails during authentication. Determine whether the attempt can reach REGISTERED under the rules supplied for this scenario. | 1. UE → AMF: Registration Request. 2. AMF → UE: Authentication Request. 3. UE → AMF: Authentication Response, rejected by the AMF. | The Authentication Response was rejected. From AUTHENTICATION_FAILED, Security Mode Command and Registration Accept are prohibited; no later successful authentication is observed. | No. The attempt cannot reach REGISTERED because authentication failed, and the rules prohibit both Security Mode Command and Registration Accept from the resulting state. |
5G Core Network Registration Procedure Deductive Reasoning Dataset
Focused on 5G core network registration procedures, each example provides an initial state, observed messages, and explicit process rules, then asks the model to infer state changes, eligible next steps, or conditions that block progress. Examples include a derived conclusion and its reasoning basis, supporting the development and evaluation of rule-following and deductive reasoning in telecommunications protocol scenarios. Use the dataset for reasoning SFT, procedure logic validation, and 5G core network question-answering applications.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| question | string | Records the question to be answered using the states, messages, and process rules. |
| initial_state | string | Records the known core network or registration procedure state at the start of the reasoning task. |
| process_rules | string | Records the explicit rules provided in the prompt for determining state changes, next steps, or blocking conditions. |
| reachable_state | string | Specifies a state reachable under the given rules; may be empty when the question does not involve state inference. |
| reasoning_basis | string | Explains how the conclusion follows from the states, messages, and explicit process rules in the prompt. |
| scenario_context | string | Describes the scenario and relevant context for this registration procedure reasoning example. |
| observed_messages | string | Records the registration procedure messages explicitly provided in the prompt and their order. |
| blocking_condition | string | Specifies a condition that prevents the procedure from continuing or makes the target state unreachable; may be empty if there is no blocker or the question is unrelated. |
| derived_conclusion | string | Provides the direct answer inferred from the prompt, including a reachable state, next step, or blocking determination. |
| applicable_next_step | string | Specifies a next step whose rule prerequisites are met and that can be executed under the current conditions; may be empty if none applies or the question is unrelated. |
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
- -