hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.21.1 Successful operation
|
To initiate a VGCS/VBS call set-up procedures the MSC sends to the BSS a VGCS/VBS SETUP message across VGCS/VBS call controlling SCCP connection. This connection is established for the life time of the VGCS/VBS call. The BSS allocates resources to the call and returns VGCS/VBS SETUP ACK message to the MSC.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.21.2 VGCS/VBS call set-up abnormal cases
|
If the BSS detects that the VGCS/VBS call is already set-up it will clear all resources associated with the previous call and proceed with the new call.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.21.3 VGCS/VBS call set-up failure
|
If the BSS can not set-up the VGCS/VBS call then it will send an VGCS/VBS SETUP REFUSE message to the MSC. 3.1.22 Voice group call service and voice broadcast service Assignment procedure The purpose of the VGCS/VBS Assignment procedure is to ensure that the correct dedicated radio resources are allocated to the VGCS/VBS call on a per cell basis. The VGCS/VBS Assignment procedure is performed on a VGCS/VBS resource controlling SCCP connection. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 43 (GSM 08.08 version 6.5.0 Release 1997) The MSC can command that the radio resources are either allocated immediately or delayed.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.22.1 Successful operation
|
It is assumed that the VGCS/VBS controlling SCCP connection and the VGCS/VBS resource controlling SCCP connection(s) have been set-up before the VGCS/VBS Assignment procedure takes place. The MSC initiates the VGCS/VBS Assignment procedure to the BSS by sending an VGCS/VBS ASSIGNMENT REQUEST on a VGCS/VBS resource controlling SCCP connection. The BSS will return VGCS/VBS ASSIGNMENT RESULT to the MSC to inform the MSC of the resources allocated by the BSS for the concerned cell. The BSS shall initiate the radio interface notification procedure on the NCH of the cell in which the call is to take place, this may continue at regular intervals until the call is released. The BSS may on SACCH indicate that a change of notification has occurred and/or initiate notification on FACCH. In the case where the BSS deallocates/allocates resources to the cell, the BSS sends an VGCS/VBS ASSIGNMENT RESULT message on the VGCS/VBS resource controlling SCCP connection associated to the cell.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.22.2 VGCS/VBS Assignment abnormal cases
|
In the abnormal case, where a BSS detects that a voice broadcast or voice group call already exists with the same group call reference in a cell (this may occur due to SCCP problems), the BSS shall release the radio resources associated with the cell for the present existing voice broadcast or voice group call and shall allocate resources to the new call.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.22.3 VGCS/VBS Assignment failure
|
In the case were the VGCS/VBS call is unknown by the BSS, the BSS shall return the VGCS/VBS ASSIGNMENT FAILURE message (cause "VGCS/VBS call non existent"). In the case where no radio resource can be allocated to the VGCS/VBS call, the BSS shall return the VGCS/VBS ASSIGNMENT FAILURE message (cause "No radio resource available"). In the case where the MSC has attempted to assign a terrestrial circuit and an VGCS/VBS ASSIGNMENT FAILURE message has been returned then both the MSC and the BSS shall consider that the terrestrial circuit is idle and therefore no explicit clearing sequence is needed.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.23 Spare
| |
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24 Voice group call uplink control procedure
|
In the case of voice group calls the uplink resource allocated to the call is controlled by the uplink control procedure. The uplink control procedure uses messages sent on the VGCS/VBS controlling SCCP connection set-up by the VGCS/VBS call set-up procedure. The procedure is split into three procedures: uplink allocation; uplink release; & uplink seize. The uplink allocation is controlled by the BSSs and group call anchor MSC. The BSS controls the uplink access for the cells in the group call area which are under its control. The group call anchor MSC controls the uplink access for the complete service area. Any allocation of the uplink access by a BSS may be refused later by the group call anchor MSC (due to the allocation of the uplink by other BSSs involved in the same voice group call). The uplink release & uplink seize procedure is controlled and initiated by the MSC, the BSS obeys the MSC's requests. When the voice group call is initially set-up the state of the uplink in each BSS is such that the uplink is seized. The MSC will control the state of the uplink in each BSS by use of the uplink release and uplink seize procedures. Before an uplink may be allocated by the BSS, the MSC must have released the uplink by initiating the uplink release procedure. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 44 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24.1 Uplink allocation procedure
|
The uplink allocation procedure allows a listening user in a voice group call to talk on the uplink of the TCH dedicated to the voice group call in the cell. The uplink allocation procedure can only occur once the group call anchor MSC has released the uplink (by use of the uplink release procedure). When a mobile relinquishes the uplink or the BSS detects that the MS is no longer connected, the BSS sends to the MSC an UPLINK RELEASE INDICATION message cause "Call control" or "Radio interface message failure" respectively, the BSS may initiate the radio interface uplink free procedure.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24.1.1 Successful uplink allocation operation
|
On reception of a request to talk, the BSS sends an UPLINK REQUEST message to the MSC. The MSC sends the UPLINK REQUEST ACKNOWLEDGE message to confirm to the BSS that the uplink is granted to the requesting MS. The MSC also sends to all the other BSSs in the voice group call an UPLINK SEIZED COMMAND message. The BSS sends UPLINK REQUEST CONFIRMATION message with the complete layer information, once the radio link has been established.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24.1.2 Unsuccessful uplink allocation operation
|
In the case that the radio link could not be established the BS sends the Uplink release indication with the cause "Radiolink interface message failure". In the case the MSC does not want to grant the uplink, the MSC will send an UPLINK REJECT COMMAND message to the appropriate BSS. On reception of this the BSS will release the uplink for the requesting MS.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24.2 Uplink release procedure
|
This procedure shall be used in one of the following cases: - the group call anchor MSC detects that none of the parties involved in a voice group call are talking . The Uplink release procedure is then used to allow the listening subscribers to talk - the group call anchor or relay MSC detects that the talker has left the Group Call Area To initiate this procedure the group call anchor MSC sends the UPLINK RELEASE COMMAND message to each BSS involved in the voice group call. When the BSS receives the Uplink release request command, the BSS shall initiate the radio interface uplink release procedure.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.24.3 Uplink seize procedure
|
Once the group call anchor MSC has released the uplink it may detect speech on dedicated channel(s), in this case the MSC will send to all BSSs involved in the voice group call an UPLINK SEIZED COMMAND message. On reception of the UPLINK SEIZED COMMAND message the BSS will initiate the radio interface uplink busy procedure.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.25 PDSS1 flow control
|
The purpose of the PDSS1 flow control procedure is to inform the MSC that it should stop or resume transmission of PDSS1 data on this particular transaction. The BSS may on the relevant SCCP connection associated with an MS transaction send a SUSPEND message to the MSC to ask the MSC not to transmit DTAP messages carrying air interface layer 3 messages of the PDSS1 protocol. A typical reason is that too many messages are scheduled for transmission on the air interface. The BSS may on the relevant SCCP connection associated with an MS transaction send a RESUME message to the MSC to indicate to the MSC that DTAP messages carrying air interface layer 3 messages of the PDSS1 protocol may be transmitted (the typical reason is that congestion on the air interface signalling channel does no more exist). ETSI ETSI TS 100 590 V6.5.0 (2000-06) 45 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.26 Circuit re-selection procedure
|
This procedure has to be supported by a BSS if and only if it allocates the A interface circuits. The MSC can request the BSS to change the circuit allocated to a connection by sending a CHANGE CIRCUIT message to the BSS on the corresponding SCCP connection. The MSC releases the allocated circuit at the sending of the CHANGE CIRCUIT message. The MSC shall not start the circuit re-selection procedure if another procedure is on-going that may result in the change of the circuit (e.g., circuit re-selection, handover or clearing). At the reception of a CHANGE CIRCUIT message, and if the BSS is not already engaged in a procedure that normally results in the release of the allocated circuit (e.g., handover or clearing), the BSS allocates a new circuit and indicates it in CHANGE CIRCUIT ACKNOWLEDGE message sent back to the MSC. The BSS releases the previously allocated circuit after the sending of the CHANGE CIRCUIT ACKNOWLEDGE message. If the MSC receives a message from the BSS indicating the start of a procedure that may result in the change of the circuit (e.g., reception of HANDOVER REQUIRED or CLEAR REQUEST), the MSC shall abort the circuit re- selection procedure. The MSC may not be able to use the terrestrial resource that the BSS has indicated. In this case, the procedure is nevertheless considered terminated successfully, and it is up to the MSC to correct the situation, e.g., by a new circuit re- selection procedure.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2 Message Formats and Coding
|
This subclause defines the coding and format of the messages required for the BSSMAP. For each message there is, in subclause 3.2.1, a table listing the signalling elements in their order of appearance in the transmitted message. There is no general rule for the order of signalling elements: it happens that the same elements appear in various orders depending on the message. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 46 (GSM 08.08 version 6.5.0 Release 1997) All the BSSMAP messages are listed in the following table: Message name Reference ASSIGNMENT REQUEST 3.2.1.1 ASSIGNMENT COMPLETE 3.2.1.2 ASSIGNMENT FAILURE 3.2.1.3 BLOCK
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.4 BLOCK
|
ING ACKNOWLEDGE 3.2.1.5 CIRCUIT GROUP BLOCK
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.41 CIRCUIT GROUP BLOCK
|
ING ACKNOWLEDGE 3.2.1.42 CIRCUIT GROUP UNBLOCK
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.43 CIRCUIT GROUP UNBLOCK
|
ING ACKNOWLEDGE 3.2.1.44 CLEAR COMMAND 3.2.1.21 CLEAR COMPLETE 3.2.1.22 CLEAR REQUEST 3.2.1.20 UNBLOCK
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.6 UNBLOCK
|
ING ACK 3.2.1.7 HANDOVER CANDIDATE ENQUIRE 3.2.1.14 HANDOVER CANDIDATE RESPONSE 3.2.1.15 HANDOVER REQUEST 3.2.1.8 HANDOVER REQUIRED
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.9 HANDOVER REQUIRED
|
REJECT 3.2.1.37 HANDOVER REQUEST ACKNOWLEDGE 3.2.1.10 HANDOVER COMMAND 3.2.1.11 HANDOVER COMPLETE 3.2.1.12 HANDOVER SUCCEEDED 3.2.1.13 HANDOVER FAILURE 3.2.1.16 HANDOVER PERFORMED 3.2.1.25 HANDOVER DETECT 3.2.1.40 RESOURCE REQUEST 3.2.1.17 RESET
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.23 RESET
|
ACK 3.2.1.24 RESOURCE INDICATION 3.2.1.18 PAGING 3.2.1.19 OVERLOAD 3.2.1.26 MSC INVOKE TRACE 3.2.1.27 BSS INVOKE TRACE 3.2.1.28 CLASSMARK UPDATE 3.2.1.29 CLASSMARK REQUEST 3.2.1.46 CIPHER MODE COMMAND 3.2.1.30 CIPHER MODE COMPLETE 3.2.1.31 CIPHER MODE REJECT 3.2.1.48 COMPLETE LAYER 3 INFORMATION 3.2.1.32 QUEUING INDICATION 3.2.1.33 SAPI “N” REJECT 3.2.1.34 RESET CIRCUIT
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.38 RESET CIRCUIT
|
ACKNOWLEDGE 3.2.1.39 CONFUSION 3.2.1.45 UNEQUIPPED CIRCUIT 3.2.1.47 LOAD INDICATION 3.2.1.49 VGCS/VBS SETUP
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.50 VGCS/VBS SETUP
|
ACK 3.2.1.51 VGCS/VBS SETUP REFUSE 3.2.1.52 VGCS/VBS ASSIGNMENT REQUEST 3.2.1.53 VGCS/VBS ASSIGNMENT RESULT 3.2.1.54 VGCS/VBS ASSIGNMENT FAILURE 3.2.1.55 VGCS/VBS QUEUING INDICATION 3.2.1.56 (continued) ETSI ETSI TS 100 590 V6.5.0 (2000-06) 47 (GSM 08.08 version 6.5.0 Release 1997) (concluded): Message name Reference UPLINK REQUEST
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.57 UPLINK REQUEST
|
ACKNOWLEDGE 3.2.1.58 UPLINK REQUEST CONFIRMATION 3.2.1.59 UPLINK RELEASE INDICATION 3.2.1.60 UPLINK REJECT COMMAND 3.2.1.61 UPLINK RELEASE COMMAND 3.2.1.62 UPLINK SEIZED COMMAND 3.2.1.63 SUSPEND 3.2.1.64 RESUME 3.2.1.65 CHANGE CIRCUIT
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.66 CHANGE CIRCUIT
|
ACKNOWLEDGE 3.2.1.67
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1 Message Contents
| |
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 48 (GSM 08.08 version 6.5.0 Release 1997) 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 1 The cell identifier is used to indicate a new cell, if during the assignment the serving cell has changed. 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 49 (GSM 08.08 version 6.5.0 Release 1997) 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 50 (GSM 08.08 version 6.5.0 Release 1997) 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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 51 (GSM 08.08 version 6.5.0 Release 1997) 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 3.2.2.30 MSC-BSS M# 2 Classmark Information 2 3.2.2.19 MSC-BSS M (6) 4-5 Cell Identifier (Serving) 3.2.2.17 MSC-BSS M 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 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 1) 3.2.2.59 2) MSC- BSS 3) O ( 1 3 ) 2-n 1 If the MSC has not sent a CIPHER MODE COMMAND for this RR connection (or has had all such CIPHER MODE COMMANDs 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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 52 (GSM 08.08 version 6.5.0 Release 1997) 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. 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 3.2.2.27 BSS-MSC M 2n+3 (Preferred) 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.59 BSS-MSC O 2-n 1 Shall be included when cause "switch circuit pool" and the MSC allocates the A interface circuit. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 53 (GSM 08.08 version 6.5.0 Release 1997) 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. 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 1 This information field carries a radio interface HANDOVER COMMAND message. 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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 54 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 HANDOVER COMMAND message.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 55 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 56 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 57 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 58 (GSM 08.08 version 6.5.0 Release 1997) 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 59 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 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 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. Typical Cause values: as for the handover required message, except response to MSC invocation.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 60 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 61 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.32 COMPLETE LAYER 3 INFORMATION
|
The message is sent from the BSS to the MSC as described in subclause 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 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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). ETSI ETSI TS 100 590 V6.5.0 (2000-06) 62 (GSM 08.08 version 6.5.0 Release 1997) INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN Message Type 3.2.2.1 MSC-BSS M 1
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.35 [spare]
| |
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.36 [spare]
| |
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 63 (GSM 08.08 version 6.5.0 Release 1997) 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 64 (GSM 08.08 version 6.5.0 Release 1997) 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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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; ETSI ETSI TS 100 590 V6.5.0 (2000-06) 65 (GSM 08.08 version 6.5.0 Release 1997) protocol error between BSS and MSC; and invalid cell.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 66 (GSM 08.08 version 6.5.0 Release 1997) 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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 67 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 68 (GSM 08.08 version 6.5.0 Release 1997) 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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 69 (GSM 08.08 version 6.5.0 Release 1997) INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN Message Type 3.2.2.1 MSC-BSS M 1
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 channel 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 message failure Call control O and M intervention
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 70 (GSM 08.08 version 6.5.0 Release 1997) Call control
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
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 ressource unavailable, Terrestrial circuit already allocated.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.67 CHANGE CIRCUIT ACKNOWLEDGE
|
This message is sent from the BSS to the MSC.It allocates a new circuit. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 71 (GSM 08.08 version 6.5.0 Release 1997) 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
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.1.68 Spare
| |
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2 Signalling element coding
|
This paragraph contains the CODING of the signalling elements used. The following conventions are assumed for the sequence of transmission of bits and bytes: - Each bit position is marked as 1 to 8. Bit 1 is the least significant bit and is transmitted first. - In an element octets are identified by number, octet 1 is transmitted first, then octet 2 etc. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. - For variable length elements a length indicator is included, this indicates the number of octets following in the element. - All fields within Information Elements are mandatory unless otherwise specified. The Information Element Identifier shall always be included. All spare bits are set to 0. The elements used and their CODING are: Element Identifier Coding Element name Reference 0000 0001 Circuit Identity Code 3.2.2.2 0000 0010 Reserved * 0000 0011 Resource Available 3.2.2.4 0000 0100 Cause 3.2.2.5 0000 0101 Cell Identifier 3.2.2.17 0000 0110 Priority 3.2.2.18 0000 0111 Layer 3 Header Information 3.2.2.9 0000 1000 IMSI 3.2.2.6 0000 1001 TMSI 3.2.2.7 0000 1010 Encryption Information 3.2.2.10 0000 1011 Channel Type 3.2.2.11 0000 1100 Periodicity 3.2.2.12 0000 1101 Extended Resource Indicator 3.2.2.13 0000 1110 Number Of MSs 3.2.2.8 0000 1111 Reserved * 0001 0000 Reserved * 0001 0001 Reserved * 0001 0010 Classmark Information Type 2 3.2.2.19 0001 0011 Classmark Information Type 3 3.2.2.20 0001 0100 Interference Band To Be Used 3.2.2.21 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 72 (GSM 08.08 version 6.5.0 Release 1997) Element Identifier Coding Element name Reference 0001 0101 RR Cause 3.2.2.22 0001 0110 Reserved * 0001 0111 Layer 3 Information 3.2.2.24 0001 1000 DLCI 3.2.2.25 0001 1001 Downlink DTX Flag 3.2.2.26 0001 1010 Cell Identifier List 3.2.2.27 0001 1011 Response Request 3.2.2.28 0001 1100 Resource Indication Method 3.2.2.29 0001 1101 Classmark Information Type 1 3.2.2.30 0001 1110 Circuit Identity Code List 3.2.2.31 0001 1111 Diagnostic 3.2.2.32 (continued) (concluded) Element Identifier Coding Element name Reference 0010 0000 Layer 3 Message Contents 3.2.2.35 0010 0001 Chosen Channel 3.2.2.33 0010 0010 Total Resource Accessible 3.2.2.14 0010 0011 Cipher Response Mode 3.2.2.34 0010 0100 Channel Needed 3.2.2.36 0010 0101 Trace Type 3.2.2.37 0010 0110 Triggerid 3.2.2.38 0010 0111 Trace Reference 3.2.2.39 0010 1000 Transactionid 3.2.2.40 0010 1001 Mobile Identity 3.2.2.41 0010 1010 OMCId 3.2.2.42 0010 1011 Forward Indicator 3.2.2.43 0010 1100 Chosen Encryption Algorithm 3.2.2.44 0010 1101 Circuit Pool 3.2.2.45 0010 1110 Circuit Pool List 3.2.2.46 0010 1111 Time Indication 3.2.2.47 0011 0000 Resource Situation 3.2.2.48 0011 0001 Current Channel type 1 3.2.2.49 0011 0010 Queueing Indicator 3.2.2.50 0100 0000 Speech Version 3.2.2.51 0011 0011 Assignment Requirement 3.2.2.52 0011 0101 Talker Flag 3.2.2.54 0011 0110 Connection Release Requested 3.2.2.3 0011 0111 Group Call Reference 3.2.2.55 0011 1000 eMLPP Priority 3.2.2.56 0011 1001 Configuration Evolution Indication 3.2.2.57 0011 1010 Old BSS to New BSS Information 3.2.2.59 * Information Element codes marked as "reserved" are reserved for use by previous versions of this interface specification.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.1 Message Type
|
Message Type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. Bit 8 is reserved for future extension of the code set. All unassigned codes are spare. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 73 (GSM 08.08 version 6.5.0 Release 1997) 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 Reserved. ASSIGNMENT MESSAGES 0 0 0 0 0 0 0 1 ASSIGNMENT REQUEST 0 0 0 0 0 0 1 0 ASSIGNMENT COMPLETE 0 0 0 0 0 0 1 1 ASSIGNMENT FAILURE HANDOVER MESSAGES 0 0 0 1 0 0 0 0 HANDOVER REQUEST 0 0 0 1 0 0 0 1 HANDOVER REQUIRED 0 0 0 1 0 0 1 0 HANDOVER REQUEST ACKNOWLEDGE 0 0 0 1 0 0 1 1 HANDOVER COMMAND 0 0 0 1 0 1 0 0 HANDOVER COMPLETE 0 0 0 1 0 1 0 1 HANDOVER SUCCEEDED 0 0 0 1 0 1 1 0 HANDOVER FAILURE 0 0 0 1 0 1 1 1 HANDOVER PERFORMED 0 0 0 1 1 0 0 0 HANDOVER CANDIDATE ENQUIRE 0 0 0 1 1 0 0 1 HANDOVER CANDIDATE RESPONSE 0 0 0 1 1 0 1 0 HANDOVER REQUIRED REJECT 0 0 0 1 1 0 1 1 HANDOVER DETECT RELEASE MESSAGES 0 0 1 0 0 0 0 0 CLEAR COMMAND 0 0 1 0 0 0 0 1 CLEAR COMPLETE 0 0 1 0 0 0 1 0 CLEAR REQUEST 0 0 1 0 0 0 1 1 RESERVED 0 0 1 0 0 1 0 0 RESERVED 0 0 1 0 0 1 0 1 SAPI “N” REJECT 0 0 1 0 0 1 1 0 CONFUSION OTHER CONNECTION RELATED MESSAGES 0 0 1 0 1 0 0 0 SUSPEND 0 0 1 0 1 0 0 1 RESUME GENERAL MESSAGES 0 0 1 1 0 0 0 0 RESET 0 0 1 1 0 0 0 1 RESET ACKNOWLEDGE 0 0 1 1 0 0 1 0 OVERLOAD 0 0 1 1 0 0 1 1 RESERVED 0 0 1 1 0 1 0 0 RESET CIRCUIT 0 0 1 1 0 1 0 1 RESET CIRCUIT ACKNOWLEDGE 0 0 1 1 0 1 1 0 MSC INVOKE TRACE 0 0 1 1 0 1 1 1 BSS INVOKE TRACE TERRESTRIAL RESOURCE MESSAGES 0 1 0 0 0 0 0 0 BLOCK 0 1 0 0 0 0 0 1 BLOCKING ACKNOWLEDGE 0 1 0 0 0 0 1 0 UNBLOCK 0 1 0 0 0 0 1 1 UNBLOCKING ACKNOWLEDGE 0 1 0 0 0 1 0 0 CIRCUIT GROUP BLOCK 0 1 0 0 0 1 0 1 CIRCUIT GROUP BLOCKING ACKNOWLEDGE 0 1 0 0 0 1 1 0 CIRCUIT GROUP UNBLOCK 0 1 0 0 0 1 1 1 CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE 0 1 0 0 1 0 0 0 UNEQUIPPED CIRCUIT 0 1 0 0 1 1 1 0 CHANGE CIRCUIT 0 1 0 0 1 1 1 1 CHANGE CIRCUIT ACKNOWLEDGE (continued) ETSI ETSI TS 100 590 V6.5.0 (2000-06) 74 (GSM 08.08 version 6.5.0 Release 1997) (concluded) 8 7 6 5 4 3 2 1 RADIO RESOURCE MESSAGES 0 1 0 1 0 0 0 0 RESOURCE REQUEST 0 1 0 1 0 0 0 1 RESOURCE INDICATION 0 1 0 1 0 0 1 0 PAGING 0 1 0 1 0 0 1 1 CIPHER MODE COMMAND 0 1 0 1 0 1 0 0 CLASSMARK UPDATE 0 1 0 1 0 1 0 1 CIPHER MODE COMPLETE 0 1 0 1 0 1 1 0 QUEUING INDICATION 0 1 0 1 0 1 1 1 COMPLETE LAYER 3 INFORMATION 0 1 0 1 1 0 0 0 CLASSMARK REQUEST 0 1 0 1 1 0 0 1 CIPHER MODE REJECT 0 1 0 1 1 0 1 0 LOAD INDICATION VGCS/VBS 0 0 0 0 0 1 0 0 VGCS/VBS SETUP 0 0 0 0 0 1 0 1 VGCS/VBS SETUP ACK 0 0 0 0 0 1 1 0 VGCS/VBS SETUP REFUSE 0 0 0 0 0 1 1 1 VGCS/VBS ASSIGNMENT REQUEST 0 0 0 1 1 1 0 0 VGCS/VBS ASSIGNMENT RESULT 0 0 0 1 1 1 0 1 VGCS/VBS ASSIGNMENT FAILURE 0 0 0 1 1 1 1 0 VGCS/VBS QUEUING INDICATION 0 0 0 1 1 1 1 1 UPLINK REQUEST 0 0 1 0 0 1 1 1 UPLINK REQUEST ACKNOWLEDGE 0 1 0 0 1 0 0 1 UPLINK REQUEST CONFIRMATION 0 1 0 0 1 0 1 0 UPLINK RELEASE INDICATION 0 1 0 0 1 0 1 1 UPLINK REJECT COMMAND 0 1 0 0 1 1 0 0 UPLINK RELEASE COMMAND 0 1 0 0 1 1 0 1 UPLINK SEIZED COMMAND
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.2 Circuit Identity Code
|
This element defines the terrestrial channel over which the call will pass. If a 2048Kbits/s digital path is used then the circuit identification code contains in the 5 least significant bits a binary representation of the actual number of the timeslot which is assigned to the circuit. The remaining bits in the CIC are used where necessary, to identify one among several systems interconnecting an originating and destination point. The element is 2 octets in length: 8 7 6 5 4 3 2 1 Element identifier octet 1 a b c d e f g h octet 2 i j k X X X X X octet 3 a-k defines the PCM multiplex in use. XXXXX define the actual timeslot in use. The circuit identity code defines the PCM multiplex and timeslot in use at the MSC. In cases where remultiplexing takes place between the MSC and BSS a translation may be necessary at the BSS.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.3 Connection Release Requested
|
The element has a fixed length of one octet. 8 7 6 5 4 3 2 1 Element identifier octet 1 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 75 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.4 Resource Available
|
This element gives the number of full and half rate channels available on any given cell at the time of construction of the message. It defines these parameters in terms of the number of channels available in five interference bands, the boundaries of these bands being set by O and M as follows: Interference level: 0 --------------------------- Band 1 X1 --------------------------- Band 2 X2 --------------------------- Band 3 X3 --------------------------- Band 4 X4 --------------------------- Band 5 X5 --------------------------- The element is coded as follows: 8 7 6 5 4 3 2 1 Element identifier octet 1 Number of full rate octet 2 channels available in band 1 octet 3 Number of half rate octet 4 channels available in band 1 octet 5 Number of full rate octet 18 channels available in band 5 octet 19 Number of half rate octet 20 channels available in band 5 octet 21 Octets (2,3,4,5,) are then repeated for each of the other interference bands giving a total message length of 21 octets. Octets 2 and 3 give a 16 bit binary representation of the number of full rate channels available for service but not currently assigned. Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels available for service but not currently assigned. This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels. (e.g. If there is a spare half rate channel and a spare full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.5 Cause
|
The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 76 (GSM 08.08 version 6.5.0 Release 1997) The cause value is a single octet element if the extension bit (bit 8) is set to 0. If it is set to 1 then the cause value is a 2 octet field. If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national applications, (XXX will still indicate the class). 8 7 6 5 4 3 2 1 Element identifier octet 1 Length octet 2 0/1 ext Cause Value octet 3 (octet 4) The length indicator is a binary representation of the length of the following element. Cause Value: Class (000) : Normal event Class (001) : Normal event Class (010) : Resource unavailable Class (011) : Service or option not available Class (100) : Service or option not implemented Class (101) : invalid message (eg parameter out of range) Class (110) : protocol error Class (111) : interworking In the following table, "reserved for international use" means that this codepoint should not be used until a meaning has been assigned to it following the process of international standardisation. "Reserved for national use" indicates codepoints that may be used by operators without the need for international standardisation. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 77 (GSM 08.08 version 6.5.0 Release 1997) ┌─────────────┬──────┬───────────────────────────────────────┐ │Cause value │Cause │ │ ├─────┬───────┤Number│ │ │Class│Value │ │ │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │7 6 5│4 3 2 1│ │ │ │ │ │ │ │ │0 0 0│0 0 0 0│ │Radio interface message failure │ │ │ │ │ │ │0 0 0│0 0 0 1│ │Radio interface failure │ │ │ │ │ │ │0 0 0│0 0 1 0│ │Uplink quality │ │ │ │ │ │ │0 0 0│0 0 1 1│ │Uplink strength │ │ │ │ │ │ │0 0 0│0 1 0 0│ │Downlink quality │ │ │ │ │ │ │0 0 0│0 1 0 1│ │Downlink strength │ │ │ │ │ │ │0 0 0│0 1 1 0│ │Distance │ │ │ │ │ │ │0 0 0│0 1 1 1│ │O and M intervention │ │ │ │ │ │ │0 0 0│1 0 0 0│ │Response to MSC invocation │ │ │ │ │ │ │0 0 0│1 0 0 1│ │Call control │ │ │ │ │ │ │0 0 0│1 0 1 0│ │Radio interface failure, reversion to │ │ │ │ │old channel │ │0 0 0│1 0 1 1│ │Handover successful │ │ │ │ │ │ │0 0 0│1 1 0 0│ │Better Cell │ │ │ │ │ │ │0 0 0│1 1 0 1│ │Directed Retry │ │ │ │ │ │ │0 0 0│1 1 1 0│ │Joined group call channel │ │ │ │ │ │ │0 0 0│1 1 1 1│ │Traffic │ │ │ │ │ │ │0 0 1│0 0 0 0│ │} │ │ to │ │}Reserved for international use │ │0 0 1│0 1 1 1│ │} │ │ │ │ │ │ │0 0 1│1 0 0 0│ │} │ │ to │ │}Reserved for national use │ │0 0 1│1 1 1 1│ │} │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │ │ │ │ │ │0 1 0│0 0 0 0│ │Equipment failure │ │ │ │ │ │ │0 1 0│0 0 0 1│ │No radio resource available │ │ │ │ │ │ │0 1 0│0 0 1 0│ │Requested terrestrial resource │ │ │ │ │unavailable │ │0 1 0│0 0 1 1│ │CCCH overload │ │ │ │ │ │ │0 1 0│0 1 0 0│ │Processor overload │ │ │ │ │ │ │0 1 0│0 1 0 1│ │BSS not equipped │ │ │ │ │ │ └─────┴───────┴──────┴───────────────────────────────────────┘ ETSI ETSI TS 100 590 V6.5.0 (2000-06) 78 (GSM 08.08 version 6.5.0 Release 1997) ┌─────────────┬──────┬───────────────────────────────────────┐ │Cause value │Cause │ │ ├─────┬───────┤Number│ │ │Class│Value │ │ │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │0 1 0│0 1 1 0│ │MS not equipped │ │ │ │ │ │ │0 1 0│0 1 1 1│ │Invalid cell │ │ │ │ │ │ │0 1 0│1 0 0 0│ │Traffic Load │ │ │ │ │ │ │0 1 0│1 0 0 1│ │Preemption │ │ │ │ │ │ │0 1 0│1 0 1 0│ │} │ │ to │ │}Reserved for national use │ │0 1 0│1 1 1 1│ │} │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │0 1 1│0 0 0 0│ │Requested transcoding/rate adaption │ │ │ │ │unavailable │ │ │ │ │ │ │0 1 1│0 0 0 1│ │Circuit pool mismatch │ │ │ │ │ │ │0 1 1│0 0 1 0│ │Switch circuit pool │ │ │ │ │ │ │0 1 1│0 0 1 1│ │Requested speech version unavailable │ │ │ │ │ │ │0 1 1│0 1 0 0│ │} │ │ to │ │}Reserved for international use │ │0 1 1│1 1 1 1│ │} │ │ │ │ │ │ │1 0 0│0 0 0 0│ │Ciphering algorithm not supported │ │ │ │ │ │ │1 0 0│0 0 0 1│ │} │ │ to │ │}Reserved for international use │ │1 0 0│0 1 1 1│ │} │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │1 0 0│0 1 1 1│ │} │ │ to │ │}Reserved for national use │ │1 0 0│1 1 1 1│ │} │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │1 0 1│0 0 0 0│ │Terrestrial circuit already allocated │ │ │ │ │ │ │1 0 1│0 0 0 1│ │Invalid message contents │ │ │ │ │ │ │1 0 1│0 0 1 0│ │Information element or field missing │ │ │ │ │ │ │1 0 1│0 0 1 1│ │Incorrect value │ │ │ │ │ │ │1 0 1│0 1 0 0│ │Unknown Message type │ │ │ │ │ │ │1 0 1│0 1 0 1│ │Unknown Information Element │ │ │ │ │ │ │1 0 1│0 1 1 0│ │} │ │ to │ │}Reserved for international use │ │1 0 1│0 1 1 1│ │} │ │ │ │ │ │ │1 0 1│1 0 0 0│ │} │ │ to │ │}Reserved for national use │ │1 0 1│1 1 1 1│ │} │ └─────┴───────┴──────┴───────────────────────────────────────┘ ETSI ETSI TS 100 590 V6.5.0 (2000-06) 79 (GSM 08.08 version 6.5.0 Release 1997) ┌─────────────┬──────┬───────────────────────────────────────┐ │Cause value │Cause │ │ ├─────┬───────┤Number│ │ │Class│Value │ │ │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │1 1 0│0 0 0 0│ │Protocol Error between BSS and MSC │ │ │ │ │ │ │1 1 0│0 0 0 1│ │VGCS/VBS call non existent │ │ │ │ │ │ │1 1 0│0 0 1 0│ │} │ │ to │ │}Reserved for international use │ │1 1 0│0 1 1 1│ │} │ │ │ │ │ │ │1 1 0│1 0 0 0│ │} │ │ to │ │}Reserved for national use │ │1 1 0│1 1 1 1│ │} │ ├─────┼───────┼──────┼───────────────────────────────────────┤ │ │ │ │ │ │1 1 1│0 0 0 0│ │} │ │ to │ │}Reserved for international use │ │1 1 1│0 1 1 1│ │} │ │ │ │ │ │ │1 1 1│1 0 0 0│ │} │ │ to │ │}Reserved for national use │ │1 1 1│1 1 1 1│ │} │ └─────┴───────┴──────┴───────────────────────────────────────┘
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.6 IMSI
|
The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and includes a length indicator. The remainder of this element is coded as defined in GSM 04.08. The element coding is: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Rest of element coded as in GSM 04.08, │octet 3 - n│ │ not including GSM 04.08 element identifier │ │ │ or GSM 04.08 octet length value │ │ └───────────────────────────────────────────────┴────────────┘
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.7 TMSI
|
The TMSI is a fixed length element. The TMSI is an unstructured number of 4 octets in length. The coding is: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ TMSI │octet 3 - 6│ └───────────────────────────────────────────────┴────────────┘ The TMSI field is unstructured.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.8 Number Of MSs
|
This is a fixed length element which indicates the number of handover candidates that have been sent to the MSC. The coding is: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 80 (GSM 08.08 version 6.5.0 Release 1997) ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Number of handover candidates │octet 2 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the number of handover candidates. Bit 1 is the least significant bit.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.9 Layer 3 Header Information
|
This element is used to supply the BSS with information that needs to be included in the header of layer 3 messages over the radio interface. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Protocol discriminator │octet 3 │ ├───────────────────────────────────────────────┼────────────┤ │ Transaction identifier │octet 4 │ └───────────────────────────────────────────────┴────────────┘ The length indicator is a binary indication of the number of octets following in the element. The transaction identifier and protocol discriminator fields are coded as defined in GSM 04.08. The protocol discriminator occupies bit 1 to 4 in octet 3 of Layer 3 header information, the Transaction identifier occupies bit 1 to 4 in octet 4 of the Layer 3 header information.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.10 Encryption Information
|
This element contains the user data encryption information used to control any encryption equipment at the BSS. It is a variable length element. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Permitted algorithms │octet 3 │ ├───────────────────────────────────────────────┼────────────┤ │ Key │octet 4 - n│ └───────────────────────────────────────────────┴────────────┘ The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. The permitted algorithms octet is a bit map indicating the A5 encryption algorithms and no encryption. From this bit map the BSS may select an A5 algorithm or no encryption to be used. Bit No: 1 No encryption 2 GSM A5/1 3 GSM A5/2 4 GSM A5/3 5 GSM A5/4 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 81 (GSM 08.08 version 6.5.0 Release 1997) 6 GSM A5/5 7 GSM A5/6 8 GSM A5/7 A bit position encoded as 1 indicates that the BSS may use the option repesented by that bit position. A bit position encoded as 0 indicates that the BSS shall not use the option represented by that bit position. A permitted algorithms octet containing all bits encoded as 0 shall not be used. The key shall be present if at least one of the A5 encryption algorithms is permitted. When present, the key shall be 8 octets long.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.11 Channel Type
|
This element contains all of the information that the BSS requires to determine the required radio resource(s). The channel type information element has a minimum length of 5 octets and a maximum length of 10 octets. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Spare │Speech / data indicator│octet 3 │ ├───────────────────────┴───────────────────────┼────────────┤ │ Channel rate and type │octet 4 │ ├───────────────────────────────────────────────┼────────────┤ │ Permitted speech version indication / │octet 5 │ │ data rate + transparency indicator │ or │ │ │octet 5 with│ │ │extension *│ └───────────────────────────────────────────────┴────────────┘ * If the speech / data indicator (octet 3) indicates "speech" or “data”, octet 5 may optionally be extended. Otherwise octet 5 shall not be extended. The "speech / data indicator" field is coded as follows: 0001 Speech 0010 Data 0011 Signalling All other values are reserved. For values 0001 and 0010 a dedicated terrestrial resource is also required. The "channel rate and type" is coded as follows: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 82 (GSM 08.08 version 6.5.0 Release 1997) If octet 3 indicates data then octet 4 shall be coded as: 0000 1000 Full rate TCH channel Bm 0000 1001 Half rate TCH channel Lm 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. 0010 0xxx Full rate TCH channels in a multislot configuration, changes by the BSS of the the number of TCHs and if applicable the used radio interface rate per channel allowed after first channel allocation as a result of the request. 0011 0xxx Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs or the used radio interface rate per channel not allowed after first channel allocation as a result of the request. xxx (bits 3-1) indicates maximum number of traffic channels; 321 000 1 TCHs 001 2 TCHs 010 3 TCHs 011 4 TCHs 100 5 TCHs 101 6 TCHs 110 7 TCHs 111 8 TCHs All other values are reserved. If octet 3 indicates speech then octet 4 shall be coded as: 0000 1000 Full rate TCH channel Bm. Preference between the permitted speech versions for full rate TCH as indicated in octet 5, 5a etc. 0000 1001 Half rate TCH channel Lm. Preference between the permitted speech versions for half rate TCH as indicated in octet 5, 5a etc. 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 83 (GSM 08.08 version 6.5.0 Release 1997) 0000 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate allowed also after first channel allocation as a result of the request. 0001 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate not allowed after first channel allocation as a result of the request. All other values are reserved. If octet 3 indicates signalling then octet 4 shall be coded as: 0000 0000 SDCCH or Full rate TCH channel Bm or Half rate TCH channel Lm 0000 0001 SDCCH 0000 0010 SDCCH or Full rate TCH channel Bm 0000 0011 SDCCH or Half rate TCH channel Lm 0000 1000 Full rate TCH channel Bm 0000 1001 Half rate TCH channel Lm 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. All other values are reserved. The "permitted speech version indication / data rate + transparency indicator" octet is coded as follows: If octet 3 indicates speech then octet 5 shall be coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┼─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ext │permitted speech version identifier │octet 5 │ ├─────┼─────────────────────────────────────────┼────────────┤ │ext │permitted speech version identifier │octet 5a │ ├─────┼─────────────────────────────────────────┼────────────┤ │ext │permitted speech version identifier │octet 5b │ ├─────┼─────────────────────────────────────────┼────────────┤ │ext │permitted speech version identifier │octet 5c │ ├─────┼─────────────────────────────────────────┼────────────┤ │ext │permitted speech version identifier │octet 5d │ ├─────┼─────────────────────────────────────────┼────────────┤ │0 │permitted speech version identifier │octet 5e │ └─────┴─────────────────────────────────────────┴────────────┘ Bit 8 indicates extension of octet 5. 0 no extension, i.e. value "0" indicates that this octet is the last octet. 1 extension, i.e. value "1" indicates that at least one additional octet is included. If more than one permitted speech version is indicated by octet 5 (with extension), then the speech version choice is left to the BSS. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 84 (GSM 08.08 version 6.5.0 Release 1997) Bits 7-1 indicate the permitted speech version identifier; 765 4321 000 0001 GSM speech full rate version 1 001 0001 GSM speech full rate version 2 010 0001 GSM speech full rate version 3 000 0101 GSM speech half rate version 1 001 0101 GSM speech half rate version 2 010 0101 GSM speech half rate version 3 NOTE: Bits 7-1 indicate six speech versions. All other values of permitted speech version identifiers are for future use. If an unknown value is received and more than one octet 5 is received the sender expects the receiver to behave as if it has made a choice of speech version. The rules for coding preferences in octet 5, 5a - 5e are the following: - In those cases when one specific channel rate is indicated in octet 4, the non-empty set of permitted speech versions is included. Within this set the permitted speech versions are included in order of speech version preferences. - In those cases when a preference for a channel rate is indicated in octet 4, the non-empty sets of permitted speech versions for the respective channel rate are included in order of the channel rate preferences indicated in octet 4. Within a set of permitted speech versions for a channel rate, the permitted speech versions are included in order of speech version preferences. - In those cases when no preference or specific channel rate is indicated in octet 4, the permitted speech versions are included in order of speech version preferences. Always octet 5 has the highest preference followed by octet 5a and so on. For each channel rate allowed by octet 4 at least one speech version shall be present. If octet 5 indicates no extension and bits 7-1 is coded "000 0001", then the preference is interpreted based upon the octet 4 value as follows: - in those cases when octet 4 indicates one specific channel rate, then “speech version 1” for the indicated channel rate is permitted. - in those cases when octet 4 indicates a preference for a channel rate, then “speech version 1” for any of the allowed channel rates is permitted. - in those cases when octet 4 does neither indicate a preference for a channel rate nor a specific channel rate, then “speech version 1” for any of the allowed channel rates is permitted and speech full rate version 1 is preferred. If octet 3 indicates data, and octet 4 does not indicate multislot configuration, then octet 5 shall be coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┼─────┼─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ext │T/NT │ Rate │octet 5 │ ├─────┼─────┴─────┴─────┼─────┴─────┴─────┴─────┼────────────┤ │ext │ spare │ allowed │octet 5a │ │ │ │ r i/f rates │ │ └─────┴─────────────────┴───────────────────────┴────────────┘ Bit 8 indicates extension of octet 5. 0 no extension, i.e. value "0" indicates that this octet is the last octet. 1 extension, i.e. value "1" indicates that at least one additional octet is included. Bit 7: 0 Transparent service 1 Non-transparent service. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 85 (GSM 08.08 version 6.5.0 Release 1997) For non-transparent service bits 6-1 indicate the radio interface data rate; 65 4321 00 0000 12 kbit/s if the channel is a full rate TCH, or 6 kbit/s if the channel is a half rate TCH 01 1000 14.5 kbit/s 01 0000 12 kbits/s 01 0001 6 kbits/s If bit 7 in octet 5 indicates non-transparent service and octet 5a is included the ‘rate’ in octet 5 indicates the wanted air interface data rate and the ‘allowed r i/f rates’ indicates the other possible data rates allowed. All other values are reserved. For transparent service bits 6-1 indicate the data rate; 65 4321 01 1000 14.4 kbit/s 01 0000 9.6kbit/s 01 0001 4.8kbit/s 01 0010 2.4kbit/s 01 0011 1.2Kbit/s 01 0100 600 bit/s 01 0101 1200/75 bit/s (1200 network-to-MS / 75 MS-to-network) If bit 7 in octet 5 indicates transparent service octet 5 shall not be extended. All other values are reserved. Octet 5a shall be coded as follows; Bit 8 reserved for extension. A coding of 0 indicates no extension. Bits 4 to 1 indicate allowed radio interface data rate, per channel; Bit 4: 0 14.5 kbit/s (TCH/F14.4) not allowed 1 14.5 kbit/s (TCH/F14.4) allowed Bit 3: Spare Bit 2: 0 12.0 kbit/s (TCH/F9.6) not allowed 1 12.0 kbit/s (TCH/F9.6) allowed Bit 1: 0 6.0 kbit/s (TCH/F4.8) not allowed 1 6.0 kbit/s (TCH/F4.8) allowed If octet 3 indicates data and octet 4 indicates Full rate TCH channels in a multislot configuration, octet 5 and 5a shall be coded as follows; ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┼─────┼─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ext │T/NT │ Rate │octet 5 │ ├─────┼─────┴───────────┬───────────┬───────────┼────────────┤ │ext │ spare │ │allowed │octet 5a │ │ │ │ │r i/f rate │ │ └─────┴─────────────────┴───────────┴───────────┴────────────┘ Octet 5 shall be coded as follows; Bit 8 : extension bit 0 indicates no extension 1 indicates that at least one additional octet is included ETSI ETSI TS 100 590 V6.5.0 (2000-06) 86 (GSM 08.08 version 6.5.0 Release 1997) Bit 7 : 0 Transparent service 1 Non-transparent service. For non-transparent service bits 6-1 indicates wanted total radio interface data rate; 65 4321 01 0110 58 kbit/s (4x14.5 kbit/s) 01 0100 48.0 / 43.5 kbit/s (4x12 kbit/s or 3x14.5 kbit/s) 01 0011 36.0 / 29.0 kbit/s (3x12 kbit/s or 2x14.5 kbit/s) 01 0010 24.0 / 24.0 / 29.0 kbit/s (4x6 kbit/s or 2x12 kbit/s or 2x14.5 kbit/s) 01 0001 18.0 / 24.0 / 14.5 kbit/s (3x6 kbit/s or 2x12 kbit/s or 1x14.5 kbit/s) 01 0000 12.0 / 14.5 kbit/s (1x12 kbit/s or 1x14.5 kbit/s) All other values are reserved. For transparent service bits 6-1 indicates requested air interface user rate; 65 4321 01 1111 64 kbit/s, bit transparent 01 1110 56 kbit/s, bit transparent 01 1101 56 kbit/s 01 1100 48 kbit/s 01 1011 38.4 kbit/s 01 1010 28.8 kbit/s 01 1001 19.2 kbit/s 01 1000 14.4 kbit/s 01 0000 9.6 kbit/s All other values are reserved. Octet 5a shall be coded as follows; Bit 8 reserved for extension. A coding of 0 indicates no extension. Bits 4 to 1 indicates allowed radio interface data rate, per channel; Bit 4: 0 14.5/14.4 kbit/s (TCH/F14.4) not allowed 1 14.5/14.4 kbit/s (TCH/F14.4) allowed Bit 3: Spare Bit 2: 0 12.0/9.6 kbit/s (TCH F/9.6) not allowed 1 12.0/9.6 kbit/s (TCH F/9.6) allowed Bit 1: 0 6.0/4.8 kbit/s (TCH F/4.8) not allowed 1 6.0/4.8 kbit/s (TCH F/4.8) allowed If octet 5a is not included, allowance of radio interface data rates of 12.0 and 6.0 shall be presumed. NOTE: For data services, the information in the channel type Information Element is used to set the "E-bits" and map the "D-bits" (as described in GSM 04.21 and 08.20) and to select the correct channel coding. If octet 3 indicates signalling then octet 5 is spare.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.12 Periodicity
|
This element defines the periodicity of a particular procedure. It is fixed length, 2 octets. The coding is as follows: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 87 (GSM 08.08 version 6.5.0 Release 1997) ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Periodicity │octet 2 │ └───────────────────────────────────────────────┴────────────┘ When the Resource Indication Method IE is set to either "method i) of subclause 3.1.3.1" or "method iii) of subclause 3.1.3.1" and the periodicity parameter is not 0000 0000 then the coding of the periodicity parameter is: 0000 0001 Period 1111 1111 - where the period is the binary value of octet 2 * 100 ms (ie 100 ms to 25,500 ms). When the Resource Indication Method IE is set to "method i) of subclause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall ignore this IE. When the Resource Indication Method IE is set to "method iii) of subclause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall treat the message according to subclause 3.1.19.4, case 2. When the Resource Indication Method IE is set to either "method ii) of subclause 3.1.3.1" or "method iv) of subclause 3.1.3.1" then the Periodicity IE shall be ignored.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.13 Extended Resource Indicator
|
This element defines which additional resource information related to a given cell the BSS shall transfer to the MSC. It may also indicate the subsequent reporting mode for that cell. The coding is as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────┬─────┬─────┼────────────┤ │ spare │SM │TARR │octet 2 │ └───────────────────────────────────┴─────┴─────┴────────────┘ SM = Subsequent mode TARR = Total Accessible Resource Requested The coding of the Total Accessible Resource Requested field is as follows: 0 no extra Resource Information is requested 1 The total number of accessible channels is requested If the Resource Indication Method is not set to "method ii of subclause 3.1.3.1" then the Subsequent Mode field is ignored. If the Resource Indication Method is set to "method ii of subclause 3.1.3.1" then the Subsequent Mode field is decoded as follows: 0 method iv) of subclause 3.1.3.1. 1 if the reporting mode prior to receipt of this IE was i) or iii) of subclause 3.1.3.1 then the subsequent mode shall be respectively i) or iii); otherwise the subsequent mode shall be method iv) of subclause 3.1.3.1.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.14 Total Resource Accessible
|
This element gives the total number of full and half rate channels accessible on any given cell at the time of construction of the message. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 88 (GSM 08.08 version 6.5.0 Release 1997) It defines these parameters in terms of the number of channels which are accessible or in use. No separation between the defined interference bands is made. The element is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Total number of accessible │octet 2 │ │ full rate channels │octet 3 │ ├───────────────────────────────────────────────┼────────────┤ │ Total number of accessible │octet 4 │ │ half rate channels │octet 5 │ └───────────────────────────────────────────────┴────────────┘ Octets 2 and 3 give a 16 bit binary representation of the total number of full rate channels accessible (i.e. available for service or currently assigned). Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels accessible (i.e. available for service or currently assigned). This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels. (eg. If there is an accessible half rate channel and an accessible full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.