hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 ha... |
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... |
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 ... |
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... |
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 LOA... |
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). -... |
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/V... |
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 cont... |
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 shal... |
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 a... |
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 allocat... |
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 reli... |
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 se... |
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 re... |
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... |
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 proce... |
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 carry... |
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 ... |
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 el... |
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 INDICA... |
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 U... |
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.... |
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 Caus... |
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... |
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... |
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 ... |
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 REF... |
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 in... |
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 5... |
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... |
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... |
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 Resourc... |
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... |
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 M... |
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.... |
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.... |
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 ... |
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 DIREC... |
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). INFOR... |
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 SC... |
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... |
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.... |
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 Bot... |
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 In... |
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 Encr... |
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 connectio... |
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 DIRE... |
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.2... |
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 failur... |
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 ... |
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 t... |
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.... |
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 messa... |
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.... |
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... |
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 ar... |
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 ... |
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 19... |
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... |
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... |
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 ... |
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 ... |
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-B... |
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... |
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 ... |
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... |
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-0... |
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... |
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 ... |
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-MS... |
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 ... |
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 Reserv... |
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... |
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 -... |
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... |
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 │ │ ├... |
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 │ ├──────────────────────────────... |
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 │ │ ├─────┴─────┴─────┴─────┴──... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.