name: CDRs
full_form: Call Detail Records
context: This functionality is used by the network to identify traffic to/from Category M UEs, e.g. for charging differentiation. A Category M UE using E-UTRA shall provide a Category M indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [51]. When the UE has provided a Category M indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an LTE-M Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ]  [3] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ]  [34]). When the AMF receives an LTE-M Indication from NG-RAN in an Initial UE Message or from an MME during EPS to 5GS handover, the AMF shall store the LTE-M Indication in the UE context, consider that the RAT type is LTE-M and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF will also receive the RAT Type as LTE-M, when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. The NFs generating CDRs shall include the LTE-M RAT type in their CDRs. Upon AMF change or inter-system mobility from 5GS to EPS, the source AMF shall provide the "LTE-M Indication" to the target AMF or MME as part of the UE context. During EPS to 5GS Mobility Registration Procedure, the AMF shall disregard any "LTE-M Indication" received from the MME in the UE context (see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ]  [26]), and take into account the "LTE-M Indication" received from NG-RAN, as specified above.
description: Call Detail Records (CDRs) are procedure  generated by network functions that contain detailed information about calls or sessions made by users. In the context of Category M UEs differentiation, CDRs play a crucial role in charging differentiation and include the LTE-M RAT type when applicable.
explanation: CDRs are classified as Charging Data Record (CDR) is a record generated by network functions to track and log telecommunications usage data for billing and charging purposes. In LTE-M, the RAT type is included in the CDR to ensure charging differentiation based on the Category M UE's traffic
section_title: 5.31.20 Category M UEs differentiation
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,B-Device,O,B-Technology,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,B-Protocol,O,O,O,O,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-Device,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,B-Protocol,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Specification,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,B-Network Function,O,B-Network,O,B-Technology,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Service,O,O,O,O,B-Network Function,O,B-Connection,O,O,O,B-Connection,O,O,O,O,B-Network Function,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Network Function,O,B-Service,O,O,O,O,B-Service,O,O,O,O,O,B-Network,O,B-Procedure,O,O,O,O,B-Technology,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Technology,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Device,O,O,B-Network,O,B-Technology,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,B-Specification,O,B-Technology,I-Technology,I-Technology,I-Technology,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Device,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O