1.1.1 VALIDATE Function

Document Sample
1.1.1 VALIDATE Function Powered By Docstoc
					1    1.1.1     VALIDATE Function

2    1.1.1.1   Definition and Applicability
3    It shall be mandatory for all cards complying with [1] to support all functions described
4    therein.

5    This command requests validation of a single block of data.

6    1.1.1.2   Conformance Requirement

 7      CR1      If the requested Block ID in the Validate Request Message is not supported (see [13]
 8               Table 4.5.4-1 Validation Parameter Block Types), the R-UIM shall return a Result
 9               Code of ‘07’ “Rejected – Block ID value not supported” and shall set the Block ID to
10               the received parameter block identifier.

11      CR2      If the Validate Request Message contains a Parameter Block having a size different
12               from that supported by the R-UIM, the R-UIM shall return a Result Code of ‘02’,
13               “Rejected - Data size mismatch” and shall set the Block ID to the received parameter
14               block identifier.
15      CR3      If the Validate Request Message contains a Parameter Block with a parameter value
16               that is out-of-range, the R-UIM shall set the Result Code to ‘04’, “Rejected - Invalid
17               parameter” and shall set the Block ID to the received parameter block identifier.
18      CR4      If the Validate Request Message is not accepted for any other reason, the R-UIM shall
19               set the Result Code to ‘01’, “Rejected - Unknown reason” and shall set the Block ID
20               to the received parameter block identifier.

21      Note: CR4 cannot be tested.

22      CR5      If the Validate Request Message contains the Verify SPC Parameter Block and the
23               SPCr received in the message does not match the SPCs stored in the R-UIM, the R-
24               UIM shall set the Result Code to ‘0B’, “Rejected - Invalid SPC” and shall set the Block
25               ID to the received parameter block identifier.

26      CR6      If the Validate Request Message contains the Verify SPC Parameter Block and the
27               SPCr received in the message matches the SPCs stored in the R-UIM, the R-UIM
28               shall set the Result Code to ‘00’, “Accepted - Operation successful” and shall set the
29               Block ID to the received parameter block identifier. The R-UIM shall set the
30               SP_LOCK_STATE to ‘0’. (Note: This latter requirement cannot be verified since
31               SP_LOCK_STATE is inaccessible).

32      CR7      If the Validate Request Message contains the Change SPC Parameter Block and if
33               SP_LOCK_STATE = ‘1’, the R-UIM shall set the Result Code to ‘0A’, “Rejected - Mobile
34               station locked” and shall set the Block ID to the received parameter block identifier.
1    CR8    If the Validate Request Message contains the Change SPC Parameter Block and if
2           SP_LOCK_STATE = ‘0’ and the stored SPCs is set to the default value, the R-UIM
3           shall a) accept the SPC change (see 3.3.6 of [13]), b) set the Result Code to ‘00’,
4           “Accepted - Operation successful”, c) set the Block ID to the received parameter block
5           identifier and d) set the stored SPCs to SPCr received in the message.
 6   CR9    If the Validate Request Message contains the Change SPC Parameter Block,
 7          SP_LOCK_STATE = ‘0’, the stored SPCs is set to the default value and bit 5
 8          (SPC_Change_Enable) of EFOTAPASPC is set to ‘1’ (to deny SPC change), the R-UIM shall
 9          set the Result Code to ‘0C’, “Rejected - SPC change denied by the user” and shall set
10          the Block ID to the received parameter block identifier.
11   CR10 If the Validate Request Message contains the Change SPC Parameter Block,
12        SP_LOCK_STATE = ‘0’ and the stored SPCs is not set to the default value, the R-UIM
13        shall a) set the stored SPCs to SPCr received in the message, b) set the Result Code
14        to ‘00000000’, “Accepted - Operation successful” and c) the Block ID to the received
15        parameter block identifier.

16   CR11 If the Validate Request Message contains the Validate SPASM Parameter Block, if
17        EFNAMLOCK has been updated by UPDATE BINARY and if bit 3 (OTA_MODE) in
18        EFNAMLOCK is set to ‘0’ (user-initiated programming session) - see Sec. 3.2.1 of [13]),
19        the R-UIM shall set the Result Code to ‘0E’, “Rejected – Block ID not expected in this
20        mode” and shall set the Block ID to the received parameter block identifier.
21   CR12 If the Validate Request Message contains the Validate SPASM Parameter Block and
22        NAM_LOCK_STATE = ‘0’ in EFNAMLOCK, the R-UIM shall a) set the Result Code to ‘00’,
23        “Accepted - Operation successful”, b) set the Block ID to the received parameter
24        block identifier and c) set NAM_LOCKs stored in the R-UIM to NAM_LOCKr received
25        in the command.
26   CR13 If the Validation Request Message contains the Validate SPASM Parameter Block,
27        NAM_LOCK_STATE = ‘1’ in EFNAMLOCK and AUTH_OTAPAr received in the message
28        does not match the AUTH_OTAPA calculated by the R-UIM using the SPASM
29        Validation Procedure defined in Sec. 3.3.7 of [13], the R-UIM shall set the Result
30        Code to ‘0D’, “Rejected - Invalid SPASM” and shall set the Block ID to the received
31        parameter block identifier.
32   CR14 If the Validation Request Message contains the Validate SPASM Parameter Block,
33        NAM_LOCK_STATE = ‘1’ in EFNAMLOCK and AUTH_OTAPAr received in the message
34        matches the AUTH_OTAPA calculated by the R-UIM using the SPASM Validation
35        Procedure defined in Sec. 3.3.7 of [13], the R-UIM shall a) set the Result Code to ‘00’,
36        “Accepted - Operation successful” b) set the BLOCK_ID to the received parameter
37        block identifier, c) set the NAM_LOCK_STATE to ‘0’ and d) set the stored
38        NAM_LOCKs to the NAM_LOCKr received in the message.

39   CR15 After the R-UIM successfully changes the SPC in EFSPC (VALIDATE with Change SPC)
40        and after receiving the COMMIT Request, then the EFSPCS shall correctly reflect the
41        current state of EFSPC.
1       CR16 After the R-UIM successfully changes the NAM_LOCK (VALIDATE with Validate
2            SPASM) and after receiving the COMMIT Request, then EFNAMLOCK shall correctly
3            reflect NAM_LOCK (bit 2).

4       CR1 through CR14 are based on section 3.3.1 of [13]. CR15 is based on section 3.4.36
5       EFSPCS of [1]. CR16 is based on section 3.4.21 EFNAMLOCK of [1]. Any CR related to
6       SP_LOCK_STATE and EFSPCS is also based on section x.x (New section in C.S0023-D vx.x –
7       See Contribution C10-20110523-021).

8    1.1.1.3     Test Purpose
9    Verify that the VALIDATE function conforms to the above requirements.

10   1.1.1.4     Method of Test

11   1.1.1.4.1       Initial Conditions

12     1) The R-UIM is connected to an ME Simulator.

13     2) EFSPC = ‘00 00 00’.

14     3) EFOTAPASPC = ‘00’

15     4) EFSPCS = ‘00’

16     5) EFNAMLOCK = ‘04’

17     6) The A-key in the ME simulator is matched to that in the R-UIM.

18   1.1.1.4.2       Procedure

19      a) The ME Simulator resets the R-UIM.
20      b) The ME Simulator gains ADM access to the R-UIM using a card specific procedure.

21      c) The ME Simulator sends a VERIFY CHV with CHV1 command to the R-UIM.

22      d) The ME Simulator sends a SELECT command to the R-UIM to select DFCDMA.
23      e) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
24         ‘80’ and RANDSeed = ‘00 00 00 00’.
25             The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
26             executed with length SW2 of the response data.

27      f) The ME Simulator sends a GET RESPONSE command to the R-UIM.

28             The R-UIM shall return Result Code=‘00’ (Accepted – Operation successful) and NAM_LOCK
29             indicator=’00’.

30      g) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘FF’
31         (Reserved Block ID) and Block Length=‘00’.
32             The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
33             executed with length SW2 of the response data.
1    h) The ME Simulator sends a GET RESPONSE command to the R-UIM.

2      The R-UIM shall return Block ID=‘FF’ and Result Code=‘07’ (Rejected -          Block ID not
3      supported). [CR1]

4    i) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘00’ and
5       Block Length=‘00’.
6      The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
7      executed with length SW2 of the response data.

8    j) The ME Simulator sends a GET RESPONSE command to the R-UIM.
 9     The R-UIM shall return Block ID=‘00’ and Result Code=‘02’ (Rejected – Data size mismatch).
10     [CR2]

11   k) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘00’, Block
12      Length=‘03’ and Parameter Data = ‘0A 00 00’ (This Parameter Data is invalid since it
13      must be BCD encoded).

14     The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
15     executed with length SW2 of the response data.

16   l) The ME Simulator sends a GET RESPONSE command to the R-UIM.

17     The R-UIM shall return Block ID=‘00’ and Result Code=‘04’ (Rejected – Invalid parameter).
18     [CR3]

19   m) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘00’, Block
20      Length=‘03, and Parameter Data=‘01 01 01’ (incorrect SPC code).
21     The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
22     executed with length SW2 of the response data.

23   n) The ME Simulator sends a GET RESPONSE command to the R-UIM.

24     The R-UIM shall return the Block ID=‘00’ and Result Code=‘0B’ (Rejected - Invalid SPC).
25     [CR5]

26   o) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘01’, Block
27      Length=‘03’, Parameter Data=‘00 00 01’.
28     The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
29     executed with length SW2 of the response data.
30   p) The ME Simulator sends a GET RESPONSE command to the R-UIM.

31     The R-UIM shall return Block ID=‘01’ and Result Code=‘00’ (Accepted – Operation
32     successful). [CR8]

33   q) The ME Simulator sends a COMMIT command to the R-UIM.
34   r) The ME Simulator sends a GET RESPONSE command to the R-UIM.

35     The R-UIM shall return a Result Code=‘00’ (Accepted – Operation successful).

36   s) The ME Simulator sends a SELECT command to the R-UIM to select EFSPCS.
1    t) The ME Simulator sends a READ BINARY command to the R-UIM.

2          The data string returned shall be ‘01’. [CR8,15]

3    u) The ME Simulator sends a SELECT command to the R-UIM to select EFSPC.

4    v) The ME Simulator sends a READ BINARY command to the R-UIM.
5          The data string returned shall be ’00 00 01’. [CR8,15]

6    w) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
7       ‘00’ and RANDSeed = ’00 00 00 00’.
8          The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘06’ – correctly
9          executed with length SW2 of the response data.

10   x) The ME Simulator sends a GET RESPONSE command to the R-UIM.

11         The R-UIM shall return Result Code=‘00’ (Accepted – Operation successful) and NAM_LOCK
12         indicator=’00.

13   y) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
14      ‘80’ and RANDSeed = ’00 00 00 00’.
15   z) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘00’, Block
16      Length=‘03’, Parameter Data=‘00 00 01’.

17         The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
18         executed with length SW2 of the response data.

19   aa) The ME Simulator sends a GET RESPONSE command to the R-UIM.

20          The R-UIM shall return Block ID=‘00’ and Result Code=‘00’ (Accepted – Operation
21          successful). [CR6]

22   bb) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘01’, Block
23       Length=‘03’, Parameter Data=‘00 00 00’ (change SPC to a default value).
24          The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
25          executed with length SW2 of the response data.

26   cc) The ME Simulator sends a GET RESPONSE command to the R-UIM.
27          The R-UIM shall return Block ID=‘01’ and Result Code=‘00’ (Accepted – Operation
28          successful). [CR10]

29   dd) The ME Simulator sends a COMMIT command to the R-UIM.
30   ee) The ME Simulator sends a GET RESPONSE command to the R-UIM.

31          The R-UIM shall return a Result Code=‘00’ (Accepted – Operation successful).

32   ff)    The ME Simulator sends a SELECT command to the R-UIM to select EFSPCS.

33   gg) The ME Simulator sends a READ BINARY command to the R-UIM.
34          The data string returned shall be ‘00’. [CR10,15]

35   hh) The ME Simulator sends a SELECT command to the R-UIM to select EFSPC.
1    ii)   The ME Simulator sends a READ BINARY command to the R-UIM.

2          The data string returned shall be ’00 00 00’. [CR10,15]

3    jj)   The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
4          ‘00’ and RANDSeed = ’00 00 00 00’.
5          The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
6          executed with length SW2 of the response data.

7    kk) The ME Simulator sends a GET RESPONSE command to the R-UIM.

8          The R-UIM shall return Result Code=‘00’ (Accepted – Operation successful) and
9          NAM_LOCK indicator=’00’.

10   ll)   The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
11         ‘80’ and RANDSeed = ’00 00 00 00’.
12   mm) The ME Simulator sends a SELECT command to the R-UIM to select EFOTAPASPC.

13   nn) The ME Simulator sends an UPDATE BINARY command to the R-UIM with ‘10’
14       (EFOTASPCS = ‘10’ to indicate that the user denies permission for the service provider to
15       change the value of SPC).

16   oo) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘01’, Block
17       Length=‘03’, Parameter Data=‘00 00 11’.
18         The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
19         executed with length SW2 of the response data.

20   pp) The ME Simulator sends a GET RESPONSE command to the R-UIM.
21         The R-UIM shall return Block ID=‘01’ and Result Code=‘0C’ (Rejected – SPC changed
22         denied by the user). [CR9]

23   qq) The ME Simulator sends a SELECT command to the R-UIM to select EFOTAPASPC.

24   rr) The ME Simulator sends an UPDATE BINARY command to the R-UIM with ‘00’.

25   ss) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
26       ‘00’ and RANDSeed = ’00 00 00 00’
27   tt)   The ME Simulator sends an OTAPA REQUEST command to the R-UIM with Start_Stop=
28         ‘80’ and RANDSeed = ’00 00 00 00’.

29   uu) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID=‘02’, Block
30       Length=‘01’, Parameter Data=‘40’ (AUTH_OTAPA_INCL=’0’ and NAM_LOCK=’0’).
31         The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
32         executed with length SW2 of the response data.
33   vv) The ME Simulator sends a GET RESPONSE command to the R-UIM.

34         The R-UIM shall return Block ID=‘02’ and Result Code=‘00’ (Accepted – Operation
35         successful). [CR12]

36   ww) The ME Simulator sends a COMMIT command to the R-UIM.
1    xx) The ME Simulator sends a GET RESPONSE command to the R-UIM.

2           The R-UIM shall return a Result Code=‘00’ (Accepted – Operation successful).

3    yy) The ME Simulator sends a SELECT command to the R-UIM to select EFNAMLOCK.

4    zz) The ME Simulator sends a READ BINARY command to the R-UIM.
5           The data string returned shall be ‘06’. [CR12,16]

6    aaa) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with
7         Start_Stop= ‘00’.

8    bbb) The ME Simulator sends a SELECT command to the R-UIM to select EFNAMLOCK.
9    ccc)    The ME Simulator sends a UPDATE BINARY command to the R-UIM with ‘07’.

10   ddd) The ME Simulator sends an OTAPA REQUEST command to the R-UIM with
11        Start_STOP = ‘80’ and RANDSeed = ’00 00 00 00’.
12           The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘06’ – correctly
13           executed with length SW2 of the response data.

14   eee)    The ME Simulator sends a GET RESPONSE command to the R-UIM.

15           The R-UIM shall return Result Code=‘00’ (Accepted – Operation successful), NAM_LOCK
16           indicator=‘01’, and RAND OTAPA.

17   fff)    The ME Simulator generates AUTH_OTAPA based on RAND OTAPA and the R-UIM’s
18           SSD-A and A-key.

19   ggg) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID =‘02’,
20        Block Length=‘03’, and AUTH_OTAPA from the previous step.
21           The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
22           executed with length SW2 of the response data.

23   hhh) The ME Simulator sends a GET RESPONSE command to the R-UIM.

24           The R-UIM shall return the Block ID=‘02’ and Result Code=‘00 (Accepted – Operation
25           successful), access to the NAM parameters and indicators are no more protected by
26           SPASM, i.e. NAM_LOCK_STATE is set to ‘0’). [CR14]

27   iii)    The ME Simulator sends a SELECT command to the R-UIM to select EFNAMLOCK.

28   jjj)    The ME Simulator sends a READ BINARY command to the R-UIM.

29           The data string returned shall be ‘06’. [CR14]

30   kkk) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID =‘02’,
31        Block Length=‘03’, and AUTH_OTAPA = ’00 00 00’ parameter (incorrect SPASM
32        validation).
33           The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
34           executed with length SW2 of the response data.

35   lll)    The ME Simulator sends a GET RESPONSE command to the R-UIM.
1           The R-UIM shall return the Block ID=‘02’ and Result Code=‘0D’ (Rejected – Invalid
2           SPASM). [CR13]

3    mmm) The ME Simulator sends a SELECT command to the R-UIM to select EFNAMLOCK.

4    nnn) The ME Simulator sends an UPDATE BINARY command to the R-UIM with ‘00’.

5    ooo) The ME Simulator sends a VALIDATE command to the R-UIM with Block ID =‘02’,
6         Block Length=‘01’, and Parameter Data = ‘00’.

7           The status condition returned by the R-UIM shall be SW1=‘9F’, SW2=‘02’ – correctly
8           executed with length SW2 of the response data.

9    ppp) The ME Simulator sends a GET RESPONSE command to the R-UIM.

10          The R-UIM shall return the Block ID=‘02’ and Result Code=‘0E’ (Rejected – BLOCK ID not
11          expected in this mode). [CR11] (Note: It’s not clear in [1] how to indicate to the R-UIM that
12          the User Initiated programming session has been terminated).

13   Note: The following steps restore the values of the initial conditions:

14   qqq) The ME Simulator sends a SELECT command to the R-UIM to select EFNAMLOCK.
15   rrr)   The ME Simulator sends an UPDATE BINARY command to the R-UIM with ‘04’.

16   sss)   The ME Simulator sends a SELECT command to the R-UIM to select EFSPC.

17   ttt)   The ME Simulator sends an UPDATE BINARY command to the R-UIM with ’00 00 00’.
18   uuu) The ME Simulator sends a SELECT command to the R-UIM to select EFSPCS.

19   vvv) The ME Simulator sends an UPDATE BINARY command to the R-UIM with ’00’.

20   www) The ME Simulator sends a SELECT command to the R-UIM to select EFOTAPASPC.

21   xxx) The ME Simulator sends an UPDATE BINARY command to the R-UIM with ‘00’.

22

				
DOCUMENT INFO
Categories:
Tags:
Stats:
views:5
posted:3/18/2012
language:English
pages:8