hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.3.4 Interleaving | The interleaving is done as specified for SACCH in subclause 4.1.4. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.3.5 Mapping on a burst | The mapping is given by the rule: e(B,j) = i(B,j) and e(B,59+j) = i(B,57+j) for j = 0,1,...,56 and e(B+m,57) = q(2m) and e(B+m,58) = q(2m+1) for m = 0,1,2,3 where q(0),q(1),...,q(7) = 0,0,1,0,0,0,0,1 identifies the coding scheme CS-3. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4 Packet data block type 4 (CS-4) | |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4.1 Block constitution | The message delivered to the encoder has a fixed size of 431 information bits {d(0),d(1),...,d(430)}. It is delivered on a burst mode. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4.2 Block code | a) USF precoding: The first three bits d(0),d(1),d(2) are block coded into twelve bits u’(0),u’(1),...,u’(11) according to the following table: d(0),d(1),d(2) u’(0),u’(1),...,u’(11) 000 000 000 000 000 001 000 011 011 101 010 001 101 110 110 011 001 110 101 011 100 110 100 001 011 101 110 111 010 110 110 111 001 111 10... |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4.3 Convolutional encoder | No convolutional coding is done. ETSI TS 100 909 V6.1.1 (1998-07) 30 GSM 05.03 version 6.1.1 Release 1997 |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4.4 Interleaving | The interleaving is done as specified for SACCH in section 4.1.4. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.1.4.5 Mapping on a burst | The mapping is given by the rule: e(B,j) = i(B,j) and e(B,59+j) = i(B,57+j) for j = 0,1,...,56 and e(B+m,57) = q(2m) and e(B+m,58) = q(2m+1) for m = 0,1,2,3 where q(0),q(1),...,q(7) = 0,0,0,1,0,1,1,0 identifies the coding scheme CS-4. 5.2 Packet control channels (PACCH, PBCCH, PAGCH, PPCH, PNCH, PTCCH) The coding schem... |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.3 Packet random access channel (PRACH) | Two coding schemes are specified for access bursts on the packet switched channels. The packet access burst containing 8 information bits and the extended packet access burst containing 11 information bits. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.3.1 Packet Access Burst | The encoding of this burst is as defined in section 4.6 for the random access channel (RACH). The BSIC used shall be the BSIC of the BTS to which the burst is intended. |
b03a5e12102d53d92940a49c0e1cfb88 | 100 909 | 5.3.2 Extended Packet Access Burst | The burst carrying the extended packet random access uplink message contains 11 information bits d(0),d(1),...,d(10). Six parity bits p(0),p(1),...,p(5) are defined in such a way that in GF(2) the binary polynomial: d(0)D16 +...+ d(10)D6 + p(0)D5 +...+ p(5), when divided by D6 + D5 + D3 + D2 + D + 1 yields a remainder ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 0 Scope | The present document defines the requirements for and gives guidelines on the MMI for calls on the GSM Mobile Station (MS). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 0.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 0.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04 [1]. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 0.3 Definitions | Directory Number: a string consisting of one or more of the characters from the set {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, #, a, b, c} associated with a nature of address indicator and number plan indicator. When using the public MMI for the control of supplementary services however, * and # cannot be part of any SC or SI f... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 1 General | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 1.1 Basic philosophy | The basic idea behind the present document is that it should give a minimum level of requirements, with emphasis on items which are seen as important from a pan-European usage point of view. This means, that the requirements are mainly dealing with standardized control procedures of access to services i.e. call establi... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 1.2 Structure of the specification | The TS is divided into sections describing respectively the control procedures, the input features and the output features. The final section defines the basic public MMI. For a lot of items for which no particular MMI specification is necessary there is a reference to the specifications where the basic requirements ar... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2 Physical user input features | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2.1 General | This clause gives the requirements or guidelines for the MMI of the input related MS features. Basic requirements on these features are given in GSM 02.07 [3] and GSM 02.40 [7]. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2.2 MMI related to MS access | No requirements additional to those in other GSM specifications (Reference GSM 02.17 [5], 11.10 [20]). |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2.3 MMI related to MS features | The three first issues are covered in GSM 02.07 [3]: * Country / PLMN selection: The method is manufacturer optional. * International Access Function ("+" key): and * Keypad: The physical means of entering the characters 0-9, +, * and # (i.e. the SELECT function) may be keypad, voice input device, DTE or other, but the... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2.4 MMI related to user information | These issues are covered in GSM 02.40 [7]: * Selection of language of announcements: No additional requirements are defined in the present document. ETSI TS 100 907 V6.1.0 (1999-03) 10 GSM 02.30 version 6.1.0 Release 1997 |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 2.5 Other input features | No requirements additional to those in other GSM specifications (Reference GSM 03.14 [14] 11.10 [20]). |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3 Indications and output features | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3.1 General | This clause gives the requirements and guidelines of the MMI aspects of the outputs such as displayed information, indications and tones. Basic requirements on these features are given in GSM 02.07 [3] and GSM 02.40 [7]. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3.2 MMI related to MS access | No requirements additional to those in other GSM specifications (ref. GSM 03.12 [13], GSM 04.08 [16], GSM 05.08 [18]). |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3.3 MMI related to MS features | Country/PLMN Indication: * The country/PLMN Indication (see GSM 02.07 [3] for definition) should be displayed as such that the user can uniquely identify the country and PLMN e.g. by alpha or numeric means or other. These issues are covered in GSM 02.07 [3]. No additional requirements are defined in this specification:... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3.4 MMI related to user information | These issues are covered in GSM 02.40 [7]. No additional requirements are defined in this specification: * Selection of language of announcements; * Supervisory tones. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 3.5 Other output features | No requirements additional to those in other GSM specifications (ref. GSM 03.01 [11], 03.09 [12], 03.12 [13], 04.08 [16] and 05.08 [18]). |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4 Procedures | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.1 General | ETSI TS 100 907 V6.1.0 (1999-03) 11 GSM 02.30 version 6.1.0 Release 1997 This clause defines the MMI of the service access procedures, and supplementary service control procedures. These procedures are defined as logical procedures and in general no mandatory methods are specified. In order to make the descriptions con... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.2 MS access | The MS access procedure is comprised of the initial actions the user has to take before calls can be established or received. This procedure includes e.g. insertion of subscriber-card and entering the PIN-code. As there exist different types of MS and as requirements in other GSM specifications allow different options ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.3 Definition of functions | The following functions are applicable and mandatory for the logical procedures for Mobile originated and terminated calls and for the control of Supplementary Services: ACCEPT: Acceptance of a mobile terminated call. SELECT: Entry of information. SEND: Transmission of the entered information to the network. INDICATION... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4 Call Control | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4.1 General | Voice calls to and from a Mobile Station shall be controlled in accordance with the procedures described below. "Data calls" are expected to be controlled in a similar way but are not here specified. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4.2 Voice calls | The voice call is either a normal telephony call or an emergency call. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4.2.1 Mobile originated calls | The following sequence of functions shall be used: SELECT: Entry of called address information. SEND: Transmission of the called address. INDICATION: See subclause 4.3. ETSI TS 100 907 V6.1.0 (1999-03) 12 GSM 02.30 version 6.1.0 Release 1997 END: Termination of the call. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4.2.2 Emergency calls | With Mobile Stations supporting Telephony, it shall be possible to place an emergency call by entering 112 followed by SEND in the manner specified in subclause 4.4.2.1. It may also be possible for a user to enter a preferred emergency MMI code of up to six digits (such as 999) followed by SEND to invoke an emergency c... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.4.2.3 Mobile terminated calls | The following sequence of functions shall be used: INDICATION: Alert to the user that she is being called. ACCEPT: Acceptance of the incoming call by the user. INDICATION: See subclause 4.3. END: Termination of the call. User Determined User Busy (UDUB): If, on being alerted by an incoming call, the called user enters ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5 Supplementary Services Control | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.1 General | 4. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.1 General | The supplementary services shall be controlled in accordance with the procedures described below. All Mobile Stations with MMI shall be able to be controlled in this way, to minimize the confusion of users using different types of Mobile Station (quite likely, due to the use of the SIM IC card) and to permit the introd... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.2 Structure of the MMI | The following sequence of functions shall be used for the control of Supplementary Services: SELECT: Entry of the procedure information (may be a digit or a sequence of characters). SEND: Transmission of the information to the network. INDICATION: See subclause 4.3. ETSI TS 100 907 V6.1.0 (1999-03) 13 GSM 02.30 version... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.3 Handling of supplementary services | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.3.1 Handling of defined GSM supplementary services | The MMI procedure for the defined GSM Supplementary Services shall be converted to the mobile radio interface Layer 3, as specified in GSM 04.80 [17]. An appropriate message should be given/displayed to the user in accordance with the "return result/error" from the network. The service codes for the defined GSM Supplem... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.3.2 Handling of not-implemented supplementary services | The MS shall act in accordance with figure 4.5.3.2 when digits are entered to the MS to determine whether to interpret these as call set-up requests or supplementary service control procedures etc.. This may involve a mechanism, referred to as Unstructured SS Data, which allows the support of GSM SS services which are ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.4 Registration of new password | The following procedure permits the user to change the password relating to use of Supplementary Services. The only control procedure supported is Registration of a new password, which replaces any previous password for the same service. The password may not be Erased or Interrogated. ETSI TS 100 907 V6.1.0 (1999-03) 1... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5 Handling of supplementary services within a call | 4.5.5.1 Call Deflection, Call Waiting, Call Hold, MultiParty Services, Explicit Call Transfer and Completion of Calls to Busy Subscriber general principles During a call, the following general procedures shall be available, where applicable, for the subscriber to control the operation of - Call Deflection - Call Waitin... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.2 Call Waiting (CW) | During a call, provided this service is active for the called party, if a second call attempts to make contact, a "call waiting" indication will be presented to the called party. To clear the current call and accept the waiting call, enter 1 followed by SEND, within the time out period. Alternatively, either party in t... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.3 Call hold | During a call, the initial call may be held while another call is made by entering the second directory number followed by SEND. To shuttle between the two calls enter 2 followed by SEND irrespective of whether the second call was acquired using the Call Hold or acceptance of Call Waiting procedures. If no waiting call... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.4 MultiParty | Having established calls to these two parties with one call active and the other on hold, enter 3 followed by SEND for a multiparty conversation. ETSI TS 100 907 V6.1.0 (1999-03) 19 GSM 02.30 version 6.1.0 Release 1997 To add another remote party, the same procedure applies. Another call is established and either this ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.5 Explicit Call Transfer | Having established calls to these two parties with one call active and the other on hold, enter 4 followed by SEND to transfer the calls. If a subscriber has one active, one held and one waiting call, and by entering 4 SEND the active and held call are connected, after the successful completion of the transfer, the ser... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.6 Special case | Provided both Call Hold and Call Waiting is active, it is possible to have one active and one held call and then a third call attempting to make contact. In this case, to clear the active call and accepting the waiting call (the held call not affected) enter 1 followed by SEND (If entering 2 followed by SEND the call s... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.7 Call Deflection | If informed about an incoming call this call may be redirected to an another destination by entering 4 * "Directory Number" followed by SEND. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.5.8 Completion of calls to busy subscribers - $(CCBS)$ | In a situation where a calling party A encounters busy of congestion on the B side, the network may offer the possibility to apply the CCBS supplementary service. If subscriber A, after being notified that CCBS is possible and during the period where the retention timer is running (minimum 15 seconds), enters 5 followe... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.6 Other handling of supplementary services | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.6.1 Multiple Subscriber Profile - $(MSP)$ | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.6.1.1 Registering an alternative profile | An alternative profile is registered by entering the profile ID of the new profile, as illustrated: * 59n # SEND Where n is the identity of the profile desired. ETSI TS 100 907 V6.1.0 (1999-03) 20 GSM 02.30 version 6.1.0 Release 1997 An indication is given to the user showing whether this procedure was successful. The ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.5.6.1.2 Selecting an alternative profile on a per call basis | An alternative profile to the registered profile is selected by entering the profile ID of the new profile along with the desired Directory Number, as illustrated: * 59n # DN SEND Where n is the identity of the profile desired Continued processing of the call shall implicitly indicate that the selection was successful,... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6 SIM interfaces | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6.1 Entry of PIN and PIN2 | After insertion of the IC card while the MS is switched on, or when the MS is switched on while the IC card is inserted, or when the MS is switched on in the case of a plug-in SIM, an indication is given to the user that the PIN must be entered, unless the PIN is not applicable. If the user wishes to perform a function... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6.2 Change of PIN or PIN2 | The following procedure permits the user to change the PIN or PIN2 in the SIM: PIN: **04*OLD_PIN*NEW_PIN*NEW_PIN# PIN2: **042*OLD-PIN2*NEW_PIN2*NEW_PIN2# Note that the SEND function is not used in these procedures. An indication is given to the user showing whether this procedure was successful. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6.3 Unblocking of PIN or PIN2 | The following procedure permits the user to unblock the PIN or PIN2: PIN: **05*PIN_UNBLOCKING_KEY*NEW_PIN*NEW_PIN# PIN2: **052*PIN2_UNBLOCKING_KEY*NEW_PIN2*NEW_PIN2# Note that the SEND function is not used in these procedures. The new PIN or PIN2 must be entered whether or not it is intended to change the PIN or PIN2. ... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6.4 Reading the abbreviated dialling code | An abbreviated dialling code shall be able to be read using the following procedure: N(N)(N)# Alternative additional procedures are also permitted. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.6.5 Status information - return codes | The SIM gives status information, as responses to instructions, in two-byte codes (see GSM 11.11 [21] clause "Status Conditions Returned by the Card"). Some of the possible return codes are deeply related to the user's actions and should therefore be indicated to her. It is mandatory to give the user the appropriate in... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 4.7 Presentation of IMEI | The following procedure shall instruct the ME to display its IMEI: *#06# The procedure shall be accepted and performed with and without an inserted SIM. The ME shall then display the 14 digits of the IMEI (not including the spare digit), the Check Digit and optionally the Software Version Number as defined in GSM 02.16... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5 The basic public MMI | 5.1 General In order to improve the standardization of the MMI for GSM Mobile Stations intended for general use by the public to access voice services, the following additional specification is provided. Equipment which meets the present document may quote "Approved to 02.30-Section 5" in its specification. This proced... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2 Basic public MMI specific features | |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.1 Keyboard layout | - Layout of 12-keypad as per figure 5.2. - Layout of all other keys are optional. - Control key functions: No additional functions standardized (exception: see subclause 5.2.3). - Control key symbols: No additional standardization. - Control key positions: No requirements. 1 2 3 4 5 6 7 8 9 * 0 # Figure 5.2 |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.2 Number entry | - No restriction on number entry or editing. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.3 Call control | - A hand-set shall be present to place and receive calls. - SEND and END function keys are mandatory for execution of call initiation/termination respectively. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.4 Call acceptance | - On receiving "Ring Alert", the user may lift the hand-set "Off Hook" or press the SEND-function key. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.5 Call initiation | ETSI TS 100 907 V6.1.0 (1999-03) 23 GSM 02.30 version 6.1.0 Release 1997 |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.5.1 "Off Hook" call initiation | 1) Lift the hand-set "Off Hook" - Dial tone is presented. 2) Enter number. Dial tone is cancelled after entry of the first digit (including * and #). 3) Press SEND-function key. 4) If the unit is "Off Hook" and the SEND-function key is not pressed, call set up may be automatically initiated after expiry of a time-out o... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.5.2 "On Hook" call initiation | Time-out dialling in "On Hook" - mode is not allowed for mobiles fitted with an "On Hook" dialling feature. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.6 Call termination | - The call is terminated by replacing the hand-set "On Hook" or by pressing the END-function key. - The call may also be terminated by e.g. replacing "On Hook" by B-party, radio path interruption and invalidation of payment. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.7 Supplementary services control | The primary function of the * and # on the Basic Public MMI will be for control of supplementary services in accordance with the procedures defined in subclause 4.5. of the present document. |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.8 Payment | If the MS requires to be set up with some means of payment e.g. cash, prepaid card or credit card, a "payment indication" will be presented to the user when payment is required at the initial step (see subclause 5.2.5, Call Initiation Steps). When a call is in progress and payment which has been made is nearly used up,... |
752c9139d9e1304cc597ae9d738009a7 | 100 907 | 5.2.9 Country/PLMN selection | (For definition, see GSM 02.07 [3]). PLMN selection shall be in accordance with GSM 02.11 [4], but "automatic" shall be the default mode. ETSI TS 100 907 V6.1.0 (1999-03) 24 GSM 02.30 version 6.1.0 Release 1997 Annex A (normative): MS access mealy graph MS - OFF Enter- card Enter- PIN Serv -AV Enter - PLMN Failure - Tr... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 1 Scope | This Technical Specification describes the Cell Broadcast short message service (CBS). It defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in GSM 02.03 ... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 1.1 Normative references | References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" befor... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 1.2 Abbreviations | Abbreviations used in this TS are listed in GSM 01.04 [1]. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 2 General description | The CBS service is analogous to the Teletex service offered on television, in that like Teletex, it permits a number of unacknowledged general messages to be broadcast to all receivers within a particular region. CBS messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may com... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 3 Network Architecture | The basic network structure of CBS is depicted by figure 1. ETSI TS 100 902 V6.1.0 (1998-07) 8 GSM 03.41 version 6.1.0 Release 1997 CBC CBE CBE BSC BTSs MSs MSs MSs 1 1 2 2 2 3 3 3 4 4 4 outside scope of GSM Specs. inside scope of GSM Specs. Figure 1 - message transfer on link 1 is outside the scope of GSM Specificatio... |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 4 CBE Functionality | The functionality of the CBE is outside of the scope of GSM Specifications; however it is assumed that the CBE is responsible for all aspects of formatting CBS, including the splitting of a CBS message into a number of pages. |
78cca9fc7c3cacbff09961357dbc9595 | 100 902 | 5 CBC Functionality | As the CBC (and any originating point for cell broadcast short messages) is regarded as a node outside the PLMN, only the requirements placed upon the CBC by CBS functionality are specified by this specification. The CBC may be connected to several BSCs. The CBC may be connected to several CBEs. The CBC shall be respon... |
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 de... |
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 ra... |
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 octe... |
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, implementat... |
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 cons... |
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.1... |
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 comb... |
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 ... |
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 ... |
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 STATU... |
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-... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.