The following types of Management and Administration Messages are included in the MUP and are each identified by a different heading code H1:
2.8.1 Restart Information Message (RES)
2.8.2 Restart Information Acknowledgement Message (REA)
2.8.3 Security Failure Notification Message (SFN)
2.8.4 Security Failure Notification Acknowledge Message (SFA)
2.8.5 Manufacturer Specific Data Message(MSD)
2.8.6 Manufacturer Specific Data Acknowledge Message (MSA)
2.8.1 Restart Information Message (RES)
Basic format:
|
g |
f |
e |
d |
c |
b |
a |
|
D.....BA |
L.....BA |
D.....BA |
L.....BA |
D.....BA |
D.....BA |
fe.........BA |
|
SPARE |
MTXV IDENTITY |
SPARE |
MTXH IDENTITY |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
0/16 Optional |
4 |
12 |
4 |
4 |
32 |
|
Figure 2.8.1 Restart Information Message.
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0110.
c) Heading code H1 is coded 0001.
d) MTXH Identity.
See paragraph 2.4.1.e.
e) Spare
f) MTXV Identity.
This field is optional (In case the RES message is extended in a future edition of the spec, the validity of this field will be optional).
See paragraph 2.4.1.e.
g) Spare
This field is optional (In case the RES message is extended in a future edition of the spec, the validity of this field will be optional).
2.8.2 Restart Information Acknowledgement Message (REA)
Basic format:
|
c |
b |
a |
|
D.....BA |
D.....BA |
fe.........BA |
|
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
4 |
4 |
32 |
Figure 2.8.2 Restart Information Acknowledgement Message.
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0110.
c) Heading code H1 is coded 0010.
Basic format:
|
f |
e |
d |
c |
b |
a |
|
H.....BA |
DCBA |
DCBA |
DCBA |
DCBA |
fe.........BA |
|
MOBILE STATION IDENTITY |
NUMBER OF DIGITS |
REASON |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
n*8 |
4 |
4 |
4 |
4 |
32 |
|
4<n<5 |
|||||
|
l |
k |
j |
i |
h |
g |
|
L.....BA |
b.....BA |
X.....BA |
X.....BA |
DCBA |
L.......BA |
|
BASE STATION IDENTITY |
RAND C1...C7 |
RECEIVED SRES R1...R4 |
SRES R1...R4 |
TRAFFIC CASE |
RECEIVED MOBILE STATION PASSWORD |
|
12 |
28 |
16 |
16 |
4 |
12 |
Figure 2.8.3 Security Failure Notification Message
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0110.
c) Heading code H1 is coded 0011.
d) Reason
Bit DCBA:
|
0000 |
Failed password check |
|
|
0001 |
Failed Authentication |
e) Number of digits
The field indicates the number of digits contained in the following subfield. It is expressed in the binary form.
f) Mobile Station Identity
Coded as in the paragraph 2.4.1.g
g) Received mobile Station Password (K1K2K3)
This is the mobile station password received from the mobile station.
The digits in the Mobile Station Password, (K1K2K3), are coded as in the paragraph 2.4.1.g. The most significant digit is sent first.
h) Traffic Case
Bit DCBA:
|
0000 |
Originating call from a mobile subscriber |
|
|
0001 |
Terminating call to a mobile subscriber |
|
|
0010 |
Location updating call |
|
|
0011 |
Not used |
|
|
0100 |
Spare |
|
|
: |
: |
|
|
1111 |
Spare |
i) SRES
Coded as in the paragraph 2.9.2.f
j) Received SRES
This is the signed response received from the mobile station. Coded as in the paragraph 2.9.2.f.
k) RAND
Coded as in the paragraph 2.9.2.D.
l) Base Station Identity (B1 B2 B3)
The Identity of the Base Station serving the Mobile Station. The digits B1B2B3 are coded as in paragraph 2.4.1.g. The most significant digit is sent first.
2.8.4 Security Failure Notification Acknowledgement Message (SFA)
Basic format:
|
c |
b |
a |
|
D.....BA |
D.....BA |
fe.........BA |
|
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
4 |
4 |
32 |
Figure 2.8.4 Security Failure Notification Acknowledge Message
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0110.
c) Heading code H1 is coded 0100.
Basic format:
|
f |
e |
d |
c |
b |
a |
|
......BA |
D.....BA |
D..........BA |
D.....BA |
D.....BA |
fe.........BA |
|
SYSTEM DATA |
SPARE |
MANUFACTURER INDICATORS |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
n*8 |
4 |
4 |
4 |
4 |
32 |
Figure 2.8.5 Manufacturer Specific Data Message
The following codes are used:
a) Transaction number
See paragraph 2.2
b) Heading code H0 is coded 0110
c) Heading code H1 is coded 0101
d) Manufacturer indicators
Bit DCBA:
|
0000 |
Not in use |
|
|
0001 |
Manufacturer no 1 |
|
|
0010 |
Manufacturer no 2 |
|
|
0011 |
Manufacturer no 3 |
|
|
0100 |
Spare |
|
|
: |
: |
|
|
1111 |
Spare |
e) Spare
f) System data
Contents, coding and length of this field is specified by the manufacturer. This message is for operator-internal use between network elements. Transmit capacity of network elements define the maximum length of the message.
Basic format:
|
d |
e |
d |
c |
b |
a |
|
......BA |
D.....BA |
D..........BA |
D.....BA |
D.....BA |
fe.........BA |
|
SYSTEM DATA |
SPARE |
MANUFACTURER INDICATORS |
HEADING CODE H1 |
HEADING CODE H0 |
TRANSACTION NUMBER |
|
n*8 |
4 |
4 |
4 |
4 |
32 |
Figure 2.8.6 Manufacturer Specific Data Acknowledge Message.
The following codes are used:
a) Transaction number.
See paragraph 2.2.
b) Heading code H0 is coded 0110.
c) Heading code H1 is coded 0110.
d) Manufacturer indicators
Bit DCBA:
|
0000 |
Not in use |
|
|
0001 |
Manufacturer no 1 |
|
|
0010 |
Manufacturer no 2 |
|
|
0011 |
Manufacturer no 3 |
|
|
0100 |
Spare |
|
|
: |
: |
|
|
1111 |
Spare |
e) Spare
f) System data.
Contents, coding and length of this field is specified by the manufacturer. This message is for internal use between network elements. Transmit capacity of network elements define the maximum length of the message.