|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
V4.1 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.1 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.004 |
geran2 |
|
Layer 1 - General Requirements |
The present document defines the service offered by the physical layer (TS 45 series of Technical Specifications) of the MS BS interface (TS 45 and 44 series of Technical Specifications). Its main objective is to be a guidance for the interface between the 3GPP Technical Specifications in the 45 series and the 44 series. It also specifies the format of signalling channels and the order of bit transmission.
As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210.
|
|
|
- | |
V4.2 | |
V5.3 | |
V6.1 | |
V7.1 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.005 |
geran2 |
|
Data Link (DL) Layer General Aspects |
The present document describes in general terms the Link Access Procedures on the Dm channel, LAPDm. The application of this protocol to other channel types is for further study. Details are provided in TS 44.006.
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS to network interface) using the Dm channel.
NOTE: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also TS 44.003.
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.1 | |
V7.2 | |
V8.1 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.3 | |
V5.2 | |
V6.8 | |
V7.2 | |
V8.0 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.012 |
geran2 |
|
Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface |
SMSCB is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS)s. SMSCB messages come from different sources (e.g. traffic reports, weather reports). The source and subject of the SMSCB message is identified by a message identifier in the SMSCB message header. A sequence number in the SMSCB message header enables the MS to determine when a new message from a given source is available.
SMSCB messages are not acknowledged by the MS. Reception of SMSCB messages by the MS is only possible in idle mode. The geographical area over which each SMSCB message is transmitted is selected by the PLMN operator, by agreement with the provider of the information.
A SMSCB message is an end-to-end message that is formatted by/for the SMSCB application, and which is intended for customer viewing. Its format is described in detail in 3GPP TS 23.041. A CB message is any message sent on the basic or extended CBCH (see TS 45.002). It can be an occurrence of a SMSCB message, or a schedule message.
The SMS Cell Broadcast service is designed to minimize the battery usage requirements for a MS. A MS can read the first part of a CB message and then decide whether or not to read the rest of the message. In addition, the network may broadcast Schedule Messages, providing information in advance about the CB messages that will be sent immediately afterwards. The MS may use this scheduling information to restrict reception to those messages the customer is interested in receiving. This SMSCB DRX feature is optional in the network and the MS.
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.013 |
ct1 |
|
Performance requirements on the mobile radio interface |
The present document specifies measurable performance requirements for signalling aspects of Mobile Stations (MS)s. To allow implementation flexibility it has been chosen to specify requirements on the whole Mobile Station rather than to specify requirements on each "OSI layer". As a consequence the performance requirements do not fit conveniently in specifications such as 3GPP TS 24.008 and TS 44.018 (layer 3 only) or TS 44.006 (layer 2 only).
The main aim of the present document is to provide the justification for testing of requirements that are not included in other GSM specifications. Where specific requirements are included in other GSM specifications they are not duplicated here.
MSs have to perform a wide variety of functions. As a consequence most performance measurements have to be made under a set of defined conditions: where necessary, these are included in the present document.
Where necessary certain assumptions are made about the interaction times between the mobile equipment and the SIM. If the (test) SIM does not respond within the assumed time then appropriate allowances shall be made.
Additionally, it is intended that the present document should contain sufficient requirements to enable some undefined network timers in 3GPP TS 24.008 and TS 44.018 to be calculated.
|
|
|
- | |
V4.1 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.014 |
geran2 |
|
Individual equipment type requirements and interworking; Special conformance testing functions |
The present document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by 3rd Generation Partnership Project (3GPP), those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station.
For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within the present document. In this state, the MS must be able to perform all functions specified in the present document; in addition however, the special conformance testing functions must be operational.
The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see TS 51.010-1 Annex 4). SIM, in general, is described in TS 51.011. The ME recognizes the test SIM by the Administrative Data Field.
The present document applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
The present document is part of the 3GPP TS series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
|
|
|
- | |
V4.4 | |
V5.3 | |
V6.4 | |
V7.3 | |
V8.1 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.018 |
geran2 |
|
Mobile radio interface layer 3 specification - Radio Resource Control (RRC) protocol |
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource (RR) management.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007.
|
|
|
- | |
V4.23 | |
V5.23 | |
V6.24 | |
V7.19 | |
V8.11 | |
V9.5 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.021 |
ct3 |
|
Rate adaption on the Mobile Station - Base Station System (MS-BSS) interface |
The present document defines the rate adaptation functions to be used in PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with TS 43.010.
The provision of these functions will depend on the services a particular station is designed to support.
NOTE 1: The present document should be considered together with TS 48.020 (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation.
NOTE 2: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
|
|
- | |
V4.1 | |
V5.2 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.14 | |
V5.14 | |
V6.9 | |
V7.13 | |
V8.6 | |
V9.2 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.1 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.056 |
ct1 |
|
GSM Cordless Telephony System (CTS), Phase 1 - CTS radio interface layer 3 specification |
The present document specifies the procedures used at the CTS radio interface (Reference Point Um*, see TS 03.56) for Call Control (CC), Mobility Management (MM), Radio Resource (RR).
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The CTS control channels are described in TS 03.52.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 04.07.
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.057 |
ct1 |
|
GSM Cordless Telephony System (CTS), Phase 1 - CTS supervising system layer 3 specification |
The present document specifies the procedures used at the CTS system interface with the supervision part i.e. the interface between the CTS-FP and the CTS-SN.
Only CTS regular supervising procedures are described; FMC management is not intended to be standardised.
The present document does not specify the transmission layer but only the layer 3.
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 04.07.
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.23 | |
V5.21 | |
V6.28 | |
V7.21 | |
V8.9 | |
V9.4 | |
V10.1 | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.064 |
ct1 |
|
Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification |
The present document defines the Logical Link Control (LLC) layer protocol to be used for packet data transfer between the Mobile Station (MS) and Serving GPRS Support Node (SGSN).
It defines the frame structure, elements of procedure, format of fields, and procedures for the proper operation of the logical link control layer. It is based on ideas contained in IS-130, ISO 3309, ISO 4335, and ISO 7809 (HDLC of ISO), as well ITU-T Q.920 and Q.921 (LAPD). The concepts, the overview description of LLC layer functions and procedures, and the relationship with other Technical Specifications are described in general terms in 3GPP TS 23.060.
LLC spans from the Mobile Station (MS) to the Serving GPRS Support Node (SGSN). LLC is intended for use with both acknowledged and unacknowledged data transfer.
The frame formats defined for LLC are based on those defined for LAPD and RLP. However, there are important differences between LLC and other protocols, in particular with regard to frame delimitation methods and transparency mechanisms. These differences are necessary for independence from the radio path.
The LLC procedures are modelled upon the concepts of HDLC as outlined in ISO 4335. Data sequence integrity between the data source and data sink is effected by means of a cyclic numbering scheme. An independent numbering scheme is used for each logical data link, as identified by the a data link connection identifier. LLC supports two modes of operation:
|
| - |
Unacknowledged peer-to-peer operation:
| |
| |
A logical link entity may initiate transmissions to a peer entity without prior establishment of a logical connection with the peer entity. LLC does not guarantee in-order delivery. LLC can detect errors in a received frame, and, depending on whether the frame is sent in protected mode or not, either discard or deliver the erroneous frame. No error recovery procedures are defined at the LLC layer. Higher-layer protocols can be used to provide reliability, if needed. This mode of operation is known as Asynchronous Disconnected Mode (ADM).
| |
| - |
Acknowledged peer-to-peer operation:
| |
| |
A balanced data link involves two participating entities, and each entity assumes responsibility for the organisation of its data flow and for error recovery procedures associated with the transmissions that it originates. Each entity operates as both a data source and data sink in a balanced link, allowing information to flow in both directions. This mode of operation is known as Asynchronous Balanced Mode (ABM), and provides a reliable service with in-order delivery.
|
|
|
|
- | |
V4.3 | |
V5.1 | |
V6.2 | |
V7.3 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.065 |
ct1 |
|
Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) |
The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).
The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g. AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer and the Session Management (SM) sub-layer.
The main functions of SNDCP are:
|
| - |
Multiplexing of several PDPs.
| |
| - |
Compression / decompression of user data.
| |
| - |
Compression / decompression of protocol control information.
| |
| - |
Segmentation of a network protocol data unit (N PDU) into Logical Link Control Protocol Data Units (LL PDUs) and re-assembly of LL PDUs into an N PDU.
|
This TS is applicable to GPRS MS and SGSN.
|
|
|
- | |
V4.3 | |
V5.2 | |
V6.6 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.3 | |
V5.0 | |
V6.0 | |
V7.2 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.3 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.071 |
geran2 |
|
Location Services (LCS) - Mobile radio interface layer 3 LCS specification |
The present document contains the coding of information necessary for support of location service operation on the mobile radio interface layer 3 between the LMU and SMLC.
Clause 4 defines generic procedures for the control of location services. In clause 5 location service support procedures are defined. Clause 6 gives the functional definitions and contents of messages for location service operations. Clause 7 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. Clause 6 gives the detailed message format and information elements coding between the LMU and SMLC.
Clause 8 gives the specification of the LMU LCS Protocol (LLP) operations. In clause 9 LMU - SMLC messages, data types and identifiers are given.
This version does not support segmentation of messages.
|
|
|
- | |
V4.3 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
GSM TS 44.118 |
geran2 |
|
Mobile radio interface layer 3 specification, Radio Resource Control (RRC) protocol; Iu mode |
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource management. The Radio Resource Control Protocol (RRC) is specified. RRC is the Radio Resource control plane protocol for Radio Resource management that is used when a mobile station is operating in Iu mode.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007.
|
|
|
- | |
- | |
V5.11 | |
V6.4 | |
V7.2 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
V5.8 | |
V6.5 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
V6.14 | |
V7.9 | |
V8.7 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
GSM TR 44.901 |
geran2 |
|
External Network Assisted Cell Change (NACC) |
This Technical Report provides background information, motivations, concepts and requirements regarding an extended
Network Assisted Cell Change (NACC) feature for external cell change support. Cell change between GERAN and
UTRAN cells is outside the scope of this report, although consideration has been taken in order to allow an easier
extensibility to that case. The extension is based on the Release 4 version of the NACC feature where the mobile station
is only supported by the NACC when performing internal cell re-selection, i.e. within a BSC. The extension of the
feature is for GERAN just affecting BSS and for the core network the SGSN and signalling links between these network
nodes. To support cell changes between GERAN and UTRAN, also the Um and the Uu interfaces are affected.
The evolved Release 4 NACC proposal as described in this TR provides the basis for the detailed Stage 2 and stage 3
specification work. The feature will be developed in a phased approach and a longer-term vision is presented in the
report.
The focus of the TR is to:
|
| - |
Define the requirements on different nodes
| |
| - |
Specify the requirements for the interfaces
| |
| - |
Propose a plan for the work item project
| |
| - |
Evaluation of what does and does not need to be standardised
|
|
|
|
- | |
- | |
V5.1 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|