Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   None

TS 12.71 (SA5)
Location Services (LCS) – Location services management

ToC   3GPP‑Page   ETSI‑search   Help    
(P) GSM Rel-99 v8.0.1  2000/11  65 p.
(P) GSM Rel-98 v7.0.1  2000/11  66 p.

Rapporteur:  PATEL, Milan
See also:  –

This TS addresses the network management architecture, functions, and protocol for LCS operations and maintenance. The information model included here defines the managed entities and how they are addressed for purposes of operations and maintenance activities.

There is a requirement for the network management interface to be open to allow interoperation between LMUs and GMLCs of different manufacturers working to the same SMLC. This TS addresses this requirement from an operations and maintenance point of view, which allows this interworking to take place. It shows the split of network management functions between GMLC, SMLC and LMU. The procedures and coding of the messages are specified in detail. In practice, in addition to this TS, it is necessary that the content of manufacturer-dependent information fields be specified to fulfil the functionality.

It is essential for operation that a SMLC can handle the functions used by all its LMUs. Therefore, all items in this TS are considered mandatory unless otherwise indicated in this TS.


Here   Top



1  ScopePDF-p. 7
2  References
3  Symbols and AbbreviationsPDF-p. 8
4  LCS O&M ArchitecturePDF-p. 9
5  LCS managed entitiesPDF-p. 11
6  LCS O&M FunctionsUp
7  LCS O&M Protocol
7.1  LMU LCS O&M Messages and ProceduresUp
7.1.1  Management Information Model
7.1.2  Elementary ProceduresPDF-p. 18
7.1.3  Message CodingPDF-p. 27
7.2  SMLC LCS O&M Messages and ProceduresPDF-p. 38
7.3  GMLC LCS O&M Messages and Procedures
A  Messages and Procedures DescriptionsPDF-p. 39
A.1  LMU Messages
A.1.1  Message Details
A.1.1.1  Message Categories
A.1.1.2  SW Download Management MessagesPDF-p. 41
A.1.1.3  Test Management Messages
A.1.1.4  State Management MessagesPDF-p. 44
A.1.1.5  Event Report MessagesUp
A.1.1.6  Equipment Management MessagesPDF-p. 46
A.1.1.7  General Management Messages
A.1.1.8  Report Messages
A.1.2  Coding
A.1.2.1  Message TypePDF-p. 48
A.1.2.2  Managed Entity ClassPDF-p. 50
A.1.2.3  Managed Entity Instance
A.1.2.4  Attributes and ParametersPDF-p. 51Up
A.  Additional Info
A.  Additional Text
A.  Administrative StatePDF-p. 52
A.  Attenuator Enable
A.  Autonomous Swap
A.  Autonomously Report
A.  Availability StatusPDF-p. 53
A.  Calibration Required
A.  Destination
A.  DiversityUp
A.  Event TimePDF-p. 54
A.  Event Type
A.  File Data
A.  File Id
A.  File Version
A.  HW ConfigurationPDF-p. 55
A.  HW Description
A.  Latitude
A.  LMU PositionPDF-p. 56
A.  LongitudeUp
A.  Manufacturer-Dependent State
A.  Manufacturer-Dependent Thresholds
A.  Manufacturer Id
A.  MethodPDF-p. 57
A.  NACK Causes
A.  Number of SegmentsPDF-p. 58
A.  Operational State
A.  Outstanding Alarm SequencePDF-p. 59
A.  Perceived Severity
A.  Physical ConfigurationUp
A.  Probable Cause
A.  Pseudo-rangePDF-p. 60
A.  Result
A.  Satellite Info
A.  Self-Position Capability
A.  Set Own Position Upon Startup
A.  Software Download CapabilityPDF-p. 61
A.  Source
A.  Specific Problems
A.  SW ConfigurationPDF-p. 62Up
A.  SW Description
A.  Test Duration
A.  Test Number
A.  Test Report Info
A.  Time
A.  Time of FixPDF-p. 63
A.  Timing Source
A.  Type
A.  Window Size
A.2  SMLC MessagesUp
A.3  GMLC Messages
B  Change historyPDF-p. 64

Up   Top