-
Notifications
You must be signed in to change notification settings - Fork 16
/
map.db
8009 lines (7103 loc) · 257 KB
/
map.db
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
October 2009 U14SSS
www.dialogic.com
Dialogic® DSI SS7 Protocol Stack
MAP Programmer's Manual
Section 1 Introduction
2
Copyright and Legal Notice
Copyright © 1997-2009 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part
without permission in writing from Dialogic Corporation at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and do not
represent a commitment on the part of Dialogic Corporation or its subsidiaries (“Dialogic”). Reasonable effort is made to ensure
the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information
and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR
IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT
AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER,
AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS
INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR
INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear
facility applications.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in
specific countries, and thus may not function properly in other countries. You are responsible for ensuring that your use of such
products occurs only in the countries where such use is suitable. For information on specific products, contact Dialogic
Corporation at the address indicated below or on the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in
marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual
property rights owned by third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic
products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic
and no such licenses are provided except pursuant to a signed agreement with Dialogic. More detailed information about such
intellectual property is available from Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada
H4M 2V9. Dialogic encourages all users of its products to procure all necessary intellectual property licenses
required to implement any concepts or applications and does not condone or encourage any intellectual property
infringement and disclaims any responsibility related thereto. These intellectual property licenses may differ from
country to country and it is the responsibility of those who develop the concepts or applications to be aware of
and comply with different national license requirements.
Dialogic, Dialogic Pro, Brooktrout, Diva, Cantata, SnowShore, Eicon, Eicon Networks, NMS Communications, NMS (stylized),
Eiconcard, SIPcontrol, Diva ISDN, TruFax, Exnet, EXS, SwitchKit, N20, Making Innovation Thrive, Connecting to Growth, Video
is the New Voice, Fusion, Vision, PacketMedia, NaturalAccess, NaturalCallControl, NaturalConference, NaturalFax and Shiva,
among others as well as related logos, are either registered trademarks or trademarks of Dialogic Corporation or its
subsidiaries. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such permission may only be
granted by Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized
use of Dialogic's trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time
and any use of Dialogic’s trademarks requires proper acknowledgement.
The names of actual companies and products mentioned herein are the trademarks of their respective owners.
Any use case(s) shown and/or described herein represent one or more examples of the various ways, scenarios or
environments in which Dialogic® products can be used. Such use case(s) are non-limiting and do not represent
recommendations of Dialogic as to whether or how to use Dialogic products. This document discusses one or more open source
products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic
products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such
usage might have, including without limitation effects on your products, your business, or your intellectual property rights.
Publication Date: October 2009
Document Number: U14SSS, Issue 13
MAP Programmer's Manual Issue 13
3
REVISION HISTORY
ISSUE DATE CHANGES
1 03-Oct-97 Initial Text
2 19-Mar-98 Support for SMS services conforming to the MAP Phase 1 specifications.
3 27-Oct-99 Support for MAP-SEND-ROUTING-INFO.
4 08-Mar-00 Support for MAP-UNSTRUCTURED-SS-REQUEST, MAP-UNSTRUCTURED-SS-
NOTIFY AND MAP-PROCESS-UNSTRUCTURED-SS-REQUEST.
5 22-Aug-00 Support for MAP-ANYTIME-INTERROGATION, MAP-PROVIDE-SUBSCRIBER-
INFO, and MAP-SEND-IMSI.
6 22-May-01 Support for MAP-SEND-INFO-FOR-GPRS.
7 11-Jul-03 Support for MAP V3.
8 27-Feb-04 Support for MAP-UPDATE-GPRS-LOCATION and MAP-SEND-ROUTING-INFO-
FOR-LCS.
9 17-Jun-05 Support for MAP-CHECK-IMEI, MAP-PROVIDE-SUBSCRIBER-LOCATION, MAP-
SUBSCRIBER-LOCATION-REPORT, MAP-ACTIVATE-SS, MAP-DEACTIVATE-SS,
MAP-REGISTER-SS, MAP-ERASE-SS, MAP-GET-PASSWORD, MAP-REGISTER-
PASSWORD, MAP-ANYTIME-SUBSCRIPTION-INTERROGATION, MAP-RESUME-
CALL-HANDLING and MAP-RESTORE-DATA
Minor changes to existing operations.
10 25-Feb-08 Added new messages Network Context Configuration Request and Read
Module Status,
V3 Support for MAP-SEND-AUTHENTICATION-INFO operation.
New status in confirmation messages and new Software error indications
Support for MAP-SEND-PARAMETERS, MAP-ACTIVATE-TRACE-MODE, MAP-
DEACTIVE-TRACE-MODE and MAP-TRACE-SUBSCRIBER-ACTIVITY operations.
Minor changes to existing operations.
Updated document for MAP-FAILURE-REPORT, MAP-FORWARD-CHECK-SS-
INDICATION, MAP-NOTE-MS-PRESENT-FOR-GPRS and MAP-PURGE-MS
operations.
11 30-Sep-08 Updates to trace mask definitions
Support for MAP Handover Services MAP-PREPARE-HANDOVER, MAP-
PREPARE-SUBSEQUENT-HANDOVER- MAP-PROCESS-ACCESS-SIGNALLING,
MAP-FORWARD-ACCESS-SIGNALLING and MAP-AUTHENTICATE-FAILURE-
REPORT
V3 Support for CHECK IMEI operation
Added Application Context Negotiation documentation
12 13-Jul-09 Support for SEND-AUTHENTICATION-INFO, ANY-TIME-MODIFICATION,
RESET, SET-REPORTING-STATE, STATUS-REPORT, REMOTE-USER-FREE,
REGISTER-CC-ENTRY and ERASE-CC-ENTRY services.
Added parameters to ANY-TIME-INTERROGATION-ACK, PROVIDE-
SUBSCRIBER-INFO-ACK and SEND-ROUTING-INFO-ACK.
Additional Configuration Trace information.
13 19-Oct-09 Support for INTERROGATE-SS service under MAP v1.
Section 1 Introduction
4
CONTENTS
1 INTRODUCTION .................................................................................................................................. 5
1.1 Abbreviations ..................................................................................................................................... 5
1.2 Related Documentation ..................................................................................................................... 5
2 GENERAL DESCRIPTION ................................................................................................................... 6
2.1 Feature Overview .............................................................................................................................. 6
2.2 Module Overview ............................................................................................................................... 6
2.3 Module Configuration ........................................................................................................................ 7
2.4 Dialogue ID assignment .................................................................................................................... 7
2.5 Application Context ............................................................................................................................ 7
2.6 Application Context negotiation ......................................................................................................... 8
2.7 Invoke ID ............................................................................................................................................ 8
2.8 Operation timeout .............................................................................................................................. 8
2.9 Constant definitions ........................................................................................................................... 8
2.10 Module Dimensions ......................................................................................................................... 8
3 INTERFACE TO TCAP ....................................................................................................................... 10
3.1 Dialogue handling ............................................................................................................................ 10
3.2 Component handling ....................................................................................................................... 10
4 INTERFACE TO MAP-USER ............................................................................................................. 11
4.1 Introduction ...................................................................................................................................... 11
4.2 Primitive parameters ........................................................................................................................ 12
4.3 Dialogue Primitive Types ................................................................................................................. 12
4.4 Service Primitive Types ................................................................................................................... 13
4.5 MAP Dialogue Request ................................................................................................................... 23
4.6 MAP Dialogue Indication ................................................................................................................. 25
4.7 MAP Dialogue Primitive Parameters ............................................................................................... 27
4.8 MAP Service Request ..................................................................................................................... 32
4.9 MAP Service Indication ................................................................................................................... 96
4.10 MAP Service Primitive Parameters ............................................................................................... 97
5 NON-PRIMITIVE INTERFACE ......................................................................................................... 169
5.1 MAP Configuration Request .......................................................................................................... 170
5.2 MAP Network Context Configuration Request .............................................................................. 174
5.3 MAP Timer Configuration Request ................................................................................................ 176
5.4 MAP Software Event Indication ..................................................................................................... 177
5.5 Management Event Indication ....................................................................................................... 181
5.6 MAP Trace Mask Request ............................................................................................................. 182
5.7 Set Selective Trace Mask Request ............................................................................................... 186
5.8 Trace Event Indication ................................................................................................................... 187
5.9 Selective Trace Event Indication ................................................................................................... 188
5.10 MAP Software Event Mask Request ........................................................................................... 190
5.11 Read Revision Request ............................................................................................................... 191
5.12 Read Module Status Request ...................................................................................................... 192
5.13 Read Dialogue Status Request ................................................................................................... 194
MAP Programmer's Manual Issue 13
5
1 Introduction
The Dialogic® DSI MAP Layer, a member of the Dialogic® DSI SS7 Protocol Stack, is a software
implementation of the GSM Mobile Application Part (MAP). The DSI Map Layer ("MAP module")
implements the “MAP Provider” parts of MAP as specified in GSM TS 09.02 and TS 29.002.
The MAP module uses the services provided by the underlying Transaction Capabilities (TCAP)
service for the transfer of operations between peer MAP entities. It provides services to “MAP
User” applications while remaining independent of both the TCAP layer and the MAP User
application.
This Programmer’s Manual is intended for users who choose to develop their own applications that
interface to and make use of the functionality provided by the MAP module.
The MAP module is an event driven task that uses standard structured message types for
communication with other layers of the protocol stack. These messages are used to convey the
protocol primitives between MAP and the MAP User application and MAP and TCAP. Each
message contains the primitive parameters as defined in the ETSI & ITU-T recommendations such
that the module can easily be interfaced to other vendor implementations of adjacent layers.
Typically, the MAP module is used in conjunction with the Dialogic® DSI TCAP Layer (“TCAP
module”).
This manual provides an overview of the internal operation of the MAP module and defines the
structure of the messages used to interface to the MAP module.
1.1 Abbreviations
ANSI American National Standards Institute
APDU Application Protocol Data Unit
CCITT The International Telegraph & Telephone Consultative Committee
GPRS General Packet Radio Service
ITU-T International Telecommunication Union (formerly CCITT)
MAP Mobile Application Part
MTP Message Transfer Part
SCCP Signaling Connection Control Part
SMS Short message service
TCAP Transaction Capabilities Application Part
USSD Unstructured Supplementary Service Data
1.2 Related Documentation
[1] ETSI ETS 300 599 – Mobile Application Part (MAP) Specification (GSM 09.02)
[2] ETSI ETS 300 974 – Mobile Application Part (MAP) Specification (GSM 09.02)
[3] ETSI TS 100 974 – Mobile Application Part (MAP) Specification (GSM 09.02)
[4] Mobile Application Part (MAP) Specification (TS 29.002)
[5] ITU-T recommendations Q.771 – Q.775 (TCAP)
[6] ITU-T recommendations Q.711 – Q.714 (SCCP)
[7] U06SSS, Dialogic® DSI TCAP Programmer’s Manual
[8] U10SSS, Dialogic® DSI Software Environment Programmer’s Manual
Section 2 General Description
6
2 General Description
2.1 Feature Overview
Key features of the Dialogic® DSI MAP Layer include:
- Implementation of Common MAP Services dialogue control functionality
- Implementation of a number of MAP services, including Short Message Service (SMS),
Unstructured Supplementary Service Data (USSD), Supplementary Services, Location Service
Management Services, IMEI Management Services and Any Time Information Handling
Services
- Error handling for supported services
- Class 1, 2, 3, and 4 operations
- Dialogue support for application context, user information and components.
- Message-oriented interface
2.2 Module Overview
The MAP module is an implementation of the MAP Service-provider block specified in GSM 09.02
(ETS 300 599 and ETS 300 974) and TS 29.002. The MAP module provides an implementation of
the MAP Service-provider block - common MAP services which permit control of dialogues with
peer MAP entities. The MAP module also provides an implementation of a number of the MAP
Service-provider block services, including those required for SMS and USSD. See Appendix C for
a list of MAP services supported.
The functions of the MAP service-user block specified GSM 09.02 form part of the user’s
application and are not implemented here.
MAP Service-provider block Common MAP Services: The MAP module implements the Common
Services of the MAP protocol. These services permit handling of dialogues between MAP User
entities. Whenever a MAP User wishes to request a service of a remote peer the MAP User must
first establish a dialogue with the peer. Subsequent service requests and responses (MAP Protocol
Data Units) exchanged with the peer are transferred via this dialogue. The MAP Provider Block
Common Services allow the MAP User to open (MAP-OPEN), close (MAP-CLOSE) and abort
(MAP-U-ABORT) dialogues with the remote peer. They also permit the MAP module to report
problems (MAP-NOTICE) and permit the MAP user to explicitly request the transfer (MAP-
DELIMITER) of any MAP Protocol Data Units.
MAP Service-provider block User Specific Services: The MAP User is provided with a primitive
interface by which the MAP User may request and receive services from the remote peer.
The MAP module is event driven. It has a single input queue into which events from other modules
(Dialogic® DSI TCAP Layer ("TCAP module"), MAP-User, management etc.) are written. The MAP
module processes each event in turn until the input queue is empty, in which case it will do nothing
until the next event is received. Output from the MAP module is directed depending on the type of
event to either the TCAP module, the MAP-User module, the Management module, or the
Maintenance module
The MAP module requires a periodic timer tick notification to be issued to it via the input queue
every tenth of a second. This is generated by the timer module for the selected operating system.
The format of timer related messages is described in Appendix A -.Timer services.
In addition to the primitive interface and the management interface to the TCAP module (which are
described in later sections), the MAP module requires a few basic system services to be supplied
by the underlying operating system. These include the ability to allocate, send, receive and release
messages. This functionality is described in the Software Environment Programmer’s Manual.
MAP Programmer's Manual Issue 13
7
2.3 Module Configuration
The MAP module provides flexibility by allowing a number of user configuration options to be set
up at run time. This allows users to customize the operation of the MAP module to suit the
requirements of the final application. Configuration parameters are sent to the MAP module’s input
event queue in the same manner as MAP protocol messages.
The first message sent to the MAP module must be the global configuration message. Any
messages received prior to the global configuration message will be discarded. The global
configuration message specifies the module id for the modules to which MAP issues messages. It
also supplies values for the maximum number of dialogues (incoming and outgoing), base values
for the incoming and outgoing ranges of dialogue ids available to MAP-User and TCAP and the
maximum number of active invocations that are required. The MAP module checks that the values
requested are compatible with the internal dimensions it has been built with.
The MAP module may also be sent a timer configuration message. The time for which the MAP
module will wait for a MAP-User response may be supplied as a message parameter. The
message may also be sent without parameters in order to use a default value.
2.4 Dialogue ID assignment
The MAP module may support a number of active dialogues at a time. MAP-User primitives are
associated with a particular dialogue using a Dialogue ID.
The Dialogue ID is assigned when the opening primitive is exchanged between the MAP-User and
MAP. For a dialogue initiated by the MAP-User (an ‘outgoing dialogue’), the value is selected by
the MAP-User. For a dialogue initiated by a remote MAP-User peer (an ‘incoming dialogue’), the
value is selected by the MAP module. Once a dialogue has started, all user primitives that refer to
this dialogue must include its Dialogue ID value.
The dialogue ID is a 16-bit value. Separate ranges of values must be used for outgoing and
incoming dialogues. The global configuration message sent to the module on initialization specifies
the range of IDs available to MAP for incoming dialogues, as well as the range of IDs available to
the MAP User for outgoing dialogues.
The Dialogue ID is of purely local significance between the MAP-User and MAP.
Maximum values for the number of incoming and outgoing dialogues that the MAP module can
support are set up at configuration time. These values are then fixed for both TCAP and MAP-User
interfaces.
The dialogue ID selected by the MAP-User for an outgoing dialogue must lie within the configured
range of outgoing dialogue IDs. Dialogue IDs for incoming dialogues are allocated automatically by
the MAP module (from the configured range of incoming dialogue IDs) so that the dialogue ID that
has been unused for the longest period is used next. It is important that MAP and the MAP User
use separate ranges of IDs so that is not possible for the MAP-User to select an ID for an outgoing
dialogue at the same time that MAP selects the same ID for use with an incoming dialogue.
Dialogue ID values also exist on the MAP–TCAP interface, but the MAP-User is not generally
concerned with these. However, both MAP and TCAP must be configured to use separate ranges
of values for incoming and outgoing dialogue IDs on this interface. The Dialogue IDs used on this
interface are of purely local significance to MAP and TCAP.
2.5 Application Context
When the MAP-User requests the establishment of a dialogue with a peer, the MAP-User must
provide the application context for that dialogue. The application context identifies the mobile
network entities (HLR, GMSC etc.) at which the MAP peers reside and the services that may be
requested.
Section 2 General Description
8
The use of application context is mandatory under the MAP GSM 09.02 Phase 2 specifications.
The use of application context is not specified under the MAP GSM 09.02 Phase 1 specifications
but is required by the MAP module to identify those dialogues for which the MAP User requires
MAP Phase 1 compatible messaging. The MAP User should supply the version 1 contexts
specified in MAP GSM 09.02 Phase 2 to obtain MAP Phase 1 compatible messaging.
2.6 Application Context negotiation
Application context version negotiation may now be performed by the user. This is necessary for
dialogues to be successful when the application supports an older version than the MAP module
for a particular application context.
If, for example, a V3 application context is received for a dialogue but the highest version that the
application supports is V2, application context negotiation may be performed by setting the Refuse
reason parameter in the MAP-OPEN-RSP to “application context not supported” and also including
the preferred application context.
2.7 Invoke ID
When the MAP-User has established a dialogue with a peer, it may request a service from the
remote peer by sending a specific service request primitive to the MAP module.
Requests for service from the remote peer are sent to the MAP-User in a specific service indication
primitive. This may require the MAP-User to respond with a specific service response primitive,
which the peer MAP-User will receive as a specific service confirmation primitive.
Each request for service is termed an invocation of the service. Each primitive associated with a
particular invocation of a service must carry the invoke ID of that invocation. The invoke ID is
supplied by the MAP-User and must be unique for each outgoing service invocation on the
dialogue. Each incoming service invocation will also have a unique invoke ID – in this case the ID
is supplied by the remote peer.
2.8 Operation timeout
The timer value to be used when waiting for a response to an operation may be specified by
including a parameter in the service request primitive. If the parameter is not included, a default
value is used.
2.9 Constant definitions
To assist the user who chooses to write an application, a ‘C’ language header file (map_inc.h) is
available containing all the definitions and constants necessary to interface with the MAP module.
This file contains definitions for all the mnemonics (e.g. primitives and primitive parameters) listed
in this Programmer’s Manual.
2.10 Module Dimensions
Internally, there are a number of data structures used by the MAP module.
The maximum dimensions of these structures are determined by compile time constants. The two
constants of importance to the user are:
a) The maximum number of simultaneous dialogues supported by the MAP module.
b) The maximum number of simultaneous invocations supported by the MAP module.
MAP Programmer's Manual Issue 13
9
Host-based
(Linux,
Windows®,
Solaris)
SS7G31
SS7G32
SS7HDP
SS7HDC
Maximum
number of
dialogues
supported
65535 65535 0, 8192 or
32768
(depending on
run-time
license)
Maximum
number of
invokes
supported
65535 65535 0, 8192 or
32768
(depending on
run-time
license)
Section 3 Interface to TCAP
10
3 Interface to TCAP
The Dialogic® DSI Map Layer ("MAP module") is usually used in conjunction with the DSI TCAP
Layer ("TCAP module"). However, the use of primitives in accordance with Q.771 ensures that it
can also be integrated with other Transaction Capabilities implementations if required.
The MAP module communicates with the TCAP module using the following primitives, all of which
are defined in CCITT Recommendation Q.771:
3.1 Dialogue handling
UNI-REQ UNI-IND
BEGIN-REQ BEGIN-IND
CONTINUE-REQ CONTINUE-IND
END-REQ END-IND
U-ABORT-REQ U-ABORT-IND
P-ABORT-IND
NOTICE-IND
The message format used to convey these primitives is defined in the Dialogic® DSI TCAP
Programmer’s Manual. The following messages are used:
TCP_MSG_DLG_REQ Messages issued by MAP
TCP_MSG_DLG_IND Messages issued to MAP
3.2 Component handling
NULL-IND
INVOKE-REQ INVOKE-IND
RESULT-L-REQ RESULT-L-IND
RESULT-NL-REQ RESULT-NL-IND
U-ERROR-REQ U-ERROR-IND
U-CANCEL-REQ L-CANCEL-IND
U-REJECT-REQ L-REJECT-IND
R-REJECT-IND
U-REJECT-IND
The message format used to convey these primitives is defined in the Dialogic® DSI TCAP
Programmer’s Manual. The following messages are used:
TCP_MSG_CPT_REQ Messages issued by MAP
TCP_MSG_CPT_IND Messages issued to MAP
MAP Programmer's Manual Issue 13
11
4 Interface to MAP-User
4.1 Introduction
All primitives at the MAP-User MAP-Provider interface are passed by sending messages between
the MAP-User and MAP modules.
Request and Response primitives are sent by the MAP-User. These request MAP to control
dialogues and issue MAP service requests.
Indication and Confirmation primitives are sent by MAP to indicate received MAP dialogue events
and MAP service events to the MAP-User.
The following messages are used:
MAP-DIALOGUE-REQ Transfers dialogue request primitives and dialogue response primitives
from MAP-User to MAP.
MAP-DIALOGUE-IND Transfers dialogue indication primitives and dialogue confirmation
primitives from MAP to MAP-User.
MAP-SERVICE-REQ Transfers service request primitives and service response primitives
from MAP-User to MAP.
MAP-SERVICE-IND Transfers service indication primitives and service confirmation
primitives from MAP to MAP-User.
The basic structure of each message (irrespective of the MAP primitive contained within it) is the
same and is described in the ‘Software Environment Programmer’s Manual’.
The message must be contained in a single buffer, which should be allocated by the sending
module (using the getm function) and either released (using the relm function) or passed to
another module by the receiving module. The getm and relm functions are described in the
‘Software Environment Programmer’s Manual’.
The message header contains a ‘type’, the value of which indicates the primitive that is being
conveyed by the message. The following message types have been defined:
Primitive Message type Value
MAP-SERVICE-REQ MAP_MSG_SRV_REQ 0xc7e0
MAP-SERVICE-IND MAP_MSG_SRV_IND 0x87e1
MAP-DIALOGUE-REQ MAP_MSG_DLG_REQ 0xc7e2
MAP-DIALOGUE-IND MAP_MSG_DLG_IND 0x87e3
Section 4 Interface to MAP-User
12
4.2 Primitive parameters
Each MAP-User primitive includes a number of parameters. These parameters are conveyed in the
parameter area of the message that conveys the primitive.
The first byte in the parameter area is the primitive type octet and the last byte is a zero byte to
indicate that there are no further parameters in the parameter area. Parameters associated with
the message are placed between the message type code and the final (zero) byte. Therefore the
parameter area is formatted as follows:
Primitive
Type Parameter Parameter Parameter Zero
Within each message there are mandatory parameters, which must always be present, and
optional parameters, which may or may not be present. The parameters may be placed in any
order. The encoding of the MAP parameter data aligns with the parameter format specified in the
appropriate ETSI recommendation whenever possible. Therefore, each parameter is formatted as
follows:
1. For MAP parameters whose value is less than 240 (0xf0), the first byte of a parameter is
the parameter name, the second byte is the length of the parameter data to follow
(excluding the parameter name and the length byte itself), this is followed by the parameter
data as shown below:
Name Length Data
1 byte 1 byte ‘Parameter length’ bytes (0 to 255)
2. MAP parameter 240 is used for the extension as described in the next paragraph.
Parameters 241 till 255 are reserved for future use.
3. For MAP parameters whose value is greater than 255 (0xff), the first byte is 240 (0xf0), the
second byte is the length of the entire parameter; this length is defined by 3 (for the
parameter name and the length byte) + the length of the MAP parameter to follow
(excluding the parameter name and the length byte itself).The data area contains the
name, length and data of the actual MAP parameter as shown below.
Name
(0xf0) Length + 3 Data
‘Parameter’ Name ‘Parameter’
Length ‘Parameter’ Data
1 byte 1 byte 2 bytes 1 byte ‘Parameter length’ bytes (0
to 255)
4.3 Dialogue Primitive Types
Dialogue-handling primitives provide the mechanism by which service requests etc. may be
exchanged with peer MAP-User entities.
Dialogue primitives sent by the MAP-User to MAP. These convey a dialogue request or response:
MAP Programmer's Manual Issue 13
13
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-OPEN-REQ MAPDT_OPEN_REQ 1 0x01
MAP-CLOSE-REQ MAPDT_CLOSE_REQ 3 0x03
MAP-DELIMITER-REQ MAPDT_DELIMITER_REQ 5 0x05
MAP-U-ABORT-REQ MAPDT_U_ABORT_REQ 7 0x07
MAP-OPEN-RSP MAPDT_OPEN_RSP 129 0x81
Dialogue primitives sent by the MAP to MAP-User. These convey a dialogue indication or
confirmation:
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-OPEN-IND MAPDT_OPEN_IND 2 0x02
MAP-CLOSE-IND MAPDT_CLOSE_IND 4 0x04
MAP-DELIMITER-IND MAPDT_DELIMITER_IND 6 0x06
MAP-U-ABORT-IND MAPDT_U_ABORT_IND 8 0x08
MAP-OPEN-CNF MAPDT_OPEN_CNF 130 0x82
MAP-P-ABORT-IND MAPDT_P_ABORT_IND 9 0x09
MAP-NOTICE-IND MAPDT_NOTICE_IND 10 0x0a
The following sections define the message format and content of the parameter area for each of
the messages exchanged between the MAP-User and MAP.
4.4 Service Primitive Types
Once a dialogue is established between two MAP peers, they may request services from each
other.
Only services belonging to the application context that was specified at the establishment of the
dialogue may be requested.
A service type primitive code must be passed in the message to indicate the type of service being
defined. Two methods are defined for passing this code –
1. The single octet Service Type code is passed as the first octet of the message.
2. The single or double octet Service Type Code is passed in a parameter
‘MAPPN_SERVICE_TYPE’ and the first octet of the message is set to
‘MAPST_EXTENDED_SERVICE_TYPE’.
The first method is only possible for services were the Service Type code can be defined in a
single octet (see following tables). The second method is always possible and can be used with
single or double octet Service Type codes. The MAP User can choose to use either method,
except for services where the Service Type code requires two octets, where the second method
must be used.
Section 4 Interface to MAP-User
14
When the MAP module returns service messages to the MAP User, it will normally use first method
when the Service Type can be defined in a single octet and the second method (using
MAPST_EXTENDED_SERVICE_TYPE), where a double octet Service Type is required. A
configuration option (MAPF_USE_TYPE_PARMS) is provided to force the module to use the
second method for all Service messages sent to the MAP User.
The following table details service primitives sent by the MAP-User to MAP. These convey a
request to perform a service, or a response to a service request from the peer entity.
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-ACTIVATE-SS-REQ MAPST_ACTIVATE_SS_REQ 75 0x4b
MAP-ACTIVATE-SS-RSP MAPST_ACTIVATE_SS_RSP 197 0xc5
MAP-ACTIVATE-TRACE-MODE-REQ MAPST_ACTIV_TRACE_MODE_REQ 45 0x2d
MAP-ACTIVATE-TRACE-MODE-RSP MAPST_ACTIV_TRACE_MODE_RSP 167 0xa7
MAP-ALERT-SC-WITHOUT-RESULT-
REQ MAPST_ALERT_SC_WO_RESULT_REQ 17 0x11
MAP-ALERT-SERVICE-CENTRE-REQ MAPST_ALERT_SC_REQ 9 0x09
MAP-ALERT-SERVICE-CENTRE-RSP MAPST_ALERT_SC_RSP 137 0x89
MAP-ANYTIME-INTERROGATION-REQ MAPST_ANYTIME_INT_REQ 29 0x1d
MAP-ANYTIME-INTERROGATION-RSP MAPST_ANYTIME_INT_RSP 151 0x97
MAP-ANYTIME-MODIFICATION-REQ MAPST_ANYTIME_MOD_REQ 115 0x73
MAP-ANYTIME-MODIFICATION-RSP MAPST_ANYTIME_MOD_RSP 231 0xe7
MAP-ANYTIME-SUBSCRIPTION-
INTERROGATION-REQ MAPST_ATSI_REQ 81 0x51
MAP-ANYTIME-SUBSCRIPTION-
INTERROGATION-RSP MAPST_ATSI_RSP 203 0xcb
MAP-AUTHENTICATION-FAILURE-
REPORT-REQ MAPST_AUTHFAILREPORT_REQ 111 0x6f
MAP-AUTHENTICATION-FAILURE-
REPORT-RSP MAPST_AUTHFAILREPORT_RSP 227 0xe3
MAP-CANCEL-LOCATION-REQ MAPST_CANCEL_LOCATION_REQ 41 0x29
MAP-CANCEL-LOCATION-RSP MAPST_CANCEL_LOCATION_RSP 163 0xa3
MAP-CHECK-IMEI-REQ MAPST_CHECK_IMEI_REQ 79 0x4f
MAP-CHECK-IMEI-RSP MAPST_CHECK_IMEI_REQ 201 0xc9
MAP-DEACTIVATE-SS-REQ MAPST_DEACTIVATE_SS_REQ 77 0x4d
MAP-DEACTIVATE-SS-RSP MAPST_DEACTIVATE_SS_RSP 199 0xc7
MAP Programmer's Manual Issue 13
15
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-DEACTIVATE-TRACE-MODE-REQ MAPST_DEACTIV_TRACE_MODE_REQ 97 0x61
MAP-DEACTIVATE-TRACE-MODE-RSP MAPST_DEACTIV_TRACE_MODE_RSP 219 0xdb
MAP-DELETE-SUBSCRIBER-DATA-
REQ MAPST_DEL_SUBS_DATA_REQ 49 0x31
MAP-DELETE-SUBSCRIBER-DATA-
RSP MAPST_DEL_SUBS_DATA_RSP 171 0xab
MAP-ERASE-CC-ENTRY-REQ MAPST_ERASE_CC_ENTRY_REQ 532 0x0214
MAP-ERASE-CC-ENTRY-RSP MAPST_ERASE_CC_ENTRY_RSP 533 0x0215
MAP-ERASE-SS-REQ MAPST_ERASE_SS_REQ 83 0x53
MAP-ERASE-SS-RSP MAPST_ERASE_SS_RSP 205 0xcd
MAP-EXTENDED-SERVICE-TYPE MAPST_EXTENDED_SERVICE_TYPE 255 0xff
MAP-FAILURE-REPORT-REQ MAPST_FAIL_REPORT_REQ 53 0x35
MAP-FAILURE-REPORT-RSP MAPST_FAIL_REPORT_RSP 175 0xaf
MAP-FORWARD-ACCESS-
SIGNALLING-REQ MAPST_FWDACCESS_SIG_REQ 101 0x65
MAP-FORWARD-CHECK-SS-
INDICATION-REQ MAPST_FWD_CHK_SS_INDICAT_REQ 67 0x43
MAP-FORWARD-SHORT-MESSAGE-
REQ (versions 1 and 2) MAPST_FWD_SM_REQ 3 0x03
MAP-FORWARD-SHORT-MESSAGE-
RSP (versions 1 and 2) MAPST_FWD_SM_RSP 131 0x83
MAP-GET-PASSWORD-REQ MAPST_GET_PASSWORD_REQ 89 0x59
MAP-GET-PASSWORD-RSP MAPST_GET_PASSWORD_RSP 211 0xd3
MAP-INFORM-SERVICE-CENTRE-REQ MAPST_INF_SC_REQ 11 0x0b
MAP-INSERT-SUBSCRIBER-DATA-REQ MAPST_INS_SUBS_DATA_REQ 43 0x2b
MAP-INSERT-SUBSCRIBER-DATA-RSP MAPST_INS_SUBS_DATA_RSP 165 0xa5
MAP-INTERROGATE-SS-REQ MAPST_INTERROGATE_SS_REQ
73 0x49
MAP-INTERROGATE-SS-RSP MAPST_INTERROGATE_SS_RSP
195 0xc3
MAP-MO-FORWARD-SHORT-
MESSAGE-REQ (version 3 onwards) MAPST_MO_FWD_SM_REQ 3 0x03
MAP-MO-FORWARD-SHORT-
MESSAGE-RSP (version 3 onwards) MAPST_MO_FWD_SM_RSP 131 0x83
MAP-MT-FORWARD-SHORT-
MESSAGE-REQ (version 3 onwards) MAPST_MT_FWD_SM_REQ 69 0x45
MAP-MT-FORWARD-SHORT-
MESSAGE-RSP (version 3 onwards) MAPST_MT_FWD_SM_RSP 191 0xbf
MAP-NOTEMM-EVENT-REQ MAPST_NOTE_MM_EVENT_REQ 65 0x41
MAP-NOTEMM-EVENT-RSP MAPST_NOTE_MM_EVENT_RSP 187 0xbb
MAP-NOTE-MS-PRESENT-GPRS-REQ MAPST_NOTE_MS_PRES_GPRS_REQ 51 0x33
MAP-NOTE-MS-PRESENT-GPRS-RSP MAPST_NOTE_MS_PRES_GPRS_RSP 173 0xad
MAP-NOTE-SUBSCRIBER-PRESENT-
REQ MAPST_NOTE_SUB_PRESENT_REQ 19 0x13
Section 4 Interface to MAP-User
16
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-PREPARE-HANDOVER-REQ MAPST_PREPAREHO_REQ 103 0x67
MAP-PREPARE-HANDOVER-RSP MAPST_PREPAREHO_RSP 221 0xdd
MAP-PREPARE-SUBSEQUENT-
HANDOVER-REQ MAPST_PREPARESUBHO_REQ 105 0x69
MAP-PREPARE-SUBSEQUENT-
HANDOVER-RSP MAPST_PREPARESUBHO_RSP 223 0xdf
MAP-PROCESS-ACCESS-SIGNALLING-
REQ MAPST_PROACCESS_SIG_REQ 107 0x11
MAP-PROCESS-UNSTRUCTURED-SS-
REQUEST-REQ MAPST_PRO_UNSTR_SS_REQ_REQ 27 0x1b
MAP-PROCESS-UNSTRUCTURED-SS-
REQUEST-RSP MAPST_PRO_UNSTR_SS_REQ_RSP 149 0x95
MAP-PROVIDE-ROAMING-NUMBER-
REQ MAPST_PROV_ROAM_NUM_REQ 37 0x25
MAP-PROVIDE-ROAMING-NUMBER-
RSP MAPST_PROV_ROAM_NUM_RSP 159 0x9f
MAP-PROVIDE-SUBSCRIBER-INFO –
RSP MAPST_PROV_SUB_INFO_RSP 153 0x99
MAP-PROVIDE-SUBSCRIBER-INFO-
REQ MAPST_PROV_SUB_INFO_REQ 31 0x1f
MAP-PROVIDE-SUBSCRIBER-
LOCATION-REQ MAPST_PROVIDE_SUBS_LOC_REQ 61 0x3d
MAP-PROVIDE-SUBSCRIBER-
LOCATION-RSP MAPST_PROVIDE_SUBS_LOC_RSP 183 0xb7
MAP-PURGE-MSUBSCRIBER-DATA-
REQ MAPST_PURGE_MS_REQ 57 0x39
MAP-PURGE-MSUBSCRIBER-DATA-
RSP MAPST_PURGE_MS_RSP 179 0xb3
MAP-READY-FOR-SM-REQ MAPST_RDY_FOR_SM_REQ 7 0x07
MAP-READY-FOR-SM-RSP MAPST_RDY_FOR_SM_RSP 135 0x87
MAP-REGISTER-CC-ENTRY-REQ MAPST_REGISTER_CC_ENTRY_REQ 528 0x0210
MAP-REGISTER-CC-ENTRY-RSP MAPST_REGISTER_CC_ENTRY_RSP 529 0x0211
MAP-REGISTER-PASSWORD-REQ MAPST_REGISTER_PASSWORD_REQ 91 0x5b
MAP-REGISTER-PASSWORD-RSP MAPST_REGISTER_PASSWORD_RSP 213 0xd5
MAP-REGISTER-SS-REQ MAPST_REGISTER_SS_REQ 85 0x55
MAP-REGISTER-SS-RSP MAPST_REGISTER_SS_RSP 207 0xcf
MAP-REMOTE-USER-FREE-REQ MAPST_REMOTE_USER_FREE_REQ 524 0x020c
MAP-REMOTE-USER-FREE-RSP MAPST_REMOTE_USER_FREE_RSP 525 0x020d
MAP-REPORT-SM-DELIVERY-STATUS-
REQ MAPST_RPT_SMDST_REQ 5 0x05
MAP-REPORT-SM-DELIVERY-STATUS-
RSP MAPST_RPT_SMDST_RSP 133 0x85
MAP-RESET-REQ MAPST_RESET_REQ 512 0x0200
MAP-RESTORE-DATA-REQ MAPST_RESTORE-DATA_REQ 93 0x5d
MAP-RESTORE-DATA-RSP MAPST_RESTORE-DATA_RSP 215 0xd7
MAP Programmer's Manual Issue 13
17
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-RESUME-CALL-HANDLING-REQ MAPST_RES_CALL_REQ 87 0x57
MAP-RESUME-CALL-HANDLING-RSP MAPST_RES_CALL_RSP 209 0xd1
MAP-SEND-AUTHENTICATION-INFO-
REQ MAPST_SEND_AUTH_INFO_REQ 71 0x47
MAP-SEND-AUTHENTICATION-INFO-
RSP MAPST_SEND_AUTH_INFO_RSP 193 0xc1
MAP-SEND-END-SIGNAL-REQ MAPST_SEND_ENDSIG_REQ 109 0x6d
MAP-SEND-ENG-SIGNAL-RSP MAPST_SEND_ENDSIG_RSP 225 0xe1
MAP-SEND-IDENTIFICATION-REQ MAPST_SEND_IDENT_REQ 47 0x2f
MAP-SEND-IDENTIFICATION-RSP MAPST_SEND_IDENT_RSP 169 0xa9
MAP-SEND-IMSI-REQ MAPST_SEND_IMSI_REQ 33 0x21
MAP-SEND-IMSI-RSP MAPST_SEND_IMSI_RSP 155 0x9b
MAP-SEND-PARAMETERS-REQ MAPST_SEND_PARAMETERS_REQ 95 0x5f
MAP-SEND-PARAMETERS-RSP MAPST_SEND_PARAMETERS_RSP 217 0xd9
MAP-SEND-ROUTING-INFO-FOR-
GPRS-REQ MAPST_SND_RTIGPRS_REQ 35 0x23
MAP-SEND-ROUTING-INFO-FOR-
GPRS-RSP MAPST_SND_RTIGPRS_REQ 157 0x9d
MAP-SEND-ROUTING-INFO-FOR-LCS-
REQ MAPST_ROUT_INFO_LCS_REQ 59 0x3b
MAP-SEND-ROUTING-INFO-FOR-LCS-
RSP MAPST_ROUT_INFO_LCS_RSP 181 0xb5
MAP-SEND-ROUTING-INFO-FOR-SM-
REQ MAPST_SND_RTISM_REQ 1 0x01
MAP-SEND-ROUTING-INFO-FOR-SM-
RSP MAPST_SND_RTISM_RSP 129 0x81
MAP-SEND-ROUTING-INFO-REQ MAPST_SEND_ROUTING_INFO_REQ 21 0x15
MAP-SEND-ROUTING-INFO-RSP MAPST_SEND_ROUTING_INFO_RSP 143 0x8f
MAP-SET-REPORTING-STATE-REQ MAPST_SET_REPORTING_STATE_REQ 516 0x0204
MAP-SET-REPORTING-STATE-RSP MAPST_SET_REPORTING_STATE_RSP 517 0x0205
MAP-STATUS-REPORT-REQ MAPST_STATUS_REPORT_REQ 520 0x0208
MAP-STATUS-REPORT-RSP MAPST_STATUS_REPORT_RSP 521 0x0209
MAP-SUBSCRIBER-LOCATION-
REPORT-REQ MAPST_SUBS_LOC_REPORT_REQ 63 0x3f
MAP-SUBSCRIBER-LOCATION-
REPORT-RSP MAPST_SUBS_LOC_REPORT_RSP 185 0xb9
MAP-TRACE-SUBSCRIBER-ACTIVITY-
REQ MAPST_TRACE_SUB_ACTIV_REQ 99 0x63
MAP-UNSTRUCTURED-SS-NOTIFY-
REQ MAPST_UNSTR_SS_NOTIFY_REQ 25 0x19
MAP-UNSTRUCTURED-SS-NOTIFY-
RSP MAPST_UNSTR_SS_NOTIFY_RSP 147 0x93
MAP-UNSTRUCTURED-SS-REQUEST-
REQ MAPST_UNSTR_SS_REQ_REQ 23 0x17
MAP-UNSTRUCTURED-SS-REQUEST-
RSP MAPST_UNSTR_SS_REQ_RSP 145 0x91
Section 4 Interface to MAP-User
18
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-UPDATE-GPRS-LOCATION-REQ MAPST_UPDATE_GPRS_LOC_REQ 55 0x37
MAP-UPDATE-GPRS-LOCATION-RSP MAPST_UPDATE_GPRS_LOC_RSP 177 0xb1
MAP-UPDATE-LOCATION-REQ MAPST_UPDATE_LOCATION_REQ 39 0x27
MAP-UPDATE-LOCATION-RSP MAPST_UPDATE_LOCATION_RSP 161 0xa1
The following table details service primitives received by the MAP-User from MAP. These convey a
service indication, or a confirmation to a service request from the peer entity:
MAP Programmer's Manual Issue 13
19
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-ACTIVATE-SS-CNF MAPST_ACTIVATE_SS_CNF 198 0xc6
MAP-ACTIVATE-SS-IND MAPST_ACTIVATE_SS_IND 76 0x4c
MAP-ACTIVATE-TRACE-MODE-CNF MAPST_ACTIV_TRACE_MODE_CNF 168 0xa8
MAP-ACTIVATE-TRACE-MODE-IND MAPST_ACTIV_TRACE_MODE_IND 46 0x2e
MAP-ALERT-SC-WITHOUT-RESULT-
IND MAPST_ALERT_SC_WO_RESULT_IND 18 0x12
MAP-ALERT-SERVICE-CENTRE-CNF MAPST_ALERT_SC_CNF 138 0x8a
MAP-ALERT-SERVICE-CENTRE-IND MAPST_ALERT_SC_IND 10 0x0a
MAP-ANYTIME-INTERROGATION-CNF MAPST_ANYTIME_INT_CNF 152 0x98
MAP-ANYTIME-INTERROGATION-IND MAPST_ANYTIME_INT_IND 30 0x1e
MAP-ANYTIME-MODIFICATION-CNF MAPST_ANYTIME_MOD_CNF 232 0xe8
MAP-ANYTIME-MODIFICATION-IND MAPST_ANYTIME_MOD_IND 116 0x74
MAP-ANYTIME-SUBSCRIPTION-
INTERROGATION-CNF MAPST_ATSI_CNF 204 0xcc
MAP-ANYTIME-SUBSCRIPTION-
INTERROGATION-IND MAPST_ATSI_IND 82 0x52
MAP-AUTHENTICATION-FAILURE-
REPORT-IND MAPST_AUTHFAILREPORT_IND 112 0x70
MAP-AUTHENTICATION-FAILURE-
REPORT-CNF MAPST_AUTHFAILREPORT_CNF 228 0xe4
MAP-CANCEL-LOCATION-CNF MAPST_CANCEL_LOCATION_CNF 164 0xa4
MAP-CANCEL-LOCATION-IND MAPST_CANCEL_LOCATION_IND 42 0x2a
MAP-CHECK-IMEI-CNF MAPST_CHECK_IMEI_CNF 202 0xca
MAP-CHECK-IMEI-IND MAPST_CHECK_IMEI_IND 80 0x50
MAP-DEACTIVATE-SS-CNF MAPST_DEACTIVATE_SS_CNF 200 0xc8
MAP-DEACTIVATE-SS-IND MAPST_DEACTIVATE_SS_IND 78 0x4e
MAP-DEACTIVATE-TRACE-MODE-
CNF MAPST_DEACTIV_TRACE_MODE_CNF 220 0xdc
MAP-DEACTIVATE-TRACE-MODE-IND MAPST_DEACTIV_TRACE_MODE_IND 98 0x62
MAP-DELETE-SUBSCRIBER-DATA-
CNF MAPST_DEL_SUBS_DATA_CNF 172 0xac
MAP-DELETE-SUBSCRIBER-DATA-
IND MAPST_DEL_SUBS_DATA_IND 50 0x32
MAP-EXTENDED-SERVICE-TYPE MAPST_EXTENDED_SERVICE_TYPE 255 0xff
MAP-ERASE-CC-ENTRY-CNF MAPST_ERASE_CC_ENTRY_CNF 535 0x0217
MAP-ERASE-CC-ENTRY-IND MAPST_ERASE_CC_ENTRY_IND 534 0x0216
MAP-ERASE-SS-CNF MAPST_ERASE_SS_CNF 84 0x54
MAP-ERASE-SS-IND MAPST_ERASE_SS_IND 206 0xce
MAP-FAILURE-REPORT-IND MAPST_FAILURE_REPORT_IND 54 0x36
MAP-FAILURE-REPORT-CNF MAPST_FAILURE_REPORT_CNF 176 0xb0
MAP-FORWARD-ACCESS-
SIGNALLING-IND MAPST_FWDACCESS_SIG_IND 102 0x66
Section 4 Interface to MAP-User
20
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-FORWARD-CHECK-SS-
INDICATION-IND MAPST_FWD_CHK_SS_INDICAT_IND 68 0x44
MAP-FORWARD-SHORT-MESSAGE-
CNF (versions 1 and 2) MAPST_FWD_SM_CNF 132 0x84
MAP-FORWARD-SHORT-MESSAGE-
IND (versions 1 and 2) MAPST_FWD_SM_IND 4 0x04
MAP-GET-PASSWORD-CNF MAPST_GET_PASSWORD_CNF 212 0xd4
MAP-GET-PASSWORD-IND MAPST_GET_PASSWORD_IND 90 0x5a
MAP-INFORM-SERVICE-CENTRE-IND MAPST_INF_SC_IND 12 0x0c
MAP-INSERT-SUBSCRIBER-DATA-
CNF MAPST_INS_SUBS_DATA_CNF 166 0xa6
MAP-INSERT-SUBSCRIBER-DATA-
IND MAPST_INS_SUBS_DATA_IND 44 0x2c
MAP-INTERROGATE-SS-CNF MAPST_INTERROGATE_SS_CNF
196 0xc4
MAP-INTERROGATE-SS-IND MAPST_INTERROGATE_SS_IND
74 0x4a
MAP-MO-FORWARD-SHORT-
MESSAGE-CNF (version 3 onwards) MAPST_MO_FWD_SM_CNF 132 0x84
MAP-MO-FORWARD-SHORT-
MESSAGE-IND (version 3 onwards) MAPST_MO_FWD_SM_IND 4 0x04
MAP-MT-FORWARD-SHORT-
MESSAGE-CNF (version 3 onwards) MAPST_MT_FWD_SM_CNF 192 0xc0
MAP-MT-FORWARD-SHORT-
MESSAGE-IND (version 3 onwards) MAPST_MT_FWD_SM_IND 70 0x46
MAP-NOTEMM-EVENT-CNF MAPST_NOTE_MM_EVENT_CNF 188 0xbc
MAP-NOTEMM-EVENT-IND MAPST_NOTE_MM_EVENT_IND 66 0x42
MAP-NOTE-SUBSCRIBER-PRESENT-
IND MAPST_NOTE_SUB_PRESENT_IND 20 0x14
MAP-NOTE-MS-PRESENT-GPRS-IND MAPST_NOTE_MS_PRES_GPRS_IND 52 0x34
MAP-NOTE-MS-PRESENT-GPRS-CNF MAPST_NOTE_MS_PRES_GPRS_CNF 174 0xae
MAP-PREPARE-HANDOVER-CNF MAPST_PREPAREHO_CNF 222 0xde
MAP-PREPARE-HANDOVER-IND MAPST_PREPAREHO_IND 104 0x68
MAP-PREPARE-SUBSEQUENT-
HANDOVER-CNF MAPST_PREPARESUBHO_CNF 224 0xe0
MAP-PREPARE-SUBSEQUENT-
HANDOVER-IND MAPST_PREPARESUBHO_IND 106 0x6a
MAP-PROCESS_UNSTRUCTURED-
SS-REQUEST-IND MAPST_PRO_UNSTR_SS_REQ_IND 28 0x1c
MAP-PROCESS-UNSTRUCTURED-
SS-REQUEST-CNF MAPST_PRO_UNSTR_SS_REQ_CNF 150 0x96
MAP-PROVIDE-ROAMING-NUMBER-
CNF MAPST_PROV_ROAM_NUM_CNF 160 0xa0
MAP-PROVIDE-ROAMING-NUMBER-
IND MAPST_PROV_ROAM_NUM_IND 38 0x26
MAP-PROVIDE-SUBSCRIBER-INFO –
CNF MAPST_PROV_SUB_INFO_CNF 154 0x9a
MAP-PROVIDE-SUBSCRIBER-INFO-
IND MAPST_PROV_SUB_INFO_IND 32 0x20
MAP Programmer's Manual Issue 13
21
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-PROVIDE-SUBSCRIBER-
LOCATION-CNF MAPST_PROVIDE_SUBS_LOC_CNF 184 0xb8
MAP-PROVIDE-SUBSCRIBER-
LOCATION-IND MAPST_PROVIDE_SUBS_LOC_IND 62 0x3e
MAP-PURGE-MSUBSCRIBER-DATA-
IND MAPST_PURGE_MS_IND 58 0x3a
MAP-PURGE-MSUBSCRIBER-DATA-
CNF MAPST_PURGE_MS_CNF 180 0xb4
MAP-READY-FOR-SM-CNF MAPST_RDY_FOR_SM_CNF 136 0x88
MAP-READY-FOR-SM-IND MAPST_RDY_FOR_SM_IND 8 0x08
MAP-REGISTER-CC-ENTRY-CNF MAPST_REGISTER_CC_ENTRY_CNF 531 0x0213
MAP-REGISTER-CC-ENTRY-IND MAPST_REGISTER_CC_ENTRY_IND 530 0x0212
MAP-REGISTER-PASSWORD-CNF MAPST_REGISTER_PASSWORD_CNF 214 0xd6
MAP-REGISTER-PASSWORD-IND MAPST_REGISTER_PASSWORD_IND 92 0x5c
MAP-REGISTER-SS_CNF MAPST_REGISTER_SS_CNF 86 0x56
MAP-REGISTER-SS_IND MAPST_REGISTER_SS_IND 208 0xd0
MAP-REMOTE-USER-FREE-CNF MAPST_REMOTE_USER_FREE_CNF 527 0x020f
MAP-REMOTE-USER-FREE_IND MAPST_REMOTE_USER_FREE_IND 526 0x020e
MAP-REPORT-SM-DELIVERY-
STATUS-CNF MAPST_RPT_SMDST_CNF 134 0x86
MAP-REPORT-SM-DELIVERY-
STATUS-IND MAPST_RPT_SMDST_IND 6 0x06
MAP-RESET-IND MAPST_RESET_IND 513 0x0201
MAP-RESTORE-DATA-CNF MAPST_RESTORE-DATA_CNF 216 0xd8
MAP-RESTORE-DATA-IND MAPST_RESTORE-DATA_IND 94 0x5e
MAP-RESUME-CALL-HANDLING-CNF MAPST_RES_CALL_CNF 210 0xd2
MAP-RESUME-CALL-HANDLING-IND MAPST_RES_CALL_IND 88 0x58
MAP-SEND-AUTHENTICATION-INFO-
RSP MAPST_SEND_AUTH_INFO_CNF 194 0xc2
MAP-SEND-AUTHENTICATION-INFO-
REQ MAPST_SEND_AUTH_INFO_IND 72 0x48
MAP-SEND-END-SIGNAL-CNF MAPST_SEND_ENDSIG_CNF 226 0xe2
MAP-SEND-END-SIGNAL-IND MAPST_SEND_ENDSIG_IND 110 0x6e
MAP-SEND-IDENTIFICATION-CNF MAPST_SEND_IDENT_CNF 170 0xaa
MAP-SEND-IDENTIFICATION-IND MAPST_SEND_IDENT_IND 48 0x30
MAP-SEND-IMSI-CNF MAPST_SEND_IMSI_CNF 156 0x9c
MAP-SEND-IMSI-IND MAPST_SEND_IMSI_IND 34 0x22
MAP-SEND-PARAMETERS-CNF MAPST_SEND_PARAMETERS_CNF 218 0xda
MAP-SEND-PARAMETERS-IND MAPST_SEND_PARAMETERS_IND 96 0x60
MAP-SEND-ROUTING-INFO-CNF MAPST_SND_RI_CNF 144 0x90
MAP-SEND-ROUTING-INFO-FOR-
GPRS-CNF MAPST_SND_RTIGPRS_CNF 158 0x9e
Section 4 Interface to MAP-User
22
Primitive Mnemonic Value
(dec)
Value
(hex)
MAP-SEND-ROUTING-INFO-FOR-
GPRS-IND MAPST_SND_RTIGPRS_IND 36 0x24
MAP-SEND-ROUTING-INFO-FOR-LCS-
CNF MAPST_ROUT_INFO_LCS_CNF 182 0xb6
MAP-SEND-ROUTING-INFO-FOR-LCS-
IND MAPST_ROUT_INFO_LCS_IND 60 0X3c
MAP-SEND-ROUTING-INFO-FOR-SM-
CNF MAPST_SND_RTISM_CNF 130 0x82
MAP-SEND-ROUTING-INFO-FOR-SM-
IND MAPST_SND_RTISM_IND 2 0x02
MAP-SEND-ROUTING-INFO-IND MAPST_SND_RI_IND 22 0x16
MAP-SET-REPORTING-STATE-IND MAPST_SET_REPORTING_STATE_IND 518 0x0206
MAP-SET-REPORTING-STATE-CNF MAPST_SET_REPORTING_STATE_CNF 519 0x0207
MAP-STATUS-REPORT-IND MAPST_STATUS_REPORT_IND 522 0x0208
MAP-STATUS-REPORT-CNF MAPST_STATUS_REPORT_CNF 523 0x0209
MAP-SUBSCRIBER-LOCATION-
REPORT-CNF MAPST-SUBS-LOC-REPORT-CNF 186 0xba
MAP-SUBSCRIBER-LOCATION-
REPORT-IND MAPST-SUBS-LOC-REPORT-IND 64 0x40
MAP-TRACE-SUBSCRIBER-IND MAPST_TRACE_SUB_ACTIV_IND 100 0x64
MAP-UNSTRUCTURED-SS-NOTIFY-
CNF MAPST_UNSTR_SS_NOTIFY_CNF 148 0x94
MAP-UNSTRUCTURED-SS-NOTIFY-
IND MAPST_UNSTR_SS_NOTIFY_IND 26 0x1a
MAP-UNSTRUCTURED-SS-REQUEST-
CNF MAPST_UNSTR_SS_REQ_CNF 146 0x92
MAP-UNSTRUCTURED-SS-REQUEST-
IND MAPST_UNSTR_SS_REQ_IND 24 0x18
MAP-UPDATE-GPRS-LOCATION-CNF MAPST_UPDATE_GPRS_LOC_CNF 178 0Xb2
MAP-UPDATE-GPRS-LOCATION-IND MAPST_UPDATE_GPRS_LOC_IND 56 0x38
MAP-UPDATE-LOCATION-CNF MAPST_UPDATE_LOCATION_CNF 162 0xa2
MAP-UPDATE-LOCATION-IND MAPST_UPDATE_LOCATION_IND 40 0x28
MAP Programmer's Manual Issue 13
23
4.5 MAP Dialogue Request
Synopsis:
Message sent from the MAP-User to MAP containing a dialogue request primitive. Used by
MAP-User to open and close dialogues with the remote peer MAP-User.
Message Format:
MESSAGE HEADER
FIELD NAME MEANING
Type MAP_MSG_DLG_REQ (0xc7e2)
Id dialogue ID
Src Sending module ID
Dst MAP_TASK_ID
rsp_req 0
Hclass 0
Status 0
err_info 0
Len Number of bytes of user data
PARAMETER AREA
OFFSET SIZE NAME
0 1 Dialogue primitive type octet.
1 len – 2 Parameters in Name-Length-Data format.
len – 1 1 Set to zero indicating end of message.
Description:
This message is used by the MAP-User to send dialogue primitives to MAP.
The MAP-User makes use of MAP to establish dialogues with MAP-User peers. The dialogue
may then be used to send and receive service requests.
All dialogue primitives contain a dialogue ID, which is encoded in the message header. It does
not form part of the parameter area. It must be provided by the MAP-User with the MAP-
OPEN primitive and used in the message header of all subsequent dialogue and service
primitives associated with that dialogue. Dialogues initiated remotely will have a dialogue id
assigned by MAP.
Section 4 Interface to MAP-User
24
Parameter area contents:
The dialogue primitive type octet is coded as defined in Section 4.3 Dialogue Primitive Types.
The following table lists the parameters associated with each dialogue request primitive and
shows whether the parameter is Mandatory (M), in which case the message will be discarded
if the parameter is omitted, or Optional (O), in which case the parameter is not considered
essential.
MAP Primitive