GSM 11.11 version 6.2.0 - TTFN Smart card pages

(GSM 11.11 version 6.2.0 Release 1997)100TS 100 977 V6.2.0 (1999-05)11.5.12 Enhanced Multi Level Pre-emption and Priority ServiceRequirement:Service n°18 "allocated and activated".Enhanced Multi Level Pre-emption and PriorityRequest: The ME performs the reading procedure with EF eMLPP .Automatic Answer on eMLPP serviceRequest: The ME performs the reading procedure with EF AAeM .Update: The ME performs the updating procedure with EF AAeM .11.5.13 Cell Broadcast Message range identifierRequirement:Service n°30 "allocated and activated".Request: The ME performs the reading procedure with EF CBMIR .Update: The ME performs the updating procedure with EF CBMIR .11.5.14 Depersonalisation Control KeysRequirement:Service n°33 "allocated and activated".Request: The ME performs the reading procedure with EF DCK .11.5.15 Short message status reportRequirement:Request:Update:Service n°35 "allocated and activated".If the status of a stored short message indicates that there is a corresponding status report, the MEperforms the seek function with EF SMSR to identify the record containing the appropriate statusreport. The ME performs the reading procedure with EF SMSR .If a status report is received, the ME first seeks within the SMS record identifiers of EF SMSR for thesame record number it used for the short message in EF SMS . If such a record identifier is found inEF SMSR , it is used for storage. If such a record identifier is not found, then the ME seeks for a freeentry in EF SMSR for storage. If no free entry is found the ME runs the Purge procedure with EF SMSR .If there is still no free entry, the status report is not stored.If the ME found an appropriate record in EF SMSR for storage, it updates the record with the statusreport setting the record identifier in EF SMSR to the appropriate record number of the short messagein EF SMS .The status in EF SMS is updated accordingly (see 10.4.3) by performing the update procedure withEF SMS .Erasure:Purge:The ME runs the update procedure with EF SMSR by at least storing '00' in the first byte of therecord. The ME may optionally update the following bytes with 'FF'.The ME shall read the SMS record identifier (byte 1) of each record of EF SMSR . With each recordthe ME checks the corresponding short messages in EF SMS . If the status (byte 1) of thecorresponding SMS is not equal '1D' (status report requested, received and stored in EF SMSR ), theME shall perform the erasure procedure with the appropriate record in EF SMSR .11.5.16 Network's indication of alertingRequirement: Service n°36 "allocated and activated".Request: The ME performs the reading procedure with EF NIA .ETSI