hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
6 BSC Functionality
|
The BSC shall interface to only one CBC. A BSC may interface to several BTSs as indicated by GSM 08.52. The BSC shall be responsible for: - interpretation of commands from the CBC; - storage of cell broadcast messages; - scheduling of cell broadcast messages on the CBCH; - providing an indication to the CBC when the desired repetition period cannot be achieved; - providing to the CBC acknowledgement of successful execution of commands received from the CBC; - reporting to the CBC failure when a command received from the CBC is not understood or cannot be executed; - routing cell broadcast messages to the appropriate BTSs; - transferring CBS information to each appropriate BTS via a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message (see GSM 08.58), indicating the channel which shall be used. - optionally generating Schedule Messages, indicating the intended schedule of transmissions (see GSM 04.12); - optionally receiving CBCH Load Indication messages and reacting by broadcasting a burst of scheduled SMSCB messages or by suspending the broadcast for a period indicated by BTS (see GSM 08.58); To work efficiently on the interfaces, the BSC should forward CB related messages to the CBC using cell lists as far as applicable.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
7 BTS Functionality
|
The BTS is responsible for conveying CBS information received via SMS BROADCAST REQUEST or SMS BROADCAST COMMAND messages over the radio path to the MS. - optionally generating CBCH Load Indication messages, indicating an underflow or overflow situation on the CBCH (see GSM 08.58).
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
8 MS Functionality
|
The MS is responsible for recombination of the blocks received via the radio path to reconstitute the cell broadcast short message. The precise method of display of cell broadcast short messages is outside the scope of GSM Specifications, however it is assumed that an MS will: - discard sequences transferred via the radio path (see GSM 04.12) which do not consist of consecutive blocks; - have the ability to discard CBS information which is not in a suitable data coding scheme; - have the ability to discard a message which has a message identifier indicating that it is of subject matter which is not of interest to the MS; ETSI TS 100 902 V6.1.0 (1998-07) 10 GSM 03.41 version 6.1.0 Release 1997 - have the ability to ignore repeat broadcasts of messages already received (message has not changed since it was last broadcast i.e. sequence number has not changed within the message's indicated geographical area); - have the ability to transfer a message via the R interface when the R interface is supported; - optionally enter SMSCB DRX mode based upon received Schedule Messages (see GSM 04.12); - optionally skip reception of the remaining block(s) of a cell broadcast message which do(es) not contain cell broadcast information (see GSM 04.12); - optionally read the extended channel.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9 Protocols and Protocol Architecture
|
Commands interpreted by the BSC will result in a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message being sent to a BTS, which in turn result in a sequence of 4 messages being transferred via the BTS-MS interface (see GSM 04.12). With the SMS BROADCAST REQUEST mode of operation, the 88 octet fixed length CBS page which is specified in Section 9.3 is split into four 22 octet blocks which are carried in SMS BROADCAST REQUEST messages as follows: octets 1-22 are transferred in the 1st SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating first block octets 23-44 are transferred in the 2nd SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating second block octets 45-66 are transferred in the 3rd SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating third block octets 67-88 are transferred in the 4th SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating fourth block. Figure 2 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST REQUEST mode of operation. ETSI TS 100 902 V6.1.0 (1998-07) 11 GSM 03.41 version 6.1.0 Release 1997 GSM 08.58 GSM 04.12 GSM 03.41 Section 9.3 GSM 03.41 Section 9.1 CBC BSC BTS MSs Write-Replace Report-Success SMS BROADCAST REQUEST 1 SMS BROADCAST REQUEST 2 SMS BROADCAST REQUEST 3 SMS BROADCAST REQUEST 4 1 2 3 4 Figure 2 With the SMS BROADCAST COMMAND mode of operation, the BSC sends to the BTS in one single message the 88 octet fixed length CBS page. The BTS then splits the page into four 22 octet blocks, adds the sequence number (see GSM 04.12) and transmits the four resulting blocks on the air. Figure 3 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST COMMAND mode of operation. ETSI TS 100 902 V6.1.0 (1998-07) 12 GSM 03.41 version 6.1.0 Release 1997 GSM 08.58 GSM 04.12 GSM 03.41 Section 9.3 GSM 03.41 Section 9.1 CBC BSC BTS MSs Write-Replace Report-Success SMS BROADCAST COMMAND 1 2 3 4 Figure 3
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1 CBC-BSC Primitives
|
The term primitive is used to indicate "an abstract, implementation independent interaction between a service user and a service provider" (see CCITT X.210). For the CBC-BSC interface, the service provider would be the protocol interconnecting CBC and BSC. A Primitive may therefore be viewed as an abstract, implementation independent request/indication or response/confirm interaction between the service user (CBC or BSC) and the service provider (protocol). A set of primitives for use between the CBC and BSC is specified appropriate to the functionality assigned to the CBC and BSC in Sections 5 and 6. In order to allow future extensions to the primitives, where possible a primitive shall not be rejected because a parameter is not recognised; the recipient shall ignore the parameter in question and process the remainder of the primitive’s parameters as usual. No mandatory protocol between the CBC and the BSC is specified by GSM, this is a matter of agreement between CBC and PLMN operators. GSM 03.49 (see also annex A of this TS) provides example protocol stacks using the primitives defined as follows. NOTE: In the following definitions, M indicates "mandatory parameter" and O indicates "optional parameter".
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.1 Identification of a message
|
Within a CBC-BSC interface, a message is uniquely identified by the quartet (message_identifier, serial_number, Cell Identifier, Channel Indicator). This means that even when two messages have the same semantic containts (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet. The serial number is managed cyclically and therefore this does not prevent the re-use of the same quartet for a different message when the serial number have been incremented a sufficient number of times. How to manage the ambiguity is described subsequently. This unique identification of a message across the CBC-BSC interface is used in all the primitives defined hereafter. This means that the quartet will be implicitly or explicitly present in every interface primitive which applies to a given message. ETSI TS 100 902 V6.1.0 (1998-07) 13 GSM 03.41 version 6.1.0 Release 1997 This unique quartet will be referred in the rest of the document as the « message reference ».
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.2 WRITE-REPLACE Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 O New-Serial-Number 9.2.3 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O Category 9.2.7 O Repetition-Period 9.2.8 M No-of-Broadcasts-Requested 9.2.9 M Number-of-Pages 9.2.4 M Data Coding Scheme 9.2.18 M CBS-Message-Information-Page 1 9.2.19 M CBS-Message-Information-Length 1 9.2.20 M CBS-Message-Information-Page 2 9.2.19 O CBS-Message-Information-Length 2 9.2.20 O : : CBS-Message-Information-Page n 9.2.19 O CBS-Message-Information-Length n 9.2.20 O This primitive is sent by the CBC to the BSC. As this primitive can be used either to broadcast a new message or replace a message already broadcast, the CBC will use the presence and content of the Old-Serial-Number and New-Serial- Number fields in this primitive to instruct the BSC as follows:- - Old-Serial-Number not present/New-Serial-Number present This is a write request which will be interpreted by the BSC as an instruction to broadcast a new message in all the cells of the Cell list and on the channel derived by the Channel Indicator (see the section on parameters that describes the implicit value of the Channel Indicator when not present in the message). The following table identifies the BSC’s behaviour: Success/Failure of write request BSC behaviour Success The BSC completes the following parameters to be returned in the Report PDU: • a ‘0’ value is entered in the number of broadcasts completed list for the cell • no entry is made in the failure list for the cell Failure The BSC completes the following parameters to be returned in the Report PDU: • no entry is made in the number of broadcasts completed list for the cell • an entry is made in the failure list for the new message identifying the failure cause for the cell The BSC will build as many message references as the number of cells in the list. These message references will be used in particular in the subsequent primitives. When a message reference is already known by the BSC for certain cells in the list (even if the Update field of the Serial-Number is different), the primitive will be rejected with the cause « message reference already used ». The list of cells where the message reference is not valid will be provided in the REPORT message. No entry will be made in the number of broadcasts completed parameter. ETSI TS 100 902 V6.1.0 (1998-07) 14 GSM 03.41 version 6.1.0 Release 1997 - Old-Serial-Number present/New-Serial-Number present This is a replace request which will be interpreted by the BSC as a kill request for the message with the old serial number, followed by a write request for the message with the new serial number. The handling of the new serial number in the write part of this request, is as described above in the write request where no Old-Serial-Number is supplied. These two kill and write requests are executed sequentially. If the kill request is unsuccessful, the BSC does not proceed to execute the write request. The kill request will stop broadcast of, and cause all information currently associated with the combination of message identifier, old serial number, Channel Indicator and the list of cells in the Cell list to be deleted from the cells in the BSC (i.e. for all cells provided in the Cell- List parameter). If the kill request is successful, the subsequent write request information conveyed in the primitive replaces the killed message. The following table identifies the BSC’s behaviour: Success/Failure of kill request BSC behaviour Success The BSC proceeds to execute the write request: • Write successful: the BSC completes the following parameters to be returned in the Report PDU: • an entry is made in the number of broadcasts completed list for the cell • no entry is made in the failure list for the cell • Write unsuccessful: the BSC completes the following parameters to be returned in the Report PDU: • an entry is made in the number of broadcasts completed list for the cell • an entry is made in the failure list for the new message identifying the failure cause for the cell Failure The BSC does not proceed to execute the write request, and completes the following parameters to be returned in the Report PDU: • no entry is made in the number of completed broadcasts list • an entry is made for the old message in the failure list identifying the failure cause for the cell All cells which should perform the broadcasting are mentioned in the Cell-List parameter. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. If no category is present, the default category is interpreted by the BSC, see the parameter section. This primitive is responded by a REPORT or REJECT primitive. NOTE: in the case of multipage messages, the individual pages are considered as independent by the BSC scheduling algorithm.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.3 KILL Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O ETSI TS 100 902 V6.1.0 (1998-07) 15 GSM 03.41 version 6.1.0 Release 1997 This primitive is sent by the CBC to the BSC. The CBC will use this primitive to kill the message indicated by the combination of message identifier, serial number, Channel Indicator and the cells indicated in the Cell-List of this KILL request, i.e. the primitive will halt broadcast of the message in the indicated cells and remove any knowledge of the message from the BSC for these cells. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. This primitive is responded with a REPORT or REJECT primitive.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.4 REPORT Response/Confirm
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Serial-Number 9.2.2 M Channel Indicator 9.2.6 O No-of-Broadcasts-Completed-List 9.2.10 O Failure-List 9.2.14 O This primitive will be sent by the BSC to the CBC in response to WRITE-REPLACE and KILL primitives. The Serial- Number field will contain the old serial number if this primitive is sent in response to a KILL primitive, and the new serial number if the primitive is sent in response to a WRITE-REPLACE primitive. The No-of-Broadcasts-Completed-List if present, may contain for each cell the number of broadcasts of the (replaced or killed) CB message with the old message reference sent to this particular cell for broadcast. The serial number information element in the case of a WRITE-REPLACE does not refer to the message for which the number of broadcasts completed information is supplied. The Failure-List if present, may contain those cells which were present in the related WRITE-REPLACE or KILL primitive and failed the requested operation.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.5 STATUS-CBCH-QUERY Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O This primitive is sent by the CBC to the BSC in order to obtain the current loading of the CBCH of particular cells referenced in the Cell-List parameter. This primitive is responded by a STATUS-CBCH-QUERY Response/Confirm or a REJECT primitive.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.6 STATUS-CBCH-QUERY Response/Confirm
|
PARAMETER REFERENCE PRESENCE CBCH-Loading-List 9.2.15 O Failure-List 9.2.14 O Channel Indicator 9.2.6 O This primitive will be sent by the BSC in response to the STATUS-CBCH-QUERY Request/Indication primitive. The CBCH-Loading-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the CBCH loading of this particular cell. (Note that for cells with DRX the load caused by the schedule messages will be included in the CBCH load). The CBCH-Loading-List will not be present if all cells indicated in the related STATUS-CBCH-QUERY Request/Indication failed the requested operation. The Failure-List, if present, may contain all cells for which the requested operation failed (e.g. because the cells CBCH is not available). The STATUS-CBCH-QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-CBCH-QUERY Request failed the requested operation. ETSI TS 100 902 V6.1.0 (1998-07) 16 GSM 03.41 version 6.1.0 Release 1997
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.7 STATUS-MESSAGE-QUERY Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O This primitive is sent by the CBC to the BSC in order to obtain the current status of a CB-message for the cells referenced in the Cell-List parameter. This primitive is responded by the STATUS-MESSAGE-QUERY Response/Confirm or by a REJECT Response/Confirm.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.8 STATUS-MESSAGE-QUERY Response/Confirm
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M No-of-Broadcasts-Completed-List 9.2.10 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 STATUS-MESSAGE-QUERY Request/Indication primitive. The No-of-Broadcasts-Completed-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the number of times this CB message has been sent to this particular cell for broadcast (parameter Number-of-Broadcasts-Completed; this parameter is not included for the cell if the old message reference is not known to the BSC, and an entry is made in the failure list). The No-of-Broadcasts-Completed-List will not be present if all cells indicated in the related STATUS-MESSAGE-QUERY Request failed the requested operation. The Failure-List may contain all cells for which the requested operation failed (e.g. because the broadcast of the requested message was never requested before or because the cells CBCH is not available). The STATUS-MESSAGE- QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-MESSAGE-QUERY Request failed the requested operation.
|
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 initialises). Any referenced cell are again in CB-operational state (have resumed CB operation). The parameter Recovery Indication, if present, indicates whether CB related data are lost for the cells referenced in the Cell-List and have to be re-loaded. If ETSI TS 100 902 V6.1.0 (1998-07) 17 GSM 03.41 version 6.1.0 Release 1997 the Recovery Indication parameter is absent, the CBC shall interpret it as the Recovery Indication with the value data lost. The CBC upon receiving a RESTART INDICATION indication, marks the cell as operational again. It will usually generate WRITE-REPLACE requests for this cell, according to the actual CB message loading at the moment of the restart. Note that a RESTART INDICATION indication may be triggered from the CBC by a RESET Request. This allows to recover from situations, where a PDU occasionally may be lost.
|
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 station controller (BSC) receives a RESET Indication, the indicated cells enter idle state (same state as after "power on"). All CB related information concerning earlier CB messages in a referenced cell is lost. The BSC acknowledges the RESET Indication for each cell by an RESTART- or, if not adequate, by a FAILURE- INDICATION request. Of course, several responses may be combined using a cell list in the RESTART or FAILURE INDICATION.
|
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 remains in not-operational state until a RESTART-INDICATION request (see 9.1.10) indicates normal CB operation (again). The CBC upon receiving a FAILURE indication, marks this cell as failed. It will generally not generate further WRITE- REPLACE requests for this cell, up to the point, when the CBC is informed by a RESTART indication, that the cell has resumed CB operation. The BSC refuses further WRITE-REPLACE requests from the CBC with the cause “cell-broadcast-not-operational” when any referenced cell is in the CB-not-operational state. Note, that a Failure-Indication may be triggered by a RESET Request. This allows to recover from situations, where a PDU occasionally may be lost.
|
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 Schedule-Period or Reserved-Slots parameters must be present in the primitive. If this primitive is not supported, the BSC may use default values. ETSI TS 100 902 V6.1.0 (1998-07) 18 GSM 03.41 version 6.1.0 Release 1997 If a base station controller (BSC) receives a SET-DRX Indication, the new DRX parameters will be taken into account starting from the next schedule period in each cell, see GSM 04.12. If a BSC receives a SET-DRX Indication, the new DRX parameters will be applied for all cells that do not handle any broadcast message (null loading).
|
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 operation. If the new schedule period parameters are not acceptable on a cell due to the load of the cell, the cause “bss-capacity- exceeded” is used in the Failure-list. 9.2 Parameters
|
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 all cells in a LAC or in a complete BSC. If supplied, the Cell-List parameter must refer to at least one cell. Given the above differences between cell identification in the two directions, a cell list sent from the CBC to the BSC has a different structure compared to a cell list sent from the BSC to the CBC. The different cell lists are described in sections 9.2.5.1 and 9.2.5.2. ETSI TS 100 902 V6.1.0 (1998-07) 19 GSM 03.41 version 6.1.0 Release 1997
|
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-Discriminator M Cell-Identification M The Cell-Id-Discriminator is described as per section 3.2.2.27 of GSM 08.08 and has one of the following formats: - LAC and CI; - CI only; - all cells in the BSC belonging to a certain Location Area; - all cells in the BSC. The Cell-identification is repeated for each cell included in the list. The Cell-List must refer to at least one cell.
|
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. Background: to be broadcast in the slots left free by messages of category "High Priority" and "Normal", possibly shared with unscheduled schedule messages, see GSM 04.12. The repetition period defines the minimum broadcast requirement. Normal: to be broadcast according to the associated repetition period. If the category is omitted, the default category implied is "Normal" message.
|
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 6.1.0 Release 1997 The value of "Repetition-Period" shall be in the range 1 to 1024 where each unit will represent one 8 x 51 multiframe sequence. In the event of a conflict where the BSS has more than one message to send at the same time, the BSC shall decide the order of such messages as an implementation matter.
|
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 receives an appropriate Kill- Message Request/Indication primitive).
|
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 of list elements: PARAMETER PRESENCE Cell Identifier M No-of-Broadcasts-completed M No-of-Broadcasts-Compl-Info O The information above is repeated for the number of cells in the list. To each cell in the list the information element No-of-Broadcasts-completed is associated. This information element is related to the particular referenced cell in the list and contains the number of times a CB message (i.e. all pages of a CB message) has been sent to this cell for broadcast. The No-of-Broadcasts-completed information element represents the number of full broadcasts made of a message, and that the message is being (or had been) broadcast. The optional No-of-Broadcasts-Compl-Info information element may be supplied to indicate to the CBC one of the following cases: - overflow the count of the number of full broadcasts made of a message has overflowed, and that the message is being (or had been) broadcast. The actual number of broadcasts completed is greater than the value indicated in the No-of- Broadcasts-completed information element. - unknown indicates that there is no information regarding the number of broadcasts completed in the BSC for the message with the old serial number. The value indicated in the No-of-Broadcasts-completed information element is undefined in this case. The No-of-Broadcasts-Completed-List must contain at least one cell.
|
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 (1998-07) 21 GSM 03.41 version 6.1.0 Release 1997 - LAC and CI, - CI only. The BSC can use the 'LAC and CI' format for a cell identifier in any response to the CBC. The BSC may also use the 'CI only' format for a cell identifier when responding to a CBC primitive that had contained a cell with 'CI only' format for a cell identifier.
|
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 period length shall be reduced to 40.
|
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 shall receive a 40 value at maximum, taking into account the constraint for schedule period length.
|
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 Cause M Diagnostic O The information above is repeated for the number of cells that failed. To each cell in the list the information elements Cause and, as an implementation option, Diagnostic are associated. These are related to the particular referenced cell in the list. The Failure-List must contain at least one cell.
|
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 section 3.2.2.17 of GSM 08.08 and can be identified by LAC and CI or CI only. Description of list elements: ETSI TS 100 902 V6.1.0 (1998-07) 22 GSM 03.41 version 6.1.0 Release 1997 PARAMETER PRESENCE Cell Identifier M CBCH-Loading M The information above is repeated for the number of cells in the list. To each cell in the list the information element CBCH-Loading is associated. This information element is related to the particular referenced cell in the list and contains the cells load. Note that for cells with DRX the load caused by the schedule messages will be included in the CBCH load. The CBCH-Loading-List must contain at least one cell.
|
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 only because a parameter is not recognized as this would prevent extensions to the service parameter-value-invalid Sent when a failure occurred due to the value of a parameter being invalid, e.g. out of range, or in Write-Replace, the parameter "no of pages" does not equal the number of pages received valid-CBS-message-not- identified Sent when the BSC does not recognize the CBS message reference cell-identity-not-valid Sent when the BSC does not recognize a cell Identity unrecognized-primitive Sent when the BSC did not recognize the primitive at all missing-mandatory-element Sent when a mandatory element is missing from the primitive bss-capacity-exceeded Sent when a write-replace fails because the BSC cannot meet the requested repetition period or when the set-drx parameters cannot be applied because of the cell loading cell-memory-exceeded Sent when the local cell memory has been exceeded bss-memory-exceeded Sent when the BSS is unable to store a message as the BSS memory has been exceeded cell-broadcast-not-supported Sent when the CBCH is not configured for a cell cell-broadcast-not-operational Sent when the CBCH is not available because of error conditions or due to maintenance activities incompatible-DRX-parameter Sent when the DRX parameter(s) cannot be applied. Extended-channel-not-supported Sent when a write-replace fails because the extended channel is not configured for a cell message-reference already-used Sent when the recipient (BSC) was unable to act upon the write_replace received due to a previous write_replace received with the same message_reference. unspecified-error Sent when none of the above cause values apply
|
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 in the Mobile Station, because it allows the MS to ignore transmissions of messages the customer is not interested in. Use and formatting of the Schedule Message is described in GSM 04.12. The use and the formatting of the SMSCB messages, which contain information for the MS user, is described in this section.
|
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 Number is a 16 bit integer which identifies a particular message (which may be one to 15 pages in length) from the source and type indicated by the Message Identifier and is altered every time the message with a given Message Identifier is changed. The two octets of the serial number field are divided into a 2-bit Geographical Scope indicator, a 10-bit Message Code and a 4-bit Update Number in the following structure : ETSI TS 100 902 V6.1.0 (1998-07) 24 GSM 03.41 version 6.1.0 Release 1997 1 2 0 3 4 5 6 7 Octet 1 Octet 2 Message Code Update Num ber GS 1 2 0 3 4 5 6 7 The most significant bit of the Message Code is octet 1 bit 5 and the least significant bit of the Message Code is octet 2 bit 4. The most significant bit of the update number is octet 2 bit 3. The Message Code will differentiate between messages from the same source and type (with the same Message Identifier). Message Codes are for allocation by PLMN operators. The Message Code identifies different message themes. So, for example, let the value for the message identifier be "Automotive Association"= source), "Traffic Reports" = type). Then "Crash on A1 J5" could be one value for the message code "Cow on A32 J4" could be another "Slow vehicle on M3 J3" yet another. The Geographical Scope (GS) indicates the geographical area over which the Message Code is unique, and the display mode. The message is not necessarily broadcast by all cells within the geographical area. When two messages are received with identical Serial Numbers/Message Identifiers in two different cells, the Geographical Scope may be used to determine if the messages are indeed identical. In particular, the Geographical Scope tells the mobile if the message is only cell wide (which means that any message if received in the next cell is regarded as "new"), or PLMN wide (which means that the Message Code and/or Update Number must change in the next cell for the message to be "new"), or location area wide (which means that a message with the same Message Code and Update Number may or may not be "new" in the next cell according to whether the next cell is in the same location area as the current cell). The display mode indicates whether the message is supposed to be on the display all the time ("immediate") or only when the user wants to see it ("normal"). The coding of this field that indicates the scope of the message is: CODE DISPLAY MODE GEOGRAPHICAL SCOPE 00 Immediate Cell wide 01 Normal PLMN wide 10 Normal Location Area wide 11 Normal Cell wide Immediate = default direct display; Normal = default display under user interaction. NOTE 1: These display modes are indicative of intended use, without indicating a mandatory requirement or constraining the detailed implementation by mobile manufacturers. The user may be able to select activation of these different modes. NOTE 2: Code 00 is intended for use by the network operators for base station IDs. The Update Number indicates a change of the message content of the same message, i.e. the message with the same Message Identifier, Geographical Scope, and Message Code. In other words, the Update Number will differentiate between older and newer versions of the same message, within the indicated geographical area. A new message may have Update Number 0000; however this number will increment by 1 for each update. Any Update Number eight or less higher (modulo 16) than the last received Update Number will be considered more recent, and shall be treated as a new message, provided the mobile has not been switched off. (ii) Message Identifier identifies the source and type of message. For example "Automotive Association" (= source), " Traffic Reports" (= type) could be one value. A number of messages may originate from the same source and/or be of the same type. These will be distinguished by Serial Number. The Message Identifier is coded in binary. ETSI TS 100 902 V6.1.0 (1998-07) 25 GSM 03.41 version 6.1.0 Release 1997 The ME shall attempt to receive the CBS messages whose Message Identifiers are in the "search list". This "search list" shall contain the Message Identifiers stored in the EFCBMI, EFCBMID and EFCBMIR files on the SIM (see GSM 11.11) and any Message Identifiers stored in the ME in a "list of CBS messages to be received". If an ME has restricted capabilities with respect to the number of Message Identifiers it can search for, then the Message Identifiers stored in the SIM shall take priority over any stored in the ME. The use/application of the Message Identifiers is as follows: 0000 - 03E7 (hex) to be allocated by PLMN operator associations. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this message. 03E8 - 0FFF (hex) intended for standardization in future versions of GSM 03.41. These values shall not be transmitted by networks that are compliant to this version of GSM 03.41. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this message. 1000 - 10FF (hex) Networks shall only use Message Identifiers from this range for Cell Broadcast Data Download to the SIM (see GSM 11.14). If a message Identifier from this range is in the "search list", then the ME shall attempt to receive this message. NOTE: This version of GSM 03.41 does not prohibit networks from using Message identifiers in the range 0000 - 03E7 (hex) for Cell Broadcast Data Download to the SIM. 1100 - FFFE (hex) intended for standardization in future versions of GSM 03.41. These values shall not be transmitted by networks that are compliant to this version of GSM 03.41. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this message. FFFF (hex) Reserved, and should not be used for new services, as this value is used on the SIM to indicate that no Message Identifier is stored in those two octets of the SIM. If this Message Identifier is in the "search list", then the ME shall attempt to receive this message. In the above list, octet 3 of the Message Identifier is shown first, followed by octet 4. Thus "1234" (hex) represents octet 3 = 0001 0010 and octet 4 = 0011 0100. NOTE 3: Optionally, the user can select the language(s) required by using an MMI, to determine whether a particular message should be read and displayed. Generally, the MMI for entering these codes in the ME is left to the manufacturers' discretion, however the 1000 lowest codes shall be enterable by their decimal representation i.e: Octet 3 Octet 4 0000 0000 0000 0000 (decimal '000') 0000 0000 0000 0001 (decimal '001') 0000 0000 0000 0010 (decimal '002') 0000 0000 0000 0011 (decimal '003') : : : : : : 0000 0011 1110 0111 (decimal '999') (iii) Data Coding Scheme indicates the intended handling of the message at the MS, the alphabet/coding, and the language (when applicable). This is defined in GSM 03.38 [3]. When the SIM indicates one or more language preferences, the ME shall, by default, use the language(s) stored in the SIM (in the EFLP file) to set any language filter mechanisms provided by the ME. (iv) The page parameter is coded as two 4-bit fields. The first field (bits 0-3) indicates the binary value of the total number of pages in the message and the second field (bits 4-7) indicates binary the page number within that sequence. The coding starts at 0001, with 0000 reserved. If a mobile receives the code 0000 in either the first field or the second field then it shall treat the message exactly the same as a message with page parameter 0001 0001 (i.e. a single page message). ETSI TS 100 902 V6.1.0 (1998-07) 26 GSM 03.41 version 6.1.0 Release 1997
|
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 subindex") or it can physically be in a separate index message ("child subindex"). Every index message has a unique message identifier. They are always of the same type. Message Code 1010101010b shall be used to indicate this type. The root of the index structure shall be the index message with message identifier 0. Other index messages are linked to the root index with links. Definition of their message identifiers is left to the operator. A format ("enhanced format") for the index messages is described in this section. If this enhanced format is used in the index message the ms can present the index messages in its preferred format. Available SMSCB services are introduced in the index. This means that their message identifier and name are stated. Enhanced format includes a mechanism for separating a normal service introduction from embedded subindex introduction and child subindex introduction. The introduction of an embedded subindex specifies the "subindex-id" used for identifying services that belong to this subindex. Embedded subindexes can have subindexes embedded in them etc. If these "second level embedded subindexes" are introduced their subindex-id shall begin with the subindex-id of their parent. Same principle applies for subindexes in third, fourth etc. level. An example of an index structure is given in figure 4. Enhanced format includes a mechanism which allows the terminals to identify that the format of the index message is enhanced. The index-id -field and the above mentioned Message Code (1010101010b) constitute this mechanism: message-format = index-id index-element-intro+ index-id = "EI" version crlf version = number+ number = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" | "0" index-element-intro = subindex-intro | service-intro subindex-intro = subindex-id " " subindex-name crlf subindex-id = subindex-character+ subindex-character = "a" | "b" | … | "z" | "A" | "B" | … | "Z" subindex-name = name-character+ name-character = <gsm03.38character excluding <CR> and <LF> > crlf = <CR> <LF> service-intro = subindex-id message-id delimiter service-name crlf. message-id = number+ delimiter = "." | " " service-name = name-character+ Current version used is 1. The use of "." as delimiter means that this service is a child subindex of the index structure. Delimiter " " is used in all other cases. ETSI TS 100 902 V6.1.0 (1998-07) 27 GSM 03.41 version 6.1.0 Release 1997 Subindex-id shall not be used if the service introduced is in the first level of the index. Subindex-id:s are used in alphabetical order within an index message. They can be re-used in a child subindex. 0 Index: (MsgId=0, Message Code = 1010101010b) EI1 20 Hospitals 34 Taxis a News a201 Int News a202 Nat News a203 Local News b Sports b301 Football News b302 Hockey Results b303 Basketball c Finance c401 Finance News ca Quotes NYSE ca412 NYSE industrial ca413 NYSE electronics ca414 NYSE blue c420.Quotes Tokyo 420 Quotes Tokyo: (MsgId = 420, Message Code = 1010101010b) d Weather d501 Local Weather d502 National Weather d503 Weather in Europe d504 Weather in the World EI1 421 Tokyo Industrial 422 Tokyo Finance 423 Tokyo Blue 900.Buy and Sell 900 Buy and Sell: (MsgId = 900, Message Code = 1010101010b) EI1 901 Cars 902 Bikes 903 Boats a Home Electronics a911 Computers a912 Televisions a913 Radios 920 Baby Clothes 930 Magazines 940 Books Figure 4 ETSI TS 100 902 V6.1.0 (1998-07) 28 GSM 03.41 version 6.1.0 Release 1997 Annex A (informative): Protocols for interconnecting CBC and BSC No mandatory protocol between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC) is specified by GSM; this is a matter of agreement between CBC and PLMN operators. Some example protocols are provided in GSM 03.49 to assist CBC and PLMN operators. These are based on the following principles, which CBC and PLMN operators are recommended to follow even if they choose not to use one of the examples given in GSM 03.49. The protocol(s) between CBC and BSC should: a) provide the service defined for the CBC-BSC interface (see section 9); b) be based on protocols normally used for communication between switching and/or computer equipment; c) permit open interconnection - preferably using the OSI stack or equivalent (e.g. CCITT Number 7 Stack). ETSI TS 100 902 V6.1.0 (1998-07) 29 GSM 03.41 version 6.1.0 Release 1997 Annex B (informative): Change Request History SMG SPEC CR PHA VERS NEW_VE SUBJECT s25 03.41 A053 R97 5.8.0 6.0.0 SMSCB Message serial number update s26 03.41 A055 R97 6.0.0 6.1.0 Alignment of 03.41 with 11.11 ETSI TS 100 902 V6.1.0 (1998-07) 30 GSM 03.41 version 6.1.0 Release 1997 History Document history V6.1.0 July 1998 Publication ISBN 2-7437-2408-0 Dépôt légal : Juillet 1998
|
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 BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC.
|
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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 03.09: "Digital cellular telecommunications system (Phase 2+); Handover procedures". [3] GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [4] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". [5] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [6] GSM 09.10: "Digital cellular telecommunications system (Phase 2+); Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)". ETSI ETSI TS 100 626 V7.2.0 (1999-12) 6 (GSM 09.08 version 7.2.0 Release 1998)
|
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-services Switching Centre MSC-A Mobile-services Switching Centre, Anchor (Anchor MSC) MSC-I Mobile-services Switching Centre, Intermediate (Intermediate MSC) MSC-T Mobile-services Switching Centre, Target (Target MSC) SAPI Service Access Point Identifier SCCP Signalling Connection Control Part TCAP Transaction Capabilities Application Part Other abbreviation used in the GSM specifications are listed in GSM 01.04.
|
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 messages relating to one MS on the MSC-BSS interface a TCAP dialogue is used on the E-interface for messages relating to one MS. As no correspondence to the connectionless service on the MSC-BSS interface is used on the E-interface none of the global procedures (see GSM 08.08 subclause 3.1) are applicable. The management of the terrestrial circuits between the MSCs is outside the scope of the E-interface (see GSM 03.09), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the BSSMAP procedures and messages used on the E-interface. 4.2 Transfer of DTAP and BSSMAP layer 3 messages on the E-interface The BSSAP data which on the MSC-BSS interface is contained in the user data field of the exchanged SCCP frames (see GSM 08.06) is on the E-interface transferred as the contents of the signalling info in a BSS-APDU parameter as described in GSM 09.02. The BSSAP data consists of a BSSAP header and a DTAP or BSSMAP layer 3 message. The BSSAP header contains, as specified in GSM 08.06 (subclauses 6.3.1, 6.3.2 and 6.3.3), of a discrimination parameter, possibly a Data Link Connection Identification (DLCI) parameter, and a length indicator. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 7 (GSM 09.08 version 7.2.0 Release 1998)
|
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 originally established and the switching point for handover between MSCs. (This corresponds to MSC-A as defined in GSM 03.09 and 09.02). The MSC that is the MSC-A will not be changed during the duration of a call/connection. MSC-T is the part relating to the transitory state during the handover for the MSC to which the MS is handed over when Basic handover or Subsequent handover (see GSM 03.09) take place. (This corresponds, depending on the type of handover to MSC-A, MSC-B or MSC-B' in GSM 03.09 and 09.02). MSC-I is the part of an MSC through which the MSC-A, via an E-interface (or an internal interface) is in contact with the MS. (This corresponds, depending on the type of handover to MSC-A, MSC-B or MSC-B' in GSM 03.09 and 09.02). The MSC that is the MSC-A can also have the role of either the MSC-I or the MSC-T during a period of the call/connection. The following is applicable for the involved MSCs concerning the exchange of BSSAP data on an E-interface before and after a successful inter MSC handover: 1) At Basic handover, two MSCs are involved, one MSC being MSC-A and one being MSC-T. When this handover has been performed, the two MSCs interworking on the E-interface have the roles of MSC-A and MSC-I respectively, i.e. the MSC that is the MSC-T during the handover is now the MSC-I. 2) At Subsequent handover back to MSC-A, two MSCs are involved. The MSC having the role of MSC-A has also the role of MSC-T. The other MSC involved has the role of MSC-I. When this handover has been completed, there is no exchange of BSS data on the E-interface, i.e. the MSC being the MSC-I before and during the handover is now no longer taking part. 3) At subsequent handover to an MSC not being MSC-A, three MSCs are involved. The roles of these MSCs are MSC-A, MSC-I, and MSC-T respectively. When this handover has been performed, the two MSCs interworking on an E-interface have the roles of MSC-A and MSC-I respectively, i.e. the MSC that is the MSC-T during the handover is now the MSC-I and the MSC being MSC-I during the handover is now no longer taking part.
|
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 generated reasons; - classmark handling; - cipher mode control; - trace invocation; - queuing indication; - data link control SAPI not equal to "0"; ETSI ETSI TS 100 626 V7.2.0 (1999-12) 8 (GSM 09.08 version 7.2.0 Release 1998) - Location Acquisition. - LSA handling.
|
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 procedure (GSM 08.08 subclause 3.1.5.2) is applied on the E-interface with the following conditions: - the MSC-I acts as the MSC; - the MSC-T acts as the BSS; - if the MSC that is the MSC-A is not also the MSC-T, then this MSC shall act as the target BSS towards the MSC-I and as the MSC towards the MSC-T. The handling of terrestrial resources is not applicable.
|
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, acts as the MSC; - the MSC that is the MSC-I, if it is not also the MSC-A, acts as the serving BSS; - the MSC that is the MSC-T, if it is not also the MSC-A, acts as the target BSS. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 9 (GSM 09.08 version 7.2.0 Release 1998)
|
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 with the connected BSSs. At completion of the handover execution the MSC-I initiates the internal handover indication procedure.
|
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 the MSC that is the MSC-A is not also the MSC-T, then this MSC acts as the target BSS towards the MSC-I and as the MSC towards the MSC-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-I -> MSC-A) Excluded information elements: CIRCUIT POOL, CIRCUIT POOL LIST ETSI ETSI TS 100 626 V7.2.0 (1999-12) 11 (GSM 09.08 version 7.2.0 Release 1998) * HANDOVER REQUEST (MSC-A -> MSC-T and MSC-I -> MSC-A) Excluded information element: CIRCUIT IDENTITY CODE * HANDOVER REQUEST ACKNOWLEDGE(MSC-T -> MSC-A and MSC-A -> MSC-I) Excluded information element: CIRCUIT POOL, CIRCUIT IDENTITY CODE * HANDOVER COMPLETE (MSC-T -> MSC-A) * HANDOVER FAILURE (MSC-T -> MSC-A and MSC-I -> MSC-A) Excluded information elements: CIRCUIT POOL, CIRCUIT POOL LIST HANDOVER PERFORMED (MSC-I -> MSC-A) * HANDOVER DETECT (MSC-T -> MSC-A) CLEAR REQUEST (MSC-I -> MSC-A) SAPI "n" REJECT (MSC-I -> MSC-A) CONFUSION (MSC-T -> MSC-A, MSC-A -> MSC-T, MSC-I -> MSC-A and MSC-A -> MSC-I) # MSC INVOKE TRACE (MSC-A -> MSC-I) # BSS INVOKE TRACE (MSC-I -> MSC-A and MSC-A -> MSC-T) CIPHER MODE COMMAND (MSC-A -> MSC-I) CIPHER MODE COMPLETE (MSC-I -> MSC-A) CIPHER MODE REJECT (MSC-I -> MSC-A) ** QUEUING INDICATION (MSC-T -> MSC-A, MSC-I -> MSC-A, and MSC-A -> MSC-I) CLASSMARK UPDATE (MSC-I -> MSC-A and MSC-A -> MSC-T) CLASSMARK REQUEST (MSC-A -> MSC-I) CONNECTION ORIENTED INFORMATION (MSC-I -> MSC-A, MSC-A->MSC-I) LSA INFORMATION (MSC-A -> MSC-I) PERFORM LOCATION REQUEST (MSC-I->MSC-A, MSC-A -> MSC-I) PERFORM LOCATION ABORT (MSC-I->MSC-A, MSC-A -> MSC-I) PERFORM LOCATION RESPONSE (MSC-I -> MSC-A, MSC-A->MSC-I) All other BSSMAP messages shall be considered as non-existent on the E-interface. NOTE: Segmentation procedures for LCS CONNECTION ORIENTED INFORMATION message in GSM 08.08 apply to the corresponding message on the E-interface. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 12 (GSM 09.08 version 7.2.0 Release 1998) Some of the messages above are qualified by *, ** or #. This signifies whether the message, when sent on the E-interface, is considered as: - handover related message (*); - handover related when sent as a response to HANDOVER REQUEST (**); or - trace related message (#). 7 Exceptions for BSSMAP message contents and information element coding when transferred on the E-interface
|
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 with an unrecognisable identifier. Assignment complete message: - excluded information element: - circuit pool; - circuit identity code. - if received, the information element shall be treated as an information element with an unrecognisable identifier. Assignment failure message: - excluded information elements: - circuit pool; - circuit pool list. - if received, the information element shall be treated as an information element with an unrecognisable identifier. Handover request message: - excluded information element: - circuit identity code. - if received, the information element shall be treated as an information element with an unrecognisable identifier. Handover request acknowledge message: - excluded information element: - circuit pool; - circuit identity code. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 13 (GSM 09.08 version 7.2.0 Release 1998) - if received, the information element shall be treated as an information element with an unrecognisable identifier. Handover failure message: - excluded information elements: - circuit pool; - circuit pool list. - if received, the information element shall be treated as an information element with an unrecognisable identifier.
|
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; - terrestrial circuit already allocated; - circuit pool mismatch; - switch circuit pool. The corresponding cause values shall be considered as reserved for national use. Cell identifier information element: - excluded format: - Cell Identity. The corresponding cell identification discriminator value shall be considered as reserved. 8 BSSAP message error handling when transferred on the E-interface The handling of abnormal events related to the BSSAP header (GSM 08.08 subclause 2.4) and the BSSMAP error handling (GSM 08.08 subclause 3.1.19) are applicable with exception of the following: - the handling of faults concerning the use of SCCP is not applicable. The BSSMAP error messages sent on the E-interface shall only be sent as response to BSSAP messages received on the same interface. ETSI ETSI TS 100 626 V7.2.0 (1999-12) 14 (GSM 09.08 version 7.2.0 Release 1998) Annex A (informative): Document change history Meeting Level Doc Spec CR Rev Phase Subject Cat Current Version New Version s29 P-99- 476 09.08 A133 R98 Application of the Base Station System Application Part (BSSAP) on the E-interface for LCS B 6.0.0 7.0.0 s30 P-99- 617 09.08 A134 R98 Addition of LSA Information message B 7.0.0 7.1.0 NP-06 NP- 99446 09.08 A137 R98 Changes due to LCS enhancements C 7.0.0 7.2.0 NP-06 NP- 99446 09.08 A139 R98 LCS CR for GSM 09.08 C 7.0.0 7.2.0 ETSI ETSI TS 100 626 V7.2.0 (1999-12) 15 (GSM 09.08 version 7.2.0 Release 1998) History Document history V7.0.0 July 1999 Publication V7.2.0 December 1999 Publication
|
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 interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. The present document addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to this GTS it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality. It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
|
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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1996 document, references to GSM documents are for Release 1996 versions (version 5.x.y). [1] GSM 01.04 (ETR 100): "Digital cellular telecommunication system (Phase 2); Abbreviations and acronyms". [2] GSM 04.06 (ETS 300 555): "Digital cellular telecommunication system (Phase 2); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". [3] GSM 04.08 (ETS 300 557): "Digital cellular telecommunication system (Phase 2); Mobile radio interface layer 3 specification". [4] GSM 05.02 (ETS 300 574): "Digital cellular telecommunication system (Phase 2); Multiplexing and multiple access on the radio path". [5] GSM 05.05 (ETS 300 577): "Digital cellular telecommunication system (Phase 2); Radio transmission and reception". [6] GSM 05.08 (ETS 300 578): "Digital cellular telecommunication system (Phase 2); Radio subsystem link control". [7] GSM 08.51 (ETS 300 592): "Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface General aspects". [8] GSM 08.52 (ETS 300 593): "Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Interface principles". [9] GSM 08.56 (ETS 300 595): "Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 2 specification". [10] GSM 08.58 (ETS 300 596): "Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 3 specification". ETSI 9 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) [11] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunication system (Phase 2); Objectives and structure of Network Management (NM)". [12] GSM 12.01 (ETS 300 612-2): "Digital cellular telecommunication system (Phase 2); Common aspects of GSM Network Management (NM)". [13] GSM 12.06 (ETS 300 617): "Digital cellular telecommunication system (Phase 2); GSM Network Configuration Management and Administration". [14] GSM 12.20 (ETS 300 622): "Digital cellular telecommunication system (Phase 2); Base Station System (BSS) Management Information". [15] GSM 12.22 (ETS 300 624): "Digital cellular telecommunication system (Phase 2); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controller (BSC)".
|
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 adjusted as appropriate) MMI Man-machine Interface MSB Most Significant Byte MSC Mobile-services Switching Centre NE Network Element NM Network Management O&M Operations and Maintenance OMC Operations and Maintenance Centre RF Radio Frequency SAPI Service Access Point Indicator SW Software TEI Terminal End-point Identifier TMN Telecommunications Management Network TSC Training Sequence Code Further GSM related abbreviations may be found in GSM 01.04 (ETR 100)[1]. ETSI 10 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
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 (req,ex,rpt) NS - fault detection X X fault localization X X fault reporting X X Configuration Management Hardware control/monitor control Software control/monitor monitor State control/monitor control/monitor Parameters control/monitor monitor Performance Management Collection X X (radio path only) Reporting X X (radio path only) Administration X - Security Management (Access Control to BTS) Control - X Monitoring - X NOTE: When fault localisation is not possible at the BTS it must be deduced at the BSC. Legend: Abbreviations: NS= Not Specified; req = request; X = Function exists; ex = execution - = Function non-exists; rpt = report ETSI 11 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
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 specify how information is transferred inside the site. That is, the manner of communication between an object and objects under it is not specified in this GTS. As shown in Figure 1, the Object Classes used on the A-bis interface are a subset of those found under Site Manager on the OMC-BSC interface. The Object Classes are listed below and the functionalities that describe them are found in table 2. Site Manager: manages common control functions of several BTSs and transceivers on one site. These can include managing external alarms, front-end switch, etc. This model describes logical sites. There can be multiple logical sites in one physical site. Communication between entities within a logical site is manufacturer dependent. BTS: is associated with one cell. BTSs are typically created at installation phase by connecting transceivers to antennas thus forming cells from the air interface point of view. The BTS can also contain control functions common to various transceivers. The way BTSs are formed from transceivers and how corresponding BTS numbers are determined is configuration dependent information, which is stored during installation. Radio Carrier: represents manageable properties pertaining to radio transmission and reception of one carrier. Baseband Transceiver: represents functions common to eight radio time slots. Channel: is a physical channel in air interface, which can contain several logical channels depending on channel combination. A Channel is described with radio time slot and frequency hopping attributes (see GSM 05.02). containment Multiplicity of association: 1+ one or more n numerically specified 1+ 1+ 1+ 8 Site Manager BTS Baseband Transceiver Radio carrier Channel NOTE: Site Manager and BTS don't necessarily require separate equipment. For example, the Site Manager and a Baseband Transceiver can be associated with the same physical equipment. Figure 1/GSM 12.21: Object model seen across A-bis interface ETSI 12 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Table 2/GSM 12.21: Objects, attributes and procedures seen across A-bis interface Object class Attributes Procedures Site Manager Abis Channel Availability Status HW Configuration Manufacturer Dependent State Manufacturer Id Operational State Site Inputs Site Outputs SW Configuration Equipment Management Establish TEI Get Attributes Measurement Management Set Site Outputs State Management and Event Report SW Download Management Test Management BTS Administrative State Availability Status BCCH ARFCN BSIC BTS Air Timer CCCH Load Ind. Period CCCH Load Threshold Connection Failure Criterion GSM Time HW Configuration Intave Parameter Interterference Level Boundaries Manufacturer Dependent State Max Timing Advance Ny1 Operational State Overload Period RACH Busy Threshold RACH Load Averaging Slots SW Configuration T200 Equipment Management Get Attributes Measurement Management Report Procedures Set BTS Attributes State Management and Event Report SW Download Management Test Management Radio Carrier Administrative State ARFCN List Availability Status HW Configuration Manufacturer Dependent State Manufacturer Id Operational State Power Class RF Max Power Reduction SW Configuration Equipment Management Get Attributes Measurement Management Set RadioCarrier Attributes State Management and Event Report SW Download Management Test Management Baseband Transceiver Abis Channel* Administrative State Availability Status HW Configuration Manufacturer Dependent State Manufacturer Id Operational State SW Configuration Connect Terrestrial Signalling Disconnect Terrestrial Signalling Equipment Management Get Attributes Measurement Management State Management and Event Report SW Download Management Test Management ETSI 13 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Table 2/GSM 12.21 (continued): Objects, attributes and procedures seen across A-bis interface Object class Attributes Procedures Channel Abis Channel* Administrative State ARFCN List* Availability Status Channel Combination HW Configuration HSN* MAIO* Operational State SW Configuration TSC Connect Terrestrial Traffic Disconnect Terrestrial Traffic Equipment Management Get Attributes Measurement Management Set Channel Attributes State Management and Event Report SW Download Management Test Management NOTE: If more than one layer 2 link is defined to handle this information model, the actual implementation may affect on which layer 2 link attributes concerning frequency hopping and front-end switch are sent. Equipment used to implement frequency hopping can be common to several radio carriers or located inside one radio carrier. Front-end switch is handled by Site Manager, therefore all 'Abis Channel' attributes must be sent to it. Those attributes that need a link identifier in BSC data structures are marked with an asterisk (*).
|
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 must be in the BSC an object model with a complete layer 2 link description for each object instance in the BTS (e.g., Baseband Transceiver 1, Baseband Transceiver 2, Baseband Transceiver 3,...). When a message has to be sent to an object instance this mapping is used to find the correct link. The first connection shall be established from the BTS site by using a (semi-) permanently programmed default TEI. Subsequent to the establishment of the default connection to the site, further initial connections to other objects shall be established using TEIs provided by procedures in subclause 6.3.1. Possible additional TEIs to an object already having an initial TEI are assigned with a GSM 12.21 message found in subclause 6.3.1 through an already assigned signalling link. Object instances also have a layer 3 address. The instance number is used to address the object instance. Regardless of whether the layer 2 address uniquely identifies the object instance or not, the layer 3 address must also be provided so that it can be used by management agent to determine which object instance is being addressed. This combination of layer 2 and layer 3 addressing accommodates BTS sites with either single or multiple physical links. Specific equipment configuration information is manufacturer dependent. However, for interoperability, link configuration, default TEI assignment and instance numbering must be known by both manager and agent. This, as well as supported functions, is considered as Shared Management Knowledge.
|
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 point of view of management". In this GTS there are two different factors (CCITT Recommendation X.731 defines usage state in addition to these two) that are considered to affect the management state of a managed object. They are: - administration: permission to use or prohibition against using the resource, imposed through the management services; ETSI 14 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) - operability: whether or not the resource is physically installed and working. The present document defines the following three state management attributes to represent the management state of a managed object: - administrative state; - operational state; - availability status (this elaborates the operational state).
|
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 (traffic and signalling) information transmission on A-bis interface. Setting the administrative state of a Radio Carrier to locked means that it has to discontinue all RF emission on Air interface for the frequencies it is responsible. Setting the administrative state of a Baseband Transceiver to locked means that it has to discontinue all telecommunication tramissions and the Channels which are affected should indicate that they are Disabled or Degraded. Setting the administrative state of a BTS to locked means it has to discontinue all RF emission on all Radio Carriers and all telecommunication transmissions on all Channels of all Baseband Transceivers, i.e., Radio Carriers, Channels and Baseband Transceivers are in Disabled, Dependency state. The administrative state at the BTS site is also used to provide information e.g., for a local MMI user at a BTS site. The locked state of a 12.21 managed object means that BSC has disconnected all the calls that go through the resource that is represented by the managed object. No new traffic is connected through this resource any more. The shutting down state means that no new traffic is connected through this resource any more. The on-going calls remain. The unlocked state means that new traffic is allowed through the resource represented by the managed object.
|
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 Disabled represents the following conditions that the resources could have: - hardware or software is not installed; - power is turned off; - failure has occurred; - radio parameters has not yet been set by elementary procedures, therefore, the resource is off line. The availability status elaborates the operational state attribute. In this GTS the following values are used (availability status is a set value): In test: the resource is undergoing a test procedure. Failed: the resource has an internal fault that prevents it from operating. The operational state is disabled. ETSI 15 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Power off: the resource requires power to be applied and is not powered on. The operational state is disabled. Off line: the resource requires some manual and/or automatic operation(s) to be performed to make it available for the use. Dependency: the resource cannot operate because some other resource on which it depends is unavailable. The operational state is disabled. Degraded: the service available from the resource is degraded in some respect, such as in speed or operating capacity. The operational state is enabled. Not installed: the hardware or the software associated with the managed object has not been installed at the site. Operational state is disabled. Figure 2 illustrates the operational state and availability status behaviour of GSM 12.21 objects (i.e., Site Manager, BTS, Radio Carrier, and Baseband Transceiver) during initialization. The initial value of the administrative state is locked. SW Activate Request SW Activate Changed State Event Report Attribute setting Opstart Changed State Event Report BTS related object (Site Manager, BTS, Radio Carrier, and Baseband Transceiver) requests downloading and activation of the running software version. Software downloading and activation takes place when object is in this state. Operational state = Disabled Availability status = Not installed The last file belonging to the running software version has been downloaded and activated. Operational state = Disabled Availability status = Off line Object doesn't have correct attribute values yet. They will be received when the unlock procedure is executed. Operational state = Disabled Availability status = Off line All needed attributes of the managed object are set. Opstart to attempt to put the managed object to enabled state. Operational state = Enabled Availability status = { } Disabled, Not Installed Disabled, Off Line Enabled SW Activation not required HW installed Figure 2/GSM 12.21: GSM 12.21 Objects' Operational state and availability status behaviour during initialization ETSI 16 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
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 equipment at the BTS will include manual operations, including turning the switch on, and performing local testing where relevant at the BTS, followed by an indication of the availability of the equipment to the BTS via some man-machine interface (MMI terminal, telephone). It is then a BSC function to ensure that relevant data on the existence of the equipment is resident at the BTS, and to activate (bring into service) the new equipment. Manual procedures may also be employed for software loading, at least initially. As far as software is concerned, all operational software used at the BTS shall also be kept at the BSC, and can be downloaded from the BSC. At the BTS there may be either single instance of the software, or there may also be back-up versions.
|
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 messages shall be sent using I frames at Layer 2. A number of procedures, referred to as structured procedures (see GSM 12.22), are based on a multiplicity of elementary procedures. Some structured procedures may also involve MMI messages, but these are not defined in the present document. For all elementary procedures described in Subclauses 6.2 through 6.10, the protocol scenarios are illustrated with no further explicit reference made from their corresponding subclauses because of their self-explanatory nature. Descriptions of the messages and the direction of transmission are given in the following subclauses. No elementary procedure shall be initiated to an object instance which has not yet replied to a previously initiated elementary procedure with a response, an ACK or a NACK within a layer 3 time-out. The layer 3 timeout for ACK, NACK and responses shall have a default value of 10 seconds. An ACK message is returned to inform the application which initialized the message that the command is performed or will be performed. The whole message must be rejected if there is something not understood/supported in the original message. A NACK may not be relevant for some elementary procedures. The most relevant Nack causes, not covered by the general causes (which are used for understanding of header fields), are given for each elementary procedure with reference to the coding of the Nack causes in subclause 9.4.36. The general Nack causes are relevant for any Nack message and are also found in subclause 9.4.36. ETSI 17 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
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 --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message : Ready to receive the specified file. Message specific Nack causes (see subclause 9.4.36): 23, 24.
|
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 --------------------------------------------> ¦ ¦ ¦ -+ ACK <-------------------------------------------- Load Data Segment --------------------------------------------> etc. etc. An ACK shall be sent from the BTS to the BSC every time when Window Size number of segments specified in the Load Data Initiate message are downloaded. A reception of an ACK must not reset the value of the sequence number of the subsequent message segments (see subclause 8.1.1). When all the expected blocks have been received, an ACK must be sent regardless of the window size. If the timer for a time-out for the Layer 3 acknowledgement expires, the BSC shall send a Load Data Abort message and the file transfer shall be aborted. Meaning of Ack message: A window of Load data segment messages or a complete file has been received.
|
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 version 5.0.0 Release 1996)
|
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 specific Nack causes (see subclause 9.4.36): 25.
|
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 setting. BSC BTS SW Activate Request <-------------------------------------------- ACK/NACK --------------------------------------------> Meaning of Ack message : The request is granted and software activation will be commenced. Message specific Nack causes (see subclause 9.4.36): None.
|
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 software distribution. BSC BTS Activate SW --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: File will be activated. Message specific Nack causes (see subclause 9.4.36): 23, 26, 27.
|
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 be connected in several possibilities. ETSI 19 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) There must be a default connection to the Site Manager, which manages the front-end switch. The default connection information (AbisLink, TEI) must be (semi-)permanently programmable so that it is available at power up. Through the default connection other A-bis connections are established by configuring the front-end switch. It is optional for BTS equipment to have front-end switch features.
|
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 performed and the result shall be indicated in the ACK/NACK response message. If an initial TEI assignment fails, it can mean that TEIs cannot be assigned through the default link (e.g., physical implementation doesn't support transferring TEIs from Site Manager to Baseband Transceivers). In that case there must be subsequent preprogrammed TEIs to establish more links. BSC BTS Establish TEI --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The TEI has been established as specified. Message specific Nack causes (see subclause 9.4.36): 23.
|
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 <-------------------------------------------- Meaning of Ack message: The specified signalling link has been connected. Message specific Nack causes (see subclause 9.4.36): 1E.
|
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 specific Nack causes (see subclause 9.4.36): 20. ETSI 20 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
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 <-------------------------------------------- Meaning of Ack message: The specified traffic link has been connected. Message specific Nack causes (see subclause 9.4.36): 1E.
|
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 Nack causes (see subclause 9.4.36): 20.
|
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 <-------------------------------------------- Meaning of Ack message: The specified multi-drop link connection has been connected. Message specific Nack causes (see subclause 9.4.36): 1E.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.