hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 10.1 Coding of A-TRAU frame | ................................................................................................................................10 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 10.2 Framing Pattern Substitution in A-TRAU frame | ..............................................................................................11 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 10.2.1 FPS encoding | ....................................................................................................................................................11 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 10.3 A-TRAU Synchronisation Pattern | ....................................................................................................................13 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 11 THE RAA'' FUNCTION | ....................................................................................................................... 13 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 12 The RA2 Function | ................................................................................................................................. 13 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 13 The Multiplexing Function | .................................................................................................................... 13 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14 Support of non-transparent bearer services | ........................................................................................... 14 14.1 TCH/F9.6 and TCH/F4.8 kbit/s channel codings .............................................................................................14 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14.1.1 Alignment | .........................................................................................................................................................15 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14.1.2 Support of Discontinuous Transmission (DTX) | ...............................................................................................15 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14.1.3 Order of Transmission | ......................................................................................................................................15 14.2 TCH/F14.4 channel coding...............................................................................................................................15 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14.2.1 Alignment | .........................................................................................................................................................16 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 14.2.2 Support of Discontinuous Transmission (DTX) | ...............................................................................................16 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15 Support of transparent bearer services | ................................................................................................... 16 15.1 TCH/F9.6 and TCH/F4.8 channel codings.......................................................................................................16 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.1.1 User rate adaptation on the A interface, AIUR less or | equal to 38,4 kbit/s......................................................16 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.1.2 User rate Adaptation on the A-interface, AIUR greater | than 38,4 kbit/s..........................................................17 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.1.3 Relation between AIUR and the number of channels | .......................................................................................18 ETSI ETSI TS 100 591 V7.1.0 (2001-03) 4 3GPP TS 08.20 version 7.1.0 Release 1998 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.1.4 Handling of status bits X, SA, SB | ....................................................................................................................18 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.1.5 Handling of bits E1 to E7 | .................................................................................................................................18 15.2 TCH/F14.4 channel coding...............................................................................................................................19 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.2.1 User rate adaptation on the A interface, AIUR less or | equal to 56 kbit/s.........................................................19 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.2.2 User Rate Adaptation on the A-interface, AIUR greater | than 56 kbit/s ...........................................................19 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.2.3 Relation between AIUR and the number of channels | .......................................................................................19 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 15.2.4 Handling of status bits X and SB | ......................................................................................................................19 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 16 Frame Formats | ....................................................................................................................................... 20 Annex A (informative): Frame Pattern Substitution ......................................................................... 22 A.1 Special cases........................................ |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 1 Scope | The present document specifies the layer 3 procedures used on the Base Station System (BSS) to Mobile-services Switching Centre (MSC) interface for control of GSM services. For the purposes of call control and mobility management, messages are not interpreted at the Base Station System (BSS) which acts as a relay funct... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04, see clause 5 for Vocabulary. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 11 (GSM 08.08 version 6.5.0 Release 1997) |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 2 Application to interface structures | The underlying transport mechanism defined to carry signalling information between the BSS and the MSC is the Message Transfer Part (MTP), and the Signalling Connection Control Part (SCCP) of Signalling System No.7. The MTP and SCCP are used to support communication between the MSC and two conceptual entities within th... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 2.1 The BSS Operation and Maintenance Application Part | If operation and maintenance messages are transferred by means of this interface then they shall use SCCP messages. The application protocol for the Operation and Maintenance Application Part is defined in the GSM 12 series Technical Specifications. The routing and addressing is provided by the SCCP and allows the MSC ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 2.2 The Direct Transfer Application Part | The Direct Transfer Application Part (DTAP) is used to transfer call control and mobility management messages between the MSC and the MS. The DTAP information in these messages is not interpreted by the BSS. GSM 08.06 contains more detail relating to the handling of DTAP messages at the BSS, the multiplexing of the mes... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 2.3 The BSS Management Application Part | 2. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3 The BSS Management Application Part | The BSSMAP supports all of the procedures between the MSC and the BSS that require interpretation and processing of information related to single calls, and resource management. Some of the BSSMAP procedures result in, or are triggered by, Radio Resource (RR) management messages defined in GSM 04.08. The BSSMAP procedu... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 2.4 Handling of abnormal events related to the BSSAP Header | The BSSAP header is specified in GSM 08.06. Several abnormal events may be detected by the receiver: - use of a reserved value in the DLCI or discriminator; - length octet with value zero; - length octet with a value inconsistent with that indicated by the SCCP. In these cases the receiver may send a BSSMAP CONFUSION m... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1 BSSMAP Procedures | This subclause describes the procedures used in the BSS Management Application Part. There are the following main procedures: * Assignment figure 2 # Blocking figure 10 and 25 # Resource indication figure 12 # Reset figure 11 * Handover required indication figure 4 * Handover resource allocation figure 5 * Handover exe... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.1 Assignment | The purpose of the assignment procedure is to ensure that the correct dedicated radio resource(s) can be allocated or reallocated to a MS that requires it. However, the initial random access by the MS and "Immediate Assignment" to a DCCH is handled autonomously by the BSS without reference to the MSC. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.1.1 Successful Operation | The initial conditions are assumed to be that the MS is in contact with the fixed infrastructure of a PLMN by means of one or more dedicated radio resources (and possibly a terrestrial resource), and that the MSC has analysed any relevant call control information and wishes to allocate or reallocate to the MS one or mo... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.1.2 Assignment Failure | The following failure conditions may occur: The BSS may not be able to use the terrestrial resource that the MSC has indicated in which case an ASSIGNMENT FAILURE message will be returned to the MSC with the cause set to "requested terrestrial resource unavailable". If the requested channel type or resource (e.g. chann... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.1.3 Abnormal Conditions | If the BSS receives an ASSIGNMENT REQUEST message calling up a terrestrial circuit that is already assigned to another call then an ASSIGNMENT FAILURE message will be returned with a Cause value of: "terrestrial circuit already allocated" and no action will be taken on the radio interface. ETSI ETSI TS 100 590 V6.5.0 (... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.2 Blocking and Unblocking | As described in subclause 3.1.1 the assignment procedure depends upon one side, the MSC or the BSS, choosing the terrestrial resource to be used. If the entity on one side puts out of service any terrestrial circuit, it needs to inform the peer entity on the other side of the interface. This is performed by using a sim... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.2.1 Successful Operation | The procedure operates as follows: Initial conditions are assumed to be that all circuits are remotely unblocked. An entity may locally block a terrestrial circuit because: - Operation and Maintenance intervention makes the circuit unavailable for use (Cause value: "O and M intervention"). - An equipment failure makes ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.2.2 Abnormal Conditions | If a blocking acknowledge message is not received for a block message within T1 (T20, T21, T22) seconds then the block message will be repeated. If this occurs a second time the circuits will be kept marked as locally blocked, and the situation must then be resolved internally within the circuit slave or by O&M procedu... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.2.2.1 Applying to the Single Circuit Block Procedure | i) If a BLOCK message is received for a circuit already remotely blocked, a BLOCKING ACKNOWLEDGE message will be sent. ii) If an UNBLOCK message is received for a remotely unblocked circuit, an UNBLOCKING ACKNOWLEDGE message will be sent. iii) If a BLOCKING ACKNOWLEDGE message, which is not expected as an acknowledgeme... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.2.2.2 Applying to the Circuit Group Block Procedure | v) If a CIRCUIT GROUP BLOCK message is received relating to remotely blocked circuits then blocking acknowledgement indications for those circuits are given in the status field of the corresponding CIRCUIT GROUP BLOCKING ACKNOWLEDGE message which will be sent in response. vi) If a CIRCUIT GROUP UNBLOCK message is recei... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.3 Resource Indication | The purpose of the resource indication procedure is: - To inform the MSC of the amount; - of radio resource that is spare at the BSS and available for traffic carrying purposes; and - of the total amount of the accessible radio resource (i.e. available for service or currently assigned). This cannot easily be derived f... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.3.1 Successful Operation | The procedure relates to a single cell. The MSC determines the resource information (i.e. the resource available information and optionally the total resource accessible information) and the manner in which the BSS transfers this resource information to the MSC by sending a RESOURCE REQUEST message to the BSS. This mes... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4 Reset | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.1 Global Reset Procedure | The purpose of the reset procedure is to initialise the BSS and MSC in the event of a failure. The procedure is a global procedure applying to a whole BSS, and therefore all messages relating to the reset procedure are sent as global messages using the connectionless mode of the SCCP. If only a limited part of the MSC ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.1.1 Reset at the BSS | In the event of a failure at the BSS which has resulted in the loss of transaction reference information, a RESET message is sent to the MSC. This message is used by the MSC to release affected calls and erase all affected references, and to put all circuits into the idle state. After a guard period of T2 seconds a RES... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.1.2 Reset at the MSC | In the event of a failure at the MSC which has resulted in the loss of transaction reference information, a RESET message is sent to the BSS. This message is used by the BSS to release affected calls and erase all affected references. After the sending of the RESET to the BSS, an MSC that does not allocate the circuits... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.1.3 Abnormal Conditions | 3.1.4.1.3.1 Abnormal Condition at the BSS If the BSS sends a RESET message to the MSC and receives no RESET ACKNOWLEDGE message within a period T4 then it shall repeat the entire reset procedure. The sending of the RESET message is repeated a maximum of "n" times where n is an operator matter. After the n-th unsuccessf... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.2 Reset Circuit | The purpose of the reset circuit procedure is to restore the information in MSC/BSS in the case of a failure which has affected only a small part of the equipment (e.g. abnormal SCCP connection release). |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.2.1 Reset Circuit at the BSS | If a circuit has to be put to idle at the BSS due to an abnormal SCCP-connection release, a RESET CIRCUIT message will be sent to the MSC. When the MSC receives this message, it clears the possible call and puts the circuit, if known, to the idle state. If the circuit is known, a RESET CIRCUIT ACKNOWLEDGE message is re... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.2.2 Reset Circuit at the MSC | If a circuit has to be put to idle at the MSC due to an abnormal SCCP-connection release, a RESET CIRCUIT message will be sent to the BSS. When the BSS receives a RESET CIRCUIT message, it shall respond with a RESET CIRCUIT ACKNOWLEDGE message in case the circuit can be put to idle. If circuit allocation is done by the... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.4.2.3 Abnormal conditions | If a RESET message is received after sending of a RESET CIRCUIT message and before receipt of the corresponding response the respective reset circuit procedure is stopped, i.e. reception of the corresponding RESET CIRCUIT ACKNOWLEDGE message is not required and no repetition is necessary. If a RESET CIRCUIT message is ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5 External Handover | The details of the radio information as far as handover is concerned are given in GSM 04.08. The relevant network information is given in GSM 03.09. Using this protocol the BSS should support handover transitions to and from any combinations of the following: Channel SDCCH Full Rate TCH Half Rate TCH Multiple Full Rate... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.1 Handover Required Indication | The handover required indication procedure allows a BSS to request that a handover is to be carried out for a particular MS, currently allocated one or more dedicated resources. This is done by generating a HANDOVER REQUIRED message and sending it from the BSS to the MSC. If so required by the BSS the MSC informs the B... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.1.1 Generation of the HANDOVER REQUIRED message | Generation of the HANDOVER REQUIRED message can be for the following reasons: - The BSS has detected that a radio reason exists for a handover to occur. - The MSC has initiated a handover candidate enquiry procedure, and this MS is currently a candidate. - A cell change is required at call setup due to congestion, e.g.... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.2 Handover Resource allocation | This procedure has been defined to allow the MSC to request resources from a BSS in a manner similar to that used for the assignment case. However it does not result in the transmission of any messages over the radio interface, only in the reservation of the resource(s) identified at the BSS, which awaits access of a M... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.2.1 Operation of the procedure | The correct operation of the handover resource allocation procedure is as follows: The MSC sends a HANDOVER REQUEST message to the new BSS (note) from which it requires radio resources. This message contains details of the resource(s) required. If the MSC allocates the A interface circuits, and if the requested resourc... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.2.2 Handover Resource Allocation Failure | The following failure conditions of this procedure may occur: The BSS may not be able to use the terrestrial resource that the MSC has indicated in which case a HANDOVER FAILURE message will be returned with the Cause value set to: "requested terrestrial resource unavailable". The BSS may not be able to support the req... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.2.3 Abnormal conditions | If after receipt of a HANDOVER REQUEST message, the new BSS receives another HANDOVER REQUEST message on the same SCCP connection, then the later message will be discarded. If the BSS receives a HANDOVER REQUEST allocating a terrestrial circuit which the BSS has marked as blocked by a previous blocking procedure, then ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.3 Handover execution | Handover execution in the context of the BSS/MSC interface is the process whereby an MSC instructs an MS to tune to a new dedicated radio resource or to a group of radio resources, which may be on a different cell. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.3.1 Operation of the procedure | The correct operation of the procedure is as follows: The BSSMAP HANDOVER COMMAND message is generated by the MSC and transmitted over the BSSAP connection to the old BSS which is currently supporting the concerned MS. At the old BSS timer T8 is started on the receipt of the BSSMAP HANDOVER COMMAND message. A radio int... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.3.2 Handover Failure | If a HANDOVER FAILURE radio interface message is received from the MS on the old (main) channel by the old BSS, the old BSS shall then send to the MSC the BSSMAP message HANDOVER FAILURE. If the radio interface HANDOVER FAILURE message is the result of the MS returning to the old BSS after failing to establish on the n... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.5.3.3 Abnormal Conditions | Whilst the handover execution procedure is in operation, any other messages received at the old BSS relating to this connection and concerning assignment, handover, or cipher mode control should be discarded. Whilst the handover execution procedure is in operation the old BSS should not attempt to invoke any other proc... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.6 Internal Intra-Cell Handover Procedure | The definition of internal intra cell handover is given in clause 5. It is optional that a BSS support internal intra-cell handover. However if it is supported, it should be as follows: It should be possible to inhibit internal intra-cell handover at an BSS that supports it by operation and maintenance command. Interna... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.7 Internal Inter-Cell Handover Procedure | The definition of internal inter-cell handover is given in clause 5. It should be possible to inhibit internal inter-cell handover at a BSS that supports it by operation and maintenance command. Multi cell BSSs would normally be expected to support internal inter-cell handover, however it is optional that they do so. H... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.8 Handover Candidate Enquiry | The purpose of this procedure is to allow the MSC to ascertain if it is possible to handover any MSs that are currently being served by a particular cell to another nominated cell. The procedure uses both global and dedicated resource messages, and is relevant to an individual cell. The algorithm in which a MSC decides... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.8.1 Successful Operation | The procedure operates as follows: The MSC sends a HANDOVER CANDIDATE ENQUIRE message to a BSS. The message indicates that the MSC wishes the BSS to identify handover candidates in a particular cell, that can be handed over to other nominated cells. The maximum number of candidates is also indicated to the BSS. For eac... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.8.2 Abnormal conditions | If at the BSS a HANDOVER CANDIDATE ENQUIRE message is received when a handover enquiry procedure has already been invoked then the new HANDOVER CANDIDATE ENQUIRE message shall be discarded. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.9 Release of Radio Resource And Terrestrial Resource | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.9.1 Release Due To Transaction Completion | The release of assigned radio resources at the end of a transaction will take place as follows: Release negotiation will take place directly between the MS and MSC using transparent messages via the DTAP in the BSS (see GSM 04.08). The MSC will then send a BSSMAP CLEAR COMMAND, indicating that the radio resource(s) sho... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.9.2 Release due to BSS generated reason | If a radio channel release is required because of a BSS generated reason (e.g. "O and M intervention", "equipment failure") then, the BSS shall generate a CLEAR REQUEST message towards the MSC. This message shall include a Cause Information Element, indicating the reason for the failure. If transmission from the MS is ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.9.3 Release due to successful handover | If a radio channel release is required because of a handover being successfully completed on another BSS, then the resources at the old BSS are released by the MSC using the clearing sequence with a Cause value; "handover successful". In the case of handover of a group call talker from a group call channel the MSC shal... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.10 Paging | PAGING messages for all MSs shall be sent via the BSSMAP as a connectionless message. These will include the IMSI of the MS to allow derivation of the paging population number; they may also include an indication of which combination of channels will be needed for the subsequent transaction related to the paging. This ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.11 Trace Invocation | The purpose of the trace invocation procedure is to inform the receiving entity that it should begin producing a trace record on this particular transaction. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 32 (GSM 08.08 version 6.5.0 Release 1997) The trace is invoked either by the MSC sending a MSC INVOKE TRACE message to the B... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.12 Flow Control | These procedures are defined to give some degree of flow control. At the BSS processor overload and CCCH scheduler overload are catered for, and at the MSC processor overload is catered for. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.12.1 Philosophy | The philosophy used is to stem the traffic at source with known effect on the service. The algorithm used is: - On receipt of the first OVERLOAD message or signalling point congested information, the traffic is reduced by one step. At the same time, timers T5(T17) and T6(T18) are started. During T5(T17) all received ov... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.12.2 Processor Overload at the MSC | The MSC can indicate to the BSS that it is in a congested state by sending an OVERLOAD message. This is sent as a connectionless global message. At the BSS receipt of this message causes the reduction of random access traffic using the method described in subclause 3.1.12.1. For example, the amount of random access tra... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.12.3 Processor/CCCH overload at the BSS | If the CCCH scheduler at the BSS is overloaded (queue passed a predefined threshold) then the BSS sends an OVERLOAD message to the MSC with the appropriate cause (Cause value: "CCCH overload") and indicating the cell in question. If the BSS processing is overloaded then the BSS sends an OVERLOAD message with the Cause ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.12.4 Message throughput congestion | If the lower layers of the protocol become congested then it is assumed that the MTP congestion indication will take place (see GSM 08.06) and the source of the traffic will receive primitives from the transport protocols resulting in it reducing the generated load. A suitable method to achieve this reduction could be ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.13 Classmark Handling Procedures | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.13.1 Classmark request procedure | The purpose of this procedure is to allow the MSC to trigger a classmark updating procedure. This is done by sending a CLASSMARK REQUEST message to the BSS on the appropriate SCCP connection. When receiving this message the BSS shall initiate the appropriate actions on the radio path. |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.13.2 Classmark updating procedure | The purpose of the classmark updating procedure is to inform the receiving entity about classmark information received from the MS. At any point when an SCCP connection has been established for BSSAP messages, the BSS must be able to send to the MSC a CLASSMARK UPDATE message if a classmark update is received from the ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.14 Cipher Mode Control | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.14.1 Successful Operation | The cipher mode control procedure allows the MSC to pass cipher mode information to the BSS to select and load the user data and signalling encryption device with the appropriate key. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 34 (GSM 08.08 version 6.5.0 Release 1997) This is achieved by sending the BSS a CIPHER MODE COMMAN... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.1.14.2 Abnormal Conditions | If the BSS is unable to support the ciphering algorithm specified in the CIPHER MODE COMMAND message then it shall return a CIPHER MODE REJECT message with Cause value "Ciphering algorithm not supported". A CIPHER MODE REJECT message shall also be returned if the MSC requests a change of ciphering algorithm when cipher... |
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. W... |
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 specifi... |
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... |
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 opera... |
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 ... |
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 mes... |
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 cod... |
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 Informa... |
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 connectio... |
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 informa... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.