hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.15 General SCCP Abnormal Conditions
|
If a user-out-of-service information or signalling-point-inaccessible information is received by the BSSAP or BSSOMAP no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received. When a user-out-of-service information or signalling-point-inaccessible is received by the BSS an optional timer may be started. When the timer expires all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped. If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the BSSAP procedures are being performed or while a dedicated resource is still allocated the following actions are taken: At BSS: The radio resources associated with the SCCP connection are cleared by an appropriate radio procedure. Any BSS procedure relating to that connection is abandoned. The resources allocated to the call associated to the connection are released. At MSC: The call associated with the SCCP connection is cleared as soon as possible. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 35 (GSM 08.08 version 6.5.0 Release 1997) At the BSS, communication over assigned radio channels shall be assumed to be continuing until either the SCCP connection is lost, a clearing sequence is received, or no signal is received from an MS for longer than the guard time defined in GSM 04.08. If the BSS recognises that a call has terminated then a CLEAR REQUEST message should be generated. If a 2Mbit/s system fails and one of the standard alarms is received, no action is taken at the BSS on the calls associated with the traffic channels involved. At the MSC, calls should be cleared if either subscriber clears, or if the BSS sends a CLEAR REQUEST message. Clearing of affected calls by the MSC may take place after loss of the traffic channels for a period defined by the operator. For the procedures controlled by the MSC, and in particular procedures where the MSC sends a request for resources at the BSS and waits for an acknowledge, the implementation in the MSC must provide means for avoiding deadlock situations at the BSS as e.g. hanging resources.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.16 Initial MS message
|
When the SCCP connection establishment is performed by the BSS, the radio interface initial L3 message received from the MS (piggybacked on the SABM frame) is processed as follows: The BSS shall analyse the protocol discriminator of the message. If the BSS does not support the protocol, reactions of the BSS are specified in GSM 04.08. If the BSS supports the protocol, it shall, if the protocol is PDSS2, continue as specified in GSM 03.63; otherwise the BSS shall continue as follows: The BSS shall analyse the message to a level which allows the extraction by the BSS of the Classmark information. However, except for the NOTIFICATION RESPONSE, the entire radio interface initial L3 message (e.g. CM SERVICE REQUEST, PAGING RESPONSE, CM REESTABLISHMENT REQUEST, LOCATION UPDATING REQUEST, IMSI DETACH, IMMEDIATE SETUP) is also passed to the MSC, using a COMPLETE LAYER 3 INFORMATION message. The BSS does not analyse the contents of the initial layer 3 message, other than the Classmark information. The BSS may also give the MSC a description of the channel on which the initial layer 3 message was received.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.17 Queuing Indication
|
The purpose of the QUEUING INDICATION message is t inform the MSC about a delay in the allocation of the necessary dedicated radio resources. The procedure is only relevant if the system is using a queuing procedure for traffic channels in the BSS, (subclause 3.1.17.1) and/or for handover of traffic channels (subclause 3.1.17.2)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.17.1 Operation of the procedure in case of assignment procedure
|
After the ASSIGNMENT REQUEST message without having the necessary TCH available the ASSIGNMENT REQUEST message shall be put into a queue; the QUEUING INDICATION message shall be returned to the MSC and the timer T11 shall be started. The timer value T11 specifies the maximum queuing delay and is determined by the operator. The procedure shall be terminated with a successful or unsuccessful assignment of the required traffic channel(s) by sending an ASSIGNMENT COMPLETE or an ASSIGNMENT FAILURE message, respectively, to the MSC. If the timer T11 expires the ASSIGNMENT REQUEST message shall be removed from the queue and a CLEAR REQUEST message shall be sent to the MSC, with the Cause "no radio resource available". 3.1.17.2 Operation of the procedure in case of hand-over resource allocation procedure After the HANDOVER REQUEST message without having the necessary TCH available the HANDOVER REQUEST shall be put into a queue; the QUEUING INDICATION message shall be returned to the MSC and the timer Tqho shall be started. The timer value Tqho specifies the maximum queuing delay and is determined by the operator. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 36 (GSM 08.08 version 6.5.0 Release 1997) The procedure shall be terminated with a successful or unsuccessful reservation of the required traffic channel(s) by sending a HANDOVER REQUEST ACKNOWLEDGE or a HANDOVER FAILURE message, respectively, to the MSC. If the timer Tqho expires the HANDOVER REQUEST shall be removed from the queue and a HANDOVER FAILURE message shall be sent to the MSC with the Cause value "no radio resource available".
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.18 Data Link Control SAPI not Equal to "0"
|
The radio interface can support data links with the SAPI not equal to "0".
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.18.1 Data link set up across the radio interface
|
This subclause deals with the impact of data link establishment (SAPI not equal to "0") on the MSC to BSS interface.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.18.1.1 MS to MSC direction
|
In the MS to MSC direction the receipt of a layer 3 message via a data link where SAPI does not equal "0" at the BSS will be transferred to the MSC as a DTAP message with the DLCI (Data Link Connection Identification) octet set appropriately.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.18.1.2 MSC to MS Direction
|
Receipt of a layer 3 (DTAP) message from the MSC with the SAPI (indicated in the DLCI) not equal to "0" will cause one of the following actions: - the triggering of a data link set up to support the message transfer across the radio interface if no suitable link exists; - the transmission of the message to the MS if a suitable link has already been established; - the sending of a BSSMAP SAPI "N" REJECT message to the MSC if for any reason the data link cannot be established, A Cause Information Element is included; typical Cause values are: "O&M intervention", "processor overload", "BSS not equipped", "MS not equipped".
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.18.2 Choice of the signalling link
|
When the BSS relays a message of the PDSS1 protocol received on the air interface to the MSC, it shall indicate in the DLCI (see GSM 08.06) on which control channel and SAPI the message was received. When the MSC sends a DTAP message to the BSS, it shall, – if the protocol of the corresponding air interface layer 3 message is PDSS1, specify on which control channel and SAPI of the air interface the L3 message shall be sent – otherwise not further specify the control channel on the air interface. When the BSS relays an air interface L3 message received in a DTAP message on the A interface to the MS, it shall – if the DLCI does not further specify the signalling channel of the air interface, send it on the appropriate signalling link – if the BSS supports PDSS1 and the DLCI specifies which control channel is to be used for transmission on the air interface, the BSS shall transfer the air interface L3 message on the specified control channel. NOTE: If the BSS does not support PDSS1, it considers the part of the DLCI possibly indicating the control channel to be used on the air interface as spare bits, see GSM 08.06. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 37 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19 BSSMAP Error Handling
|
To allow for the introduction of new functions the following rules shall be used to determine the actions of a receiving entity when it receives a message, part or all of which it is unable to understand. As the recipient is unable to tell the difference between a new, previously unspecified coding and an erroneous coding, the recipient also uses the same rules for error handling. The robustness of a recipient in handling erroneous messages does not relax the requirement that the transmitter shall obey the present document. However, it is intended that functionality can be gradually added to an entity, and no obstacle to intermediate phase equipment is intended. With the exception of subclause 3.1.19.6, the specific 'abnormal case' handling in other subclauses of 08.08 take precedence over this subclause.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.1 Definitions of Types of Information Elements
|
The following definitions shall be used in subclause 3.1.19 and only in this subclause. Essential Elements These are the conditional elements when the condition for their reception is fulfilled, plus the Mandatory elements excluding the Cause value information element (3.2.2.5). Mandatory Elements These are the Information Elements marked as 'M' in subclause 3.2.1. Non-Essential Elements Non-essential elements are all the information elements that are not defined as essential. Conditional Elements In the indicated messages the following elements are conditional: Circuit identity code in 3.2.1.1 and 3.2.1.8. NOTE: A conditional IE is an IE whose presence or absence in a message can be determined by information contained in the rest of the message. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 38 (GSM 08.08 version 6.5.0 Release 1997) Transparent Elements The following elements are defined as transparent: for the BSS: TMSI; RR cause; Layer 3 information in the BSSMAP HANDOVER COMMAND message; and Layer 3 message contents; and for the MSC: Resource situation. Layer 3 information in the BSSMAP HANDOVER REQUEST ACKNOWLEDGE message; and "Old BSS to new BSS information" in the BSSMAP HANDOVER REQUIRED message Non-Transparent Elements Non-transparent elements are all the information elements that are not defined as transparent.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.2 Erroneous Events
|
The following events shall be regarded as errors by the recipient: 1 a message whose type is non-existent, unrecognisable, not consistent with the recipient's state, or, that is sent in the wrong direction. This includes messages that should use the SCCP connectionless service but that are received on an SCCP connection, and vice versa; 2 a missing essential information element; 3 use of a reserved codepoint in an information element that is both essential and non-transparent; and 4 an essential and non-transparent information element which is too short (the contents of any 'Length' octet shall be used to determine the boundary of the element). When a recipient detects one or more of these events it shall return the appropriate error message with a suitable Cause value and the message shall be discarded.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.3 Non-erroneous Events
|
The following events shall not be regarded as errors by the recipient: 1 spare bits with an unexpected value in any information element; 2 the use of additional octets in any information element with a length octet; 3 a missing non-essential information element; 4 use of reserved codepoints in any non-essential information element or in any transparent information element; and 5 a non-essential information element or a transparent information element whose length is too short. When the recipient detects one or more of these events the receiving entity shall ignore the information that it is unable to understand and treat the message on the basis of the information that remains. Additionally, all information in a message that is received after the start of an information element with an unrecognisable identifier shall be ignored. The message shall be accepted or rejected solely on the basis of the information received before the start of the unrecognisable element; and, when more information elements of a particular type are received than are expected, the last one(s) shall be ignored. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 39 (GSM 08.08 version 6.5.0 Release 1997)
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.4 Other Events
|
The following events should be treated on a case by case basis and the outcome may depend upon the capabilities of the recipient. 1 The recipient may accept messages that contain information elements that do not appear to be in the correct sequence. Elements that occur more than once in a message shall be assumed to have been transmitted in the correct order. Recipients that do not accept out of sequence information elements shall regard the message as containing unexpected and/or missing information elements and follow the procedures of subclauses 3.1.19.1 and/or 3.1.19.2. 2 Where a field in an information element contains a value, which the recipient knows to be incorrect, the recipient shall either reject the message or it shall ignore that field, and treat the information that remains in the message. (e.g. if the 'Number of MSs' in a Handover Candidate Response message is greater than the number of Handover Required messages received).
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.5 Appropriate Error Message and Cause Value
|
The choice of error message depends upon the received message type: Received message type Error Message ASSIGNMENT REQUEST ASSIGNMENT FAILURE HANDOVER REQUEST HANDOVER FAILURE HANDOVER REQUIRED if "Response Request" i.e. is present HANDOVER REQUIRED REJECT if "Response Request" i.e. is not present CONFUSION CIPHER MODE COMMAND CIPHER MODE REJECT VGCS/VBS SETUP VGCS/VBS SETUP REFUSE VGCS/VBS ASSIGNMENT REQUEST VGCS/VBS ASSIGNMENT FAILURE CONFUSION an error message shall not be used all other message types CONFUSION When a problem is experienced with a message sent over an SCCP connection, the error message is returned over that connection. When a problem occurs in a message sent using the SCCP connectionless service, the error message is returned using the SCCP connectionless service. To avoid overload of the A-interface, transmission of error messages may be inhibited. (However, the transmission of Assignment Failure, Handover Failure, Handover Required Reject and Cipher Mode Reject messages in the cases required by 3.1.1, 3.1.5 and 3.1.14 shall not be inhibited.) When the transmission of error messages is inhibited, they shall be replaced by some kind of notification to O&M. Several settings may be used to allow various subsets of 'error events' to trigger error messages while the remaining events only lead to O&M notification. The Error pointer in the Diagnostics information element should be used to indicate the position of a detected error in the received message. Typical Causes are: Cause Usage Invalid cell Indicated cell not controlled by the BSS or not reachable through the MSC. Invalid message contents May be used in any error message. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 40 (GSM 08.08 version 6.5.0 Release 1997) Protocol error between BSS The received message is not and MSC consistent with the receiver's state, or the message has been sent in the wrong direction, or the message uses the wrong SCCP service (connection oriented instead of connectionless or vice versa). Information element or Data missing from the area field missing indicated by the error pointer. Incorrect value A field (that should be indicated by the error pointer) contains an incorrect or incompatible value, or uses a reserved codepoint. Unknown message type The received message was of an unknown type. Unknown information element An information element identifier (that should be indicated by the error pointer) contains an unknown value.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.6 Unequipped Circuit Identification Code
|
If a MSC or BSS receives a message indicating one or more circuit which are unknown the following actions shall be taken: - If an ASSIGNMENT REQUEST, a VGCS/VBS ASSIGNMENT REQUEST or a HANDOVER REQUEST message is received containing a circuit identity code which is unknown to the BSS the appropriate failure message is returned to the MSC. In addition the UNEQUIPPED CIRCUIT message is sent to the MSC for the circuit concerned. - If an ASSIGNMENT COMPLETE, a VGCS/VBS ASSIGNMENT RESULT, a HANDOVER REQUEST ACKNOWLEDGE or a CHANGE CIRCUIT ACKNOWLEDGE Message is received containing a circuit identity code which is unknown to the MSC, it is up to the MSC to correct the situation, e.g. by performing a circuit re-selection procedure and sending an UNEQUIPPED CIRCUIT Message to the BSS. - If a circuit supervision message (BLOCK, UNBLOCK or RESET CIRCUIT) is received containing a circuit identity code which is not known no respective acknowledgement is returned. Instead an UNEQUIPPED CIRCUIT Message is sent to the peer entity for the circuit concerned. - If a circuit supervision acknowledgement message (BLOCKING ACKNOWLEDGE, UNBLOCKING ACKNOWLEDGE or RESET CIRCUIT ACKNOWLEDGE) is received containing a circuit identity code which is not known, an UNEQUIPPED CIRCUIT message is sent to the peer entity for the circuit concerned. - If a circuit group supervision message (GROUP BLOCK, GROUP UNBLOCK) is received which affects one or more circuits which are unknown to the own entity the returned acknowledgement message shall not contain any information about these circuit(s), i.e. the respective status bit(s) in the status field shall not be set. Instead an UNEQUIPPED CIRCUIT Message is sent to the peer entity for the circuit(s) concerned. - If a circuit group supervision acknowledgement message (CIRCUIT GROUP BLOCKING ACKNOWLEDGE or CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE) is received which affects one or more circuits which are unknown to the own entity an UNEQUIPPED CIRCUIT message is sent to the peer entity for the circuit(s) concerned. - If an UNEQUIPPED CIRCUIT Message is received indicating a circuit which is unknown in the own entity no UNEQUIPPED CIRCUIT Message will be returned. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 41 (GSM 08.08 version 6.5.0 Release 1997) If an UNEQUIPPED CIRCUIT Message is received indicating a circuit(s) that is known to the recipient, the indicated circuit(s) should be removed from service and the situation should be reported to the maintenance system for further intervention. The UNEQUIPPED CIRCUIT message is not to be acknowledged by the recipient.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.19.7 Field Elements
|
This section defines the generic error handling to be applied to the field elements found in the "Old BSS to new BSS information" information element. All field elements shall be treated as non-essential. The following events shall not be regarded as errors by the recipient: 1 spare bits with an unexpected value in any field element; 2 the use of additional octets in any field element; 3 a missing field element; 5 a field element whose length is either too short or too long. When the recipient detects one or more of these events the receiving entity shall ignore the information that it is unable to understand and treat the message on the basis of the information that remains. Additionally, When an unknown field element identifier is encountered, the unknown field element shall be skipped and the receiver shall continue processing any remaining field elements; and, when more field elements of a particular type are received than are expected, the last one(s) shall be ignored; and, when a sub-field in a field element contains a value, which the recipient knows to be incorrect, the recipient shall either ignore that sub-field or ignore the entire field (treating it as if the field element had not been received). and, when a sub-field in a field element contains a reserved value, the recipient shall ignore the entire field element (treating it as if the field element had not been received).
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.20 Load Indication Procedure
|
The purpose of the load indication procedure is to inform all neighbour BSS's about the traffic situation of a cell. The philosophy is to control the incoming handover traffic at the source, i.e. the BSS of the concerned cell informs all of its neighbour BSS's about the load situation. This is achieved by sending a LOAD INDICATION message to the neighbour BSS's. On receipt of the LOAD INDICATION message the BSS may analyse the load information and take the traffic load into consideration when deciding a handover. The algorithm in which the BSS decides on starting a Load Indication procedure is operator dependent. The implementation of the Load Indication procedure shall be regarded as optional, that means, if this procedure is not used, the Load Indication message may be ignored by these network elements.
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.1.20.1 Operation of the procedure
|
The procedure operates as follows: The BSS shall send the LOAD INDICATION message to the MSC with the following information: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 42 (GSM 08.08 version 6.5.0 Release 1997) - Cell Identifier of the cell where the traffic load situation takes place (Cell Identifier information element). - The Time indication information element contains the time where the traffic load information shall be valid on the receiving side. - The Cell identifier list information element contains the cell identifier of the affected neighbour cells. - The information about the total number of channels accessible or in use, and the information about the current number of channels available for each reported channel type on the indicated cell (Resource situation information element). - The reason for sending this message (Cause information element). On receipt of the LOAD INDICATION message, the MSC transmits this message to all BSS's as derived from the Cell identifier list Information Element. NOTE: In the case where more than one indicated cells in the cell identifier list IE belong to the same BSS, the MSC should try to send the LOAD INDICATION message only once to this BSS. With each reception of a LOAD INDICATION message from the MSC the target BSS shall analyse the resource information and adapt the handover traffic either from all cells of the BSS-area or only from the cells contained in the Cell identifier list Information Element to the cell indicated in the Cell identifier Information Element. The BSS shall ignore all Cell identifiers for cells which do not belong to its area. In the case where the BSS receives a LOAD INDICATION message without the Resource situation information element, that means the indicated cell is not able to perform incoming handover requests and the receiving BSS may stop the whole handover traffic to this cell. The traffic load information shall only be valid the time as indicated in the Time indication Information Element. The control timer shall be stopped with the receipt of a new LOAD INDICATION message and restarted with the new value. If the Time field contains the value 0, the load information is no longer valid. 3.1.21 Voice group call service and voice broadcast service call set-up and resource assignment To set-up a VGCS/VBS call the MSC initiates the VGCS/VBS set-up procedure to the BSS. The MSC can then allocate resources to the VGCS/VBS call by initiating the VGCS/VBS Assignment procedure.
|
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
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.