3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
For the points listed the manufacturer has the choice between different solutions in implementation. The manufacturer has to describe his choice if there is any consequence for the tests.
A3.1.1 LAPDm protocol (3GPP TS 04.05 and 04.06)
A18.104.22.168 Simplified protocol – 3GPP TS 04.06 clause 6
Statement about the choice made by the manufacturer.
A22.214.171.124 Management of SAPI = 3 – 3GPP TS 04.11 subclause 2.3
Statement about the handling of SAPI = 3 on the data link layer chosen by the manufacturer.
A3.1.2 Mobility management
A126.96.36.199 IMSI detach initiation by the MS – 3GPP TS 04.08 / 3GPP TS 24.008 subclause 188.8.131.52
During a location updating, if an IMSI detach has to be performed (SIM or power off), the IMSI detach can be delayed until the location updating is finished, or can be omitted.
A184.108.40.206 IMSI detach completion by the MS – 3GPP TS 04.08 / 3GPP TS 24.008 subclause 220.127.116.11
The MS should delay the local release of the channel to allow a normal release from the network after a detach by power off command, if possible.
If not possible the RR sub-layer on the MS side should be aborted without waiting for something from the network.
A18.104.22.168 MM specific procedures – 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.4 and 22.214.171.124
During the lifetime of an MM specific procedure, if an MM connection establishment is required by a CM-entity, this request will either be rejected or delayed until the running MM specific procedure is terminated and, provided that the network has not sent a "follow-on proceed" indication, the RR connection is released.
If the LOCATION UPDATING REQUEST message has not been sent, the mobile station may include a "follow-on request" indicator in the message. The mobile station shall then delay the request until the MM specific procedure is completed, when it may be given the opportunity by the network to use the RR connection.
A126.96.36.199 Receiving an MM STATUS message – 3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.6
If the MM-entity of the Mobile Station receives a MM-STATUS message no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible.
A3.1.3 Call control
A188.8.131.52 Status enquiry procedures – 3GPP TS 04.08 / 3GPP TS 24.008 subclause 184.108.40.206
The MS may send a STATUS ENQUIRY and take the appropriate actions based on the answer (STATUS) of the network.
A220.127.116.11 Receiving a STATUS message by a CC entity – 3GPP TS 04.08 / 3GPP TS 24.008 subclause 18.104.22.168
The determination of which CC states are incompatible between the MS and the network is left as an implementation decision except in some particular cases.
A22.214.171.124 Called side compatibility checking – 3GPP TS 04.08 / 3GPP TS 24.008 clause B.3
Compatibility checking can be performed in various ways from the viewpoint of execution order and information to be checked, e.g. first DDI number, sub-address and then compatibility or vice versa.
A126.96.36.199 Disconnect on incoming call
The mobile equipment may or may not offer the possibility to disconnect an incoming call:
a) after having confirmed an incoming call, but before alerting;
b) after alerting, but before connecting.
3GPP TS 02.30 (subclause 5.2.3) allows the combination of SEND and END function in one key.
A3.1.4 Layer 1
A188.8.131.52 Optional storage of BCCH carrier information – 3GPP TS 05.08 subclause 6.3
The MS may include optional storage of BCCH carrier information. For instance, the MS may store the BCCH carriers in use by the PLMN accessed when it was last active in the GSM network, or it may store BCCH carriers for more than one PLMN.
A3.1.5 Autocalling – (ref.: 3GPP TS 02.07, annex 1)
Cause number 27 implemented in:
– category 2 (preferred);
– category 3.
A3.1.6 Transient states
The following call control states may be transient in the mobile station:
State U6 may be transient if the mobile station is not configured to support explicit refusal of an incoming call by the (human or non-human) user (e.g. via a terminal interface) before call confirmation.
If U6 is transient, there is an internal transition:
U6 > U9
or an internal transition:
U6 > U0.
State U7 is transient if the implementation allows for automatic connect after an implementation specific time T.
If U7 is transient, there is an internal transition:
after T, CONNECT
U7 > U8.
State U9 is not transient if:
– the implementation does not support immediate connect;
– an appropriate TCH is not yet assigned;
– the signalling element has not been present in the SETUP.
If the implementation supports immediate connect, there is an internal transition:
U9 > U8.
If the appropriate TCH is available or the signalling element was present in SETUP, there is an internal transition:
U9 > U7.
U12 is a stable state, if an appropriate speech traffic channel is connected and progress indicator #8 was present in the DISCONNECT message. Otherwise U12 is transient, and there is an internal transition: