3.2.1 Message Contents

08.083GPPMobile-services Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 SpecificationRelease 1999TS

3.2.1.1 ASSIGNMENT REQUEST

This message is sent from the MSC to the BSS via the relevant SCCP connection in order to request the BSS to assign radio resource(s), the attributes of which are defined within the message.

The message may also include the terrestrial circuit to be used.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Channel Type

3.2.2.11

MSC-BSS

M

5-10

Layer 3 Header Information

3.2.2.9

MSC-BSS

O (3)

4

Priority

3.2.2.18

MSC-BSS

O

3

Circuit Identity Code

3.2.2.2

MSC-BSS

O (1)

3

Downlink DTX Flag

3.2.2.26

MSC-BSS

O (2)

2

Interference Band To Be Used

3.2.2.21

MSC-BSS

O

2

Classmark Information 2

3.2.2.19

MSC-BSS

O (4)

4-5

Group Call Reference

3.2.2.55

MSC-BSS

O (5)

3-8

Talker Flag

3.2.2.54

MSC-BSS

O (6)

1

Configuration Evolution Indication

3.2.2.57

MSC-BSS

O (7)

2

LSA Access Control Suppression

3.2.2.61

MSC-BSS

O (8)

2

Service Handover

3.2.2.75

MSC-BSS

O (9)

3

1 This element is included when the MSC allocates the A interface circuits and the channel type Information Element indicates speech or data, and only in those cases.

2 This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS.

3 This information element doesn’t serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message.

4 These elements may be included if the information is known by the MSC.

5 This may be included by the MSC for either a talking or listening subscriber in a group call.

6 This information element is included for group calls, when this is included it indicates that the mobile is a talker in the call else the mobile is a listener.

7 The information is indicated by the MSC if known.

8 This information element is included if LSA access control function shall be suppressed in the BSS.

9 This information element is included if a preference for other radio access technologies shall be applied to the MS connection.

3.2.1.2 ASSIGNMENT COMPLETE

The ASSIGNMENT COMPLETE message is sent from the BSS to the MSC and indicates that the requested assignment has been completed correctly.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

RR Cause

3.2.2.22

BSS-MSC

O

2

Circuit Identity Code

3.2.2.2

BSS-MSC

O (4)

3

Cell Identifier

3.2.2.17

BSS-MSC

O (1)

3-10

Chosen Channel

3.2.2.33

BSS-MSC

O (3)

2

Chosen Encryption Algorithm

3.2.2.44

BSS-MSC

O (5)

2

Circuit Pool

3.2.2.45

BSS-MSC

O (2)

2

Speech Version (Chosen)

3.2.2.51

BSS-MSC

O (6)

2

LSA Identifier

3.2.2.15

BSS-MSC

O (7)

5

1 The cell identifier is used to indicate a new cell, if during the assignment the serving cell has changed. When sent from 3G_MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI) if the new serving cell is GSM or indication of either RNC-ID or SAI (if known) if the new serving cell is UMTS. Note; RNC-ID or SAI are only provided in the ASSIGNMENT COMPLETE message over the MAP-E interface.

2 Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the ASSIGNMENT REQUEST message.

3 Included at least when the channel rate/type choice was done by the BSS.

4 The Circuit Identity Code information element is included mandatorily by the BSS if the BSS allocates the A interface circuits and a circuit is needed.

5 Included at least when the encryption algorithm has been changed by the BSS.

6 Included at least when the speech version choice was done by the BSS.

7 Shall be included if current LSA in the serving cell has been identified (see 3GPP TS 03.73). Not included means that there is no current LSA in the serving cell.

3.2.1.3 ASSIGNMENT FAILURE

The ASSIGNMENT FAILURE message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that there has been a failure in the assignment process at the BSS and that the assignment procedure has been aborted.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

RR Cause

3.2.2.22

BSS-MSC

O

2

Circuit Pool

3.2.2.45

BSS-MSC

O (1)

2

Circuit Pool List

3.2.2.46

BSS-MSC

O (2)

V

1 Shall be included when several circuit pools are present on the BSS MSC interface.

2 May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences.

Typical Cause values are:

radio interface message failure,

O and M intervention,

equipment failure,

no radio resource available,

requested terrestrial resource unavailable,

requested transcoding/rate adaption unavailable,

terrestrial resource already allocated,

invalid message contents,

radio interface failure – reversion to old channel,

directed retry,

circuit pool mismatch,

switch circuit pool.

requested speech version unavailable.

3.2.1.4 BLOCK

This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a particular terrestrial resource (i.e. a particular timeslot within a 2Mbit system) must be remotely blocked at the circuit master, and cannot therefore be used for traffic.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

Cause

3.2.2.5

both

M

3-4

Connection Release Requested

3.2.2.3

MSC-BSS

O

1

Typical Cause values are:

no radio resource available,

O and M intervention,

equipment failure.

3.2.1.5 BLOCKING ACKNOWLEDGE

This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier BLOCK message, and to indicate that the circuit concerned has been removed from service.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

3.2.1.6 UNBLOCK

This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a particular terrestrial resource (ie a particular timeslot within a 2Mbit system) should not be remotely blocked any more on the receiver side.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

3.2.1.7 UNBLOCKING ACKNOWLEDGE

This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier UNBLOCK message.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

3.2.1.8 HANDOVER REQUEST

This message is sent from the MSC to the BSS via the relevant SCCP connection to indicate that the MS is to be handed over to that BSS.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Channel Type

3.2.2.11

MSC-BSS

M

5-10

Encryption Information

3.2.2.10

MSC-BSS

M (1)

3-n

Classmark Information 1
or
Classmark Information 2

3.2.2.30

3.2.2.19

MSC-BSS

MSC-BSS

M#
M (6)

2

4-5

Cell Identifier (Serving)

3.2.2.17

MSC-BSS

M (20)

5-10

Priority

3.2.2.18

MSC-BSS

O

3

Circuit Identity Code

3.2.2.2

MSC-BSS

O (7)

3

Downlink DTX Flag

3.2.2.26

MSC-BSS

O (3)

2

Cell Identifier (Target)

3.2.2.17

MSC-BSS

M (17)

3-10

Interference Band To Be Used

3.2.2.21

MSC-BSS

O

2

Cause

3.2.2.5

MSC-BSS

O (9)

3-4

Classmark Information 3

3.2.2.20

MSC-BSS

O (4)

3-14

Current Channel type 1

3.2.2.49

MSC-BSS

O (8)

2

Speech Version (Used)

3.2.2.51

MSC-BSS

O (10)

2

Group Call Reference

3.2.2.55

MSC-BSS

O (5)

3-8

Talker Flag

3.2.2.54

MSC-BSS

O (11)

1

Configuration Evolution Indication

3.2.2.57

MSC-BSS

O (12)

2

Chosen Encryption Algorithm (Serving)

3.2.2.44

MSC-BSS

O (2)

2

Old BSS to New BSS Information

3.2.2.58

MSC-BSS

O(13)

2-n

LSA Information

3.2.2.23

MSC-BSS

O(14)

3+4n

LSA Access Control Suppression

3.2.2.61

MSC-BSS

O (15)

2

Service Handover

3.2.2.75

MSC-BSS

O (21)

3

IMSI

3.2.2.6

MSC-BSC

O (16)

3-10

Source RNC to target RNC transparent information (UMTS)

3.2.2.76

MSC-BSS

O (18)

n-m

Source RNC to target RNC transparent information (cdma2000)

3.2.2.77

MSC-BSS

O (19)

n-m

1 If the MSC has not sent a CIPHER MODE COMMAND for this RR connection (or has had all such CIPHER MODE COMMAND messages rejected with CIPHER MODE REJECT messages) then the MSC shall indicate that the only "permitted algorithm" is "no encryption".

2 If this information element is included, it shall be equal to the last received "Chosen Encryption Algorithm" information element.

3 This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS.

4 This element is included if the MSC has received such information.

5 This element is included if the MS is in a voice broadcast or voice group call.

6 One of these two elements is sent.

7 This element is included when the channel type Information Element indicates speech or data, and only in those cases. In case of Voice Group Call talker handover, this element may contain the Circuit Identity Code already allocated during the VBS/VGCS assignment procedure, meaning that the already allocated terrestrial resource of the new cell is used.

8 This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a "Current channel type 1" information element. In this case it shall be equal to the received element.

9 This information element should always be included. Its cause value should be the same as indicated in the corresponding Handover Required message.

10 This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a "Speech version (used)" information element. In this case it shall be equal to the received element.

11 This information element is included for voice group call, when this is included it indicates that the mobile is a talker in the call else the mobile is a listener.

12 The information is indicated by the MSC if known

13 This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing an "old BSS to new BSS information" information element. Its contents shall be equal to the received element.

14 This information element is included when the subscriber has localised service area support.

15 This information element is included if LSA access control function shall be suppressed in the BSS.

16 This information element is included at least when the MS is dual transfer mode capable and the IMSI is available at the MSC.

17 If intersystem handover from GSM to UMTS or to cdma 2000 is performed, this information element indicates the target RNC-ID.

18 This information element shall be included when intersystem handover (UMTS) is performed. This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing an "Source RNC to Target RNC transparent information (UMTS)" IE. Its contents shall be equal to the received element. Note; Only provided in the HANDOVER REQUEST message on the MAP-E interface.

19 This information element shall be included when intersystem handover (cdma2000) is performed. This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing an "Source RNC to Target RNC transparent information (cdma2000)" IE. Its contents shall be equal to the received element. Note: Only provided in the HANDOVER REQUEST message on the MAP-E interface.

20 In intersystem handover from UMTS (or cdma2000) to GSM this IE indicates the serving area of the UE.

21 This information element is included if a preference for other radio access technologies shall be applied to the MS connection.

Typical Cause values are:

uplink quality,
uplink strength,
downlink quality,
downlink strength
distance,
better cell,
response to MSC invocation
O and M intervention,
directed retry,
switch circuit pool,
traffic,
preemption.

3.2.1.9 HANDOVER REQUIRED

This message is sent from the BSS to the MSC to indicate that for a given MS which already has dedicated radio resource(s) assigned, a handover is required for the reason given by the cause element.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Response Request

3.2.2.28

BSS-MSC

O

1

Cell Identifier List
(Preferred)

3.2.2.27

BSS-MSC

M (4)

2n+3
to
7n+3

Circuit Pool List

3.2.2.46

BSS-MSC

O (1)

V

Current Channel Type 1

3.2.2.49

BSS-MSC

O (2)

2

Speech Version (Used)

3.2.2.51

BSS-MSC

O (3)

2

Queueing Indicator

3.2.2.50

BSS-MSC

O

2

Old BSS to New BSS Information

3.2.2.58

BSS-MSC

O

2-n

Source RNC to target RNC transparent information (UMTS)

3.2.2.76

BSS-MSC

O (5)

3-m

Source RNC to target RNC transparent information (cdma2000)

3.2.2.77

BSS-MSC

O (6)

n-m

1 Shall be included when cause "switch circuit pool" and the MSC allocates the A interface circuit.

2 This information element should always be included.

3 This information element should always be included when the channel mode is speech, and only in this case.

4 If intersystem handover from GSM to UMTS or to cdma2000 is performed, this information element indicates the target. Only one RNC identity is included for Intersystem Handover to UTRAN or to cdma2000.

5 This information element shall be included when intersystem handover (UMTS) is performed. Source RNC to target RNC information is a general container to carry Inter RAT Handover Info (UTRAN specific information) and Inter RAT UE radio access capability (Classmark Information Type 2 and Classmark Information Type 3) from BSS to RNC. The Inter RAT Handover Info and the Inter RAT UE radio access capbility is conveyed in the RRC container Inter RAT Handover Info with Inter RAT Capbilities as defined in TS 25.331.

6 This information element shall be included when intersystem handover (cdma2000) is performed. Source RNC to target RNC information is a general container to carry cdma2000 specific information from BSS to RNC.

Typical Cause values are:

uplink quality,
uplink strength,
downlink quality,
downlink strength,
distance,
better cell,
response to MSC invocation,
O&M intervention,
directed retry,
switch circuit pool,
traffic,
preemption.

3.2.1.10 HANDOVER REQUEST ACKNOWLEDGE

This message is sent from the BSS to the MSC and indicates that the request to support a handover at the target BSS can be supported by the BSS, and also to which radio channel(s) the MS should be directed.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Layer 3 Information

3.2.2.24

BSS-MSC

M (1)

11-n

Chosen Channel

3.2.2.33

BSS-MSC

O (4)

2

Chosen Encryption Algorithm

3.2.2.44

BSS-MSC

O (5)

2

Circuit Pool

3.2.2.45

BSS-MSC

O (2)

2

Speech Version (Chosen)

3.2.2.51

BSS-MSC

O (6)

2

Circuit Identity Code

3.2.2.2

BSS-MSC

O (3)

3

LSA Identifier

3.2.2.15

BSS-MSC

O (7)

5

1 This information field carries a radio interface message. In case of Intersystem handover to UMTS the information field contains (on MAP-E interface) a HANDOVER TO UTRAN COMMAND message as defined in TS 25.331 In case of Inter BSC handover or in case of a Intersystem Handover from UTRAN to GSM a HANDOVER COMMAND as defined in TS 04.18.In case of a Intersystem Handover from cdma2000 a HANDOVER COMMAND as defined in TS 04.18. In case of Intersystem handover to cdma2000 the information field contains (on MAP-E interface) the Handover To cdma2000 Command, as defined in TS 04.18.

2 Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the HANDOVER REQUEST message.

3 The Circuit identity code information element is included mandatorily by the BSS if the BSS allocates the A interface circuits and a circuit is needed.

4 Included at least when the channel rate/type choice was done by the BSS.

5 Included at least when the encryption algorithm has been selected by the BSS.

6 Included at least when the speech version choice was done by the BSS.

7 Shall be included if a potential current LSA in the target cell has been identified (see 3GPP TS 03.73). Not included means that there is no potential current LSA in the target cell.

3.2.1.11 HANDOVER COMMAND

This message is sent from the MSC to the BSS via the relevant SCCP connection and contains the target channel to which the MS should retune.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Layer 3 Information

3.2.2.24

MSC-BSS

M (1)

11-n

Cell Identifier

3.2.2.17

MSC-BSS

O

3-10

1 This information field carries a radio interface message. In case of Intersystem handover to UMTS the information field contains a HANDOVER TO UTRAN COMMAND message as defined in TS 25.331. In case of Inter BSC handover a RR HANDOVER COMMAND as defined in TS 04.18. In case of Intersystem handover to cdma2000 the information field contains the Handover To cdma2000 Command, as defined in TS 04.18.

3.2.1.12 HANDOVER COMPLETE

This message is sent from the BSS to the MSC via the relevant SCCP connection.

It indicates that the correct MS has successfully accessed the target cell.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

RR Cause

3.2.2.22

BSS-MSC

O

2

3.2.1.13 HANDOVER SUCCEEDED

This message is sent from the MSC to the old BSS via the relevant SCCP connection.

It indicates that the correct MS has successfully accessed the target cell.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

3.2.1.14 HANDOVER CANDIDATE ENQUIRE

This message is sent from the MSC to the BSS, using the connectionless services of the SCCP.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Number Of Mss

3.2.2.8

MSC-BSS

M

2

Cell Identifier List

3.2.2.27

MSC-BSS

M

2n+3
to
7n+3

Cell Identifier

3.2.2.17

MSC-BSS

M

3-10

3.2.1.15 HANDOVER CANDIDATE RESPONSE

This message is sent from the BSS to the MSC in response to receipt of a HANDOVER CANDIDATE ENQUIRE message. It contains the number of MSs for which HANDOVER REQUIRED messages have been sent.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Number Of Mss

3.2.2.8

BSS-MSC

M

2

Cell Identifier

3.2.2.17

BSS-MSC

M

3-10

3.2.1.16 HANDOVER FAILURE

This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates to the MSC that there has been a failure in the resource allocation process on handover, and that the handover has been aborted.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

RR Cause

3.2.2.22

BSS-MSC

O

2

Circuit Pool

3.2.2.45

BSS-MSC

O (1)

2

Circuit Pool List

3.2.2.46

BSS-MSC

O (2)

V

1 Shall be included when several circuit pools are present on the BSS MSC interface.

2 May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences.

Typical Cause values are:

radio interface message failure;
O and M intervention;
Equipment failure;
no radio resource available;
requested terrestrial resource unavailable;
requested transcoding/rate adaption unavailable;
terrestrial resource already allocated;
invalid message contents;
radio interface failure – reversion to old channel;
ciphering algorithm not supported;
circuit pool mismatch;
switch circuit pool;
requested speech version unavailable.

3.2.1.17 RESOURCE REQUEST

This message is sent from the MSC to the BSS and requests the current spare and optionally the total accessible resource on a particular cell.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Periodicity

3.2.2.12

MSC-BSS

M

2

Resource Indication Method

3.2.2.29

MSC-BSS

M

2

Cell Identifier

3.2.2.17

MSC-BSS

M

3-10

Extended Resource Indicator

3.2.2.13

MSC-BSS

O

2

3.2.1.18 RESOURCE INDICATION

This message is sent from the BSS to the MSC in response to a resource request message, the message includes an explicit indication of the cell concerned.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Resource Indication Method

3.2.2.29

BSS-MSC

M

2

Resource Available

3.2.2.4

BSS-MSC

O (1)

21

Cell Identifier

3.2.2.17

BSS-MSC

M

3-10

Total Resource Accessible

3.2.2.14

BSS-MSC

O (2)

5

1 This element is not included if the message is sent only as an acknowledgement to the reception of a RESOURCE REQUEST message.

2 This element has to be included if requested by the Extended Resource Indicator, except when the message is sent only as an acknowledgement to the reception of the RESOURCE REQUEST message.

3.2.1.19 PAGING

This message is sent from the MSC to the BSS and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

IMSI

3.2.2.6

MSC-BSS

M

3-10

TMSI

3.2.2.7

MSC-BSS

O (1)

6

Cell Identifier List

3.2.2.27

MSC-BSS

M

3
to
3+7n

Channel Needed

3.2.2.36

MSC-BSS

O (2)

2

eMLPP Priority

3.2.2.56

MSC-BSS

O (3)

2

1 This element is omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the radio interface.

2 If the channel needed element is not present, the default value is assumed to be 00 (any channel).

3 If the BSS implements the eMLPP feature it should use this information element to build the radio interface Paging request messages, otherwise the information may be considered as an unrecognisable information element.

3.2.1.20 CLEAR REQUEST

This message is sent from the BSS to the MSC to indicate to the MSC that the BSS wishes to release the associated dedicated resource(s).

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Typical Cause values are:

radio interface message failure,
O and M intervention,
equipment failure,
Joined group call channel,
protocol error between BSS and MSC,
preemption.

3.2.1.21 CLEAR COMMAND

This message is sent from the MSC to the BSS to instruct the BSS to release the associated dedicated resource(s).

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Layer 3 Header Information

3.2.2.9

MSC-BSS

O (1)

4

Cause

3.2.2.5

MSC-BSS

M

3-4

1 This information element doesn’t serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message.

Typical Cause values are:

call control,
O and M intervention,
equipment failure,
handover successful,
protocol error between BSS and MSC.

3.2.1.22 CLEAR COMPLETE

This message is sent from the BSS to the MSC to inform the MSC that the associated dedicated resource(s) has been successfully cleared.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

3.2.1.23 RESET

This message can be sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has suffered a failure and has lost memory of the calls in progress, calls set up, and associated references.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Cause

3.2.2.5

Both

M

3-4

Typical Cause values are:

O and M intervention,
equipment failure.

3.2.1.24 RESET ACKNOWLEDGE

This message can be sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has cleared all calls and reset all references, and is ready to resume service.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

3.2.1.25 HANDOVER PERFORMED

This message is sent from the BSS to the MSC in order to indicate that the BSS has performed an internal handover.

The cell identifier and (if required for O and M reasons) optionally the new channel identity is included.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Cell Identifier

3.2.2.17

BSS-MSC

M (5)

3-10

Chosen Channel

3.2.2.33

BSS-MSC

O (1)

2

Chosen Encryption Algorithm

3.2.2.44

BSS-MSC

O (2)

2

Speech Version (Chosen)

3.2.2.51

BSS-MSC

O (3)

2

LSA Identifier

3.2.2.15

BSS-MSC

O (4)

5

1 Included at least when the channel rate/type has changed during the handover.

2 Included at least when the encryption algorithm has been changed by the BSS.

3 Included at least when the speech version has been changed by the BSS.

4 Shall be included if current LSA in the new serving cell has been identified (see 3GPP TS 03.73). Not included means that there is no current LSA in the new serving cell.

5 When sent from MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI).
When sent from 3G_MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI) if the handover target is GSM or indication of either RNC-ID or SAI (if known) if the handover target is UMTS (when indication of relocation complete is recieved from RNC) or indication of SAI when an indication of location report is received (intra UMTS relocation). Note; RNC-ID or SAI are only provided in the HANDOVER PERFORMED message over the MAP-E interface.

Typical Cause values: as for the handover required message, except response to MSC invocation.

3.2.1.26 OVERLOAD

This message is sent from the BSS to the MSC or from the MSC to the BSS. When sent from the BSS to the MSC it indicates either processor overload of the whole BSS (cell identifier field not present) or overload of a CCCH downlink in which case the relevant cell is identified.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Cause

3.2.2.5

Both

M

3-4

Cell Identifier

3.2.2.17

BSS-MSC

O

3-10

Typical Cause values are:

Processor overload,
CCCH overload,
O&M intervention.

3.2.1.27 MSC INVOKE TRACE

This message is sent from the MSC to the BSS in order to start production of a trace record at the BSS.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Trace Type

3.2.2.37

MSC-BSS

M

2

Triggerid

3.2.2.38

MSC-BSS

O

3-22

Trace Reference

3.2.2.39

MSC-BSS

M

3

Transactionid

3.2.2.40

MSC-BSS

O

4

Mobile Identity

3.2.2.41

MSC-BSS

O

3-10

OMCId

3.2.2.42

MSC-BSS

O

3-22

3.2.1.28 BSS INVOKE TRACE

This message is sent from the BSS to the MSC in order to start production of a trace record at the MSC and/or from the MSC to BSS to target BSSs after a handover.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Trace Type

3.2.2.37

Both

M

2

Forward Indicator

3.2.2.43

Both

O

2

Triggerid

3.2.2.38

Both

O

3-22

Trace Reference

3.2.2.39

Both

M

3

TransactionId

3.2.2.40

Both

O

4

OMCId

3.2.2.42

Both

O

3-22

3.2.1.29 CLASSMARK UPDATE

This message is sent from the BSS to the MSC or from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the classmark parameters for the concerned MS.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Classmark Information Type 2

3.2.2.19

Both

M

4-5

Classmark Information Type 3

3.2.2.20

Both

O (1)

3-14

1 This element shall be included by the BSS if it was received from the MS. It shall be included by the MSC if this information element has previously been received by the MSC.

3.2.1.30 CIPHER MODE COMMAND

This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the encryption parameters for the concerned MS.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Layer 3 Header Information

3.2.2.9

MSC-BSS

O (1)

4

Encryption Information

3.2.2.10

MSC-BSS

M

3-n

Cipher Response Mode

3.2.2.34

MSC-BSS

O

2

1 This information element doesn’t serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message.

3.2.1.31 CIPHER MODE COMPLETE

This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that a successful cipher synchronisation has been achieved across the radio interface.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Layer 3 Message Contents

3.2.2.35

BSS-MSC

O

2-n

Chosen Encryption Algorithm

3.2.2.44

BSS-MSC

O (1)

2

1 Included at least when the encryption algorithm has been selected by the BSS.

3.2.1.32 COMPLETE LAYER 3 INFORMATION

The message is sent from the BSS to the MSC as described in sub-clause 3.1.16 (on receipt of the initial layer 3 message on a dedicated channel, e.g. PAGING RESPONSE, LOCATION UPDATING REQUEST, CM REESTABLISHMENT REQUEST, CM SERVICE REQUEST, IMSI DETACH, IMMEDIATE SETUP).

The message is sent via the BSSAP SCCP connection established for the associated dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cell Identifier

3.2.2.17

BSS-MSC

M

3-10

Layer 3 Information

3.2.2.24

BSS-MSC

M

3-n

Chosen Channel

3.2.2.33

BSS-MSC

O (1)

2

LSA Identifier List

3.2.2.16

BSS-MSC

O (2)

3+3n

PADU

3.2.2.68

BSS-MSC

O (3)

3-n

1 This element is optionally used by the BSS to give the MSC a description of the channel rate/type on which the initial layer 3 message was received.

  1. This element shall be included at least when the current cell belongs to one or more LSAs.
  2. This element is optionally used by the BSS to provide Location Services related information to MSC.

3.2.1.33 QUEUEING INDICATION

This message is sent from the BSS to the MSC in order to indicate a delay in the assignment of the required TCH.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

3.2.1.34 SAPI "n" REJECT

This message is sent from the BSS to the MSC in order to indicate that a message with a SAPI value other than "0" has been rejected.

The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

DLCI

3.2.2.25

BSS-MSC

M

2

Cause

3.2.2.5

BSS-MSC

M

3-4

Typical Cause values are:

O&M intervention,
processor overload,
BSS not equipped,
MS not equipped.

3.2.1.35 (void)

3.2.1.36 (void)

3.2.1.37 HANDOVER REQUIRED REJECT

This message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the BSS that the HANDOVER REQUIRED message has not resulted in handover.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Cause

3.2.2.5

MSC-BSS

M

3-4

Typical Cause values are:

equipment failure,
no radio resource available,
requested terrestrial resource unavailable,
invalid message contents,
requested transcoding/rate adaptation unavailable,
O and M intervention.

3.2.1.38 RESET CIRCUIT

This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the state of the circuit indicated in the message is unknown, due to a failure.

This message is sent as a SCCP connectionless message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Circuit Identity Code

3.2.2.2

Both

M

3

Cause

3.2.2.5

Both

M

3-4

Typical Cause values are: as for the RESET message.

3.2.1.39 RESET CIRCUIT ACKNOWLEDGE

This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has cleared a possible call using the circuit, and is ready to resume service.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Circuit Identity

3.2.2.2

Both

M

3

3.2.1.40 HANDOVER DETECT

This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that the correct MS has successfully accessed the target cell.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

3.2.1.41 CIRCUIT GROUP BLOCK

This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a set of terrestrial resources (ie some timeslots within a system of 2Mbit PCM multiplex) must be remotely blocked at the circuit master, and cannot therefore be used for traffic.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Cause

3.2.2.5

both

M

3-4

Circuit Identity Code

3.2.2.2

both

M

3

Circuit Identity Code List

3.2.2.31

both

M

4-35

Typical Cause values:

O & M intervention,

equipment failure.

3.2.1.42 CIRCUIT GROUP BLOCKING ACKNOWLEDGE

This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier CIRCUIT GROUP BLOCK message, and to indicate that the circuits indicated in the status subfield of the Circuit Identity Code List have been remotely blocked.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

Circuit Identity Code List

3.2.2.31

both

M

4-35

3.2.1.43 CIRCUIT GROUP UNBLOCK

This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a set of terrestrial resources (ie some timeslots within a system of 2Mbit PCM multiplex) may be returned to service at the circuit master.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

Circuit Identity Code List

3.2.2.31

both

M

4-35

3.2.1.44 CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE

This message is sent from the MSC to the BSS or from the MSC to the BSS to acknowledge the receipt of an earlier CIRCUIT GROUP UNBLOCK message, and to indicate that the circuits indicated in the status subfield of the Circuit Identity Code List are remotely unblocked.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

Circuit Identity Code

3.2.2.2

both

M

3

Circuit Identity Code List

3.2.2.31

both

M

4-35

3.2.1.45 CONFUSION

This message is sent in either direction in response to a message which cannot be treated correctly for some reason, and for which another failure message cannot substitute. The use of this message may be under operator control.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Cause

3.2.2.5

Both

M

3-4

Diagnostics

3.2.2.32

Both

M

4-n

Typical Cause values are:

Invalid message contents;
information element or field missing;
incorrect value;
unknown message type;
unknown information element;
protocol error between BSS and MSC; and
invalid cell.

3.2.1.46 CLASSMARK REQUEST

This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It requests an update of the classmark parameters for the concerned MS.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

3.2.1.47 UNEQUIPPED CIRCUIT

This message is sent from the BSS to the MSC or vice versa to indicate to the partner entity that it is utilising one or several circuit identity codes which are unknown and which therefore should be locally blocked immediately and taken out of service.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Circuit Identity Code

3.2.2.2

Both

M

3

Circuit Identity Code List

3.2.2.31

Both

O

4-35

3.2.1.48 CIPHER MODE REJECT

This message is sent from the BSS to the MSC via the relevant SCCP connection associated with that MS transaction. It indicates that the BSS is unable to perform the requested ciphering.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Typical Cause values are:

Ciphering algorithm not supported,
Invalid message contents

3.2.1.49 LOAD INDICATION

The LOAD INDICATION message is sent from the BSS to the MSC and from the MSC to the BSS. It indicates to the receiving entity that the transmitting BSS has detected a load situation in the concerned cell.

This message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Time Indication

3.2.2.47

Both

M

2

Cell Identifier

3.2.2.17

Both

M

3-10

Cell Identifier List (Target)

3.2.2.27

Both

M

3
to
3+7n

Resource Situation

3.2.2.48

Both

O (1)

4-N

Cause

3.2.2.5

Both

O (2)

4-5

Typical Cause values:

O & M intervention

Equipment failure

No radio resource available

Processor overload

Traffic load

1 This information element can only be omitted, if the sending BSS wants to stop the whole incoming handover traffic to the indicated cell.

2 Included at least when the reason for sending this message is other than traffic load.

3.2.1.50 VGCS/VBS SETUP

This message is sent from the MSC to the BSS via the newly created SCCP connection in order to request the BSS to support a VGCS/VBS call.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Group Call Reference

3.2.2.55

MSC-BSS

M

3-8

Priority

3.2.2.18

MSC-BSS

O

3

3.2.1.51 VGCS/VBS SETUP ACK

This message is sent from the BSS to the MSC via the newly created SCCP connection in order to confirm that the BSS will support the VGCS/VBS call.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

3.2.1.52 VGCS/VBS SETUP REFUSE

This message is sent from the BSS to the MSC via the newly created SCCP connection in order to reject the SETUP of the VGCS/VBS call.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

3.2.1.53 VGCS/VBS ASSIGNMENT REQUEST

This message is sent from the MSC to the BSS via the newly created VGCS/VBS resource controlling SCCP connection in order to request the BSS to assign radio resources in a cell to support a VGCS/VBS call.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Channel Type

3.2.2.11

MSC-BSS

M

5

Assignment Requirement

3.2.2.52

MSC-BSS

M

2

Cell Identifier

3.2.2.17

MSC-BSS

M

3-10

Group Call Reference

3.2.2.55

MSC-BSS

M

3-8

Priority

3.2.2.18

MSC-BSS

O

3

Circuit Identity Code

3.2.2.2

MSC-BSS

O

3

Downlink DTX Flag

3.2.2.26

MSC-BSS

O

2

Encryption Information

3.2.2.10

MSC-BSS

O

3-n

3.2.1.54 VGCS/VBS ASSIGNMENT RESULT

The VGCS/VBS ASSIGNMENT RESULT message when received indicates the assignment/deassignment of radio resource for the indicated cell.

The message is sent by the BSS via the BSSAP VGCS/VBS resource controlling SCCP connection associated with the dedicated resource.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Channel Type

3.2.2.11

BSS-MSC

M

5

Cell Identifier

3.2.2.17

BSS-MSC

M

3-10

Chosen Channel

3.2.2.33

BSS-MSC

O (2)

2

Circuit Identity Code

3.2.2.2

BSS-MSC

O

3

Circuit Pool

3.2.2.45

BSS-MSC

O (1)

2

1 Shall be included when several circuit pools are present on the BSS-MSC interface and a circuit was allocated by the ASSIGNMENT REQUEST message.

2 Included at least when the channel choice was done by the BSS.

3.2.1.55 VGCS/VBS ASSIGNMENT FAILURE

The VGCS/VBS ASSIGNMENT FAILURE message is sent from the BSS to the MSC via the relevant VGCS/VBS resource controlling SCCP connection. It indicates that there has been a failure in an assignment process at the BSS and that the VGCS/VBS Assignment procedure has been aborted for the concerned cell.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Circuit Pool

3.2.2.45

BSS-MSC

O (1)

2

Circuit Pool List

3.2.2.46

BSS-MSC

O (2)

V

1 Shall be included when several circuit pools are present on the BSS-MSC interface.

2 May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences.

Typical Cause values are:
VGCS/VBS call non existent
O and M intervention,
equipment failure,
no radio resource available,
requested terrestrial resource unavailable,
requested transcoding/rate adaptation unavailable,
terrestrial resource already allocated,
invalid message contents,
circuit pool mismatch,
switch circuit pool,
ciphering algorithm not supported.

3.2.1.56 VGCS/VBS QUEUING INDICATION

The VGCS/VBS QUEUING INDICATION message is sent from the BSS to the MSC via the relevant VGCS/VBS resource controlling SCCP connection. It indicates that there is a delay in the assignment of radio resources for the cell.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

3.2.1.57 UPLINK REQUEST

This message is sent from the BSS to the MSC in order to indicate that a mobile has requested to access the uplink of a voice group call channel.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

3.2.1.58 UPLINK REQUEST ACKNOWLEDGE

This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink allocation of the voice group call channel has been granted by the MSC.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

3.2.1.59 UPLINK REQUEST CONFIRMATION

This message is sent from the BSS to the MSC in order to indicate to the MSC that the uplink of the voice group call channel has been successfully established.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cell Identifier

3.2.2.17

BSS-MSC

M

3-10

Layer 3 Information

3.2.2.24

BSS-MSC

M

3-n

3.2.1.60 UPLINK RELEASE INDICATION

This message is sent from the BSS to the MSC in order to indicate to the MSC that the uplink of the voice group call has been released.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Cause

3.2.2.5

BSS-MSC

M

3-4

Typical cause values

radio interface failure

Call control

O and M intervention

3.2.1.61 UPLINK REJECT COMMAND

This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is not available for allocation to mobiles that have requested the use of the uplink.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Cause

3.2.2.5

MSC-BSS

M

3-4

Typical cause values

radio interface message failure

Call control

O and M intervention

3.2.1.62 UPLINK RELEASE COMMAND

This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is available for allocation.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Cause

3.2.2.5

MSC-BSS

M

3-4

Typical cause values

Call control

3.2.1.63 UPLINK SEIZED COMMAND

This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is no longer available for allocation.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Cause

3.2.2.5

MSC-BSS

M

3-4

Typical cause values

Call control

3.2.1.64 SUSPEND

The SUSPEND message is sent from the BSS to the MSC on the SCCP connection associated to an MS transaction. It indicates to the receiving entity that the transmitting BSS has detected an overload situation in the corresponding connection.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

DLCI

3.2.2.25

BSS-MSC

M

2

NOTE: The SUSPEND message may be only useful for PDSS1.

3.2.1.65 RESUME

The RESUME message is sent from the BSS to the MSC on the SCCP connection associated to an MS transaction. It indicates to the receiving entity that the overload situation in the corresponding connection does no more exist.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

DLCI

3.2.2.25

BSS-MSC

M

2

NOTE: The RESUME message may be only useful for PDSS1.

3.2.1.66 CHANGE CIRCUIT

This message is sent from the MSC to the BSS. It requests a change of the circuit allocated to a connection.

This message is sent on the relevant SCCP connection.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

Cause

3.2.2.5

MSC-BSS

M

3-4

Typical Cause values are

Requested terrestrial resource unavailable,

Terrestrial circuit already allocated.

3.2.1.67 CHANGE CIRCUIT ACKNOWLEDGE

This message is sent from the BSS to the MSC .It allocates a new circuit.

This message is sent on the relevant SCCP connection.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

BSS-MSC

M

1

Circuit identity

3.2.2.2

BSS-MSC

M

3

3.2.1.68 Common ID

This message is sent from the MSC to the BSS in order to inform the BSS of the IMSI associated with this SCCP connection.

This message is sent over the relevant SCCP connection, or, in the SCCP Connection Confirm message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

IMSI

3.2.2.6

MSC-BSS

M

3-10

3.2.1.69 LSA INFORMATION

This message is sent from the MSC to the BSS via the relevant SCCP connection in order to inform the BSS as to which LSA identities the mobile subscriber has subscription.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

LSA Information

3.2.2.23

MSC-BSS

M

3+4n

3.2.1.70 CONNECTION ORIENTED INFORMATION

This message is sent from the serving MSC to the BSS or the serving BSS to the MSC via the relevant SCCP connection. It indicates to the receiving entity that actions related to Location Services needs to be perfomed.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

both

M

1

APDU

3.2.2.68

both

M

3-n

Segmentation

3.2.2.74

both

O (1)

3

1. This IE is present if and only if the APDU contains a message segment.

3.2.1.71 PERFORM LOCATION REQUEST

This message is sent either from the serving MSC to BSS or from the BSS to the MSC via the relevant SCCP connection. It indicates to the receiving entity that actions related to Location Services needs to be performed.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Location Type

3.2.2.63

Both

M

3-n

Cell Identifier

3.2.2.17

Both

C (2)

5-10

Classmark Information Type 3

3.2.2.20

Both

C (2)

3-14

LCS Client Type

3.2.2.67

Both

C (4)

3-n

Chosen Channel

3.2.2.33

Both

C (2)

2

LCS Priority

3.2.2.62

Both

O

3-n

LCS QoS

3.2.2.60

Both

C (1)

3-n

GPS Assistance Data

3.2.2.70

MSC-BSS

C (3)

3-n

APDU

3.2.2.68

Both

C (2)

3-n

1 The IE is present if location of the target MS is requested.

2 These IEs are present if the message is sent from the BSS to the MSC and optional if the message is send from the MSC to the BSC.

3 The IE is present if the GPS assistance data is requested.

4 The IE is present if the message is sent from the BSS to the MSC. If the message is sent from the MSC to the BSC, the IE is present if the location type indicates a request for a location estimate and is optional otherwise.

3.2.1.72 PERFORM LOCATION RESPONSE

This message is sent from the serving BSS to the MSC or from the MSC to the BSS via the relevant SCCP connection in response to the PERFORM LOCATION REQUEST. It contains information related to result of positioning of the target MS.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Location Estimate

3.2.2.64

Both

C (1)

3-n

Positioning Data

3.2.2.65

Both

O

3-n

Deciphering Keys

3.2.2.71

BSS-MSC

C (2)

3-n

LCS Cause

3.2.2.66

Both

C (3)

3-n

1 The IE is present if location of the target MS was requested and the procedure succeeded.

2 These IEs are present if deciphering key was requested and the procedure succeeded

3 The IE is present if the procedure failed.

3.2.1.73 PERFORM LOCATION ABORT

This message is sent from the serving MSC to BSS or from the BSS to the MSC via the relevant SCCP connection. It indicates to the receiving entity that actions related to Location Services needs to be aborted.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

MSC-BSS

M

1

LCS Cause

3.2.2.66

MSC-BSS

M

3-n

3.2.1.74 CONNECTIONLESS INFORMATION

This message is sent from the BSS to the MSC or from the MSC to the BSS. The MSC forwards the CONNECTIONLESS INFORMATION message to the BSS as to which cell is indicated in the message.The message is sent as a connectionless SCCP message.

INFORMATION ELEMENT

REFERENCE

DIRECTION

TYPE

LEN

Message Type

3.2.2.1

Both

M

1

Network Element Identity (source)

3.2.2.69

Both

M

3-n

Network Element Identity (target)

3.2.2.69

Both

M

3-n

APDU

3.2.2.68

Both

M

3-n

Segmentation

3.2,2,74

Both

O (1)

5

Return Error Request

3.2.2.72

Both

O (2)

3 -n

Return Error Cause

3.2.2.73

Both

O (3)

3-n

1 This IE is present if and only if the APDU contains a message segment.

2 The IE is present when the source of a message requests for an error response if the message cannot be delivered to its final destination. If this IE is present, then Return Error Cause shall not be present.

3 The IE is present when an error is indicated that the message was not delivered to its final destination. If this IE is present, then Return Error Request shall not be present. Please refer to 3GPP TS 09.31 for cause values