name: RAN
full_form: Radio Access Network
context: UE in RRC_INACTIVE state may send RRC Resume Request message to the RAN to establish RRC connection. When the RAN wants to reject the UE when receiving RRC Resume Request, but the RAN has no AS security context locally, which means the RAN will not fetch AS security context from the initial RAN, the RAN should not set the Wait Time greater than a specific threshold value. However, when the RAN has the AS security context locally, the RAN could set the Wait Time greater than the specific threshold value, and the target RAN should include the Wait Time and RejectMAC-I in the RRC Reject message. NOTE 1: If the RAN is busy, the RAN may not fetch UE context from the initial RAN, because it may involve additional Xn signalling overhead. So, for mobility case, the RAN treat it as the RAN has no AS security context. The RAN should calculate the RejectMAC-I as similar as calculation in clause 6.2.2 with a new input: target C-RNTI. The target C-RNTI is a freshness parameter and it changes even
description: The Radio Access Network (RAN) is a critical component of the telecommunications infrastructure, responsible for providing wireless access to user equipment (UE). It encompasses various network functions, including base stations, radio access technologies, and interfaces, to manage UE connections and mobility.
explanation: Based on the context from 3GPP TS 33.809, RAN is classified as a Network due to its role in managing wireless access, handling UE connections, and facilitating mobility between different network regions.
section_title: 6.16.2.2	Protection of RRC Reject Message in RRC_INACTIVE state
biotag_Context: B-Device,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Network,O,O,B-Protocol,O,O,O,B-Network,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,O,O,B-Network,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O