name: TS
full_form: Technical Specification
context: When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  (i.e. of clauses 3, 4, 5, 6) are performed. If however no such reactions are specified, the MS shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, or MM STATUS depending on the PD) with cause value # 95 "semantically incorrect message". If the message was a GMM message the GMM-STATUS message with cause #95 "semantically incorrect message" shall be returned. If the message was an SM message the SM-STATUS message with cause # 95 "semantically incorrect message" shall be returned. The network should follow the same procedure except that a status message is not normally transmitted. Semantic checking of the Facility information element value part (defined in 3GPP TS 24.08[ None ] 0 [24]) is the subject of the technical specifications 3GPP TS 24.010[ Mobile radio interface  layer 3; Supplementary services specification; General aspects ]  [21] and the 3GPP TS 24.08[ None ] x series.
description: A Technical Specification (TS) is a document published by the 3GPP that outlines the technical details of a specific aspect of mobile telecommunications, such as core network protocols or supplementary services. In this context, TS refers to documents like 3GPP TS 24.008 and 3GPP TS 24.010, which provide detailed specifications for the procedural part of the mobile radio interface layer 3 and supplementary services respectively.
explanation: The abbreviation 'TS' is classified as a Specification because it directly refers to technical documents published by the 3GPP that contain detailed specifications for various aspects of mobile telecommunications. The context provided highlights the importance of these specifications in defining the reactions of network components to semantically incorrect messages and the procedures for handling such situations.
section_title: 8.8 Messages with semantically incorrect contents
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,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-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,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,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O
biotag_Description: O,B-Specification,I-Specification,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Specification,I-Specification,I-Specification,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O