hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.3 SCCP messages
| |
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.3.1 E1 link (CCITT Recommendation Q.712)
|
Q.712 subclause 1.4 The Data Acknowledgement (AK) message is not used. Q.712 subclause 1.6 The Data Form 2 (DT2) message is not used. Q.712 subclause 1.7 The Expedited Data (ED) message is not used. Q.712 subclause 1.8 The Expedited Data Acknowledgement (EA) message is not used. Q.712 subclause 1.10 The Protocol Data Unit Error (ERR) message is not used: the inconsistent messages of the SCCP protocol are discarded. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 24 (GSM 08.06 version 7.0.1 Release1998) Q.712 subclause 1.13 The Reset Confirm (RSC) message is not used. Q.712 subclause 1.14 The Reset Request (RSR) message is not used. Q.712 subclause 1.16 The Subsystem-Out-Of-Service-Grant (SOG) message is not used. Q.712 subclause 1.17 The Subsystem-Out-Of-Service-Request (SOR) message is not used. Q.712 subclause 1.21 The Unitdata Service (UDTS) message is not used. Q.712 subclause 2.4 The "credit" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons. Q.712 subclause 2.7 The "error cause" parameter field is not used. Q.712 subclause 2.11 The "receive sequence number" parameter is not used. Q.712 subclause 2.14 The "reset cause" parameter field should not be used. Q.712 subclause 2.16 The "sequencing/segmenting" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.3.2 T1 link (ANSI Specification T1.112.2)
|
T1.112.2 Paragraph 2.4 The Data Acknowledgement (AK) message is not used. T1.112.2 Paragraph 2.6 The Data Form 2 (DT2) message is not used. T1.112.2 Paragraph 2.7 The Expedited Data (ED) message is not used. T1.112.2 Paragraph 2.8 The Expedited Data Acknowledgement (EA) message is not used. T1.112.2 Paragraph 2.10 The Protocol Data Unit Error (ERR) message is not used. Inconsistent messages of the SCCP protocol are discarded. T1.112.2 Paragraph 2.13 The Reset Confirm (RSC) message is not used. ETSI 25 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) T1.112.2 Paragraph 2.14 The Reset Request (RSR) message is not used. T1.112.2 Paragraph 2.16 The Unitdata Service (UDTS) message is not used. T1.112.2 Paragraph 3.4 The Subsystem-Out-Of-Service-Request (SOR) message is not used. T1.112.2 Paragraph 3.5 The Subsystem-Out-Of-Service-Grant (SOG) message is not used. T1.112.2 Paragraph 4.2 The "credit" parameter field is not used for protocol class 2. However, the parameter must still be included in the Inactivity Test (IT) message for syntax reasons. T1.112.2 Paragraph 4.6 The "error cause" parameter field is not used. T1.112.2 Paragraph 4.10 The "receive sequence number" parameter is not used. T1.112.2 Paragraph 4.13 The "reset cause" parameter field should not be used. T1.112.2 Paragraph 4.16 The "sequencing/segmenting" parameter field is not used for protocol class 2. However, the parameter must still be included in the IT message for syntax reasons.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.4 SCCP formats and codes
| |
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.4.1 E1 link (CCITT Recommendation Q.713)
|
Q.713 subclause 3.4 For point-to-point network structures (i.e. direct connections between MSC and BSS) the called party address may consist of the single element: - sub-system number. No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the called party address allow the routing of the message. Then the following encoding of the address indicator may be chosen: X1000010. If a non point-to-point network structure is used then the global title may be required. This is a national concern. Q.713 subclause 3.4.2.2 The SSN values used on the MSC - BSS interface are specified in GSM 03.03 Use of alternative values is a national concern. Q.713 subclause 3.4.2.3 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 26 (GSM 08.06 version 7.0.1 Release1998) Global title: refer to CCITT Recommendation Q.713 subclause 3.4. Q.713 subclause 3.6 Protocol class: the classes 1 and 3 are not used. Q.713 subclauses 3.8, 3.9, 3.10, 3.13, 3.14 Parameters not used. Q.713 subclauses 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16 Messages not used. Q.713 subclause 5.1.1 SOR and SOG not needed.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.4.2 T1 link (ANSI Specification T1.112.3)
|
T1.112.3 Paragraph 3.4 For point-to-point network structures (i.e., direct connections between the MSC and the BSS) the called party address may consist of the single element: - subsystem number No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the called party address allow the routing of the message. Then the following encoding of the address indicator may be chosen: X1000001. Separate SSNs are needed to distinguish BSSAP and MAP; the chosen SSNs are network specific and may need to differ from those assigned to other applications (e.g. TCAP applications). T1.112.3 Paragraph 3.4.2.2 Allocation of the subsystem number is an operator concern. T1.112.3 Paragraph 3.4.2.3 T1.112.3 Paragraph 3.4 T1.112.3 Paragraph 3.6 Protocol class: the classes 1 and 3 are not used. T1.112.3 Paragraph 3.8, 3.9, 3.10, 3.13, 3.14 Parameters are not used T1.112.3 Paragraph 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16 Messages are not used T1.112.3 Paragraph 5.1.1 Subsystem-out-of-service-request (SOR) and Subsystem-out-of-service-grant (SOG) are not needed.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.5 SCCP procedures
| |
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.5.1 E1 link (CCITT Recommendation Q.714)
|
Q.714 subclauses 1.1.2.2, 1.1.2.4 ETSI 27 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Protocol classes 1 and 3 not used. Q.714 subclause 1.1.3 A signalling connection consists of a single connection section. No intermediate nodes are defined in the MSC/BSS protocol. The use of multiple connection sections is a national concern. Q.714 subclause 1.2.1 (b) Not applicable for single connections. Q.714 subclause 2.1 (1.) Global title not used for single connections. Q.714 subclause 2.2.1 Subsystem (SSN) only is present in the called party address for single connections. Q.714 subclause 2.2.2 The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). Q.714 subclause 2.2.2.2 No SCCP translation function is required for single connections. Q.714 subclause 2.3.1 (3) Not applicable for single connections. Q.714 subclause 2.3.2 (4) Not applicable for single connections. Q.714 subclause 3.1.3 Not applicable: no protocol class and flow control negotiations. Q.714 subclause 3.1.5 Not applicable. Q.714 subclause 3.2.2 Not applicable. Q.714 subclause 3.3.4 Not applicable. Q.714 subclause 3.5.1.2 Not applicable. Q.714 subclause 3.5.2 Not applicable. Q.714 subclauses 3.6, 3.7, 3.9, 3.10 Not applicable. Q.714 subclause 4.2 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 28 (GSM 08.06 version 7.0.1 Release1998) Message return not applicable. Q.714 clause 5 Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the OMAP.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
5.5.2 T1 link (ANSI Specification T1.112.4)
|
T1.112.4 Paragraph 1.1.2.2, 1.1.2.4 Protocol classes 1 and 3 are not used. T1.112.4 Paragraph 1.1.3 A signalling connection consists of a single connection section. No intermediate nodes are defined in the MSC to BSS interface. The use of multiple connection sections is a operator option. T1.112.4 Paragraph 1.2.1 (b) Not applicable for single connections. T1.112.4 Paragraph 2.1 (1.) Global title is not used for single connections. T1.112.4 Paragraph 2.2.1 Subsystem number (SSN) only is present in the called party address for single connections. T1.112.4 Paragraph 2.2.2 The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). T1.112.4 Paragraph 2.2.2.2 No SCCP translation function is required for single connections. T1.112.4 Paragraph 2.3.1 (3) Not applicable for single connections. T1.112.4 Paragraph 2.3.2 (4) Not applicable for single connections. T1.112.4 Paragraph 3.1.3 Not applicable. No protocol class and flow control negotiations. T1.112.4 Paragraph 3.1.5 Not applicable. T1.112.4 Paragraph 3.2.2 Not applicable. T1.112.4 Paragraph 3.3.4 Not applicable. T1.112.4 Paragraph 3.5.1.2 ETSI 29 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Not applicable. T1.112.4 Paragraph 3.5.2 Not applicable. T1.112.4 Paragraph 3.6, 3.7, 3.9, 3.10 Not applicable. T1.112.4 Paragraph 4.2 Message return is not applicable. T1.112.4 Paragraph 5 Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the MAP.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6 Use of the SCCP
|
The MTP and the SCCP are used to support signalling messages between the MSC and the BSS. One user function of the SCCP, called BSS Application Part (BSSAP) is defined. In the case of point-to-point calls the BSSAP uses one signalling connection per active Mobile Station having one or more active transactions for the transfer of layer 3 messages. In the case of a voice group or broadcast call there is always one connection per cell involved in the call and one additional connection per BSS for the transmission of layer 3 messages. There is an additional connection for the speaker in a broadcast call or the first speaker in a voice group call up to the point at which the network decides to transfer them to a common channel. Additional connections may also be required for any mobile stations in the voice group or broadcast call which the network decides to place on a dedicated connection. The BSSAP user function is further subdivided into two separate functions: - The Direct Transfer Application sub-Part (DTAP) is used to transfer messages between the MSC and the MS; the layer-3 information in these messages is not interpreted by the BSS. The descriptions of the layer 3 protocols for the MS-MSC information exchange are contained in the 04-series of GSM Technical Specifications. - The BSS Management Application sub-Part (BSSMAP) supports other procedures between the MSC and the BSS related to the MS (resource management, handover control), or to a cell within the BSS, or to the whole BSS. The description of the layer 3 protocol for the BSSMAP information exchange is contained in GSM 08.08. Both connectionless and connection-oriented procedures are used to support the BSSMAP. Rec. GSM 08.08 explains whether connection oriented or connectionless services should be used for each layer 3 procedure. Connection oriented procedures are used to support the DTAP. Section 6.4 deals with the use of connectionless services of the SCCP. A distribution function located in BSSAP, which is reflected in the protocol specification by the layer 3 header defined in section 6.3, performs the discrimination between the data related to those two subparts, as illustrated in GSM 08.08 figure 1. The error handling for the BSSAP header is specified in GSM 08.08. This section describes the use of SCCP connections for MS transactions. Section 6.1 describes the connection establishment procedures. Section 6.2 describes the connection release procedures. Section 6.3 describes the distribution between BSSMAP and DTAP messages and the data transfer over a SCCP connection. The structure of the user data field in the SCCP message is described in sections 6.3 and 6.4 and in figure 3. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 30 (GSM 08.06 version 7.0.1 Release1998)
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1 Connection establishment
|
A new SCCP connection is established when information related to the communication between an MS and the network on a dedicated radio resource has to be exchanged between BSS and MSC, and no such SCCP connection exists between the MSC and the BSS involved for the concerned mobile station. A new SCCP connection for each cell, an additional connection for each BSS, and optionally connections for particular participants in a voice group or broadcast call are established when a voice group or broadcast call is established. A new SCCP connection is also established in the case of an external handover between the cells of one BSS for a point-to-point call, or for participants in a voice group or broadcast call who are supported on a dedicated channel. Various SCCP connection establishment cases have to be distinguished: i) Following an Access Request made by the MS on the Random Access Channel, a dedicated radio resource has been successfully allocated and a layer-2 connection has been established on the allocated resource. The SCCP connection establishment is then initiated by the BSS. ii) The MSC decides to perform an external handover and a new dedicated radio resource has to be reserved in the new BSS. The SCCP connection establishment is then initiated by the MSC. (Note that the old BSS and the new BSS may be the same.) iii) Following a request for a voice group or broadcast call received at a MSC, SCCP connections are established between the MSC and BSS for each cell in the group call area and the MSC and BSS for each BSS in the group call area. This is initiated by the MSC. Note that a SCCP connection for the originator has already been established via case i). iv) During a voice group or broadcast call the network may decide to place some participants on a dedicated channel and will perform SCCP connection establishment to support this channel. Such a decision will normally be based on responses received to notification messages in the case where the notification messages do not contain details of the location of the group or broadcast call channel. The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future. BSS MSC CR {SSN=BSSAP, a1, BSSMAP message} -------------------------------------------> CC {a1,a2, BSSMAP or DTAP message or no user data} <------------------------------------------ or CREF{a2, DTAP message or no user data <------------------------------------------ a1 = source local reference, a2 = destination local reference CC Connection Confirm CR Connection Request CREF Connection Refused Figure 1/08.06: Set-up of SCCP connections on the first BSS/MSC interface ETSI 31 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) BSS MSC CR {SSN=BSSAP, a1, BSSMAP message or no user data} <----------------------------------------- CC {a1, a2, BSSMAP message or no user data} ------------------------------------------> or CREF{a2, BSSMAP message or no user data} ------------------------------------------> a1 = source local reference, a2 = destination local reference CC Connection Confirm CR Connection Request CREF Connection Refused Figure 2/08.06: Set-up of SCCP connections on a new BSS/MSC (handover) interface or for a voice group or broadcast call initiation
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.1 Establishment procedure in case i)
|
In this case, the connection establishment is performed at the reception by the BSS of the first layer-3 message from the MS (piggybacked on the SABM frame). This message (LOCATION UPDATING REQUEST, CM-SERVICE REQUEST, CM REESTABLISHMENT REQUEST, IMSI DETACH, PAGING RESPONSE, or IMMEDIATE SETUP) which contains the identity of the MS is transferred to the MSC together with a cell identification, in a BSSMAP message (COMPLETE L3 INFORMATION) included in the user data field of the SCCP Connection Request message (see figure 1). After the reception of the Connection Request message, the MSC may check, based on the received identity, whether another association already exists for the same Mobile Subscriber. Two options among others are described hereafter: - after the reception of the Connection Request message, the MSC sends a Connection Confirm message and checks based on the received identity, whether another connection already exists for the same Mobile Subscriber. If another connection exists for the same Mobile Subscriber, the resources assigned for this previous connection are released after the identity of the Mobile Subscriber using the new connection has been successfully checked, e.g. by authentication or by ciphering procedure; - If such an association exists, the connection establishment is refused by sending a Connection Refused message. NOTE: The first option allows the new establishments and the reestablishments. - When the SCCP connection is to be established, a Connection Confirm message is sent back to the BSS. This message may optionally contain a BSSMAP or DTAP message in the user data field. If the connection establishment is refused for any reason, a SCCP Connection Refused message is sent back to the BSS. This message may optionally contain, in the user data field, a DTAP message which is forwarded to the MS. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.2 Establishment procedure in case ii)
|
In this case, the connection establishment is undertaken by the MSC as soon as the MSC decides to perform an external handover to a new cell for a point-to-point call or for participants in a voice group or broadcast call who are supported on a dedicated channel. A Connection Request message is sent to the BSS. The user data field of this message may contain the BSSMAP HANDOVER REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 32 (GSM 08.06 version 7.0.1 Release1998) When receiving the Connection Request message, containing the BSSMAP HANDOVER REQUEST message, the BSS allocates the necessary resources for the requested handover. A Connection Confirm message is also returned to the MSC and may contain the BSSMAP HANDOVER REQUEST ACKNOWLEDGEMENT or QUEUEING INDICATION message in the user data field. If the handover resource allocation fails (see TS GSM 08.08) before the SCCP connection is established then the SCCP Connection Refused message may contain the BSSMAP HANDOVER FAILURE message in the user data field. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.3 Establishment procedure in case iii)
|
In this case connection establishment is undertaken by the MSC on the reception of a voice group or broadcast call initiation request. At the reception of the voice group or broadcast call establishment request message, the MSC will determine that a voice group or broadcast call is required and retrieve the required information concerning, inter alia, the affected cells. SCCP connections are then established by the MSC to the BSS for each of these cells. A separate connection is established by the MSC to each affected BSS. A Connection Request message for each cell in the call and for each BSS in the call is sent to the BSS. The user data field of this message may contain the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. When receiving the Connection Request message, containing the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message, the BSS allocates the necessary resources for the requested call. A Connection Confirm message is also returned to the MSC and may contain the VGCS/VBS SETUP ACK, VGCS/VBS ASSIGNMENT RESULT or VGCS/VBS QUEUEING INDICATION message in the user data field. If the resource allocation fails (see GSM 08.08) before the SCCP connection is established then the SCCP Connection Refused message may contain the VGCS/VBS SETUP REFUSE or VGCS/VBS ASSIGNMENT FAILURE message in the user data field. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.4 Establishment procedure in case iv)
|
In this case, the connection establishment may be performed at the request of the BSS or MSC. It will normally be as a result of a response to a notification message for a voice group or broadcast call which is received by the BSS. At the reception of the Connection Request message, the MSC may check, based on the received identity, whether another association already exists for the same MS. If it is not a CM REESTABLISHMENT and such an association exists, the connection establishment is refused. If such an association exists but the new SCCP CR is for a CM REESTABLISHMENT then the old SCCP connection shall be released. When the SCCP connection is to be established, a Connection Confirm message is sent back to the BSS. This message may optionally contain a BSSMAP or DTAP message in the user data field. If the connection establishment is refused for any reason, a SCCP Connection Refused message is sent back to the BSS. This message may optionally contain, in the user data field, a DTAP message which is forwarded to the MS. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.2 Connection release
|
This procedure is always initiated at the MSC side. A connection is released when the MSC realizes that a given signalling connection is no longer required. That may occur, in normal cases: ETSI 33 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) - when a BSSAP release procedure is terminated; - when a handover resource allocation procedure has failed and a signalling connection was established. The MSC sends a SCCP released message. This message shall not contain any user data field. Abnormal cases: a connection failure may be detected by the connection supervision service provided by SCCP. The procedures in that case are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3 Transfer of DTAP and BSSMAP data
|
The DTAP and BSSMAP Layer 3 messages between the MSC and the BSS are contained in the user data field of the exchanged SCCP frames. This field is optional for the Connection Request (CR) (except for BSS originated connections, see section 6.1); Connection Confirm (CC) and Connection Refused (CREF). The use of this field in such frames in the various establishment cases, which allows reduction n in delay and improves efficiency, is described in sections 6.1. The user data field is a mandatory parameter of the Data frames (DT); the user data field always contains either a DTAP or a BSSMAP message.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.1 Distribution function
| |
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.1.1 CCITT Recommendation
|
The distribution of messages between the BSSMAP and DTAP functions and the distribution/multiplexing of DTAP messages to/from the various radio link layer 2 access points are performed in an intermediate layer of protocol between SCCP and Layer 3 later referred as the distribution sublayer. The protocol for this sublayer simply consists of the management of a one or two octet Distribution Data Unit. Each SCCP User Data field necessarily contains such a distribution Data Unit as a header, followed by the length indicator and the actual Layer 3 BSSMAP or DTAP message.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.1.2 ANSI Specification
|
The distribution of messages between the BSSMAP and DTAP functions and the distribution/multiplexing of DTAP messages to/from the various radio link layer 2 access points are performed by a function of BSSAP referred to as a distribution function. The distribution of messages is performed based on a distribution data unit. The distribution data unit includes a Discrimination Parameter (DP) field, which is coded on one octet. One bit (i.e., least significant bit) of the octet referred as a bit D indicates whether it is a DTAP (value D=1) or a BSSMAP (value D=0) message. The other bits of the octet can be used to separate message groups for different air interfaces (Figure below). If a single radio system supports one air interface, the A-interface includes only one message group and no separation between message groups is needed. The case is different when radio system supports multiple air interfaces, and the A- interface includes several message groups. In that case, there must be a mechanism which facilitates the selection of the right message group according to the used air interface. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 34 (GSM 08.06 version 7.0.1 Release1998) SCCP MTP Distributionfunction RSAP DTAP MAP RS DP=0000000D DP =1000000D DTAP MAP RS DP=0100000D DTAP MAP RS ai rinterfac e1 ai rinterfac e2 ai rinterfac e3 Figure 2a: Distribution of message groups according to examples of the air interface types
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.2 Transfer of DTAP messages
|
The DTAP function is in charge of transferring layer 3 messages from the MS (resp from the MSC) to the MSC (resp to the MS) without any analysis of the message contents. The interworking between the layer 2 protocol on the radio side and signalling system 7 at the landside is based on the use of individual SCCP connections for each MS and on the distribution function. The structure of the user data field is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. The Distribution Data Unit consists of two parameters: the Discrimination parameter and the Data Link Connection Identification (DLCI) parameter. The Discrimination parameter, which is set to the "Transparent" value, is coded on one octet, as follows: 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 D The discrimination bit D is set to the "Transparent" value 1. The DLCI parameter is used for MSC to BSS messages to indicate the type of data link connection to be used over the radio interface. In the direction BSS to MSC the DLCI parameter is used to indicate the type of originating data link connection over the radio interface. The DLCI parameter is coded in one octet, as follows: 8 7 6 5 4 3 2 1 C2 C1 0 0 0 S3 S2 S1 C2 C1 represents the control channel identification C2=0; C1=0 indicates that the control channel is not further specified; C2=1; C1=0 represents the FACCH or the SDCCH; C2=1; C1=1 represents the SACCH; other values are reserved. S3 S2 S1 represents the SAPI value used on the radio link, which coding is specified in GSM 04.06. Bits 4, 5 and 6 are spare. The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. ETSI 35 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998)
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.3 Transfer of BSSMAP messages
|
The transfer of BSSMAP messages over a SCCP connection allows the BSSMAP functions in both the MSC and the BSS to identify to which particular Mobile Station association the exchanged message (e.g. assign, handover request, etc..) applies. The structure of the user data field is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. The Distribution Data Unit only consists of the Discrimination parameter, which is set to the "Not Transparent" value. This parameter is coded on one octet, as follows: 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 D The discrimination bit D is set to the "Not Transparent" value 0. The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. The coding of the BSSMAP layer 3 messages is specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.4 Connectionless services
|
Some BSSMAP procedures described in GSM 08.08 use the connectionless services of the SCCP. The structure of the user data field of the unit data message (UDT) is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. The Distribution Data Unit only consists of the Discrimination parameter, which is set to the "Not Transparent" value.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.4.1 Discrimination parameter (CCITT Recommendation)
|
This parameter is coded on one octet, as follows: 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 D The discrimination bit D is set to the "Not Transparent" value 0. The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. The coding of the BSSMAP layer 3 messages is specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.4.2 Discrimination parameter (ANSI Specification)
|
This parameter is coded on one octet, as follows: 8 7 6 5 4 3 2 1 X x X x x x x D The discrimination bit D is set to the "BSSMAP" value 0. The bits indicated with X values denote to air interface message groups as shown in the table “Coding Of The Discrimination Parameter for PCS 1900” (see section 6.3.2.2). ETSI ETSI TS 100 589 V7.0.1 (1999-07) 36 (GSM 08.06 version 7.0.1 Release1998) The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.4.3 User Data Field Structure
|
DTAP BSSMAP +-----------------+ +-----------------+ 1 | DISCRIMINATION | 1 | DISCRIMINATION | +-----------------+ +-----------------+ +-----------------+ 2 | DLCI | +-----------------+ ------------------Distribution Data Unit---------------- +-----------------+ +-----------------+ 3 | LENGTH IND L | 2 | LENGTH IND L | +-----------------+ +-----------------+ ----------------------Length Indicator------------------ +-----------------+ +-----------------+ 4 | LAYER 3 | 3 | LAYER 3 | +-----------------+ +-----------------+ : : : : +-----------------+ +-----------------+ L+3 | MESSAGE | L+2 | MESSAGE | +-----------------+ +-----------------+ ----------------------Layer 3 message------------------- Figure 3/08.06: Structure of the User Data Field
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
7 Use of the SCCP for operations and maintenance
|
O&M messages have to be passed between the O&M functions and the BSS. If the O&M functions use the MSC-BSS interface to transport messages to the BSS, then the SCCP of No.7 should be used. X25 may also be used for the transfer of O&M messages between BSS and OMC, this is not further considered in this Technical Specification.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
7.1 Connectionless service
|
The connectionless service of the SCCP is supported at the BSS for management purposes and can be used for the transport of O&M information. Addressing should be decided by the operator and manufacturer (e.g. by E164 number, this may require additional addressing capability at the BSS). Further information is given concerning the coding of the higher levels of the O&M information in the GSM 12 series of Technical Specifications.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
7.2 Connection oriented services
|
Connection oriented services are also supported by the BSS for management and call control. Connection oriented services can also be used for the transport of O&M information. In order to set up the connection additional addressing capability may be required at the BSS. To use a signalling connection between the BSS and the OMC via the MSC requires the same BSSOMAP-SCCP interface at both the BSS and the OMC.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
7.3 BSS failure
|
If a system failure at the BSS occurs then sufficient MTP functions to allow message transmission and reception should be maintained. ETSI 37 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Annex A (informative): Change history TDoc SPEC CR REV PHAS VERS SUBJECT CAT NEW_V P-99-244 08.06 A007 1 R98 6.0.0 Numbering, addressing and identification B 7.0.0 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 38 (GSM 08.06 version 7.0.1 Release1998) History Document history V7.0.1 July 1999 Publication ISBN 2-7437-3327-6 Dépôt légal : Juillet 1999
|
8b7236eb626bfed891fdc71b1ad04207
|
100 588
|
1 Scope
|
The present document defines the structure of the physical layer (layer 1) of the BSS-MSC interface for supporting traffic channels. Use of the physical layer for supporting Signalling System No.7 signalling links is covered in Technical Specification GSM 08.06. The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium. For the present document only digital transmission will be considered, the use of analogue transmission is a national concern.
|
8b7236eb626bfed891fdc71b1ad04207
|
100 588
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] CCITT Recommendation G.705: "Characteristics required to terminate digital links on a digital exchange". [3] CCITT Recommendation G.709: "Synchronous multiplexing structure". [4] CCITT Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". [5] CCITT Recommendation G.732: "Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s". [6] GSM 08.06: "Digital cellular telecommunications system (Phase 2); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [7] ANSI T1.102-1993: "Digital Hierarchy Electrical Interface". [8] ANSI T1.403-1995: "Carrier to Customer installation, DS1 metallic interface". [9] ANSI T1.107-1995: "Digital Hierarchy Format specification".
|
8b7236eb626bfed891fdc71b1ad04207
|
100 588
|
3 Definitions and abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04 ETSI ETSI TS 100 588 V7.0.1 (1999-07) 6 (GSM 08.04 version 7.0.1 Release 1998)
|
8b7236eb626bfed891fdc71b1ad04207
|
100 588
|
4 Layer 1 Specification
|
All CCITT recommendations referred to are Blue Book. Layer 1 shall utilise digital transmission - at a rate of 2048 kbit/sec with a frame structure of 32 * 64kbit/sec time slots, as specified in CCITT Recommendation G.705 section 3 for E1 interface, or - at a rate of 1544kbit/sec with a frame structure of 24*64 kbit/s time slots, as specified in T1.102 specification for T1 interface. Therefore the physical/electrical characteristics are defined in CCITT Recommendation G.703 for E1 interface or ANSI T1.403 specification T1 interface. The functional characteristics are defined in CCITT Recommendation G.732 section 2 and 3 for E1 interface or ANSI T1.10 specification for T1 interface. Fault conditions should be treated in accordance with CCITT Recommendation G.732 section 4 for E1 interface or ANSI T1.403 specification for T1 interface. Speech encoding shall be the A-law or Mu-law (for North America) as defined in CCITT Recommendation G.711. The idle pattern must be transmitted on every timeslot that is not assigned to a channel, and to every timeslot of a channel that is not allocated to a call. The idle pattern shall be 01010100 in CCITT based systems and 01111111 in ANSI based systems. Synchronisation at the BSS for the transmitted 2048/1544 kbit/sec bit stream shall be derived from the received 2048/1544 kbit/sec bit stream. Data encoding is covered in Technical Specification GSM 08.20. NOTE: A predetermined number of the 56/64kbit/sec time slots may be used for signalling, to one or more base station systems. 56kbit/sec is applicable to T1 interface only. ETSI ETSI TS 100 588 V7.0.1 (1999-07) 7 (GSM 08.04 version 7.0.1 Release 1998) Annex A (Informative): Change History Document history September 1994 First Edition November 1995 Converted into Adobe Acrobat Portable Document Format (PDF) November 1996 Creation of version 5.0.0 (Conversion to a new GTS) February 1998 Inclusion of Harmonisation CR 08.04 A001 ETSI ETSI TS 100 588 V7.0.1 (1999-07) 8 (GSM 08.04 version 7.0.1 Release 1998) History Document history V7.0.1 July 1999 Publication ISBN 2-7437-3313-6 Dépôt légal : Juillet 1999
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
0 Introduction
| |
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
0.1 Scope
|
The present document is an introduction to the GSM 08.0X series of Technical Specifications and deals with the definition of the base station system (BSS) to mobile switching centre (MSC) (referred to as the A-interface) defined for the GSM system. It also introduces Technical Specifications in the GSM 08.20 series, dealing with the support of data services on this interface. The present document gives an overview of the content of the GSM 08.0X and GSM 08.20 series of Technical Specifications explaining how the detailed content of the Technical Specifications is partitioned and how the Technical Specifications can be used to support a full BSS-MSC interface. ETSI ETSI TS 100 587 V7.0.0 (1999-08) 5 (GSM 08.01 version 7.0.0 Release 1998)
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
0.2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] CCITT Recommendation G.703: "Physical/electrical characteristics of hierarchical digital interfaces". [3] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunications services supported by a GSM Public Land Mobile Network (PLMN)". [4] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [5] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [6] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [7] GSM 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)". [8] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) features". [9] GSM 02.08: "Digital cellular telecommunications system (Phase 2+); Quality of service". [10] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". [11] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility". [12] GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)". [13] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules Functional characteristics". [14] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". [15] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)". [16] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". [17] GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring". ETSI ETSI TS 100 587 V7.0.0 (1999-08) 6 (GSM 08.01 version 7.0.0 Release 1998) [18] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [19] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [20] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [21] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [22] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". [23] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". [24] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [25] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [26] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". [27] GSM 08.02: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Interface principles". [28] GSM 08.04: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Layer 1 specification". [29] GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [30] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". [31] GSM 08.20: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [32] GSM 12.00: "Digital cellular telecommunications system (Phase 2+); Objectives and structure of Network Management (NM)". [33] GSM 12.01: "Digital cellular telecommunications system (Phase 2+); Common aspects of GSM Network Management (NM)". [34] GSM 12.07: "Digital cellular telecommunications system (Phase 2+); Operations and performance management". [35] GSM 12.02: "Digital cellular telecommunications system (Phase 2+); Subscriber, Mobile Equipment (ME) and services data administration". [36] GSM 12.03: "Digital cellular telecommunications system (Phase 2+); Security management". [37] GSM 12.04: "Digital cellular telecommunications system (Phase 2+); Performance data measurements". [38] GSM 12.05: "Digital cellular telecommunications system (Phase 2+); Subscriber related event and call data". [39] GSM 12.06: "Digital cellular telecommunications system (Phase 2+); GSM Network change control". ETSI ETSI TS 100 587 V7.0.0 (1999-08) 7 (GSM 08.01 version 7.0.0 Release 1998) [40] GSM 12.10: "Digital cellular telecommunications system (Phase 2+); Maintenance provisions for operational integrity of Mobile Stations (MS)". [41] GSM 12.11: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Base Station System (BSS)". [42] GSM 12.13: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Mobile- services Switching Centre (MSC)". [43] GSM 12.14: "Digital cellular telecommunications system (Phase 2+); Maintenance of location registers". [44] GSM 12.20: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and messages". [45] GSM 12.21: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and message on the A-bis interface". [46] GSM 12.22: "Digital cellular telecommunications system (Phase 2+); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controller (BSC)".
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
0.3 Definitions and abbreviations
|
Abbreviations used in this specification are listed in GSM 01.04
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
1 A-Interface capabilities
|
The BSS-MSC interface shall be capable of supporting all the services offered to GSM users and subscribers. In addition it also allows for the allocation of suitable radio resources within the PLMN, and the operation and maintenance of those resources.
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
2 A-Interface specification objectives
|
The MSC to BSS interface specifications shall allow the following: i) Connection of various manufacturers BSSs to the same MSC; ii) The use of several manufacturers MSCs to the same type of BSS; iii) The use of the same BSS in any PLMN; iv) The use of the same MSC in any PLMN; v) The separate evolution of MSC and BSS technology, and; vi) The separate evolution of O&M facilities; vii) Evolution towards lower speech coding rates; viii) Support of all services defined in the GSM 02 series of Technical Specifications.
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
3 A-Interface characteristics
|
The interface is defined to be at the boundary of the MSC. The MSC to BSS interface is specified by a set of characteristics, including: i) Physical and electromagnetic parameters; ii) Channel structures; iii) Network operating procedures; iv) Operation and Maintenance information support. ETSI ETSI TS 100 587 V7.0.0 (1999-08) 8 (GSM 08.01 version 7.0.0 Release 1998) The definition of the MSC to BSS interface follows a layered approach similar to that in the ISDN. Layer 3 is for the most part based on Technical Specification GSM 04.08 with additional procedures added for the control of radio resources and the identification of transactions using the SCCP. Layer 2 is based on the signalling system No.7 (SS No.7) Message Transfer Part (MTP). Layer 1 is either digital (at 2048 kbit/s, based on CCITT Rec. G703 section 6) or analogue with the data being passed by the use of modems (this latter case is a national option).
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
4 Other specifications on the MSC-BSS interface
|
The full structure of the Technical Specifications specifying the MSC to BSS link are as follows:
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
4.1 Technical Specification GSM 08.02 Interface Principles
|
The present document deals with the functional split between the BSS and the MSC. This functional split is then supported by the other Technical Specifications in the GSM 08.0X series. Technical Specification GSM 08.02 also contains some information on the placement of transcoders/rate adapters, these being functionally part of the BSS though a degree of freedom is allowed in their geographical location. Lastly Technical Specification GSM 08.02 explains the use of transparent and non transparent signalling information across the interface. The key point is that the majority of call related signalling from the MS is passed in a fairly transparent way through the BSS.
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
4.2 Technical Specification GSM 08.04 Layer 1 - Specification
|
The present document defines the physical layer at the BSS-MSC interface point. The physical interface chosen is a 2Mbits/s (32*64kbits/s) interface according to the standard CCITT recommendations. The speech coding called up in the present document is standard A-law, coding of the traffic bit streams for data calls is dealt with in Technical Specifications GSM 04.21 & GSM 08.20. 4.3 Technical Specification GSM 08.06 Signalling Transport Mechanism - Specification In order to pass the signalling information between BSS and MSC some reliable transport mechanism has to be used. The basis of the transport mechanism is an internationally agreed protocol known as signalling system No.7. Several services are required from this protocol but two key requirements are that messages can be transferred between the BSS and MSC without corruption, and secondly that a transaction with a particular mobile can be identified. The correct transfer of messages without corruption is handled by the "Message Transfer Part" of SS No.7 and this is documented in Technical Specification GSM 08.06 which is an exceptions document to the CCITT specification. The subset so formed is designed so that it is compatible with a "full" MTP such as might be provided at an MSC. The identification of the transaction involved implies some form of logical connection. This is achieved by using the signalling connection control part (SCCP) of SS No.7. Again a minimum subset is formed in order to ease implementation. ETSI ETSI TS 100 587 V7.0.0 (1999-08) 9 (GSM 08.01 version 7.0.0 Release 1998)
|
abd9f7e0eacccd252c5ecb0a8a4dc4d0
|
100 587
|
4.4 Technical Specification GSM 08.08 Layer 3 Specification
|
In the present document the application parts are described. There are two currently identified in the BSS to MSC interface protocol, these are the: BSSOMAP; BSSAP. The BSSAP is further subdivided into two subprotocols, the BSSMAP and the DTAP. The BSSMAP and DTAP are fully defined, the BSSOMAP is only supported in terms of a signalling transport ability. The DTAP text is split between Technical Specifications GSM 08.06 and GSM 08.08 but the text in GSM 08.08 defines which layer 3 air interface messages are passed transparently through the BSS and which are analysed at the BSS. The BSSMAP (base station system management application part) is that part of the protocol responsible for all aspects of the radio resource handling at the BSS. The text is structured as a set of procedures which are defined separately and can be employed as felt appropriate by the operator/manufacturer to meet the requirements of the application in which it is being used. The procedures themselves can be driven in different modes depending upon the input parameters received from the MSC or sent from the OMC. The BSSOMAP (base station system operation and maintenance application part) supports all of the O and M communications for the BSS with either the MSC or the BSS. The actual detailed protocol at layer 3 is defined in the 12-series of GSM Technical Specification. 4.5 Technical Specification GSM 08.20 Rate adaption on the BSS-MSC interface The present document describes the means by which the radio interface data rates are adapted to the 64 kbits/s needed at the MSC and vice versa, down to the bit level. ETSI ETSI TS 100 587 V7.0.0 (1999-08) 10 (GSM 08.01 version 7.0.0 Release 1998) History Document history V7.0.0 August 1999 Publication ISBN 2-7437-3360-8 Dépôt légal : Août 1999
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
1 Scope
|
This ETSI Technical Specification (TS) is an introduction to the 05 series of the GSM technical specifications for GSM and DCS 1 800. It is not of a mandatory nature, but consists of a general description of the organization of the physical layer with reference to the technical specifications where each part is specified in detail. It introduces furthermore, the reference configuration that will be used throughout this series of technical specifications.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
1.1 Normative references
|
References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [3] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". [4] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode". [5] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". [6] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [7] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS-BSS) Interface". [8] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [9] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [10] GSM 05.04: "Digital cellular telecommunications system (Phase 2+); Modulation". [11] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". [12] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". [13] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". [14] GSM 03.30: "Digital cellular telecommunications system; Radio network planning aspects". ETSI TS 100 573 V6.1.1 (1998-07) 6 GSM 05.01 version 6.1.1 Release 1997 [15] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2".
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
1.2 Abbreviations
|
Abbreviations used in this TS are listed in GSM 01.04 [1].
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
2 Set of channels
|
The radio subsystem provides a certain number of logical channels that can be separated into two categories according to GSM 04.03 [5] and GSM 03.64 [15]: 1) The traffic channels (TCH): they are intended to carry two types of user information streams: encoded speech and data. Four types of traffic channels are defined: Bm or full-rate (TCH/F), Lm or half-rate (TCH/H), cell broadcast (CBCH), and packet data (PDTCH) traffic channels. For the purpose of this series of technical specifications, the following traffic channels are distinguished: - full rate speech TCH (TCH/FS); - half rate speech TCH (TCH/HS); - 14,4 kbit/s full rate data TCH (TCH/F14.4) - 9,6 kbit/s full rate data TCH (TCH/F9.6); - 4,8 kbit/s full rate data TCH (TCH/F4.8); - 4,8 kbit/s half rate data TCH (TCH/H4.8); - ≤ 2,4 kbit/s full rate data TCH (TCH/F2.4); - ≤ 2,4 kbit/s half rate data TCH (TCH/H2.4); - cell broadcast channel (CBCH); - packet data traffic channel (PDTCH) . All channels are bi-directional unless otherwise stated. Unidirectional downlink full rate channels, TCH/FD are defined as the downlink part of the corresponding TCH/F. Unidirectional uplink full rate channels are FFS. The allocated uplink and downlink PDTCH are used independently of each other. Dependent allocation of uplink and downlink is possible . Multislot configurations for circuit switched connections are defined as multiple (1 up to 8) full rate channels allocated to the same MS. At least one channel shall be bi-directional (TCH/F). The multislot configuration is symmetric if all channels are bi-directional (TCH/F) and asymmetric if at least one channel is unidirectional (TCH/FD). High Speed Circuit Switched Data (HSCSD) is an example of multislot configuration, in which all channels shall have the same channel mode. NOTE: For the maximum number of timeslots to be used for a HSCSD configuration, see GSM 03.34. Multislot configurations for packet switched connections are defined as multiple (1 up to 8) PDTCH/Us and one PACCH for one mobile originated communication, or multiple (1 up to 8) PDTCH/Ds and one PACCH for one mobile terminated communication respectively, allocated to the same MS. In this context allocation refers to the list of PDCH that may dynamically carry the PDTCHs for that specific MS. The PACCH shall be mapped onto one PDCH carrying one PDTCH/U or PDTCH/D. That PDCH shall be indicated in the resource allocation message (see GSM 04.60). ETSI TS 100 573 V6.1.1 (1998-07) 7 GSM 05.01 version 6.1.1 Release 1997 2) The signalling channels: these can be sub-divided into (P)BCCH ((packet) broadcast control channel), (P)CCCH ((packet) common control channel), SDCCH (stand-alone dedicated control channel), (P)ACCH ((packet) associated control channel) and packet timing advance control channel (PTCCH). An associated control channel is always allocated in conjunction with, either a TCH, or a SDCCH. A packet associated control channel is always allocated in conjunction to one or multiple PDTCH, concurrently assigned to one MS. Two types of ACCH for circuit switched connections are defined: continuous stream (slow ACCH) and burst stealing mode (fast ACCH). For the purpose of this series of technical specifications, the following signalling channels are distinguished: - stand-alone dedicated control channel, four of them mapped on the same basic physical channel as the CCCH (SDCCH/4); - stand-alone dedicated control channel, eight of them mapped on a separate basic physical channel (SDCCH/8); - full rate fast associated control channel (FACCH/F); - half rate fast associated control channel (FACCH/H); - slow, TCH/F associated, control channel (SACCH/TF); - slow, TCH/H associated, control channel (SACCH/TH); - slow, TCH/F associated, control channel for multislot configurations (SACCH/M); - slow, SDCCH/4 associated, control channel (SACCH/C4); - slow, SDCCH/8 associated, control channel (SACCH/C8); - packet associated control channel (PACCH); - packet timing advance control channel (PTCCH); - broadcast control channel (BCCH); - packet broadcast control channel (PBCCH); - random access channel (i.e. uplink CCCH) (RACH); - packet random access channel (i.e. uplink PCCCH) (PRACH); - paging channel (part of downlink CCCH) (PCH); - packet paging channel (part of downlink PCCCH) (PPCH); - access grant channel (part of downlink CCCH) (AGCH); - packet access grant channel (part of downlink PCCCH) (PAGCH); - notification channel (part of downlink CCCH) (NCH); - packet notification channel (part of downlink PCCCH) (PNCH). All associated control channels have the same direction (bi-directional or unidirectional) as the channels they are associated to. The unidirectional SACCH/MD is defined as the downlink part of SACCH/M. When there is no need to distinguish between different sub-categories of the same logical channel, only the generic name will be used, meaning also all the sub-categories (SACCH will mean all categories of SACCHs, SACCH/T will mean both the slow, TCH associated, control channels, etc.). The logical channels mentioned above are mapped on physical channels that are described in this set of technical specifications. The different physical channels provide for the transmission of information pertaining to higher layers according to a block structure. ETSI TS 100 573 V6.1.1 (1998-07) 8 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
3 Reference configuration
|
For the purpose of elaborating the physical layer specification, a reference configuration of the transmission chain is used as shown in annex A. This reference configuration also indicates which parts are dealt with in details in which technical specification. It shall be noted that only the transmission part is specified, the receiver being specified only via the overall performance requirements. With reference to this configuration, the technical specifications in the 05 series address the following functional units: - GSM 05.02: burst building, and burst multiplexing; - GSM 05.03: coding, reordering and partitioning, and interleaving; - GSM 05.04: differential encoding, and modulation; - GSM 05.05: transmitter, antenna, and receiver (overall performance). This reference configuration defines also a number of points of vocabulary in relation to the name of bits at different levels in the configuration. It must be outlined, in the case of the encrypted bits, that they are named only with respect to their position after the encryption unit, and not to the fact that they pertain to a flow of information that is actually encrypted.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
4 The block structures
|
The different block structures are described in more detail in GSM 05.03 (Channel coding). A summarized description appears in table 1, in terms of net bit rate, length and recurrence of blocks. ETSI TS 100 573 V6.1.1 (1998-07) 9 GSM 05.01 version 6.1.1 Release 1997 Table 1: Channel block structures Type of channel net bit rate (kbit/s) block length (bits) block recurrence (ms) full rate speech TCH1 13,0 182 + 78 20 half rate speech TCH2 5,6 95 + 17 20 data TCH (14,4 kbit/s) 3 data TCH (9,6 kbit/s)3 14,5 12,0 290 60 20 5 data TCH (4,8 kbit/s)3 6,0 60 10 data TCH (≤ 2,4 kbit/s)3 3,6 36 10 PDTCH (CS-1) 9.05 181 - PDTCH (CS-2) 13.4 268 - PDTCH (CS-3) 15.6 312 - PDTCH (CS-4) 21.4 428 - full rate FACCH (FACCH/F) 9,2 184 20 half rate FACCH (FACCH/H) 4,6 184 40 SDCCH 598/765 (≈ 0,782) 184 3 060/13 (235) SACCH (with TCH)4 115/300 (≈ 0,383) 168 + 16 480 SACCH (with SDCCH)4 PACCH7 299/765 (≈ 0,391) 168 + 16 6 120/13 (≈ 471) BCCH 598/765 (≈ 0,782) 184 3 060/13 (≈ 235) PBCCH6 s*181/120 (≈1.508) 181 120 AGCH5 n*598/765 (≈ 0,782) 184 3 060/13 (≈ 235) PAGCH7 181 NCH5 m*598/765 (≈ 0,782) 184 3 060/13 (≈ 235) PNCH7 181 PCH5 p*598/765 (≈ 0,782) 184 3 060/13 (≈ 235) PPCH7 181 RACH5 r*26/765 (≈ 0,034) 8 3 060/13 (≈ 235) PRACH (8 bit Access Burst)7 8 PRACH (11 bit Access Burst)7 11 CBCH 598/765 (≈ 0,782) 184 3 060/13 (≈ 235) NOTE 1: For full rate speech, the block is divided into two classes according to the importance of the bits (182 bits for class I and 78 bits for class II). NOTE 2: For half rate speech, the block is divided into two classes according to the importance of the bits (95 bits for class I and 17 bits for class II). NOTE 3: For data services, the net bit rate is the adaptation rate as defined in GSM 04.21. NOTE 4: On SACCH, 16 bits are reserved for control information on layer 1, and 168 bits are used for higher layers. NOTE 5: CCCH channels are common to all users of a cell; the total number of blocks (m, n, p, r) per recurrence period is adjustable on a cell by cell basis and depends upon the parameters (BS_CC_CHANS, BS_BCCH_SDCCH_COMB, BS_AG_BLKS_RES and NCP) broadcast on the BCCH and specified in GSM 05.02 and GSM 04.08. NOTE 6: The total number of PBCCH blocks (s) is adjustable on a cell by cell basis and depends upon the parameter BS_PBCCH_BLKS broadcast on the first PBCCH block and specified in GSM 05.02 and GSM 04.08. NOTE 7: The net bit rate for these channels in a cell can change dynamically and depends on how PDCH are configured in a cell, and upon the parameters BS_PBCCH_BLKS, BS_PAG_BLKS_RES and BS_PRACH_BLKS broadcast on the PBCCH and specified in GSM 05.02 and GSM 04.08, as well as upon how certain blocks on the PDCH are used (indicated by the message type). ETSI TS 100 573 V6.1.1 (1998-07) 10 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
5 Multiple access and timeslot structure
|
The access scheme is Time Division Multiple Access (TDMA) with eight basic physical channels per carrier. The carrier separation is 200 kHz. A physical channel is therefore defined as a sequence of TDMA frames, a time slot number (modulo 8) and a frequency hopping sequence. The basic radio resource is a time slot lasting ≈ 576,9 µs (15/26 ms) and transmitting information at a modulation rate of ≈ 270.833 kbit/s (1 625/6 kbit/s). This means that the time slot duration, including guard time, is 156,25 bit durations. We shall describe successively the time frame structures, the time slot structures and the channel organization. The appropriate specifications will be found in GSM 05.02 (multiplexing and multiple access).
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
5.1 Hyperframes, superframes and multiframes
|
A diagrammatic representation of all the time frame structures is in figure 1. The longest recurrent time period of the structure is called hyperframe and has a duration of 3 h 28 mn 53 s 760 ms (or 12 533,76 s). The TDMA frames are numbered modulo this hyperframe (TDMA frame number, or FN, from 0 to 2 715 647). This long period is needed to support cryptographic mechanisms defined in GSM 03.20. One hyperframe is subdivided in 2 048 superframes which have a duration of 6,12 seconds. The superframe is the least common multiple of the time frame structures. The superframe is itself subdivided in multiframes; three types of multiframes exist in the system: - a 26- multiframe (51 per superframe) with a duration of 120 ms, comprising 26 TDMA frames. This multiframe is used to carry TCH (and SACCH/T) and FACCH; - a 51- multiframe (26 per superframe) with a duration of ≈ 235,4 ms (3 060/13 ms), comprising 51 TDMA frames. This multiframe is used to carry BCCH, CCCH (NCH, AGCH, PCH and RACH) and SDCCH (and SACCH/C), or PBCCH and PCCCH. - a 52-multiframe (25.5 per superframe) with a duration of 240 ms, comprising 52 TDMA frames. This multiframe is used to carry PBCCH, PCCCH (PNCH, PAGCH, PPCH and PRACH), PACCH and PDTCH. The 52- multiframe is not shown in Fig. 1, but can be seen as two 26-multiframes, with TDMA frames numbered from 0 to 51. A TDMA frame, comprising eight time slots has a duration of ≈ 4,62 (60/13) ms.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
5.2 Time slots and bursts
|
The time slot is a time interval of ≈ 576,9 µs (15/26 ms), that is 156,25 bit durations, and its physical content is called a burst. Four different types of bursts exist in the system. A diagram of these bursts appears in figure 1. - normal burst (NB): this burst is used to carry information on traffic and control channels, except for RACH. It contains 116 encrypted bits and includes a guard time of 8,25 bit durations (≈ 30,46 µs); - frequency correction burst (FB): this burst is used for frequency synchronization of the mobile. It is equivalent to an unmodulated carrier, shifted in frequency, with the same guard time as the normal burst. It is broadcast together with the BCCH. The repetition of FBs is also named frequency correction channel (FCCH); - synchronization burst (SB): this burst is used for time synchronization of the mobile. It contains a long training sequence and carries the information of the TDMA frame number (FN) and base station identity code (BSIC, see GSM 03.03). It is broadcast together with the frequency correction burst. The repetition of synchronization bursts is also named synchronization channel (SCH); - access burst (AB): this burst is used for random access and is characterized by a longer guard period (68,25 bit durations or 252 µs) to cater for burst transmission from a mobile which does not know the timing advance at the first access (or after handover).This allows for a distance of 35 km. In exceptional cases of cell radii larger than 35 km, some possible measures are described in GSM 03.30. The access burst is used in the (P)RACH , after handover, on the uplink of a channel used for a voice group call in order to request the use of that uplink, as well as on the uplink of the PTCCH to allow estimation of the timing advance for MS in packet transfer mode. ETSI TS 100 573 V6.1.1 (1998-07) 11 GSM 05.01 version 6.1.1 Release 1997 0 1 2 3 4 5 6 2042 2043 2044 2045 2046 2047 0 1 2 3 0 1 1 (26-frame) multiframe = 26 TDMA frames (120 ms) (= 51 (26-frame) multiframes or 26 (51-frame) multiframes) 47 48 49 50 24 25 1 (51-frame) multiframe = 51 TDMA frames (3060/13 ms) 0 1 2 3 46 47 48 49 50 0 1 2 3 4 22 23 24 25 0 1 2 3 4 5 6 7 1 TDM A fram e = 8 tim e slots (120/26 or 4,615 m s) 1 tim e slot = 156,25 bit durations (15/26 or 0,577 m s) (1 bit duration = 48/13 or 3,69 µs) TB Encrypted bits Training sequence Encrypted bits TB GP 8,25 3 58 26 58 3 Fixed bits TB GP 8.25 3 TB Encrypted bits Encrypted bits TB GP 8,25 39 64 3 TB Encrypted bits TB GP 68,25 3 36 41 8 3 39 142 Normal burst (NB) Frequency correction burst (FB) Access burst (AB) (TB: Tail bits - GP: Guard period) 1 superfram e = 1 326 TDM A fram es (6,12 s) Synchronization sequence Synchronization sequence Synchronization burst (SB) 1 hyperfram e = 2 048 superfram es = 2 715 648 TDM A fram es (3 h 28 m n 53 s 760 m s) 3 TB Figure 1: Time frames time slots and bursts ETSI TS 100 573 V6.1.1 (1998-07) 12 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
5.3 Channel organization
|
The channel organization for the traffic channels (TCH), FACCHs and SACCH/T uses the 26-frame multiframe. It is organized as described in figure 2, where only one time slot per TDMA frame is considered. T T T T T T T T T T T T A T T T T T T T T T T T T - T t T t T t T t T t T t A T t T t T t T t T t T a (a) (b) 26 frames = 120 ms (a) case of one full rate TCH T, t: TDMA frame for TCH A, a: TDMA frame for SACCH/T -: idle TDMA frame (b) case of two half rate TCHs t Figure 2: Traffic channel organization The FACCH is transmitted by pre-empting half or all of the information bits of the bursts of the TCH to which it is associated (see GSM 05.03). The channel organization for the control channels (except FACCHs and SACCH/T) uses the 51-frame multiframe. It is organized in the downlink and uplink as described in figure 3. The channel organization for packet data channels uses the 52- multiframe. It is organized as described in figure 2a. 52 TDMA Frames B0 B1 B2 X B3 B4 B5 X B6 B7 B8 X B9 B10 B11 X X = Idle frame B0 - B11 = Radio blocks Figure 2a: 52- multiframe for PDCHs
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
6 Frequency hopping capability
|
The frequency hopping capability is optionally used by the network operator on all or part of its network. The main advantage of this feature is to provide diversity on one transmission link (especially to increase the efficiency of coding and interleaving for slowly moving mobile stations) and also to average the quality on all the communications through interferers diversity. It is implemented on all mobile stations. The principle of slow frequency hopping is that every mobile transmits its time slots according to a sequence of frequencies that it derives from an algorithm. The frequency hopping occurs between time slots and, therefore, a mobile station transmits (or receives) on a fixed frequency during one time slot (≈ 577 µs) and then must hop before the time slot on the next TDMA frame. Due to the time needed for monitoring other base stations the time allowed for hopping is approximately 1 ms, according to the receiver implementation. The receive and transmit frequencies are always duplex frequencies. The frequency hopping sequences are orthogonal inside one cell (i.e. no collisions occur between communications of the same cell), and independent from one cell to an homologue cell (i.e. using the same set of RF channels, or cell allocation). The hopping sequence is derived by the mobile from parameters broadcast at the channel assignment, namely, the mobile allocation (set of frequencies on which to hop), the hopping sequence number of the cell (which allows different sequences on homologue cells) and the index offset (to distinguish the different mobiles of the cell using the same mobile allocation). The non-hopping case is included in the algorithm as a special case. The different parameters needed and the algorithm are specified in GSM 05.02. ETSI TS 100 573 V6.1.1 (1998-07) 13 GSM 05.01 version 6.1.1 Release 1997 In case of multi band operation frequency hopping channels in different bands of operation, e.g. between channels in GSM and DCS, is not supported. Frequency hopping within each of the bands supported shall be implemented in the mobile station. It must be noted that the basic physical channel supporting the BCCH does not hop. ETSI TS 100 573 V6.1.1 (1998-07) 14 GSM 05.01 version 6.1.1 Release 1997 F S C C - D 0 D 0 D 1 D 1 D 2 D 2 D 3 D 3 D 4 D 4 D 5 D 5 D 6 D 6 D 7 D 7 A 0 A 4 D 0 D 0 D 1 D 1 D 2 D 2 D 3 D 3 D 4 D 4 D 5 D 5 D 6 D 6 D 7 D 7 A 0 A 4 A 3 A 1 A 5 A 2 A 6 A 7 - - - - - - - - - - - - A 3 A 1 A 5 A 2 A 6 A 7 - - R D 3 D 3 D 0 D 0 D 1 D 1 D 2 D 2 A 0 A 1 A 3 A 2 F S F S D 3 D 2 D 3 D 2 F S F S D 1 D 0 D 1 D 0 A 2 A 3 A 1 A 0 S: C: A: F: B: D: R: TDMA frame for frequency correction burst TDMA frame for BCCH TDMA frame for SDCCH TDMA frame for RACH BCCH + CCCH (downlink) BCCH + CCCH (uplink) 8 SDCCH/8 (uplink) 8 SDCCH/8 (downlink) BCCH + CCCH 4 SDCCH/4 (downlink) BCCH + CCCH 4 SDCCH/4 (uplink) TDMA frame for synchronization burst TDMA frame for CCCH TDMA frame for SACCH/C 51 fram es 235.38 m s » R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R F S B C F B C S F S C C F S C C F S C C C C F S C C F S F S B C R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R Figure 3: Channel organization in the 51-frame multiframe ETSI TS 100 573 V6.1.1 (1998-07) 15 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7 Coding and interleaving
| |
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7.1 General
|
A brief description of the coding schemes that are used for the logical channels mentioned in clause 2, plus the synchronization channel (SCH, see subclause 5.2), is made in the following tables. For all the types of channels the following operations are made in this order: - external coding (block coding); - internal coding (convolutional coding); - interleaving. After coding the different channels (except RACH and SCH) are constituted by blocks of coded information bits plus coded header (the purpose of the header is to distinguish between TCH and FACCH blocks). These blocks are interleaved over a number of bursts. The block size and interleaving depth are channel dependent. All these operations are specified in GSM 05.03. Type of channel bits/block data+parity+tail1 convolutional code rate coded bits per block interleaving depth TCH/FS 456 8 class I2 182 + 3 + 4 1/2 378 class II 78 + 0 + 0 - 78 TCH/HS 228 4 class I3 95+3+6 104/211 211 class II 17+0+0 17 TCH/F14.4 TCH/F9.6 290 + 0 + 4 4*60 + 0 + 4 294/456 244/456 294/456 456 19 19 TCH/F4.8 60 + 0 + 16 1/3 228 19 TCH/H4.8 4*60 + 0 + 4 244/456 456 19 TCH/F2.4 72 + 0 + 4 1/6 456 8 TCH/H2.4 72 + 0 + 4 1/3 228 19 FACCH/F 184 + 40 + 4 1/2 456 8 FACCH/H 184 + 40 + 4 1/2 456 6 SDCCHs SACCHs BCCH NCH AGCH PCH CBCH 184 + 40 + 4 1/2 456 4 RACH 8 + 6 + 4 1/2 36 1 SCH 25 + 10 + 4 1/2 78 1 NOTE 1: The tail bits mentioned here are the tail bits of the convolutional code. NOTE 2: The 3 parity bits for TCH/FS detect an error on 50 bits of class I. NOTE 3: The 3 parity bits for TCH/HS detect an error on 22 bits of class I.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7.2 Packet Traffic and Control Channels
|
All packet traffic and control channels, except PRACH, use rectangular interleaving of one Radio Block over four bursts in consecutive TDMA frames. ETSI TS 100 573 V6.1.1 (1998-07) 16 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7.2.1 Channel coding for PDTCH
|
Four different coding schemes, CS-1 to CS-4, are defined for the Radio Blocks carrying RLC data blocks. For the Radio Blocks carrying RLC/MAC Control blocks code CS-1 is always used. The exception are messages that use the existing Access Burst [9] (e.g. Packet Channel Request). An additional coding scheme is defined for the Access Burst that includes 11 information bits. The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection. For CS-1 - CS-3, the second step consists of pre-coding USF (except for CS-1), adding four tail bits and a convolutional coding for error correction that is punctured to give the desired coding rate. For CS-4 there is no coding for error correction. The details of the codes are shown in the table below, including: - the length of each field; - the number of coded bits (after adding tail bits and convolutional coding); - the number of punctured bits; - the data rate, including the RLC header and RLC information. Scheme Code rate USF Pre-coded USF Radio Block excl. USF and BCS BCS Tail Coded bits Punctured bits CS-1 1/2 3 3 181 40 4 456 0 CS-2 ≈2/3 3 6 268 16 4 588 132 CS-3 ≈3/4 3 6 312 16 4 676 220 CS-4 1 3 12 428 16 - 456 - CS-1 is the same coding scheme as specified for SDCCH. It consists of a half rate convolutional code for FEC and a 40 bit FIRE code for BCS (and optionally FEC). CS-2 and CS-3 are punctured versions of the same half rate convolutional code as CS-1 for FEC. CS-4 has no FEC. The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header. All coding schemes are mandatory for MSs supporting GPRS. Only CS-1 is mandatory for the network.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7.2.2 Channel coding for PACCH, PBCCH, PAGCH, PPCH and PNCH
|
The channel coding for the PACCH, PBCCH, PAGCH, PPCH and PNCH is corresponding to the coding scheme CS-1.
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
7.2.3 Channel Coding for the PRACH
|
Two types of packet random access burst may be transmitted on the PRACH: an 8 information bits random access burst or an 11 information bits random access burst called the extended packet random access burst. The MS shall support both random access bursts. The channel coding used for the burst carrying the 8 data bit packet random access uplink message is identical to the coding of the random access burst on the RACH. The channel coding used for the burst carrying the 11 data bit packet random access uplink message is a punctured version of the coding of the random access burst on the RACH
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
8 Modulation
|
The modulation scheme is gaussian MSK (GMSK) with BT = 0,3. As already mentioned the modulation rate is 1 625/6 kbit/s (≈ 270,83 kbit/s). This scheme is specified in detail in GSM 05.04 (Modulation and demodulation). ETSI TS 100 573 V6.1.1 (1998-07) 17 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
9 Transmission and reception
|
The modulated stream is then transmitted on a radio frequency carrier. The frequency bands and channel arrangement are the following. i) Standard or primary GSM 900 Band, P-GSM; For Standard GSM 900 Band, the system is required to operate in the following frequency band: 890 - 915 MHz: mobile transmit, base receive 935 - 960 MHz: base transmit, mobile receive ii) Extended GSM 900 Band, E-GSM (includes Standard GSM 900 band); For Extended GSM 900 Band, the system is required to operate in the following frequency band: 880 - 915 MHz: mobile transmit, base receive 925 - 960 MHz: base transmit, mobile receive iii) Railways GSM 900 Band, R-GSM (includes Standard and Extended GSM 900 Band); For Railways GSM 900 Band, the system is required to operate in the following frequency band: 876 - 915 MHz: mobile transmit, base receive 921 - 960 MHz: base transmit, mobile receive iv) DCS 1 800 Band; For DCS 1 800, the system is required to operate in the following frequency band: 1 710 - 1 785 MHz: mobile transmit, base receive 1 805 - 1 880 MHz: base transmit, mobile receive NOTE 1: The term GSM 900 is used for any GSM system which operates in any 900 MHz band. NOTE 2: The BTS may cover the complete band, or the BTS capabilities may be restricted to a subset only, depending on the operator needs. Operators may implement networks on a combination of the frequency bands above to support multi band mobile stations which are defined in GSM 02.06. The RF channel spacing is 200 kHz, allowing for 194 (GSM 900) and 374 (DCS 1 800) radio frequency channels, thus leaving a guard band of 200 kHz at each end of the subbands. The specific RF channels, together with the requirements on the transmitter and the receiver will be found in GSM 05.05 (Transmission and reception). In order to allow for low power consumption for different categories of mobiles (e.g. vehicle mounted, hand-held, ..), different power classes have been defined. For GSM 900 there are four power classes with the maximum power class having 8 W peak output power (ca 1 W mean output power) and the minimum having 0,8 W peak output power. For DCS 1 800 there are three power classes of 4 W peak output power, 1 W peak output power (ca 0,125 W mean) and 0,25 W peak output power. Multi band mobile stations may have any combinations of the allowed power classes for each of the bands supported. The power classes are specified in GSM 05.05. The requirements on the overall transmission quality together with the measurement conditions are also in GSM 05.05. ETSI TS 100 573 V6.1.1 (1998-07) 18 GSM 05.01 version 6.1.1 Release 1997
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
10 Other layer 1 functions
|
The transmission involves other functions. These functions may necessitate the handling of specific protocols between BS and MS. Relevant topics for these cases are: 1) The power control mechanisms which adjust the output level of the mobile station (and optionally of the base station) in order to ensure that the required quality is achieved with the less possible radiated power. Power levels with 2 dB steps have been defined for that purpose. This is described in GSM 05.08 (radio subsystem link control) and GSM 05.05. 2) The synchronization of the receiver with regard to frequency and time (time acquisition and time frame alignment). The synchronization problems are described in GSM 05.10 (synchronization aspects). 3) The hand-over and quality monitoring which are necessary to allow a mobile to continue a call during a change of physical channel. This can occur either because of degradation of the quality of the current serving channel, or because of the availability of another channel which can allow communication at a lower Tx power level, or to prevent a MS from grossly exceeding the planned cell boundaries. In the case of duplex point-to-point connections, the choice of the new channel is done by the network (base station control and MSC) based on measurements (on its own and on adjacent base stations) that are sent on a continuous basis by the mobile station via the SACCHs. The requirements are specified in GSM 05.08 (radio subsystem link control). 4) The measurements and sub-procedures used in the first selection or reselection of a base station by a mobile are specified in GSM 05.08 (radio subsystem link control). The overall selection and reselection procedures, together with the idle mode activities of a mobile are defined in GSM 03.22 (functions related to MS in idle mode and group receive mode and GPRS mode ). 5) The measurements and sub-procedures used by an MS in selecting a base station for reception of a voice group or a voice broadcast call are specified in GSM 05.08 (radio subsystem link control). The overall voice group and voice broadcast cell change procedures, being similar to the reselection procedures related to the idle mode activities of an MS, are defined in GSM 03.22 (functions related to MS in idle mode and group receive mode and GPRS mode ).
|
c03dccd6ab8811300bb2ead5136d757c
|
100 573
|
11 Performance
|
Under typical urban fading conditions (i.e. multipath delays no greater than 5 µs), the quality threshold for full-rate speech and PDTCH/CS1 is reached at a C/I value of approximately 9 dB. The maximum sensitivity is approximately -104 dBm for base stations and GSM mobiles and -102 dBm and -100 dBm for GSM 900 small MSs (see GSM 05.05) and DCS 1 800 hand-helds, respectively. Multi band MSs shall meet the requirements on each band of operation respectively. ETSI TS 100 573 V6.1.1 (1998-07) 19 GSM 05.01 version 6.1.1 Release 1997 Annex A (informative): Reference configuration cryptological unit interleaving and code 1 code 2 (block) inform ation bits (transm it) burst burst differential encoding m ultiplexing building m odulation transm itter receiver antenna inform ation bits (receive) air inte G SM 05.03 G SM 05.02 GSM 05.04 G SM 05.05 (convolutional) reordering partitioning (4) (3) (2) (1) (4) (5) (6) Interfaces and vocabulary: (1) info + parity bits (2) coded bits (3) interleaved bits (4) encrypted bits (5) m odulating bits (6) inform ation bits (receive) REFERENCE CONFIGURATION ETSI TS 100 573 V6.1.1 (1998-07) 20 GSM 05.01 version 6.1.1 Release 1997 Annex B (informative): Relations between specification 04.07 & 04.08 PRO TOCOLS LAYER 3 LAYER 2 LINK CO NTRO L PRO TOCOLS 03.09 & 05.08 & 03.22 04.05 & 04.06 LAYER 1 PRO TOCOLS 04.04 CHANNEL CODER/DECO DER INTERLEAVING 05.03 ENCRYPTIO N 03.20 & 03.21 M ULTIPLEXING & MULTIPLE ACCESS 05.02 05.04 DEMO DULATO R AND MODULATOR TRANSM ITTER AND RECEIVER 05.05 SPEECH CODER/DECO DER 06 series 05.10 to all blocks Relations between specifications (HAND-OVER, PO W ER CONTRO L) SYNCHRO NIZATION ETSI TS 100 573 V6.1.1 (1998-07) 21 GSM 05.01 version 6.1.1 Release 1997 Annex C (informative): Change control history SPEC SMG CR PHA VERS NEW_VE SUBJECT 05.01 S18 A005 2+ 4.6.0 5.0.0 Addition of ASCI features 05.01 S20 A006 2+ 5.0.0 5.1.0 Introduction of high speed circuit switched data 05.01 s21 A007 2+ 5.1.0 5.2.0 Introduction of R-GSM band 05.01 s22 A009 2+ 5.2.0 5.3.0 Clarification of the frequency definition text in section 05.01 s24 A010 R97 5.3.0 6.0.0 Introduction of GPRS 05.01 s25 A012 R97 6.0.0 6.1.0 14.4kbps Data Service 05.01 s25 A013 R97 6.0.0 6.1.0 Renaming of GPRS RR states ETSI TS 100 573 V6.1.1 (1998-07) 22 GSM 05.01 version 6.1.1 Release 1997 History Document history V6.1.1 July 1998 Publication ISBN 2-7437-2430-7 Dépôt légal : Juillet 1998
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
1 Scope
|
This Technical Specification (TS) defines limited sets of channel types, access capabilities and channel configurations at reference point Um (radio interface).
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
1.1 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 1". [3] GSM 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control and Medium Access Control (RLC/MAC) layer specification". [4] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
1.2 Abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
2 General definitions
|
A channel represents a specified portion of the information-carrying capacity of an interface. Channels are classified by channel types, which have common characteristics. Channel types appearing on the radio interface are specified in clauses 3 and 4. At a given time, the complete interface between a Base Station and the set of Mobile Stations in relation corresponds to some interface structure. The interface structure may change in time. The number of possible different such interface structures can be large. The BS access capability is a description of all the possible interface structures of the considered BS. BS access capabilities are specified in clause 5. At a given moment, the channel configuration of a Mobile Station is the interface structure this Mobile Station actually uses to transmit information to or receive information from the Base Station. The channel configuration may change in time. A limited number of channel configurations are identified, and are specified in clause 6. A Mobile Station access capability is the description of the set of its possible channel configurations. MS access capabilities are specified in clause 7. ETSI ETSI TS 100 552 V7.0.0 (1999-08) 6 (GSM 04.03 version 7.0.0 Release 1998) 3 Channel types and their use: Traffic channels and user channels
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
3.1 User channels
|
User channels are intended to carry a wide variety of user information streams. A distinguishing characteristic is that user channels do not carry signalling information for Connection Management (CM), Mobility Management (MM) or Radio Resource (RR) management. This signalling information is carried over other types of channels, namely the control channels. User channels may be used to provide access to the PLMN and the networks it permits access to. Different types of user channels are distinguished by their rates.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
3.2 Bm Channel
|
A Bm channel is a bi-directional or uni-directional user channel able to carry: - a 13 kbit/s rate bit stream with an error structure and a transmission delay compatible with some grade of service, intended to carry voice encoded according to Technical Specifications in GSM 06-series; or - a bit stream at a rate of 14,5, 12, 6 or 3,6 kbit/s, with an error structure and a transmission delay adapted to a wider range of services, including data transmission; or other kinds of bit stream adapted to a wider range of services (for further study). User information streams are carried on the Bm channel on a dedicated, alternate (within one call or as separate calls), or simultaneous basis, consistent with the Bm channel carrying capability. The following are samples of user information streams: i) voice encoded at 13 kbit/s according to Technical Specifications in GSM 06-series; and ii) data information corresponding to circuit switching user classes of services at bit rates compatible with the channel capability. A Bi-directional Bm Channel uses the radio resources referred to as TCH/F. Bi-directional downlink Bm Channel uses the radio resources referred to as TCH/FD. The Uni-directional Bm Channel is only defined in downlink direction. Traffic channels (TCH) are fixed physical gross rate channels, accompanied with timing (see GSM 05.02).
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
3.3 Lm Channels
|
A Lm channel is a user channel with a carrying capability lower than a Bm channel. A Lm channel is a user channel able to carry: - some bit stream to be defined with an error structure and a transmission delay compatible with some grade of service, intended to carry voice encoded according to a method to be defined; - a bit stream at a rate of 6 or 3.6 kbit/s, with an error structure and a transmission delay adapted to a wider range of services, including data transmission; or - other kinds of bit stream adapted to a wider range of services (for further study). User information streams are carried on a Lm channel on a dedicated, alternate (within one call or as separate calls), or simultaneous basis, consistent with the TCH/H channel carrying capability. The following are samples of user information streams: i) voice encoded at some rate according to a method to be specified in the future; and ETSI ETSI TS 100 552 V7.0.0 (1999-08) 7 (GSM 04.03 version 7.0.0 Release 1998) ii) data information corresponding to circuit switching user classes of services at bit rates compatible with the channel capability. A Lm Channel uses the radio resources referred to as TCH/H. Traffic channels (TCH) are fixed physical gross rate channels, accompanied with timing (see GSM 05.02). 3a Channel types and their use: Packet data traffic channels Packet data traffic channels are used to carry a wide variety of information streams, including user information and signalling information for, e.g., Session Management (SM) and Mobility Management (MM) in packet mode. A distinguishing characteristic is that a packet data traffic channel allows a plurality of information streams, associated with different users, to be multiplexed in a pre-emptive and dynamic fashion. Signalling functions between the MS and the BSS are carried out over other types of channels, namely the control channels. Uni-directional information streams are carried on the packet data traffic channel on an alternate, or simultaneous basis, consistent with the packet data traffic channel carrying capability. The packet data traffic channel uses the radio resources referred to as PDTCH (see GSM 05.02).
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
4 Channel types and their use: Control channels
|
NOTE: The term "Dm channel" may be used to refer to the controls channels used by a Mobile Station at a given moment, independently of their type. (The term "Dm channel" in conjunction with the packet control channels shall be avoided.) Control channels are used to provide all active Mobile Stations with a continuous frame oriented means of communication across the MS-BS interface. A Mobile Station Channel Configuration contains one or more control channels. These control channels may change in time, with the channel configuration. Access management signalling functions are used to insure the continuity when a change in the control channels occurs. Control channels are classified by control channel types, which have common characteristics. These control channel types are specified in subclause 4.1. The control channels are primarily intended to carry signalling information for Connection management (CM), Mobility Management (MM) and Radio Resource (RR) management. In addition to signalling information control channels may also be used to carry other data, including those relating to Short Message Services.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
4.1 Control channel types
| |
cac5298328be863191f60ee4e84455e7
|
100 552
|
4.1.1 Broadcast Control Channel
|
A broadcast control channel is a point-to-multipoint uni-directional control channel, from the fixed sub-system to the Mobile Stations. Broadcast control channels are physically sub-divided into the broadcast control channel (BCCH) and the packet broadcast control channel (PBCCH). BCCH and PBCCH are intended to broadcast a variety of information to MSs, including information necessary for MS to register in the system (e.g. synchronization data). BCCH and PBCCH use a protocol specified in Technical Specifications in GSM 04-Series. ETSI ETSI TS 100 552 V7.0.0 (1999-08) 8 (GSM 04.03 version 7.0.0 Release 1998)
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
4.1.2 Common Control Channel
|
A common control channel is a point-to-multipoint bi-directional control channel. Common control channels are physically sub-divided into the common control channel (CCCH) and the packet common control channel (PCCCH). CCCH and PCCCH are primarily intended to carry signalling information necessary for access management functions (e.g. allocation of dedicated channels or radio resource on a packet data traffic channel). The CCCH can be used for other signalling purposes. CCCH and PCCCH use a layered protocol according to Technical Specifications in GSM 04-Series. In particular the multipoint to point management is achieved through random access techniques. The following terms may be used when the context requires it: - The RACH (Random Access Channel) is the uplink (MS to network) part of the CCCH. - The PRACH (Packet Random Access Channel) is the uplink part of the PCCCH. - The AGCH (Access Grant Channel) is the part of the downlink (network to MS) part of the CCCH reserved for assignment messages. - The PAGCH (Packet Access Grant Channel) is the part of the downlink part of the PCCCH used for assignment messages. - The NCH (Notification Channel) is the part of the downlink part of the CCCH reserved for voice group and/or voice broadcast calls notification messages. - The PNCH (Packet Notification Channel) is the part of the downlink part of the PCCCH reserved for GPRS PTM-M, voice group and/or voice broadcast calls notification messages. - The PCH (Paging Channel) is the remaining part of the downlink part of the CCCH. - The PPCH (Packet Paging Channel) is the remaining part of the downlink part of the PCCCH.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
4.1.3 Dedicated Control Channel
|
A dedicated control channel (DCCH) is a point-to-point bi-directional or uni-directional control channel. DCCHs exist with a variety of bit rates. DCCHs are further classified as follows according to some technical particularities: A SDCCH (Stand-alone DCCH) is a bi-directional DCCH whose allocation is not linked to the allocation of a TCH. The bit rate of a SDCCH is 598/765 kbit/s. A FACCH (Fast Associated DCCH) is a bi-directional DCCH obtained by pre-emptive dynamic multiplexing on respectively a TCH/F or a TCH/H channel. The allocation of a FACCH is obviously linked to the allocation of a TCH. The bit rate of a FACCH is 9 200 or 4 600 bit/s. A SACCH (Slow Associated DCCH) is either a bi-directional or uni-directional DCCH of rate 115/300 or a bi- directional DCCH of rate 299/765 kbit/s. An independent SACCH is always allocated together with a TCH or a SDCCH. The co-allocated TCH and SACCH shall be either both bi-directional or both uni-directional. NOTE 1: A Multislot Configuration (described in clause 6) is an example of a case where uni-directional SACCHs may be used. The terms Bm, or Bm + ACCHs can be used to refer to a Bm channel together with the corresponding FACCH and the co-allocated SACCH when the context avoids any ambiguities. Similar remarks apply to the terms Lm, Lm + ACCHs, Lm + Lm, Lm + Lm + ACCHs. The term SDCCH can be used to refer specifically to a SDCCH together with the co- allocated SACCH when the contexts avoids any ambiguities. NOTE 2: TCH/F is sometimes used to designate Bm associated with its control channel (FACCH and SACCH). TCH/H is sometime used to designate Lm associated with its control channel (FACCH and SACCH). ETSI ETSI TS 100 552 V7.0.0 (1999-08) 9 (GSM 04.03 version 7.0.0 Release 1998) A PACCH (Packet Associated Control Channel) is a bi-directional DCCH obtained by pre-emptive dynamic multiplexing on a PDTCH. A PTCCH (Packet Timing Control Channel) is a bi-directional DCCH carrying synchronization data for a group of up to 16 MSs in packet transfer state (see GSM 04.60). The DCCHs use a layered protocol according to Technical Specifications in GSM 04- and 05-series.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
5 BS access capability
|
The BS access capability is composed of: one BCCH; one CCCH physically related to the BCCH; {{0 to 3 additional CCCHs; and a global resource. OR: BCCH, CCCH plus 4 SDCCHs and a global resource.}} The global resource can be used to accommodate: i) n1 (Bm + FACCH + SACCH); ii) 2n2 (Lm + FACCH + SACCH); iii) 8n3 (SDCCH of rate 598/765 kbit/s + SACCH); iv) n4 (Bm + SACCH); v) n5 (PBCCH + PCCCH + PDTCH + PACCH + PTCCH) ; vi) n6 (PCCCH + PDTCH + PACCH + PTCCH) ; vii)n7 (PBCCH + PCCCH) ; and viii) n8 (PDTCH + PACCH + PTCCH) ; with the constraints: n5 = 0 or 1; n5 > 0 implies that n7 = 0; n7 > 0 implies that n5 = 0 and n6 = 0; and n1 + n2 + n3 + n4 + n5 + n6 + n7 + n8 lower than some value characterizing the BS access capability. The exact use of the global resource may vary in time.
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
6 Channel configurations
|
At a given moment, a Mobile Station accesses only a limited number of the channels appearing on its radio interface. Different compositions for the accessed channels set are identified, and specified below. Different channel configurations are: i) BCCH; ii) CCCH; iii) CCCH + BCCH; ETSI ETSI TS 100 552 V7.0.0 (1999-08) 10 (GSM 04.03 version 7.0.0 Release 1998) iv) SDCCH + SACCH; v) Bm + FACCH + SACCH; vi) Lm + FACCH + SACCH; vii)Lm + Lm + FACCH + SACCH; viii) ( n + m ) Bm + FACCH + ( n + m ) SACCH where n is the number of bi-directional channels and m is the number of uni-directional channels (n = 1..8, m = 0..7, n + m =1..8) ; ix) PCCCH + PBCCH ; x) ( n + m ) PDTCH + PACCH + PTCCH where n is the number of channels allowing information streams in both directions and m is the number of channels allowing information streams in one direction (n = 0..8, m = 0..8, n + m = 1..8). Configuration i) is normally used only in the phase when the physical connection is not set (i.e. just after switch-on, or after a too long interruption of the physical connection due to poor propagation conditions). Configurations ii) or iii) are used by active but idle MS or MS in packet wait state (see GSM 04.60). Configurations iv) is used in phases when only a dedicated control channel is needed. Configurations v) to viii) are used in particular when a circuit-switched communication is in progress. Configuration viii) is a Multislot Configuration. Possible combinations of bi- and uni-directional channels are defined in GSM 05.02. Configuration ix) is used by MS in packet wait state. Configuration x) is a Multislot Configuration on packet data traffic channels. Possible combinations of bi- and uni- directional channels are defined in GSM 05.02. In addition, a MS of GPRS MS class A (see GSM 02.60) may combine one of the configurations i) to viii) (to support GSM circuit switched services and SMS) with one of the configurations ii), iii), ix) or x) (to support GSM GPRS services).
|
cac5298328be863191f60ee4e84455e7
|
100 552
|
6.1 Mandatory capabilities
|
The following access capabilities are mandatory for all MSs. - All MSs shall support the SDCCH. - If a given service is supported by an MS on a TCH/H, this MS shall support this service on a TCH/F (but not necessarily vice versa). - An MS supporting a service on TCH/F shall support the signalling only mode on TCH/F as well as the signalling modes associated with the TCH/F. - An MS supporting a service on TCH/H shall support the signalling only mode on TCH/F as well as the signalling modes associated with the TCH/H. ETSI ETSI TS 100 552 V7.0.0 (1999-08) 11 (GSM 04.03 version 7.0.0 Release 1998) Annex A (informative): Document change history SPEC SMG# CR PHA SE VERS NEW_VE RS SUBJECT 04.03 s24 A005 R97 5.2.0 6.0.0 Introduction of GPRS 04.03 s29 R98 7.0.0 Specification version upgrade to Release 1998 version 7.0.0 ETSI ETSI TS 100 552 V7.0.0 (1999-08) 12 (GSM 04.03 version 7.0.0 Release 1998) History Document history V7.0.0 August 1999 Publication ISBN 2-7437-3342-X Dépôt légal : Août 1999
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
1 Scope
|
A GSM PLMN may be described by a limited set of access interfaces (refer to GSM 04.02 and 02.01) and a limited set of GSM PLMN connection types to support the telecommunication services described in the GSM 02-series of specifications. This Global System for Mobile communications Technical Specification (GTS) identifies and defines these connection types in so far as they relate to the particular network capabilities for a GSM PLMN. The basic lower layer capabilities of a GSM PLMN are represented by a set of GSM PLMN connection types. The definition of a set of GSM PLMN connection types provides the necessary input to identify network capabilities of a GSM PLMN. In addition to describing network capabilities of a GSM PLMN, the identification of connection types facilitates the specification of network-to-network interfaces. It may also assist in the allocation of network performance parameters. The present document should be considered in conjunction with other GSM specifications with particular reference to GSM 01.02, 02.01, 02.02, 02.03, 03.01, 03.02, 04.02 and 04.03. The present document provides a bridge between the service specification in the GSM 02-series of specifications and the more detailed specifications such as the GSM 03, 04, 07 and 09 series. As such, it establishes a framework for the specification and understanding of the more detailed specifications. It is therefore not a specification against which detailed conformance testing can be performed. However, it shall be considered mandatory for the understanding of the more detailed specifications and used to resolve issues of conflict in these specifications.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". [2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [3] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunications services supported by a GSM Public Land Mobile Network (PLMN)". [4] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [5] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [6] GSM 03.01: "Digital cellular telecommunications system (Phase 2+); Network functions". [7] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [8] GSM 03.09: "Digital cellular telecommunications system (Phase 2+); Handover procedures". [9] GSM 03.34: "Digital cellular telecommunications system (Phase 2+); High Speed Circuit Switched Data (HSCSD) - Stage 2 Service Description". ETSI ETSI TS 100 528 V7.0.1 (1999-07) 7 (GSM 03.10 version 7.0.1 Release 1998) [10] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point-to-Point (PP)". [11] GSM 03.41: "Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)". [12] GSM 03.45: "Digital cellular telecommunications system (Phase 2+); Technical realization of facsimile group 3 transparent". [13] GSM 04.01: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface General aspects and principles". [14] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [15] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities". [16] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer; General aspects". [17] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". [18] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [19] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [20] GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [21] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [22] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". [23] GSM 04.22: "Digital cellular telecommunications system (Phase 2+); Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [24] GSM 05.01: "Digital cellular telecommunications system (Phase 2+); Physical layer on the radio path General description". [25] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [26] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". [27] GSM 06.31: "Digital cellular telecommunications system; Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels". [28] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [29] GSM 07.02: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities". [30] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities". [31] GSM 08.04: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Layer 1 specification". [32] GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [33] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". ETSI ETSI TS 100 528 V7.0.1 (1999-07) 8 (GSM 03.10 version 7.0.1 Release 1998) [34] GSM 08.20: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [35] GSM 09.04: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)". [36] GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access". [37] GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services". [38] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". [39] CCITT Recommendation I.460: "Multiplexing, rate adaption and support of existing interfaces". [40] CCITT Recommendation V.110: "Support of Data Terminal Equipments (DTEs) with V-Series interfaces by an integrated services digital network". [41] CCITT Recommendation V.21: "300 bits per second duplex modem standardised for use in the general switched telephone network". [42] CCITT Recommendation V.22: "1 200 bits per second duplex modem standardised for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". [43] CCITT Recommendation V.22bis: "2 400 bits per second duplex modem using the frequency division technique standardised for use on the general switched telephone network and on point-to- point 2-wire leased telephone-type circuits". [44] CCITT Recommendation V.23: "600/1 200-band modem standardised for use in the general switched telephone network". [45] CCITT Recommendation V.24: "List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE)". [46] CCITT Recommendation V.25: "Automatic answering equipment and/or parallel automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls". [47] CCITT Recommendation V.25bis: "Automatic calling and/or answering equipment on the General Switched Telephone Network (GSTN) using the 100-series interchange circuits". [48] CCITT Recommendation V.26bis: "2 400/1 200 bits per second modem standardised for use in the general switched telephone network". [49] CCITT Recommendation V.26ter: "2 400 bits per second duplex modem using the echo cancellation technique standardised for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". [50] CCITT Recommendation V.27ter: "4 800/2 400 bits per second modem standardised for use in the general switched telephone network". [51] CCITT Recommendation V.28: "Electrical characteristics for unbalanced double-current interchange circuits". [52] CCITT Recommendation V.29: "9 600 bits per second modem standardised for use on point-to- point 4-wire leased telephone-type circuits". [53] CCITT Recommendation V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9 600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". [54] CCITT Recommendation V.32bis: "A duplex modem operating at data signalling rates of up to 14 400 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". ETSI ETSI TS 100 528 V7.0.1 (1999-07) 9 (GSM 03.10 version 7.0.1 Release 1998) [55] CCITT Recommendation V.42bis: "Data Compression for Data Circuit terminating Equipment (DCE) using Error Correction Procedures". [56] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". [57] CCITT Recommendation X.21: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for synchronous operation on public data networks". [58] CCITT Recommendation X.21bis: "Use on public data networks of Data Terminal Equipment (DTE) which is designed for interfacing to synchronous V-series modems". [59] CCITT Recommendation X.24: "List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) on public data networks". [60] CCITT Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". [61] CCITT Recommendation X.26: "Electrical characteristics for unbalanced double-current interchange circuits for general use with integrated circuit equipment in the field of data communications". [62] CCITT Recommendation X.27: "Electrical characteristics for balanced double-current interchange circuits for general use with integrated circuit equipment in the field of data communications". [63] CCITT Recommendation X.28: "DTE/DCE interface for a start-stop mode data terminal equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". [64] CCITT Recommendation X.29: "Procedures for the exchange of control information and user data between a Packet Assembly/Disassembly (PAD) facility and a packet mode DTE or another PAD". [65] CCITT Recommendation X.30: "Support of X.21, X.21bis and X.20bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)". [66] CCITT Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". [67] CCITT Recommendation X.32: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and accessing a packet switched public data network through a public switched telephone network or an integrated services digital network or a circuit switched public data network". [68] CCITT Recommendation X.75: "Packet-switched signalling system between public networks providing data transmission services". [69] ITU-T Recommendation V.34 (1994): "A modem operating at data signalling rates of up to 28 800 bits for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". [70] CCITT Recommendation I.440 (1989): "ISDN user-network interface data link layer - General aspects". [71] CCITT Recommendation I.450 (1989): "ISDN user-network interface layer 3 General aspects". [72] ISO/IEC 6429 (1992): "Information technology - Control functions for coded character sets".
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
3 Definitions and Abbreviations
| |
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
3.1 Definitions
|
For the purposes of the present document, the following definitions apply. (DIGITAL) connection: A concatenation of (digital) transmission channels or (digital) telecommunication circuits, switching and other functional units set up to provide for the transfer of (digital) signals between two or more points in a telecommunication network to support a single communication. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 10 (GSM 03.10 version 7.0.1 Release 1998) GSM PLMN connection: A connection that is established through a GSM PLMN between specified GSM PLMN reference points. GSM PLMN connection type: A description of a set of GSM PLMN connections which have the same characteristics.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
3.2 Abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
4 General considerations
|
Low layer capabilities are defined in GSM 02.01 and characterized in GSM 02.02 for Bearer Services and GSM 02.03 for Teleservices. Apart from the short message service, all Bearer Services and Teleservices are provided using low layer capabilities in the connection mode. Network capabilities to support the short message services are defined in GSM 03.40 and GSM 04.11 for the point-to-point service, and in GSM 03.41 and GSM 04.12 for the cell broadcast service. 4.1 Relationship between lower layer capabilities and radio traffic channels The realization of low layer capabilities for the provision of telecommunication services will make use of a physical medium consisting of a traffic channel TCH (refer to GSM 04.03) or a combination of several full rate traffic channels (Multislot configuration for data) except for the short message point-to-point which uses a dedicated control channel DCCH (see GSM 04.11) or the cell broadcast service which uses the CBCH (see GSM 04.12). No multiplexing of data connections on one TCH is allowed. Either a full rate or a half rate channel may be used depending on the requirements of the individual service. User data rates below or equal to 4 800 bit/s may be supported either on a full rate channel or on a half rate channel. User data rate of 9 600 bit/s and 14 400 bit/s are always supported on a full rate channel. Multislot configurations for data use combinations of 4.8 kbit/s or 9.6 kbit/s or 14.4 kbit/s full rate traffic channels only. Technically every MS, regardless of whether it uses a half or a full rate TCH for speech transmission, should be able to use both half and full rate TCHs for data transmission and telematic services. However, particular designs of MS may only provide access to a limited set of services and therefore only use limited options. For the alternate speech and data bearer service and the alternate speech and group 3 facsimile teleservice, when a full rate traffic channel is required for the speech or data portion of the service, a full rate traffic channel will be used for the duration of the call, see GSM 02.02. For the speech followed by data Bearer services, when a full rate traffic channel is required for speech and a half rate traffic channel is required for the data service, a full rate traffic channel will be used for the speech phase of the call. When the data phase is entered, a half rate channel may be used instead. See GSM 02.02. Within a GSM PLMN, the transport of user data and access interface status information (if present) will use a rate adaptation method based on CCITT Recommendation V.110 except on channels using TCH/F14.4 for which a specific rate adaption is used between the mobile station and the interworking function. For the access interface, the rate adaptation schemes used are referenced in the GSM 07-series. On the radio path, rate adaptation leads to rates of 14.5, 12.0, 6.0 and 3.6 kbit/s per TCH (see GSM 04.21). However, in multislot configurations for data the 3.6 kbit/s per TCH/F rate is excluded. At the BSS to MSC interface, the rate adaptation scheme used is described in GSM 08.20. Protection of information from errors on the radio path (i.e. between MS and BSS) will be implemented by use of FEC techniques (see GSM 05.03).
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
4.2 Transparent and non-transparent lower layer capabilities
|
Two classes of low layer capabilities have been identified (see GSM 02.02 and GSM 02.03): ETSI ETSI TS 100 528 V7.0.1 (1999-07) 11 (GSM 03.10 version 7.0.1 Release 1998) - a transparent class which is characterized by constant throughput, constant transit delay and variable error rate; - a non-transparent class for which an ARQ technique is used (see GSM 04.22) on the radio path and extended to an appropriate interworking function. This class is characterized by improved error rate with variable transit delay and throughput. Data compression can optionally be used in combination of non-transparent lower layer capability, to increase the data rate on the DTE/DCE interface (or the equivalent interface depending on the TE type). The considerations described above provide the basis for the definition of a limited set of connection types to be implemented by a GSM PLMN.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
4.3 The GSM environment
| |
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
4.3.1 The hand-over procedure
|
The GSM connection is heterogeneous and merges PCM links and radio path as a unit for the user. One of the most specific characteristics of the mobile networks is the hand-over procedure (see GSM 03.09, 04.08, 05.08, 08.08) which result in a temporary break of the TCH, and consequently in a loss of information. The GSM makes it possible to use one TCH slot for signalling (frame stealing for FACCH) in one TDMA frame resulting in a loss of information. For the transparent data calls, this will result in a period of highly errored stream. For the non-transparent services, the use of the ARQ procedure (GSM 04.22) will overcome this problem. After a hand-over, in case of loss of synchronization, the process to recover synchronization, as described in GSM 09.07 and 04.21 should apply. If data compression is used, V.42bis procedure should apply.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
4.3.2 DTX procedure
|
For the full rate speech traffic channel, DTX function goes along with other procedures such as voice activity detection, generation of comfort noise, and is described in GSM 06.31. For the non-transparent traffic channels, DTX apply according to GSM 08.20.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5 Framework for the description of connection types
| |
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5.1 Introduction
|
A GSM PLMN provides a set of network capabilities which enable telecommunication services to be offered to a user. A GSM PLMN connection is a connection established between GSM PLMN reference points. A GSM PLMN connection type is a way of referring to and describing a GSM PLMN connection. Thus a GSM PLMN connection is a physical or a logical realization of a GSM PLMN connection type. Each GSM PLMN connection can be characterized as belonging to a connection type. Figure 1 illustrates the concepts (see also figure 1 of GSM 02.01). ETSI ETSI TS 100 528 V7.0.1 (1999-07) 12 (GSM 03.10 version 7.0.1 Release 1998) •••••• •••••••••• ••••••••••••••••• ••••••••••••• •••••• • TE ••••••••• • • • •••• • • • • • • ••••• • • • • •••••• TE • •••••• · •GSM PLMN•·•Transit network• •Terminating• · •••••• access • ••• • • Network • • point ••••••••••·••••••••••••••••• ••••••••••••• · • GSM PLMN • • · connection · · •<•••••••••••>• • · Network connection · •<••••••••••••••••••••••••••••••••••••••••••••>• Figure 1: Framework for the description of GSM PLMN connections
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5.2 Purpose of GSM PLMN connection types
|
The definition of a set of GSM PLMN connection types provides the necessary input to identify the network capabilities of a GSM PLMN. Other key requirements of a GSM PLMN are contained in other GSM specifications, in particular GSM 03.01, 04.01 and 04.02. In addition to describing network capabilities of a GSM PLMN, the identification of connection types facilitates the specification of network-to-network interfaces. It may also assist in the allocation of network performance parameters. NOTE 1: The user specifies only the telecommunication service required while the GSM PLMN allocates the resources to set up a connection of the specific type as necessary to support the requested service. It is further noted that, for certain service offerings, additional network functions, e.g. additional lower layer functions and/or higher layer functions, may be required (see figure 2). Service offering Network capability ••••••••••••••••••••• ••••••••••••••••••••••••••• • Telecommunication •<••••••••••••••• Limited set of GSM PLMN • • Service • • connection types • ••••••••••••••••••••• ••••••••••••••••••••••••••• • Additional network • • functions where required• • to support the service, • • e.g., additional lower • • layer functions, higher • • layer functions. • ••••••••••••••••••••••••••• Figure 2: The role of network capabilities in supporting service offerings
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5.3 Functions associated with a GSM PLMN connection
|
Any GSM PLMN connection involves an association of functions to support telecommunication services as shown in figure 3. Three sets of functions are required. i) Connection means - including transmission and switching. ii) Control functions and protocols - including signalling, flow/congestion control and routing functions. iii) Operations and management functions - including network management and maintenance functions. ••••••••••••••••••••••••••••••••••••••••• ••••••••• Connection means for user information •••••••• ••••••••••••••••••••••••••••••••••••••••• • • ••••••••••••• •••••••••••••••••• • Control • • Operations • • functions • • and management • • • • functions • ••••••••••••• •••••••••••••••••• Figure 3: Functional description ETSI ETSI TS 100 528 V7.0.1 (1999-07) 13 (GSM 03.10 version 7.0.1 Release 1998)
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5.4 Applications of GSM PLMN connection types
|
The following situations to which GSM PLMN connection types apply (see figure 4) may arise: - Between two GSM PLMN user access points (refer to GSM 02.01 and 04.02): see figure 4a. - Between a GSM PLMN user access point and a network-to-network interface: see figure 4b. - Between a GSM PLMN user access point and an interface to a specialized resource within the GSM PLMN: see figure 4c. - Between a GSM PLMN user access point and an interface to a specialized resource outside the GSM PLMN: see figure 4d. a) user access point user access point •••••••••••• (Note 1) •••••••••••••• • • • • ••••••••••••••• • • GSM PLMN • • • •••••••••••• • • • •<••••••••••••••••••••••••••••••••••>• GSM PLMN connection b) user access network-to-network point •••••••••••• interface ••••••••••• •••••••••••• • • • • •••••••••••••••• ••••••• Network • • • GSM PLMN • • • • Note 2 • • •••••••••••• • • ••••••••••• •<•••••••••••••••••••••••••••••••••>• GSM PLMN connection c) user access ••••••••••••••••••••••••••••••••••••••••••• point • •••••••••• • •••••••••••••• • • • • • • • • • • • •••••• Note 3 • • • • GSM PLMN • •••••••••• • • ••••••••••••••••••••••••••••••••••••••••••• •<••••••••••••••••••••••••••••••••••>• GSM PLMN connection d) user access network-to-specialized point •••••••••••• resource interface ••••••••••• ••••••••••• • • • • •••••••••••••••• •••••••• Network • • • GSM PLMN • • • • Note 3 • • •••••••••••• • • ••••••••••• •<••••••••••••••••••••••••••••••••>• GSM PLMN connection NOTE 1: See GSM 02.01. NOTE 2: Network means here any fixed network as described in GSM 02.01. NOTE 3: The box represents a specialized resource. Its use originates from a service request. Further study is required to give some examples. Figure 4: Applications of GSM PLMN connection types
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
5.5 GSM PLMN connection involving several networks
|
A GSM PLMN connection may comprise a number of tandem network connections. Figure 5 shows an example in which each end network is a GSM PLMN. The intermediate network(s) must offer the appropriate network capabilities for the service provided by the (overall) GSM PLMN connection. In (overall) GSM PLMN connections involving several networks, each network provides a part of the connection and may be categorized by different attribute values. The IWF/MSC can interwork with different type of networks, e.g.: ETSI ETSI TS 100 528 V7.0.1 (1999-07) 14 (GSM 03.10 version 7.0.1 Release 1998) - analogue (A); - digital circuit (D) with V.110/X.31 in band protocol; - packet (P) with X.25 in band protocol. Examples of such networks are: - GSM (D); - PSPDN (P); - ISDN (A, D, P); - PSTN (A). (Overall) GSM PLMN connection •<••••••••••••••••••••••••••••••••••••••••••••••••••••••>• • • • GSM PLMN Network GSM PLMN • • connection connection connection • •<•••••••••••••••>•<•••••••••••••••••••>•<••••••••••••••>• • •••••••••••• • ••••••••••••••••••• • •••••••••••• • •••••• • • • • •••••• • • • • • • • • •••••• • • • • ••••• access • GSM PLMN • • • Transit Network • • • GSM PLMN •access point •••••••••••• • ••••••••••••••••••• • •••••••••••• point network-to-network network-to-network interface interface Figure 5: Example of a GSM PLMN connection involving several networks
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6 GSM PLMN connection types
| |
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.1 Description of GSM PLMN connection types
|
The characterization of GSM PLMN connection types is done by using a set of attributes. A GSM PLMN connection type attribute is a specific characteristic of a GSM PLMN connection type whose values distinguish it from another GSM PLMN connection type. Particular values are assigned to each attribute when a given GSM PLMN connection type is described and specified. A list of definitions of attributes and values is contained in the annex A to the present document. A GSM PLMN connection type is partitioned into connection elements. This partitioning is based on the two most critical transitions of a connection, firstly, the change of signalling system, secondly, the type of transmission system. In a GSM PLMN, the change in signalling and transmission between the radio interface and the A interface leads to two connection elements, the radio interface connection element and the A interface connection element. Subclause 6.3 describes the relationship between the attributes values of connection elements and connection types. To complete the description of GSM PLMN connection types, the definition of functions within the different entities of a GSM PLMN which are involved in the realization of a GSM PLMN Connection is needed. These functions will be used in subclauses 6.4 and 6.5 to describe the limited set of GSM PLMN connection types. The following functions have been identified: - rate adaptation functions; - the radio link protocol function; - the forward error correction function; - the Layer 2 relay function. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 15 (GSM 03.10 version 7.0.1 Release 1998)
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.1.1 Rate adaptation
|
The RA0 rate adaptation is only used with asynchronous interfaces. Incoming asynchronous data is padded by the addition of stop elements to fit the same or nearest higher synchronous rate defined by 2 to the power n (where n≤ 6) times 600 bit/s, 14.4 kbit/s or 28.8 kbit/s. Thus both 75 and 300 bit/s user data signalling rate shall be adapted to a synchronous 600 bit/s stream. This function is described in GSM 04.21. The RA0 used in GSM is not identical to that described in ITU-T Recommendation V.110 which converts the 14,4 and 28,8 kbit/s user rates to 19,2 and 38,4 kbit/s, respectively. The intermediate rate adaptation function (RA1) is a rate adaptation function which turns either the output of the RA0 function or a synchronous user data stream into a data stream at 8 or 16 kbit/s by bit repetition and frame addition. This function is described in GSM 04.21. The adaptation of intermediate rates to 64 kbit/s (RA2) performs the final conversion from the intermediate rates generated by the RA1 function to 64 kbit/s. The radio interface intermediate rate adaptation function (RA1') is in the case of transparent data transmission a variant of the RA1 function and it adapts synchronous user data stream or the output of the RA0 function to one of the following data rates: 3.6, 6.0 or 12.0 or 14.5 kbit/s over the radio path. For the non-transparent case, the RA1' function provides direct access to the 12.0 or 6.0 kbit/s data rates. This is achieved by allowing the V.110 frame status bits to be used as additional data bits. This function is described in GSM 04.21 and GSM 08.20. RA1’ is not applied in TCH/F14.4 non- transparent operation. For TCH/F14.4 channel coding three GSM-specific adaptation functions are used: namely, RA1’/RAA’, RAA’, and RAA’’ (GSM 08.20). RA1’/RAA’ adapts between the 14.5 air-interface rate and the 16 kbit/s rate used across the Abis- interface. RAA’ adapts between the 16 kbit/s Abis Interface-rate and 16.0 kbit/s A-interface substream. (Up to four such A-interface substreams may be multiplexed into the 64kbit/s A-interface stream.) RAA’’ converts between the A- interface data substream(s) and the overall synchronous stream. In non-transparent operation the RAA’’ converts between the A-interface stream and the 290-bit blocks containing bits M1, M2, and 288 data bits as described in GSM 04.21. In multislot data configurations the intermediate rates 16, 32, and 64 kbit/s are supported on those sections of the network where the overall data stream is not split into multiple channels (GSM 04.21 and 08.20). RA1-adaptation is not applied to rates higher than 38.4 kbit/s. Instead, a GSM-specific rate adaptation function RA1’’ to user rates 48 and 56 kbit/s is applied; this function adapts between these rates and the 64 kbit/s "intermediate" rate. The RA2 function passes rate 64 kbit/s on as such. In multislot data connections, the rate adaptation functions are performed per TCH/F between the Split/Combine- functions. On the A-interface up to four TCH/Fs are multiplexed into one 64 kbit/s channel according to the procedures defined in GSM 08.20. However, multiplexing is not applied to those user rates which make use of more than four TCH/Fs; for such rates the Split/Combine-function is located at the BSS. The splitting and recombining of the data flow into/from TCH/Fs takes place at the RA1-function or RAA“ function (transparent service) at the MSC/IWF and at the MS’s RA1/RA1’- or RA1’-function, or between the RLP and RA1’ (RA1’ not applied to TCH/F14.4) (non-transparent service) at the MS and between RA1 or RAA”and RLP at MSC/IWF (figures 6 and 7). The TCH/Fs are treated as independent channels between the Split/Combine-functions. For user rates requiring more than four TCH/Fs (transparent only) the Split/Combine-function is located at the RA1/RA1’-or RA1’-function at the MS and at the RA1’/RA1-function at the BSS (figures 6 and 7). The rate adaptation functions for the various user data rates are summarized in tables 1 to 3. It should be noted that in the case of synchronous data transmission, the RA0 is not present. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 16 (GSM 03.10 version 7.0.1 Release 1998) Table 1: Rate adaptation functions for the support of TE2 in the transparent case R I/F RA0 RA1' Radio I/F async <------> sync • 2.4 <------> • 2.4 <-------------------------------------------------> 3.6 4.8 <------> 4.8 <-------------------------------------------------> 6.0 9.6 <------> 9.6 <-------------------------------------------------> 12.0 or 2 × 6.0 14.4 <------> 14.4 <-------------------------------------------------> 14.5 or 2 × 12.0 or 3 × 6.0 19.2 <------> 19.2 <-------------------------------------------------> 2 × 12.0 or 4 × 6.0 28.8 <------> 28.8 <-------------------------------------------------> 2 x 14.5 or 3 × 12.0 38.4 <------> 38.4 <-------------------------------------------------> 3 x 14.5 or 4 × 12.0 48.0 <-------------------------------------------------> 4 x 14.5 or 5 × 12.0 56.0 <-------------------------------------------------> 4 x 14.5 or 5 × 12.0 note 1 64.0 <-------------------------------------------------> 5 x 14.5 or 6 × 12.0 note 1 NOTE 1: AIUR of 11.2 kbit/s per 12.0 kbit/s air interface channel (GSM 04.21). Table 2: Rate adaptation functions for the support of TE1/TA in the transparent case RA0 RA1 RA2 S I/F RA2 RA1/RA1' Radio I/F async sync • 2.4 <------> • 2.4 <------> 8 <------> 64 <------> 8 <------> 3.6 4.8 <------> 4.8 <------> 8 <------> 64 <------> 8 <------> 6.0 9.6 <------> 9.6 <------> 16 <------> 64 <------> 16 <------> 12.0 or 2 × 6.0 14.4 <------> 14.4 <------> 32 <------> 64 <------> 32 <------> 14.5 or 2 × 12.0 or 3 × 6.0 19.2 <------> 19.2 <------> 32 <------> 64 <------> 32 <------> 2 × 12.0 or 4 × 6.0 28.8 <------> 28.8 <------> 64 <------> 64 <------> 64 <------> 2 x 14.5 or 3 × 12.0 38.4 <------> 38.4 <------> 64 <------> 64 <------> 64 <------> 3 x 14.5 or 4 × 12.0 RA1'' RA2 S I/F RA2 RA1/RA1' Radio I/F 48.0 <------> 64 <------> 64 <------> 64 <------> 4 x 14.5 or 5 × 12.0 note 1 56.0 <------> 64 <------> 64 <------> 64 <------> 4 x 14.5 or 5 × 12.0 notes 1, 2 64 <------> 64 <------> 64 <------> 5 x 14.5 or 6 × 12.0 notes 1, 2 NOTE 1: RA2 not applicable. NOTE 2: AIUR of 11.2 kbit/s per 12.0 kbit/s air interface channel (GSM 04.21). Table 3: RA1' function in the non-transparent case RA1' 6.0 <------> 6.0 12.0 <------> 12.0 NOTE: RA1’ not applicable to TCH/F14.4
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.