ETSI TS 123 195-2004 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) Provision of User Equipment Specific Behaviour Informat.pdf

1、 ETSI TS 123 195 V5.4.0 (2004-09)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Provision of User Equipment Specific BehaviourInformation (UESBI) to network entities(3GPP TS 23.195 version 5.4.0 Release 5)GLOBAL SYSTEM

2、FOR MOBILE COMMUNICATIONSRETSI ETSI TS 123 195 V5.4.0 (2004-09) 1 3GPP TS 23.195 version 5.4.0 Release 5 Reference RTS/TSGS-0223195v540 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NA

3、F 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of

4、existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present

5、document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the

6、following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2004. All

7、rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members a

8、nd of the 3GPP Organizational Partners. ETSI ETSI TS 123 195 V5.4.0 (2004-09) 2 3GPP TS 23.195 version 5.4.0 Release 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if a

9、ny, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available

10、on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server)

11、which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities o

12、r GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 123 195 V5.4.0 (2004-09) 3 3GPP TS 23.195 version 5.4.0

13、Release 5 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 General description.7 4.1 UESBI 7 4.2 UESBI-Uu 8 4.3 UESBI-Iu8 4.4 UESBI-Iu on A interface8 5 Signalling flows9 5.1 UESBI-Uu signa

14、lling flows9 5.1.1 RRC connection establishment (initial and at cell reselection towards UTRAN) 9 5.1.2 RR connection establishment9 5.1.3 SRNS relocation .9 5.1.4 Inter RAT hand-over.10 5.1.4.1 3G barb2right 2G inter-RAT hand-over 10 5.1.4.2 2Gbarb2right 3G inter-RAT hand-over 10 5.2 UESBI-Iu signa

15、lling flows .10 5.2.1 CS attach / normal location update without Gs.10 5.2.1.1 Obtaining the IMEISV 10 5.2.1.2 Transfer of UESBI-Iu to RAN 11 5.2.2 PS attach without Gs.11 5.2.3 Combined PS and CS attach with Gs11 5.2.4 PS inter-SGSN routeing area update without Gs 13 5.2.5 Inter-SGSN routeing area

16、update with Gs 14 5.2.6 CS attach when already PS attached and Gs present 16 5.2.7 CS domain, transfer of UESBI-Iu to RAN .16 5.2.7.1 MS Initiated Iu-cs Connection Establishment Procedure16 5.2.7.2 Network Initiated Iu-cs Connection Establishment.17 5.2.8 PS domain transfer of UESBI-Iu to RAN.18 5.2

17、.8.1 MS Initiated Service Request Procedure.18 5.2.8.2 Network Initiated Service Request Procedure.19 5.2.9 Intra- and inter-MSC handover from A/Gb mode to Iu mode 19 5.2.10 Inter-MSC handover GSM to GSM in A/Gb-mode20 5.2.11 Inter-MSC handover Iu mode to A/Gb-mode .21 5.2.12 Intra- and inter-MSC SR

18、NS relocation.22 5.2.13 Intra- and inter-SGSN SRNS relocation .23 5.2.14 Emergency call handling 25 5.2.14.1 Mobile with (U)SIM registered in MSC/VLR 25 5.2.14.2 Mobile without (U)SIM, or, Mobile with (U)SIM that is not registered in MSC/VLR 25 5.2.15 Special cases .25 6 Operational aspects of handl

19、ing fault information .25 6.1 General Aspects25 6.2 FIB Register .25 Annex A (Informative): Compatibility with network entities not supporting the PUESBINE Feature27 A.1 General .27 ETSI ETSI TS 123 195 V5.4.0 (2004-09) 4 3GPP TS 23.195 version 5.4.0 Release 5 A.2 Inter SGSN relocation 27 A.3 Inter

20、SGSN Routing Area Update 27 A.4 Iu interface issues .27 A.5 Gs issues.27 A.6 Inter-MSC issues 28 A.7 Iu to A-interface issues.28 A.8 A interface issues28 Annex B (informative): Void .29 Annex C (informative): Change history .30 History 31 ETSI ETSI TS 123 195 V5.4.0 (2004-09) 5 3GPP TS 23.195 versio

21、n 5.4.0 Release 5 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the presen

22、t document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under chang

23、e control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 123 195 V5.4.0 (2004-09) 6 3GPP TS 23.195 version 5.4.0

24、 Release 5 1 Scope The present document defines the stage-2 description of the mechanism to provide the 3GPP network entities with UE Specific Behaviour Information (UESBI). UESBI may be used by correcting mechanisms to overcome some of the issues that have been recognized by 3GPP in TR 25.994 (Meas

25、ures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults) 13, and other such documents. The description of these correcting mechanisms is out of the scope of this TS. ITU-T Recommendation I.130 1 describes a three-stage method for characteris

26、ation of telecommunication services, and ITU-T Recommendation Q.65 2 defines stage 2 of the method. 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 publ

27、ication, 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers

28、to the latest version of that document in the same Release as the present document. 1 ITU-T Recommendations I.130: “General modelling methods Method for the characterisation of telecommunication services supported by an ISDN and network capabilities of an ISDN“. 2 ITU-T Recommendation Q.65: “Methodo

29、logy Stage 2 of the method for the characterization of services supported by an ISDN“. 3 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 4 3GPP TS 23.060: “General Packet Radio Service (GPRS) Service description; Stage 2“. 5 3GPP TS 23.009: “Handover

30、procedures“. 6 3GPP TS 25.331: “Radio Resource Control (RRC) protocol specification“. 7 3GPP TS 44.018: “Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol“. 8 3GPP TS 44.008: “Mobile radio interface layer 3 specification“. 9 3GPP TS 25.413: “UTRAN Iu interface Radio

31、 Access Network Application Part (RANAP) signalling“. 10 3GPP TS 23.236: “Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes“. 11 3GPP TS 29.060: “General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface“. 12 3GPP

32、 TS 23.116: “Super-Charger technical realization; Stage 2“. 13 3GPP TR 25.994: “Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults“. 14 3GPP TR 25.995: “Measures employed by the UMTS Radio Access Network (RAN) to cater for legacy Us

33、er Equipment (UE) which conforms to superseded versions of the RAN interface specification“. ETSI ETSI TS 123 195 V5.4.0 (2004-09) 7 3GPP TS 23.195 version 5.4.0 Release 5 15 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 16 3GPP TS 29.010 Information element mapping between Mobile Station -

34、Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 21.

35、905 15 and the following apply. PUESBINE Feature: is the functionality described by this TS. UE Specific Behaviour Information - Uu (UESBI-Uu): is information that is sent using Access Stratum signalling from the UE to the RAN. It can be used to derive some specific information about the UEs capabil

36、ities. UE Specific Behaviour Information - Iu (UESBI-Iu): is information that is sent from the MSC and/or SGSN to the RAN that can be used to derive some specific information about the UEs capabilities. The UESBI-Iu is a Bit Map of UE Faults derived from the IMEISV. 3.2 Abbreviations For the purpose

37、s of the present document, the abbreviations given in 3GPP TS 21.905 15 and the following apply: FIB Register Faulty IMEISV to Bitmap Register PUESBINE Provision of UE Specific Behaviour Information to Network Entities UE User Equipment UESBI UE Specific Behaviour Information UESBI-Uu UE Specific Be

38、haviour Information - Uu UESBI-Iu UE Specific Behaviour Information - Iu 4 General description 4.1 UESBI Due to the potential problems that may happen in the standard or in its implementation by different types of UE, it may be needed to transfer to the RAN “information on the specific behavior of p

39、articular sets of UE“ with regard to some 3GPP features. This aims at helping the infrastructure to handle UE(s) already in the field that are facing problems to support some 3GPP features. This “information on the specific behavior of particular sets of UE“ is called UE Specific Behavior Informatio

40、n (UESBI). UESBI actually corresponds to 2 different sets of information: UESBI-Uu which is sent from UE to RAN using signalling specified in the RRC protocol (TS 25.331 6) UESBI-Iu which is sent by CN to UTRAN/GERAN over the Iu interface and is derived from IMEISV retrieved by CN from UE. UESBI-Uu

41、and UESBI-Iu may have a different nature, their coding is defined in RRC and RANAP respectively, and have different handling within the network. Whether or not UESBI-Uu or UESBI-Iu is used to describe an inter-operability issue will be determined on a case by case basis and all uses should be docume

42、nted in TRs such as 25.994 13 and 25.995 14. As a result of this process, RAN nodes should not receive conflicting information in UESBI-Uu and UESBI-Iu. ETSI ETSI TS 123 195 V5.4.0 (2004-09) 8 3GPP TS 23.195 version 5.4.0 Release 5 The SRNC uses both UESBI-Iu and UESBI-Uu to derive the specific beha

43、viour of the UE. In the context of this specification, the terms RNS and RNC refer also to a GERAN BSS or BSC (respectively) when serving UE in Iu mode. 4.2 UESBI-Uu UESBI-Uu information is sent: - (at RRC connection establishment from idle mode) directly by UE to Serving RNC at RRC connection estab

44、lishment - (at SRNS relocation) from Serving RNC to Target RNC in the RRC: SRNS RELOCATION INFO message carried through CN during SRNS relocation in the RANAP: Source RNC to Target RNC Transparent Container IE. - (at RRC connection establishment for an UE coming from another Radio Access Technology

45、e.g. in case of 2G to 3G Hand-Over) from UE to Serving RNC via “Inter RAT Hand-Over“ Information. This “Inter RAT Hand-Over Information“ is sent to the source RAN (e.g. BSS), and at handover copied by the source RAN into a transparent container that is carried through the CN towards the Target RNC.

46、- (at RR connection establishment) the UE can directly send the “Inter RAT Handover Information“ which contains the UESBI-Uu to the GERAN BSS. However, if control of GERAN BSS functions using the UESBI-Uu is needed, then new functionality will be required within the BSS to decode the ASN.1 PER infor

47、mation contained in the Inter-RAT Handover Information IE. 4.3 UESBI-Iu When the UE attaches to the VLR or SGSN or makes its first Location Update in the VLR, the IMEISV information is retrieved from the UE and stored in the VLR or SGSN. At each subsequent Iu interface connection establishment (eg f

48、or a CS domain voice call or a PS domain data transfer), the IMEISV is retrieved from the VLR or from the MM context in the SGSN and, the UESBI-Iu is derived. The UESBI-Iu is then sent to the SRNC. The UESBI-Iu is normally sent in the Common Id procedure (the same procedure that currently carries th

49、e IMSI) or by the UESBI-Iu Information procedure. This is summarised in figure 4.3-1. 1 Attach SGSN/MSC SRNC BTS IMEISV UE IMEISV Storage Attach and IMEISV interrogation 2 UESBI 3 Figure 4.3-1: UESBIIu architecture If the UE state is changed from RRC Connected to RRC Idle, all information derived from the received UESBI is released in the RNS. Thus if the UE state is changed afterwards back to RRC Connected the delivery of the UESBI-Iu from MSC or SGSN to SRNC shall be repeated. At inter-SRNS relocation or at in