The following types of Location Data Forward Messages are included in the MUP and are each identified by a different heading code H1:
2.4.1 Location Updating Message (LUM)
2.4.2 Location Cancellation Message (LCM)
2.4.3 Supplementary Updating Message (SUM)
2.4.1 Location Updating Message (LUM)
Basic format:
|
e |
d |
c |
b |
a |
|||||
|
L............BA |
H..........BA |
D.....BA |
D.....BA |
fe..........BA |
|||||
|
MTXV IDENTITY Id1Id2Id3. |
MTXV RESTRICTIONS |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|||||
|
12 |
8 |
4 |
4 |
32 |
|||||
|
k |
j |
i |
h |
g |
f |
||||
|
H.......BA |
P.....BA |
D.......BA |
D..........BA |
.............BA |
D.......BA |
||||
|
OPERATOR INDICATOR Y3 |
PREPAID CALL UNITS |
TRAFFIC AREA INDICATOR Y2 |
INFORMATION FIELD IND. SET NO.1 |
MOBILE STATION IDENTITY ZX1...X6(K1K2K3) |
NUMBER OF DIGITS |
||||
|
0/8 Optional |
0/16 Optional |
4 |
4 |
n * 8 4<n<5 |
4 |
||||
Figure 2.4.1 Location Updating Message.
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0001.
c) Heading code H1 is coded 0001.
d) MTXV restrictions.
Bit A: Added Mobile Identity Security.
0 Not required.
1 Added Security is required.
Bit B: Verified Roaming Updating
0 Set the new location
1 Do not set the new location
Bit C: SIS verified Roaming Updating
0 Ordinary Location Updating
1 Location Updating verified with SIS
Bit HGFED:
Spare
e) MTXV Identity (Id1Id2Id3)
The MTXV identity is used for routing information when the NMT-node is returning acknowledge messages to a originating node. The identity is also used for location of a roaming subscribers home node. The digits are coded as in 2.4.1.g.
f) Number of digits
A code expressing in pure binary representation the number of digits contained in the following subfield.
g) Mobile Station Identity (ZX
The MS Identity will either consist of 10 digits (including
K
Coding:
The digit signals are coded as shown below. The most significant digit is sent first. Subsequent digits are sent in successive 4-bit fields.
|
0000 |
Digit 0 |
1000 |
Digit 8 |
|
|
0001 |
Digit 1 |
1001 |
Digit 9 |
|
|
0010 |
Digit 2 |
1010 |
Code 10 |
|
|
0011 |
Digit 3 |
1011 |
Code 11 |
|
|
0100 |
Digit 4 |
1100 |
Code 12 |
|
|
0101 |
Digit 5 |
1101 |
Code 13 |
|
|
0110 |
Digit 6 |
1110 |
Code 14 |
|
|
0111 |
Digit 7 |
1111 |
Code 15 |
h) Information Field Indicator Set no 1
0 Field not included/ valid.
1 Field included/ valid.
Bit A: Indicator for the Traffic Area Indicator field Y2.
Bit B: Reserved for indicator for a second set of Information fields.
Bit C: Indicator for the Prepaid Call Units field.
Bit D: Indicator for the Operator Indicator field Y3.
i) Traffic Area Indicator Y2
The value of Traffic Area (Y2) are coded as below.
Bit DCBA:
|
0000 |
Y2 Value 0 |
1000 |
Y2 Value 8 |
|
|
0001 |
Y2 Value 1 |
1001 |
Y2 Value 9 |
|
|
0010 |
Y2 Value 2 |
1010 |
Y2 Value A |
|
|
0011 |
Y2 Value 3 |
1011 |
Y2 Value B |
|
|
0100 |
Y2 Value 4 |
1100 |
Y2 Value C |
|
|
0101 |
Y2 Value 5 |
1101 |
Y2 Value D |
|
|
0110 |
Y2 Value 6 |
1110 |
Y2 Value E |
|
|
0111 |
Y2 Value 7 |
1111 |
Y2 Value F |
j) Prepaid Call Units
The field indicates the amount of the Prepaid Call Units the subscriber has used in the previous call. If the field is empty (= zero value) the LUM message is an ordinary location updating message. Coding of the units as in field 2.4.1.g
k) Operator Indicator Y3
The digits in the Traffic Area (Y3) are binary coded 0 - 255. The least significant digit is sent first.
Example: Coding of «3»
Bit HGFEDCBA
00000011
2.4.2 Location Cancellation Message (LCM)
Basic format:
|
f |
e |
d |
c |
b |
a |
|
|
H.......BA |
D.......BA |
D.....BA |
D.....BA |
D.....BA |
fe.........BA |
|
|
MOBILE STATION IDENTITY |
NUMBER OF DIGITS |
SPARE |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
|
n*8 |
4 |
4 |
4 |
4 |
32 |
|
|
4<n<5 |
||||||
|
h |
g |
|||||
|
D.....BA |
LK......BA |
|||||
|
SPARE |
MTXV IDENTITY |
|||||
|
4 |
12 |
|||||
Figure 2.4.2 Location Cancellation Message
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0001.
c) Heading code H1 is coded 0010.
d) Spare.
e) Number of digits.
See paragraph 2.4.1.f.
f) Mobile Station Identity.
See paragraph 2.4.1.g.
g) MTXV Identity
See paragraph 2.4.1.e.
h) Spare
2.4.3 Supplementary Updating Message (SUM)
Basic format:
|
f |
e |
d |
c |
b |
a |
|
H.......BA |
D............BA |
D.......BA |
D.....BA |
D.....BA |
fe.........BA |
|
MOBILE STATION IDENTITY |
MOBILE STATION RELATED FORWARDING INFORMATION |
NUMBER OF DIGITS |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
n*8 |
4 |
4 |
4 |
4 |
32 |
|
4<n<5 |
|||||
Figure 2.4.3 Supplementary Updating Message
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0001.
c) Heading code H1 is coded 0011.
d) Number of digits.
See paragraph 2.4.1.f.
e) Mobile station related Forwarding Information
Bit A: Message Waiting reset information
0: Not reset of Message waiting indicator.
1: Reset of Message waiting indicator.
Bit B: Attach/ Detach Information
0: Mobile station considered attached to network.
1: Mobile station considered detached from network.
Bit DC: Spare
f) Mobile Station Identity.
See paragraph 2.4.1.g.