name: EPS
full_form: Evolved Packet System
context: The UCMF is used for storage of dictionary entries corresponding to either PLMN-assigned or Manufacturer-assigned UE Radio Capability IDs. An AMF may subscribe with the UCMF to obtain from the UCMF new values of UE Radio Capability ID that the UCMF assigns for the purpose of caching them locally. Provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AF that interacts with the UCMF either directly or via the NEF (or via Network Management) using a procedure defined in TS 23.502[ Procedures for the 5G System (5GS) ]  [3]. A UCMF that serves both EPS and 5GS shall require provisioning the UE Radio Capability ID with the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [51] format or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ]  [28] format or both the formats of the UE radio capabilities. The UCMF also assigns the PLMN-assigned UE Radio Capability ID values. Each PLMN-assigned UE Radio Capability ID is also associated to the TAC of the UE model(s) that it is related to. When an AMF requests the UCMF to assign a UE Radio Capability ID for a set of UE radio capabilities, it indicates the TAC of the UE that the UE Radio Capability information is related to. The UCMF stores a Version ID value for the PLMN assigned UE Radio Capability IDs so it is included in the PLMN assigned UE Radio Capability IDs it assigns. This shall be configured in the UCMF. The UCMF may be provisioned with a dictionary of Manufacturer-assigned UE Radio Capability IDs which include a "Vendor ID" that applies to the Manufacturers of these UE, and a list of TACs for which the PLMN has obtained-Manufacturer-assigned UE Radio Capability IDs. A PLMN-assigned UE Radio Capability IDs is kept in the UCMF storage as long as it is associated with at least a TAC value. When a TAC value is related to a UE model that is earmarked for operation based on Manufacturer assigned UE Radio Capability IDs, this TAC value is disassociated in the UCMF from any PLMN assigned UE Radio Capability IDs. For the case that the PLMN is configured to store PLMN assigned IDs in the Manufacturer Assigned operation requested list defined in clause 4.4.1a, the UCMF does not remove from storage any PLMN assigned UE Radio Capability ID no longer used, and rather quarantines it to avoid any future reassignment. A UCMF dictionary entry shall include also the related UE Radio Capability for Paging for each RAT.
description: The Evolved Packet System (EPS) is a Network Function Group that enables the storage and management of UE Radio Capability IDs. The EPS includes components such as the User Equipment (UE), Access and Mobility Management Function (AMF), and the Unified Data Management (UDM). The AMF may subscribe to the UCMF to obtain new values of UE Radio Capability ID for caching purposes.
explanation: The Evolved Packet System (EPS) is classified under the entity type 'Telecommunications System Architecture' because it refers to a specific system architecture designed for telecommunications, which includes various components and their interactions. The description provides an overview of the EPS's role in managing UE Radio Capability IDs, while the explanation clarifies why EPS is categorized as a telecommunications system architecture.
section_title: 6.2.21 UE radio Capability Management Function (UCMF)
biotag_Context: O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,B-Parameter,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Network Function,O,O,O,B-Network,O,B-Technology,O,O,O,O,B-Device,O,O,B-Parameter,O,O,B-Specification,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Specification,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,B-Network,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,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-Network,O,O,B-Device,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network Function,O,O,B-Network,O,B-Device,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,B-Procedure,O,O,O
biotag_Description: O,B-Network,I-Network,I-Network,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,O,O,B-Device,I-Device,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O