1、3404583 OLL9553 4T Released: July, 1994 GSM 12.05 Version: 4. I .O Date: 1 July, 1994 Source: ETSI TC-SMG Reference: GSM 12.05 UDC: 621.396.21 Key words: European digital cellular telecommunications system, Global System for Mobile communications (GSM) European digital cellular telecommunications sy
2、stem (Phase 2); Subscriber related call and event data (GSM 12.05) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42 O0 - Fax: + 33
3、93 65 47 16 European Telecommunications Standards Institute 1994. All rights reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied. Page 2 GSM 12.05 vers
4、ion 4.1 .O = 3404583 0339554 333 U 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 Editing and Standards Approval Dept.“ at the address
5、shown on the title page. Page 3 GSM 12.05 version 4.1.0 Con tents 1 . Scope 9 2 . Normative references 9 3 . Definitions 10 4 . Abbreviations . 11 5 . General 12 6 . TMN management services 6.1 . Tariff and charging administration . 13 . 13 6.1.1 . Subscriber billing 6.1 .2 . Accounting 14 6.1.2.1.
6、Inter-PLMN accounting . 14 6.1.2.1 .l. Visitors from other PLMNs . 14 6.1.2.1.2. Home subscribers roaming in other PLMNs . 14 6.1.2.2. Fixed network operators and other service providers 14 6.1.3. Service provision . 14 6.1.4. Customer administration 15 6.2. Management of mobile equipment 15 7 . TMN
7、 management service components . 16 7.1. Tariff and charging administration . 16 7.1.1 Tariff administration . 7.1 . 2. Data collection . 16 7.1.2.1 . Data generation control . 16 7.1.2.2. Data transfer control . 16 7.2. Management of mobile equipment . 17 8 . TMN management functions . 8.1 . Tariff
8、 administration 8.1.1. Tariff class managemen 8.1.1 . 1 . Charging origin functions 18 8.1 .1. 2. Charging destination functions 19 8.1.1.3. Charging zone functions . 8.1 . 1 . 4. AOC service functions . 8.1.1.5. Tariff class functions . 8.1.2. Tariff period management . 20 8 1 . 3 Day class managem
9、ent . 20 8 1.4. Tariff management 8.1.5 Tariff system mana 8.2. Data Collection 8.2.1. Data generation control 24 8.2.1.1, Record generation control . 24 8.2.1 . 1 1 . Record type generation control 24 8.2 1.1.2. Partial record generation control 8.2.1.1.3 Supplementary service recordin 8.2 1.2 Emer
10、gency call notification control 25 8.2 1.3 Observed IMEI ticket control . m 3404583 OLL9556 Lob Page 4 GSM 12.05 version 4.1.0 8.2.1.4. Log control . 25 8.2.2. Data transfer control 26 8.2.2.1. Event reporting . 26 8.2.2.1.1. Event forwarding discriminators 26 8.2.2.1.2. Call event record reporting
11、26 8.2.2.1.3. Emergency call reporting 26 8.2.2.1.4. Observed IMEI ticket reporting 26 8.2.2.2. Bulk record transfer 27 8.2.2.3. Log access . 27 Annex A (Normative) . 28 Information model 28 A.1 Overview . 28 Tariff administration, the date and time view . 29 A.l.l A.1.2 A.1.3 Tariff administration,
12、 the service and distance view 28 The call recording View . 31 A.2 Naming hierarchy . 33 A.3 Inheritance . 34 A.4 Managed object classes . 35 A.4.1 A.4.2 A.4.3 A.4.4 A.4.5 A.4.6 A.4.7 A.4.8 A.4.9 A.4.10 A.4.11 A.4.12 A.4.13 A.4.14 A.4.15 A.4.16 A.4.17 A.4.18 A.4.19 A.4.20 AOC service 35 Call and eve
13、nt log entry 36 Log (CCITT X.721) 36 Call recording function 36 Charging destination . 37 Charging origin 37 Charging zone . 38 Charging calendar . 37 Day class 38 Event forwarding discriminator 38 Roamer tariff . 38 Record class . 38 Record type control Supplementary service action control . Supple
14、mentary service control . Tariff (AOC) . 40 Tariff class . 41 Tariff System 41 . 39 Tariff administration . 40 Tariff switch pattern . 41 A.5 Attributes 44 A.5.1 AOC Service Identity A.5.3 Basic service . 44 A.5.2 AOC Service Name A.5.4 Basic Services 44 A.5.5 Calendar year . 44 A.5.6 Call duration
15、44 . 44 A.5.7 CallerID . . 45 A.5.8 A.5.9 A.5.10 Call recording function Identity . 45 A.5.1 1 Call reference . 45 .5.12 Call types 45 Call event record content . Call event record type . 45 Page 5 GSM 12.05 version 4.1.0 A513 Cause for termination 45 A.5.14 Cell identity .45 A515 Date definitions .
16、 46 A517 Day class identity 46 A.5.16 Day classes A.5.18 Day class name . .46 A.5.19 Day definitions .46 A520 Destination identity. . A.5.21 Destination name A.5.22 Emergency call indication destination . A524 El : Units per time interval A525 E2: Seconds per time interval . 47 A.5.27 E4: Unit incre
17、ment 48 A528 E5: Units per data interval . A.5.29 E6. Segments per data interval A530 E7: Initial seconds per time interval . A.5.23 Emergency call indication enable . A.5.26 E3: Scaling factor . . .47 A.5.31 Home PLMN identity . . .4a A.5.34 MSC incoming trunk group .49 A533 Mobile station classmar
18、k . A.5.35 MSC outgoing trunk group . A536 MS power classes . A. 5.37 Network-specif ic services A.5.39 Observed IMEI ticket generati A.5.40 Origin identity . . 50 . 50 . 50 A.5.47 Record class destination . A.5.48 Record class identity . 51 ASS0 Recording method . A.5.51 Record type A.5.53 Sewed MS
19、ISDN . . .52 . 51 A.5.57 Supplementary service code . A.5.62 Tariff name . . 53 53 53 .54 3404583 OLL9558 T89 Page 6 GSM 12.05 version 4.1.0 A.6 A.7 A.8 A.9 A.5.71 Type of subscribers . 54 A.5.72 Type of transaction . 55 A.5.73 Zone id 55 A.5.74 Zone name 55 Actions . 56 A.6.1 A.6.3 TS Check 56 A.6.
20、4 TS Copy tariff system 56 A.6.5 TS Unfreeze 56 TS Cancel change-over 56 A.6.2 TS Change-over 56 Notifications . 57 A.7.1 Call event record report . 57 A.7.2 Emergency call indication . 57 A.7.3 Observed IMEI ticket report 57 Name bindings . 58 Abstract syntax 60 A.l O Application Context 75 Annex B
21、 (Normative) . 76 Call and event records . 76 B.1 General 76 Use of supplementary services . 76 B.l.l.1 Use of call forwarding 76 B.l . 1.2 Use of call hold and multi-party services . 77 B.1.2 Partial records . 77 B.1.3 Use of packet data services 78 B.l . 4 Inter-msc handover . 79 B.1.5 Call re-est
22、ablishment 79 6.1.6 Restricted directory numbers . 79 B.l . 1 8.2 Record contents . 80 B.2.1 8.2.2 B.2.3 8.2.4 B.2.5 8.2.6 8.2.7 8.2.8 8.2.9 8.2.10 8.2.1 1 8.2.12 8.2.1 3 B.2.14 8.2.15 82.16 8.2.17 8.2.18 Mobile originated call attempt . 81 . 82 83 84 85 86 Mobile originated emergency call attempt .
23、 Mobile originated call forwarding attempt Mobile terminated call attempt . Roaming call attempt . Incoming gateway call attempt . Transit call attempt Supplementary service actions . 89 HLR interrogation 90 Location update (HLR) Short message service, mobile terminated Outgoing gateway call attempt
24、 . Location update (VLR) Short message service, mobile originated . 92 SMS-MO interworking record . SMS-MT gateway record . . Common equipment usage . 92 . 93 Reduced partial records 3404583 OLL9559 715 Page 7 GSM 12.05 version 4.1.0 8.3 Description of record fields . 96 8.3.1 Additional Charging In
25、formation 96 8.3.2 AOC parameters / change of AOC parameters . 96 8.3.3 B.3.4 Call duration 96 8.3.5 Call reference 97 8.3.6 Calling / called / connected / translated number 97 8.3.7 Cause for termination 97 8.3.8 Data volume 98 8.3.9 Diagnostics . 98 8.3.10 Equipment id . 98 Incoming/ outgoing trun
26、k group 99 8.3.14 Interrogation result 99 Location / change of location . 99 Mobile station classmark / change of classmark 100 8.3.18 Entity number 100 Number of forwarding 100 Old /new location . 100 8.3.23 Record type . 100 B.3.24 Routing number I roaming n . 100 8.3.25 Sequence number . 101 Basi
27、c Service / change of service / ISDN Basic Service 96 8.3.1 1 Equipment type . 98 8.3.12 Event time stamps 98 8.3.1 3 8.3.1 5 8.3.16 Message reference . 99 8.3.17 8.3.19 8.3.20 8.3.21 8.3.22 Record extensions Radio channel requested / rad . channel used / change of rad . channel 100 8.3.26 Served IM
28、EI 101 8.3.27 Served IMSI 8.3.28 Served MSISDN . . 101 B.3.29 Service centre address 101 8.3.30 Short message service result . I01 8.3.31 Supplementary service(s) . 101 8.3.32 8.3.33 5.3.34 supplementary service parameters . . 102 5.3.36 Update result . Supplementary service action . 101 Supplementa
29、ry service action result 102 8.3.35 Transparency indicator 102 6.4 Example scenarios . 103 8.4.1 Mobile to land (outgoing) call 104 105 8.4.2 Land to mobile (incoming) call 6.4.3 Mobile to mobile call within the same network 106 6.4.4 Incoming call to a roaming subscriber . . 107 6.4.5 Incoming call
30、 to a PLMN service centre B 4.6 B 4.7 Call forwarding conditional (on busy) . . 110 B.4.8 6 4.9 Call hold and multi-party service 112 Call forwarding unconditional Delivery of a mobile terminated short mes Page 8 GSM 12.05 version 4.1 .O Annex C (Nonnative) . 113 Observed IMEI Tickets 113 C.1 Genera
31、l 113 C.2 Observed IMEI tickets 113 C.3 Description of record fields . 114 C.3.1 IMEI Check Event . 114 C.3.2 IMEI Status . 114 Number of pages: 114 Page 9 GSM 12.05 version 4.1 .O 1. Scope This specification is concerned with the administration of subscriber related event and call data. This includ
32、es both the collection of call data from, and the distribution of tariff data to, the network elements. The subscriber (IMSI) and mobile equipment (IMEI) related call and event data collected is employed by a number of management activities including billing how the action is to be recorded (in MOC/
33、 MTC records or in SS-action records); and for which class of subscribers the actions are to be recorded (own/ visiting/ all subscribers). The following system management functions are required. CreateiSeGeUDelete supplServiceControl Create/Set/GeDelete ssActionContro1 8.2.1.2. Emergency call notifi
34、cation control This function permits the OS to enable/ disable the generation of the emergency call notification. It also permits the OS to define the destinations (management application entities) to which the notification is to be sent. lhe following system management functions are required: SeGet
35、 callRecordingFunction 8.2.1.3. Observed IMEI ticket control This function permits the OS to enable/ disable the generation of observed IMEI tickets. If the generation of these tickets is enabled then they shall be stored in the appropriate file type (“observed IMEI ticket“) within the local record
36、filestore. This function also permits the definition of one or more destinations (management application entities) to which the tickets may be sent in the form of event reports. The following system management functions are required: SeGet cal I Recordi ng F unct ion 8.2.1.4. Log control This functi
37、on permits the record notifications described above to be stored and retrieved from logs within the NEF. The logging of these records is performed in accordance with the log control function specified in CCIlT X.735 and no additional management functions are required W 3404583 0339578 877 Page 26 GS
38、M 12.05 Version 4.1.0 8.2.2. Data transfer control This service component contains the following groups of TMN management functions: 0 Event reporting 0 Bulk record transfer Log access 8.2.2.1. Event reporting These TMN functions control the generation and transmission of notifications from the NEF
39、to the OSF. 8.2.2.1 .l. Event forwarding discriminators In addition to the notification control functions outlined in section 8.2.1., for short-term recording of specific events and for more complicated filter conditions the event forwarding discriminator construct defined in CCITT X.734 and CCIlT X
40、.721 must be employed. The event forwarding discriminator construct is extremely flexible permitting the combination of a number of fields and logical operations with a wide variety of scheduling options. The EFD also controls the destinations to which the event reports are sent. Several such filter
41、s may be defined and scheduled for operation at different times and for different time periods. The following system management functions are required: Create/Set/Get/Delete eventForwardingDiscriminator 8.2.2.1.2. Call event record reporting This function permits the NEF to transmit a call or eveni
42、record for a particular call attempt or event to the OSF. In general the record shall be sent on completion of the call or event. This function is controlled by means of the management functions described in section 8.2.1.1. The following system management functions are required: Notification callEv
43、entRecordReport 8.2.2.1.3. Emergency call reporting This function permits the NEF to send a notification to an application entity within the OS whenever an emergency call is made within the network. The notification includes the IMEI (if available), the IMSI (if available) and the identity of the ce
44、ll from which the call is made. This notification shall be sent during the emergency call Set-up. The generation of this notification is controlled by means of the functions described in section 8.2.1.2. The following system management functions are required: Notification emergencyCalllndication 8.2
45、.2.1.4. Observed IMEI ticket reporting This function permits the NEF to send a notification to an application entity within the OS whenever an observed IMEI ticket is generated. The generation of this notification is controlled by means of the functions described in section 8.2.1.3. 3404583 0119579
46、703 page 27 GSM 12.05 version 4.1.0 The following system management functions are required: Notification observed1MEITicketRepot- 8.2.2.2. Bulk record transfer This group of TMN functions is concerned with the bulk transfer of call and event records from the NEF record filestore to the NEF. The call
47、 and event records shall be transferred from the NEF to the OSF by the use of FTAM services. For further details of the use of FTAM see TS GSM 12.01. In addition to the simple file transfer services provided by FTAM, peer-to-peer application process communication may be also be supported. The use of
48、 CMIS services for the uploading of files from the NEF to the OSF is specified in TS GSM 12.00. 8.2.2.3. Log access This TMN function control the access to the log described in section 8.2.1.4. Each log defined may contain one or more log entries. Each log entry contains a single calli event record.
49、 Note: The term log entry has been used instead of the term log record to avoid confusion between the records contained within the local filestore and the records stored within logs. For further details concerning the use of logs see CCITT X.735. The following system management functions are required: GeUDelete CallEventLogEntry W 3404583 OLL9580 425 W Page 28 GSM 12.05 Version 4.1 .O Annex A (Normative) Information model A.l Overview This annex contains the formal description of the information model for TS GSM 12.05. It consist of a simplified Entity-Relationship
