ETSI/TC SMG
`Released by: ETSI/PT 12
`Release date: February 1992
`
`RELEASE NOTE
`
`Recommendation GSM 04.08
`
`Mobile Radio Interface Layer 3 Specification
`
`(Updated Release 1/90)
`Previously distributed version: 3.13.0
`New Released version February 92: 3.13.0 (Release 92, Phase 1)
`
`l, Reason for changes
`
`No changes since the previously distributed version. ·
`
`Page 1 of 10
`
`SAMSUNG EXHIBIT 1025
`
`

`

`This page is left blank intentionally
`
`Page 2 of 10
`
`

`

`INTERIM
`EuROPEAN
`TELECOMMUNICATION
`STANDARD
`
`Source: ETSI TC-SMG
`
`UDC: 621.396.21
`
`2nd FINAL DRAFT
`pr 1-ETS 300 022
`
`February 1992
`
`Reference: GSM 04.08
`
`Key words: European Digital Cellular Telecommunications System, Global System
`Communications (GSM)
`
`for Mobile
`
`European digital cellular
`telecommunications system (phase 1 );
`Mobile radio interface layer 3 specification
`
`ETSI
`
`European Telecommunications Standards Institute
`ETSI Secretariat: B.P.152 . F - 06561 Valbonne Cedex . France
`TP. + 33 92 94 42 00 TF. + 33 93 65 47 16 Tx. 47 00 40 F
`
`© European Telecommunications Standards Institute 1992.
`All rights reserved.
`
`No part may be reproduced or used except as authorised by contract or other written permission. The
`copyright and the foregoing restriction on reproduction and use extend to all media in which the
`information may be embodied.
`
`Page 3 of 10
`
`

`

`2nd Final draft prl-ETS 300 022: 1992
`
`Whilst every care has been taken in the preparation and publication of this document, errors in
`content, typographical or otherwise, may occur. If you have comments concerning its accuracy,
`please write to "ETSI Standards Management Dept." at the address shown on the title page.
`
`Page 4 of 10
`
`

`

`2nd Final draft prl-ETS 300 022: 1992
`
`Foreword
`
`This second Final draft Interim European Telecommunication Standard (1-ETS) .has been produced by
`the Special Mobile Group (SMG), a Technical Committee of the European Telecommunications
`Standards Institute (ETSI).
`
`The final drafts dealing with the GSM system were adopted by vote in May 1991 but were not
`published. This was because amendments, agreed by ETSI TC-SMG at subsequent meetings, were
`made to some of the drafts. However, other drafts have not been amended since the first vote.
`
`This updated draft is now considered to be stable enough for submission to second vote.
`
`This 1-ETS is the mobile radio interface layer 3 specification for call control, mobility management
`and radio resource management procedures within the European digital cellular telecommunications
`system (phase 1 ) .
`
`Reference is made within this 1-ETS to the following technical specifications (NOTE 1 ):
`
`GSM 02.02
`
`GSM 02.03
`
`GSM 02.09
`
`GSM 02.17
`
`GSM 03.01
`
`GSM 03.03
`
`GSM 03.13
`
`GSM03.14
`
`GSM 03.20
`
`GSM 04.02
`
`GSM 04.03
`
`GSM 04.04
`
`GSM 04.05
`
`GSM 04.06
`
`GSM 04.07
`
`GSM 04.10
`
`GSM 04.11
`
`GSM 04.12
`
`GSM 05.02
`
`GSM 05.03
`
`Bearer services supported by a GSM PLMN.
`
`Teleservices supported by a GSM PLMN.
`
`Security aspects.
`
`Subscriber identity modules, functional characteristics.
`
`Network functions.
`
`Numbering addressing and identification.
`
`Discontinuous reception (DRX) in the GSM system.
`
`Support of DTMF via the GSM system.
`
`Security related network functions.
`
`GSM PLMN access reference configuration.
`
`Mobile Station - Base Station System
`structures and access capabilities.
`
`(MS-BSS)
`
`interface: Channel
`
`MS-BSS layer 1 - general requirements.
`
`Mobile Station - Base Station System (MS-BSS) data link layer - general
`aspects.
`
`MS - BSS data link layer specification.
`
`Mobile radio interface signalling layer 3 • general aspects.
`
`Mobile radio interface layer 3 - supplementary services specification -
`general aspects.
`
`Point-to-point short message service support on mobile radio interface.
`
`Cell broadcast short message service support on mobile radio interface.
`
`Multiplexing and multiple access on the radio path.
`
`Channel coding.
`
`Page 5 of 10
`
`

`

`2nd Final draft prl-ETS 300 022: 1992
`
`GSM 05.08
`
`Radio subsystem link control.
`
`GSM 07.01
`
`General on terminal adaptation functions for Mobile Stations.
`
`GSM 09.02
`
`Mobile application part specification.
`
`GSM 09.06
`
`GSM 09.07
`
`Interworking between a PLMN and a PSPDN/ISDN for support of packet
`switched data transmission services.
`
`General requirements on interworking between the PLMN and the ISDN or
`PSTN.
`
`GSM 11.10
`
`Mobile station conformity specification.
`
`The above specifications, together with annexes B, C, F, G and H of this standard, are normative.
`
`Annexes D and E are informative.
`
`NOTE 1:
`
`ETSI has constituted stable and consistent documents which give technical
`specifications
`for
`the
`implementation of
`the European digital cellular
`telecommunications system. Historically, these documents have been identified as
`·GsM recommendations·.
`
`Some of these recommendations may subsequently become Interim European
`(1-ETSs) or European Telecommunication
`Telecommunications Standards
`Standards (ETSs), whilst the others will be renamed ETSI-GSM Technical
`for editorial
`Specifications. These ETSI-GSM Technical Specifications are,
`reasons, still referred to as GSM recommendations in some current GSM
`documents.
`
`The numbering and version control system use
`for ETSI-GSM Technical
`Specifications is the same as that used for GSM recommendations.
`
`NOTE 2:
`
`Items in this draft indicated as not complete, or requiring further study or work,
`are not required for the Phase 1 implementation of the European digital cellular
`telecommunications system.
`
`Page 6 of 10
`
`

`

`ETSI/GSM
`
`Version 3.13.0
`
`RECOMMENDATION GSM 04.08
`
`Title:
`
`Mobile Radio Interface Layer 3 Specification
`
`Date: February 1992
`
`List of Contents:
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`
`General
`Overview of control procedures
`RR management procedures
`Elementary procedures for mobility management
`Elementary procedures for circuit-switched call control
`Packet communication across the radio interface
`Structured procedures
`Handling of error conditions
`Message functional definitions and contents
`General message format and information elements coding
`List of system parameters
`
`Annex B
`Annex C
`Annex D
`Annex E
`Annex F
`Annex G
`Annex H
`
`Compatibility checking
`Low layer information coding principles
`Examples of bearer capability information element coding
`Comparison between Q.931 and Rec. OSM o4.08
`OSM specific cause values for radio resource management
`GSM specific cause values for mobility management
`Cause values for call control
`
`{detailed list of contents given on next pages)
`
`Number of pages: 446
`
`Page 7 of 10
`
`

`

`GSM 04.08 - v. 3,13.0 - page 77
`
`4.4.4
`
`4.4.4.1
`
`Generic Location Updating procedure
`
`Location updating initiation by the Mobile Station
`
`The Mobile Station initiates the location updating procedure by sending
`a LOCATION UPDATING REQUFST message to the network and starts the timer
`T3210. The location updating type information element shall indicate
`what kind of updating is requested ••
`
`As no RR-connection exists at the time when the l9cation updating
`procedure has to be started, the MM-sublayer within the mobile station
`will request the RR-sublayer to establish a RR-connection. The
`procedure for establishing a RR- connection is described in section
`3.3.
`
`4.4.4.2
`
`Identification request from the network
`
`The network may initiate the identification procedure, e.g.if the
`network is unable to get the IMSI based on the TMSI and LAI used as
`identification by the Mobile Station (see section 4.3.3).
`
`4.4.4.3 Authentication by the network
`
`The authentication procedure (see section 4.3.2) is initiated by the
`network upon receipt of the LOCATION UPDATING REQUFST message from the
`Mobile Station in the cases defined in Rec. GSM 02.09.
`
`4.4.4.4 Ciphering mode setting by the network
`
`The ciphering mode setting procedure (see section 3.4.7) is initiated
`by the network, if a new TMSI has to be allocated.
`
`Page 8 of 10
`
`

`

`GSM 04.08 - v. 3.13.0 - page 78
`
`4.4.4.5 Location updating accepted by the network
`
`If the location updating is accepted by the network a LOCATION UPDATING
`ACCEPT message is transferred to the Mobile Station.
`
`In case the identity confidentiality service is active (see section
`4.3.1 and 4.4.4.4), the TMSI reallocation may be part of the location
`updating procedure. The TMSI allocated is then contained in the
`LOCATION UPDATING ACCEPT message together with the location area
`identifier LAI. The network shall in this case start the supervision
`timer T3250 as described in section 4.3.1.
`
`The mobile station receiving a LOCATION UPDATING ACCEPT message shall
`store the received location area identification LAI, stop timer T3210,
`reset the attempt counter and set the update status to "updatec•·. If
`the message contains an IMS!, the mobile station shall delete a.~y TMSI.
`If the message contains a TMSI, the mobile station shall store the TMSI
`and a TMSI REALLOCATION COMPLETE shall be returned to the network. If
`neither IMS! nor TMSI is received in the LOCATION UPDATING ACCEPT
`message, the old TMSI if any available shall be kept.
`After that, the mobile station shall wait for the network to release
`the RR-connection, see section 4.4.4.7.
`In normal cases, the mobile station will enter the "idle, updated"
`state after the release of the RR-connection. In this state it shall
`
`- perform normal location updating when a new location area is entered
`- perform periodic updating
`- perform IMSI detach
`perform IMSI attach if activated in the same location area
`- support requests from the CM layer
`- respond to paging
`
`Page 9 of 10
`
`

`

`GSM 04.08 - v. 3.13.0 - page 79
`
`4.4.4.6 Location updating not accepted by the network
`
`If the location updating cannot be accepted the network sends a
`~OCATION UPDATING REJECT message to the Mobile Station.
`The Mobile Station receiving a LOCATION UPDATING REJECT message shall
`stop the timer T3210, store the reject cause, start T3240 and enter the
`location updating rejected state awaiting the release of the RR(cid:173)
`connection triggered by the network. Upon the release of the RR(cid:173)
`connection the MS shall take the following actions depending on the
`stored reject cause:
`
`II 2 (IMS! unknown in HLR), or
`# 3 (Illegal MS):
`For the Mobile Station this corresponds to authentication failure. The
`Mobile Station shall delete any TMSI, stored LAI, cipher key and cipher
`key sequence number and enter the "idle, no IMS!" state. In this state
`the Mobile Station shall act in the following way:
`
`- not start any normal location updating attempt
`- not perform periodic updating
`- not perform IMS! detach if powered down
`- reject any requests from CM entities for MM-connections except
`emergency calls
`- not respond to paging
`
`Page 10 of 10
`
`