Functional Description
Table 10
Q.921
Management Entity Actions for MDL Error Indications (cont’d)
Error Type
Error
Code
Error
Condition
Affected
States
Network
Management Management
User
Action
Action
J
N(R) Error
7, 8
7, 8
Error log
Dependent on
implementation
K
Receipt of
FRMR
Error log
Dependent on
implementation
response
L
Receipt of non- 4, 5, 6, 7, 8 Error log
implemented
frame
Dependent on
implementation
Other
M (see Receipt of I-field 4, 5, 6, 7, 8 Error log
Dependent on
implementation
Note 2)
not permitted
N
Receipt of
frame with
wrong size
4, 5, 6, 7, 8 Error log
4, 5, 6, 7, 8 Error log
Dependent on
implementation
O
N201 Error
Dependent on
implementation
Note 1: For the description of the affected states see Annex B.
Note 2: According to Q.921 § 5.8.5 this error code will never be generated.
Reactions of the ISAC-S and Necessary Software Reactions
As the auto- mode is only to be used in states 7, 8 and as it has to be switched to non-auto
mode where in states 1-6, we do not have to deal with error code G and H.
A) The ISAC-S does not react at all (our implementation). The software is not informed, as
no action is mandatory according to Q.921.
B) see 4.2a)
C) "
D) "
E) "
F) "
I) see further Criteria Leading to a Reestablishment
J) see Frame Rejection Condition
K) see further Criteria Leading to a Reestablishment
L) see Frame Rejection Condition
M)
N) see Frame Rejection Condition
O) only internal software timer, no device action.
Conclusion:
For your error-processing with ISAC-S we suggest to implement the software design shown in
the following figures 60 through 64 into your interrupt service routine.
Semiconductor Group
131
INFINEON [ Infineon ]
