25 General macro description
29.1203GPPMobile Application Part (MAP) specification for Gateway Location Register (GLR)Release 17TS
25.1 MAP open macros
This subclause refers 3GPP TS 29.002.
25.2 Macros to check the content of indication and confirmation primitives
This subclause refers 3GPP TS 29.002.
25.3 Authentication processes
25.3.1 Process Obtain_Authentication_Sets_GLR
This process is initiated by the GLR to fetch authentication vectors from a subscriber’s HLR to the VLR. The process is described in figure 25.3/1.
Figure 25.3.1/1 (sheet 1 of 2): Process Obtain_Authentication_Sets_GLR
Figure 25.3.1/2 (sheet 2 of 2): Process Obtain_Authentication_Sets_GLR
25.3.2 Process Authentication_Failure_Report_GLR
This process is initiated by the GLR to notify a subscriber’s HLR about the occurrence of an authentication failure in the VLR or SGSN. The process is described in figure 25.3/2.
Figure 25.3.2/1 (sheet 1 of 2): Process Authentication_Failure_Report_GLR
Figure 25.3.2/2 (sheet 2 of 2): Process Authentication_ Failure_Report _GLR
25.4 Short Message Alert procedures
25.4.1 Subscriber_Present_GLR_AS_VLR process
The Subscriber_Present_GLR_AS_VLR process is invoked by the GLR, when GLR receives Update Location from VLR and the MNRF flag is set. The general description of the short message alert procedures is in the subclause 23.3.
The GLR sends the MAP_READY_FOR_SM request to the HLR and waits for the HLR to answer. When receiving the answer, the GLR will act as follows:
– the MNRF flag is cleared if the procedure is successful;
– the MNRF flag is not cleared if the procedure is not successful.
The Subscriber_Present_GLR_AS_VLR process is shown in the figure 25.4/1.
Figure 25.4/1: Process Subscriber_Present_GLR_AS_VLR
25.4.2 The Mobile Subscriber is present
When GLR receives Update GPRS Location from SGSN, while the MS not reachable for GPRS (MNRG) flag is set, the GLR will send the MAP_READY_FOR_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS.
When receiving the answer, the GLR will act as follows:
– MNRG is cleared if the procedure is successful.
– MNRG is not cleared if the procedure is not successful.
The Subscriber_Present_GLR_AS_SGSN process is shown in the figure 25.4/2.
Figure 25.4/2: Process Subscriber_Present_GLR_AS_SGSN
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
CN#07 |
Approved at TSGN#07 |
3.0.0 |
|||||
|
CN#09 |
001 |
1 |
Changes to support Authentication Failure Report for GLR |
3.1.0 |
|||
|
CN#09 |
002 |
Changes to support secure transport MAP for GLR |
4.0.0 |
||||
|
CN#16 |
Rel-5 created after CN#16 |
5.0.0 |
|||||
|
CN#26 |
Rel-6 created after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
2009-12 |
Update to Rel-9 version (MCC) |
9.0.0 |
|||||
|
2011-03 |
Update to Rel-10 version (MCC) |
10.0.0 |
|||||
|
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||||
|
2014-09 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||||
|
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|||||
|
2017-03 |
Update to Rel-14 version (MCC) |
14.0.0 |
|||||
|
2018-06 |
Update to Rel-15 version (MCC) |
15.0.0 |
|||||
|
2020-07 |
Update to Rel-16 version (MCC) |
16.0.0 |
|||||
|
2022-03 |
SA#95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |