hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.9 REJECT Response/Confirm | PARAMETER REFERENCE PRESENCE Cause 9.2.16 M Diagnostic 9.2.17 O Message-Identifier 9.2.1 O Serial Number 9.2.2 O This primitive is sent by the BSC to the CBC in response to any primitive which is not understood (e.g. invalid parameter or parameter value). |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.10 RESTART-INDICATION Request/Indication | PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 M Recovery Indication 9.2.20 O The RESTART-INDICATION Request is used by the BSC to indicate to the CBC a CB related restart situation in one or more of its cells (e.g. when an existing or a new cell becomes operational during normal BSC operation or when the BSC initialis... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.11 RESET Request/Indication | PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M The RESET Request is used by the CBC to force one or more cells (BTSs) of one BSC into CB-idle state. The RESET Request may also be used by the CBC to ask for the CB operational state of cells earlier indicated to have failed (polling CB operational state). If a base sta... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.12 FAILURE-INDICATION Request/Indication | PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 M The FAILURE-INDICATION Request is used by the BSC to indicate to the CBC a CB related problem situation in one or more of its cells. Any referenced cell enters CB-not-operational state. The status of the CB messages is undefined until the Restart- Indication is sent. It ... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.13 SET-DRX Request/Indication | PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M Schedule-Period 9.2.12 O Reserved-Slots 9.2.13 O Channel Indicator 9.2.6 O The SET-DRX Request is used by the CBC to set DRX specific parameters i.e. the schedule period and the number of slots reserved for high priority messages, see GSM 04.12. At least one of the Sched... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.1.14 SET-DRX- REPORT Response/Confirm | PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 O Failure-List 9.2.14 O Channel Indicator 9.2.6 O This primitive will be sent by the BSC to the CBC in response to a SET-DRX Request/Indication primitive. The Failure-List will contain those cells which were present in the Request message and which failed the requested ope... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.1 Message-Identifier | identifies source/type of message. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.2 Old-Serial-Number | This enables a particular existing message, from the source/type indicated by the message identifier, to be identified. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.3 New-Serial-Number | This enables message change to be indicated since it is altered every time the message is changed. The serial number identifies a particular message, which may be several pages in length, from the source indicated by the message identifier. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.4 Number-of-Pages | enables the number of pages in the message to be indicated. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.5 Cell-List | The cell-list identifies a sequence of one or more cells to which the primitives apply. 3The cells in the list are described as per section 3.2.2.17 of GSM 08.08 and can be identified by the CBC or BSC in LAC and CI format or CI format only. In addition (as described in GSM 08.08) it is possible for the CBC to refer to... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.5.1 Cell-List sent from CBC to BSC | The CBC to BSC Cell-List contains a length parameter identifying the number of cell-identifications present in the list, a Cell-Id-Discriminator, which is common for all cell-identifications in the list, and a sequence of cell-identifications. Description of list elements: PARAMETER PRESENCE Length M Cell-Id-Discrimina... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.5.2 Cell-List sent from BSC to CBC | The BSC to CBC Cell-List contains a sequence of cell-identifiers as defined in 9.2.11. The Cell-List must contain at least one cell-identifier as defined in 9.2.11. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.6 Channel Indicator | This parameter indicates the CB channel, which shall be used for broadcasting the data. basic channel; extended channel (supporting such a channel by the network or MSs is optional); If no channel indicator is present, it shall be interpreted as an indication to the basic channel. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.7 Category | This indicates the category of the message: High Priority:to be broadcast at the earliest opportunity in the reserved slots of the current schedule period (i.e. until the emission of the next schedule message), then according to the associated repetition period in the next schedule periods, in non reserved slots. Backg... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.8 Repetition-Period | This indicates the period of time after which broadcast of the message should be repeated. The minimum period with which a message may be broadcast over the air interface is one 8 x 51 multiframe sequence which corresponds to a period of approximately 1.883 seconds. ETSI TS 100 902 V6.1.0 (1998-07) 20 GSM 03.41 version... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.9 No-of-Broadcasts-Requested | This specifies the number of times the message is to be broadcast. The parameter may take any value up to 65535 (this maximum allows the message to be broadcast approximately every 1.883 seconds for more than 24 hours). If the parameter is set to 0 then the message will be broadcast indefinitely (i.e. until the BSC rec... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.10 No-of-Broadcasts-Completed-List | This parameter is a list indicating the number of times that the message (i.e. all pages of the message) has been sent to each Cell in the Cell-List for broadcast over the air interface. The cells in the list are described as per section 3.2.2.17 of GSM 08.08 and can be identified by LAC and CI or CI only. Description ... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.11 Cell-Identifier | The cell-identifier consists of a cell-id-discriminator and cell-identification pair. Description of list elements: PARAMETER PRESENCE Cell-Id-Discriminator M Cell-Identification M The Cell-Id-Discriminator is described as per section 3.2.2.17 of GSM 08.08 and has one of the following formats: ETSI TS 100 902 V6.1.0 (1... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.12 Schedule-Period | Indicates the DRX schedule period length, see GSM 04.12. The following values should be coded: - no DRX; - length of the schedule period. If a schedule period length greater than 40 is used, the schedule message cannot be built entirely if more than 40 messages have to be described in the period. Therefore, schedule pe... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.13 Reserved-Slots | Indicates the number of slots marked as “free slots reading advised“ in the schedule message and considered as reserved in a DRX schedule period for incoming high priority messages, not scheduled in the current schedule period, see GSM 04.12. The spacing of the reserved slots is implementation dependent. Reserved slots... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.14 Failure-List | This identifies the list of cells for which the BSC could not complete the request. The failure cause for each cell is indicated. The cells in the list are described as per section 3.2.2.17 of GSM 08.08 and can be identified by LAC and CI or CI only. Description of list elements: PARAMETER PRESENCE Cell Identifier M Ca... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.15 CBCH-Loading-List | A list of the predicted short term load of each cell in the list expressed as a percentage. The calculation of this percentage is an implementation matter. The load should reflect the number of used slots, and schedule messages and reserved slots must be taken into account. The cells in the list are described as per se... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.16 Cause | Indicates reason why the BSC was not able to interpret or execute the received primitive. The causes are given in table 1. Table 1 Cause Reason Parameter-not-recognized Sent when the recipient (CBC or BSC) was unable to act upon the primitive received due to an unrecognized parameter. A primitive should not be rejected... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.17 Diagnostic | Provides additional information associated with Cause parameter and may contain parameter which could not be interpreted/executed. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.18 Data Coding Scheme | Identifies alphabet or coding employed for the message characters. This field is defined in GSM 03.38 [3]. ETSI TS 100 902 V6.1.0 (1998-07) 23 GSM 03.41 version 6.1.0 Release 1997 |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.19 CBS-Message-Information-Page n | This carries 82 octets of CBS information. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.20 CBS-Message-Information-Length n | Gives the number of octets of the CBS-Message-Information-Page n containing cell broadcast information. The remaining octets of the CBS-Message-Information-Page n only contain padding information. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.2.21 Recovery-Indication | Indicates whether the CBS related data was lost or is still available. The following values should be coded: - Data-available; - Data-lost. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.3 Message Format on BTS-MS Interface | The messages which are transmitted by the BTS for the MS include the SMSCB message (information for the user) and Schedule Message (schedule of SMSCB messages). The Schedule Message is broadcast to support SMSCB DRX mode for Mobile Stations. The Schedule Message is helpful in minimizing battery usage for Cell Broadcast... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.3.1 General Description | Each CBS page sent to the MS by the BTS is a fixed block of 88 octets as coded in GSM 04.12. This is sent on the channel allocated as CBCH by GSM 05.02. The 88 octets of CBS information consist of a 6 octet header and 82 user octets. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.3.2 Message Content | Octet No 1-2 Serial Number 3-4 Message Identifier 5 Data Coding Scheme 6 Page Parameter 7-88 Content of Message These octets are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. The fields are used as follows: (i) Serial ... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 9.4 CBS Compression | Not yet specified |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 10 SMSCB Index | An index structure is defined in this section. Index can be used by the operator to inform the end user about the type of SMSCB services available. Index has the structure of a tree. It can thus have sub parts which are called subindexes. A subindex can be embedded in the same index message as its parent ("embedded sub... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 1 Scope | The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in GSM 08.06 and GSM 08.08, which is used on the E-interface. A general description can be found in GSM 03.02 and GSM 03.09. For the initiation and execution of handover between MSCs a subset of BS... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 2 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... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BSS Base Station System BSSAP Base Station System Application Part BSSMAP Base Station System Management Application Part CCCH Common Control CHannel DLCI Data Link Connection Identifier DTAP Direct Transfer Application Part MSC Mobile-service... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 4 Principles for the use of BSSAP on the E-interface | |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 4.1 General | The mechanisms for the transfer of the BSSAP messages on the E-interface is defined in GSM 09.02. The operation of the handover procedures between MSCs and the use of the BSSMAP messages for those procedures is described in GSM 03.09 and GSM 09.10. In the same way as a SCCP signalling connection is used for the message... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 4.3 Roles of MSC-A, MSC-I and MSC-T | For the description in this ETS, the MSC's functionality related to the handover between MSCs has been split into three logical parts, MSC-A, MSC-T and MSC-I. The different roles need not necessarily be performed by different MSCs. MSC-A is the call/connection controlling part of the MSC where the call/connection was o... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5 Use of the BSSAP on the E-interface | DTAP is used on the E-interface for the transfer of messages between the MSC-A and the MS. The dedicated BSSMAP procedures (GSM 08.08 subclause 3.1) used on the E-interface to some extent are: - assignment; - handover resource allocation; - handover execution; - internal handover indication; - release due to BSS genera... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.1 DTAP | For the exchange of the DTAP messages (GSM 08.08 subclause 2.2), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.2 Assignment | The Assignment procedure (GSM 08.08 subclause 3.1.1) is applied on the E-interface with following conditions: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. The handling of terrestrial resources is not applicable. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.3 Handover resource allocation | At Basic Inter-MSC Handover (GSM 03.09) the Handover resource allocation procedure (GSM 08.08 subclause 3.1.5.2) is applied on the E-interface with the following conditions: - the MSC-A acts as the MSC; - the MSC-T acts as the target BSS. At Subsequent Inter-MSC Handover (GSM 03.09) the Handover resource allocation pro... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.4 Handover execution | For the Handover execution procedure (GSM 08.08 subclause 3.1.5.3) the applicable parts on the E-interface are the transfer of HANDOVER DETECT, HANDOVER COMPLETE and HANDOVER FAILURE messages at inter MSC handover. For those parts, the involved MSCs shall act according to the following: - the MSC that is the MSC-A, act... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.5 Internal handover indication | For the Internal handover indication (GSM 08.08 subclause 3.1.6 and 3.1.7), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. MSC internal handovers (inter-BSS and intra-BSS handover) at the MSC-I are decided and executed autonomously by that MSC together ... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.6 Release due to BSS generated reasons | For the Release due to BSS generated reasons procedure (GSM 08.08 subclause 3.1.9.2) the involved MSCs shall act according to the following: - the MSC-I acts as the BSS; - no further action is taken by the MSC-A. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.7 Classmark handling | For the Classmark handling (GSM 08.08 subclause 3.1.13), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.8 Cipher mode control | For the Cipher mode control (GSM 08.08 subclause 3.1.14), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.9 Trace invocation | For the Trace invocation (GSM 08.08 subclause 3.1.11), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 10 (GSM 09.08 version 7.2.0 Release 1998) |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.10 Queuing indication | For the Queuing Indication (GSM 08.08 subclause 3.1.17), the involved MSCs shall act according to the following: - at Assignment and at Basic Inter-MSC handover: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. - at Subsequent Inter-MSC handover: - the MSC-I acts as the MSC; - the MSC-T acts as the BSS; - if t... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.11 Data link control SAPI not equal to "0" | For the Data Link Control SAPI not Equal to "0" (GSM 08.08 subclause 3.1.18), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.12 Location Acquisition | For the Location Acquisition procedure (GSM 08.08 subclause 3.1.28), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 5.13 LSA handling | For the LSA handling (GSM 08.08 subclause 3.1.27), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 6 BSSMAP messages transferred on the E-interface | The following BSSMAP messages, defined in GSM 08.08 subclause 3.2.1, are transferred on the E-interface: ASSIGNMENT REQUEST (MSC-A -> MSC-I) Excluded information element: CIRCUIT IDENTITY CODE ASSIGNMENT COMPLETE (MSC-I -> MSC-A) Excluded information element: CIRCUIT POOL, CIRCUIT IDENTITY CODE ASSIGNMENT FAILURE (MSC-... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 7.1 Message contents | For the applicable BSSMAP messages transferred on the E-interface the following exceptions to the descriptions in GSM 08.08 subclause 3.2.1 are valid: Assignment request message: - excluded information element: - circuit identity code. - if received, the information element shall be treated as an information element wi... |
8820490dbdf1bb2664b2e80b8ba4c7ac | 100 626 | 7.2 Information element coding | For the applicable BSSMAP information elements transferred on the E-interface the following exceptions to the description in GSM 08.08 subclause 3.2.2 are valid: Cause information element: - excluded causes: - call control; - CCCH overload; - handover successful; - requested terrestrial resource unavailable; - terrestr... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 1 Scope | The present document addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities. There is a requirement for the A-bis interfac... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 2 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... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 3 Definitions and abbreviations | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 3.1 Definitions | Definitions of terms used within the present document may be found mostly in clause5 in text context. |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 3.2 Abbreviations | For the purpose of the present document, the following abbreviations apply: ASN.1 (CCITT) Abstract Syntax Notation One BSC Base Station Controller BSS Base Station System BTS Base Transceiver Station cont. continued HW Hardware LSB Least Significant Byte man. dep. manufacturer dependent (with upper and lower case adjus... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 4 Functional Split between BSC and BTS | Functional split of management functions between BSC and BTS is shown in table 1. Table 1/GSM 12.2:. Split of management functions between BSC and BTS BSC BTS Fault Management BTS test request X - test execution - X test analysis NS - fault detection - X fault localization X (note) X fault reporting X X Link testing (r... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5 Information Model | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5.1 Managed Objects | The BCF mentioned in GSM 08.52 and GSM 08.56 is the agent at the BTS end of the A-bis O&M interface. It has four different descriptions depending on the object that is managed: Site Manager, BTS, Radio Carrier and Baseband Transceiver. This model describes how objects are managed across A-bis interface, but it doesn't ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5.2 Addressing of Objects | It is a GSM requirement that the BSC is capable of operating with BTSs from different manufacturers. So, it is necessary that the differences between BTSs, as seen by the BSC, are minimised as much as possible. This is achieved by addressing NM messages by the Managed Object Class and Managed Object Instance. There mus... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5.3 State Management of Objects | State management in this GTS is generally in line with CCITT Recommendation X.731. How state values are applied is explained below. CCITT Recommendation X.731 states that "the management state of a managed object represents the instantaneous condition of availability and operability of the associated resources from the... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5.3.1 Administrative State | Administrative states of the managed objects can be controlled only by the BSC. In fact, the control of resource usage comes from the MSC). Setting the administrative state of a Channel to locked means that it has to discontinue all transmission and reception of information on Air interface and all telecommunication (t... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 5.3.2 Operational State and Availability Status | CCITT Recommendation X.731 gives the following definitions for the values of the operational state attribute: - disabled: the resource is totally inoperable and unable to provide service to the user(s); - enabled: the resource is partially or fully operable and available for use. In the present document the value Disab... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6 Elementary Procedures | The operational procedures applicable to the BTS consist of bringing BTS equipment and software into (or taking them out of) service, initiation of tests at the BTS, collection of test results made at the BTS, reporting and clearing of any BTS faults, and reporting of any BTS external alarms. Bringing into service of e... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.1 Definition of the Procedures | All the procedures covered in this GTS are based on formatted O&M messages. Most formatted O&M messages initiated by the BSC (or by a BTS) will receive a response or acknowledgement at Layer 3. A pair of such messages, or single message if a response is not required, is referred to as an elementary procedure. All messa... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2 SW Download Management Procedures | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.1 Load Data Initiate | This message shall be sent from the BSC to the BTS to initiate the loading of a file. It indicates the number of segments for which a Layer 3 acknowledgement is required (window size). When receiving data the BTS shall send an ACK after this number of segments, except for the last batch. BSC BTS Load Data Initiate ----... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.2 Load Data Segment | These multi-segment messages shall be used to carry the files for the transfer initiated by the Load Data Initiate message. No other file transfer shall be allowed until the current transfer is finished. BSC BTS Load Data Segment -+ --------------------------------------------> ¦ Load Data Segment ¦- Window Size ------... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.3 Load Data Abort | This message shall be used by either end if the file transfer can no longer be supported. This message shall also be used by the BTS if the received amount of data exceeds the expected amount. BSC BTS Load Data Abort <-------------------------------------------> ETSI 18 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 versi... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.4 Load Data End | This message shall be sent by the BSC to the BTS. The BTS sends an ACK when the file has been received in the BTS. BSC BTS Load Data End --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message : File download is successfully terminated. Message specifi... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.5 SW Activate Request | This message shall be sent by the BTS when the resource represented by the object instance (Site Manager, BTS, Radio Carrier, or Baseband Transceiver) has started up. The initialization of mentioned object instance shall be started with software activation, which may include software download continuing with attribute ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.6 Activate SW | This message from the BSC to the BTS shall be used to activate the loaded software, indicating which file (or files) is to be activated. The acknowledgement of the Activate SW indicates that the software can be activated. If the software cannot be activated, a NACK must be sent. The activation may include BTS internal ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.2.7 SW Activated Report | This message from the BTS to the BSC shall be sent from the addressed object on the BTS at a successful completion of the software distribution to and activation on all indicated destinations in the BTS. BSC BTS SW Activated Report <-------------------------------------------- |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3 A-bis Interface Management Procedures | These procedures (excluding 'Establish TEI') are only relevant with BTSs having flexibility to configure A-bis channels to different Baseband Transceivers. This configuration flexibility is realized with equipment that can be called BTS front-end switch. In other words this switch allows an A-bis channel to be able to ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3.1 Establish TEI | When an initial/additional TEI is to be established (see GSM 08.56), this message shall be sent from the BSC on a previously established link giving initial/additional TEI number and the corresponding physical connection. For establishment of additional TEI the procedure specified in specification GSM 08.56 must be per... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3.2 Connect Terrestrial Signalling | This message shall be used to connect a particular terrestrial transmission circuit to a Baseband Transceiver. The procedure can be used only for a BTS that has the relevant flexibility. BSC BTS Connect Terrestrial Signalling --------------------------------------------> ACK/NACK <--------------------------------------... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3.3 Disconnect Terrestrial Signalling | This message shall be used to disconnect a Baseband Transceiver from a terrestrial circuit. BSC BTS Disconnect Terrestrial Signalling --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified signalling link has been disconnected. Message ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3.4 Connect Terrestrial Traffic | This message shall be used to relate a terrestrial circuit to a radio time slot, if the BTS has the flexibility. If half rate coding is implemented, two Connect Terrestrial Traffic messages shall be sent for each radio timeslot. BSC BTS Connect Terrestrial Traffic --------------------------------------------> ACK/NACK ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.3.5 Disconnect Terrestrial Traffic | This message shall be used to disconnect a terrestrial circuit from a radio timeslot. BSC BTS Disconnect Terrestrial Traffic --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified traffic link has been disconnected. Message specific Nac... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.4 Transmission Management Procedures | These prodecures are used to configure on-site transmission equipment. They may not be sufficient and are subject to further standardization. |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.4.1 Connect Multi-drop Link | This message shall be used to relate two terrestrial circuits (64 kbps timeslot in a 2 Mbps system to a radio time slot), if the BTS has the flexibility of setting up multi-drop configuration. BSC BTS Connect Multi-drop Link --------------------------------------------> ACK/NACK <---------------------------------------... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.4.2 Disconnect Multi-drop Link | This message shall be used to disconnect a multi-drop configuration in the BTS. BSC BTS Disconnect Multi-drop Link --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified multi-drop link connection has been disconnected. Message specific... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.5 Air Interface Management Procedures | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.5.1 Set BTS Attributes | This message shall be sent to provide an object instance on BTS with all the necessary attributes relating to that BTS object. This message does also include common information for all logical channels of one type, e.g., CCCH parameters. BSC BTS Set BTS Attributes --------------------------------------------> ACK/NACK ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.5.2 Set Radio Carrier Attributes | This message shall be used to set a Radio Carrier's RF-related attributes such as the frequencies and the power. BSC BTS Set Radio Carrier Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified Radio Carrier attributes have b... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.5.3 Set Channel Attributes | This message shall be sent for each Channel instance to give the channel combination as defined in GSM 05.02 for that time slot. It shall be possible to send one message, if all 8 radio time slots need the same attribute value. This shall be done by not addressing one specific Channel instance in the Instance field in ... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.6 Test Management Procedures | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.6.1 Perform Test | This message shall be used to tell the BTS to perform a test, if necessary to set a physical configuration for the BSC to carry out a test on the BTS, or to perform a test using a particular configuration. Any measurements may be performed as specific tests. Duration for the test can be given, after which the test repo... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.6.2 Test Report | This message shall be sent by the BTS giving the result of a test ordered by the BSC and is sent autonomously as soon as the result is available. A Test Report shall also be sent after a specific request from the BSC by a Send Test Report message. The Test Report indicates what was tested, the test type, and the result... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.6.3 Send Test Report | This message shall be sent from the BSC to ask for the result/report of a test which was not to be sent autonomously now to be started being reported. If the test result was already made to be autonomously reported, this message can also be used to have the present result of the test be reported immediately. The messag... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.6.4 Stop Test | This message shall be used by the BSC to stop a continuously recurring test at the BTS, to reset a physical test configuration to the normal configuration, or to stop the test and to restore to the normal physical configuration. The message must include identification of the test being performed. BSC BTS Stop Test ----... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.7 State Management and Event Report Procedures | |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.7.1 State Changed Event Report | An unsolicited report shall be sent from the BTS to the BSC whenever a change of the operational state or of the optional manufacturer dependent state of a managed object defined in this GTS occurs. The message shall be also sent when any site input changes its state. A failure, causing change of operational state, sha... |
e59ea8dcad939b2b08179091ad5f515d | 100 623 | 6.7.2 Failure Event Report | An unsolicited report shall be sent from the BTS to the BSC whenever failure events occur in the BTS. Such failure events are: - fault in a resource resulting from passing a threshold but not constituting a failure; - failure of a resource. Pertaining to a failure, there shall be a report for its start and another for ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.