ETSI TS 152 071-2001 Digital Cellular Telecommunications System (Phase 2+) Location Services (LCS) Location Services Management《数字蜂窝通信系统(第2+阶段) 定位业务(LCS) 定位业务管理 3GPP TS 52 071(版本4 .pdf

《ETSI TS 152 071-2001 Digital Cellular Telecommunications System (Phase 2+) Location Services (LCS) Location Services Management《数字蜂窝通信系统(第2+阶段) 定位业务(LCS) 定位业务管理 3GPP TS 52 071(版本4 .pdf》由会员分享，可在线阅读，更多相关《ETSI TS 152 071-2001 Digital Cellular Telecommunications System (Phase 2+) Location Services (LCS) Location Services Management《数字蜂窝通信系统(第2+阶段) 定位业务(LCS) 定位业务管理 3GPP TS 52 071(版本4 .pdf（66页珍藏版）》请在麦多课文档分享上搜索。

1、ETSI TS 152 071 V4.0.0 (2001-03) Technical Specification Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Location services management (3GPP TS 52.071 version 4.0.0 Release 4) 3GPP TS 52.071 version 4.0.0 Release 4 1 Reference RTS/TSGS-0552071 UV Keywords GSM ETSI 650

2、Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 O0017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice ETSI TS 152 071 V4.0.0 (2001-03) Individual copies of

3、the present document can be downloaded from: htttx/w.etsi. org The present document may be made available in more than one electronic version or in print. In any ase of existing c perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In

4、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 document should be aware that the document may be subject to revision or change of status. Information on the current status of this

5、 and other ETSI documents is available at hi%:i/wc%lw.esi.or/b/slatis/ If you find errors in the present document, send your comment to: ed itoretsi .fr Copyright No tification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to

6、 reproduction in all media. O European Telecommunications Standards Institute 2001. All rights reserved. ETSI 3GPP TS 52.071 version 4.0.0 Release 4 2 ETSI TS 152 071 V4.0.0 (2001-03) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared

7、to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR O00 3 14: “Intellectual Property Rights (IPRs); Essential, orpotentially Essential, IPRs notjed to ETSI in respect OfETSIstandards“, which is avail

8、able from the ETSI Secretariat. Latest updates are available on the ETSI Web server (-). 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 O00 3 14 (or the upd

9、ates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by the ETSI 3d Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3G

10、PP identities, UMTS identities or 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 www.etsi.ordkey . ETSI 3GPP TS 52.071 version 4.0.0 Release 4 3 ETSI TS 152 071

11、 V4.0.0 (2001-03) Contents Foreword 6 1 2 3 3.1 3.2 4 5 5.1 5.2 5.3 6 6.1 Scope . 7 Symbols and Abbreviations . 8 Symbols . . 8 Abbreviations . . . 8 References . 7 LCS O 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is increme

12、nted 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 3GPP TS 52.071 version 4.0.0 Release 4 7 ETSI TS 152 071 V4.0.0 (2001-03) 1 Scope The present document

13、describes the network management for LCS O Abbreviations and acronyms“. GSM 12.00 (ETS 300 612-1): “Digital cellular telecommunication system (Phase 2); Objectives and structure of Network Management (NM)“. GSM 12.01 (ETS 300 612-2): “Digital cellular telecommunication system (Phase 2); Common aspec

14、ts of GSM Network Management (NM)“. GSM 12.20 (ETS 300 622): “Digital cellular telecommunication system (Phase 2); Base Station System (BSS) Management Information“. GSM 12.21 (ETS 300 623): “Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages on the

15、A-bis interface“. 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)“. GSM 02.7 1 : Digital cellular telecommunications system (Phase 2+), Location Services (LCS), Ser

16、vice Description, Stage 1. GSM 03.71 : Digital cellular telecommunications system (Phase 2+), Location Services (LCS), Functional Description, Stage 2. 21 31 41 51 61 71 SI ETSI 3GPP TS 52.071 version 4.0.0 Release 4 8 ETSI TS 152 071 V4.0.0 (2001-03) 91 GSM 04.71: Digital cellular telecommunication

17、s system (Phase 2+), Mobile radio interface layer 3 location services specification, formats and coding. ITU Recommendation M.3400: TMN management functions. ITU Recommendation X.680: ASN. 1 Specification of Basic Notation Data Network ITU Recommendation X.691: ASSN. Encoding Rules Specification of

18、Packed Encoding Rules - Data Network. ITU Recommendation X.7 1 1 : Common Management Information Protocol: Specification. ITU Recommendation X.73 1 : Systems Management: State Management Function. lo1 111 121 i31 i41 3 3.1 Symbols and Abbreviations Symbols For the purposes of the present document, t

19、he following symbols apply: Lb Le Lg Lh LP Ls Um Interface between Serving MLC and BSC (BSC interface) Interface between External User and Gateway MLC (external interface) Interface between Gateway MLC and VMSC (Gateway MLC interface) Interface between Gateway MLC and HLR (HLR interface) Interface b

20、etween SMLC and peer SMLC (peer interface) Interface between Serving MLC and VMSC (Serving MLC interface) Air Interface to an LMU (measurement interface) 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN. 1 BSC BSS BTS CCCH CMIP DTAP GMLC GPS GSM HLR

21、HW ID IMSI LCS LLP LMU MLC MMI MS MSC NE NM NSS O - 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 entity: - Administrative state; - Operational

22、state; - Availability status (this provides additional information for understanding the operational state values). 7.1.1.3.1 Administrative State Administrative states of the managed entity can be controlled only by the SMLC. The locked state of a managed entity means that the SMLC has terminated a

23、ll requests to the resource that is represented by the managed entity. No new requests are initiated to this resource. The shutting down state means that no new requests are initiated to this resource. The on-going requests are completed. The unlocked state means that new requests are allowed to the

24、 resource represented by the managed entity. 7. I. 1.3.2 Operational State CCITT X.73 1 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

25、 or fully operable and available for use. In the present document the value disabled represents the following conditions that the resources could have: - - power is turned off; - failure has occurred; - hardware or software is not installed; radio parameters have not yet been set by elementary proce

26、dures (7.1.2), therefore, the resource is off-line. ETSI 3GPP TS 52.071 version 4.0.0 Release 4 17 ETSI TS 152 071 V4.0.0 (2001-03) 7. I. 1.3.3 Availability Status The availability status elaborates the operational state attribute. State change is only reported when the operational state changes, no

27、t when availability status changes. Availability status is only sent as information along with the state change indication. In the present document the following values are used (availability status is a set value): In test: The resource is undergoing a test procedure. The operational state may be d

28、isabled or enabled, depending on the level of intrusion of the test. Failed: The resource has an internal fault that prevents it from operating. The operational state is disabled. Power off: The resource requires power to be applied and is not powered on. The operational state is disabled. Off line:

29、 The resource requires some manual andor automatic operation(s) to be performed to make it available for use. The operational state is disabled. Dependency: The resource cannot operate because some other resource on which it depends is unavailable. The operational state is disabled. Degraded: The se

30、rvice 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 entity has not been installed at the site. Operational state is disabled. Figure 3 illustra

31、tes the operational state and availability status behaviour of managed entities. The initial value of the administrative state is locked. SW Activation HW Installed SW Activate Request Disabled, Not Installed SW Activate w Disabled, Off Line Attribute Setting Opstart Changed State Event Report ri En

32、abled LMU related objects request 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 bee

33、n downloaded and activated. Object does not 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. Attempt to put the managed object to enabled st

34、ate. Operational state = Enabled Availability status = Figure 3: Managed Entities Operational State and Availability Status Behaviour During Initialisation ETSI 3GPP TS 52.071 version 4.0.0 Release 4 18 ETSI TS 152 071 V4.0.0 (2001-03) 7.1.2 Elementary Procedures The operational procedures applicabl

35、e to the LMU consist of bringing LMU equipment and software into (or taking them out of) service, initiation of tests at the LMU, collection of test results made at the LMU, reporting and clearing of any LMU faults, and reporting of any LMU external alarms. Bringing into service of equipment at the

36、LMU will consist of manual operations, including powering on, and performing local testing where relevant at the LMU, followed by an indication to the SMLC of the LMU equipment availability. It is then an SMLC function to ensure that relevant data on the existence of the equipment is resident at the

37、 LMU, and to activate (bring into service) the new equipment. 7.1.2.1 Definition of the Procedures All the procedures covered in the present document are based on formatted O Pertaining to a failure, there shall be a report for its start and another for its end. A failure causing change of operation

38、al state shall generate two event reports: State Changed Event Report and Failure Event Report. No ACK or NACK is returned to the LMU. SMLC Failure Event Report LMU 7.1.2.5.2 Stop Sending Event Reports (See ITU Recommendation M.3400 101 Fault Management/Alarm Surveillance/Alarm Reporting/Inhibit Ala

39、rm Reporting). This inhibition of sending of event reports shall be used by the SMLC to prevent a flood of event reports which are of no benefit to the SMLC. One example of this occurs at an LMU restart following a power failure. The operational capability of the LMU hardware is unlikely to be diffe

40、rent from what it was before the failure, and a flood of reports, each stating that a piece of hardware is operating, will delay the software download. Another example concerns the case of a frequently occurring transient fault. SMLC Stop Sending Events Reports LMU r ACWNACK F Meaning of ACK message

41、: Sending of specified Event Report has been stopped. Message specific NACK causes (see Subclause A. 1.2.4.24): None. 7.1.2.5.3 Restart Sending Event Reports (See ITU Recommendation M.3400 101 Fault Management/Alarm Surveillance/Alarm Reporting/Allow Alarm Reporting). When the LMU is back in normal

42、operation or if it is of interest to check whether the LMU still generates a flood of Event Reports, a Restart Sending Event Reports shall be sent. SMLC Restart Sending Events Reports LMU r ACWNACK - Meaning of ACK message: Sending of specified Event Report has been restarted. Message specific NACK

43、causes (see Subclause A. 1.2.4.24): None. ETSI 3GPP TS 52.071 version 4.0.0 Release 4 24 ETSI TS 152 071 V4.0.0 (2001-03) 7.1.2.5.4 Report Outstanding Alarms (See ITU Recommendation M.3400 101 Fault Management/Alarm Surveillance/Alarm Reporting/Request Alarm History). This message shall be used by t

44、he SMLC to ask the LMU to report all outstanding alarms related to the managed entity instance indicated in the message. The LMU shall report alarms by sending a series of Failure Event Report messages for all outstanding alarms. Only those alarms previously reported and still outstanding shall be r

45、e-reported through this procedure. Any new alarms not yet reported but about to be reported shall be excluded and they shall be reported through a separate Failure Event Report procedure spontaneously initiated by the LMU itself. If there is no outstanding alarm, the LMU shall reply with a NACK with

46、 that cause indicated. SMLC LMU Report Outstanding Alarms ACWNACK b 4 Meaning of ACK message: Sending of Failure Event Report will start. Message specific NACK causes (see Subclause A.1.2.4.24): 40,41,42. 7.1.2.6 Equipment Management Procedures Equipment Management Procedures provide the capability

47、to control equipment during maintenance. 7.1.2.6.1 Change-over (See ITU Recommendation M.3400 101 Configuration Management/Status and ControVStatus and Control of NEs). This message shall be sent to change over between active and standby units of equipment. The action may be performed on any address

48、able functional managed entity and manufacturer-dependent HW units. Which type of HW unit to address and how to identiSl certain units of this type of HW are manufacturer-dependent. SMLC LMU Change-over r ACWNACK Meaning of ACK message: The specified change-over operation has been performed. Message

49、 specific NACK causes (see Subclause A.1.2.4.24): 25, 26, 30, 35. 7.1.2.6.2 Opstart (See ITU Recommendation M.3400 101 Configuration Management/Status and Control/NE Status and Control). This message shall be sent by the SMLC to tell the LMU to attempt to operate the identified managed entity putting it to an initial normal operational state (i.e., enabled, see Subclause 7.1.1.3.2). This message does not affect the managed entitys administrative state if there exists a value explicitly assigned by the SMLC. If there is yet no administrative state