WS/T 543.6-2017Resident health card technical specifications - Part 6: Testing requirements of user card and terminal products (English PDF)

4.1 Single test

The user card is encapsulated by a chip, a chip operation system (COS) and a card. Therefore, for each order the test requirements for all items are shown in Table 1.

4.2 Comprehensive testing

4.2.1 User Card

The user card testing items and requirements are shown in Table 2.

5.1 Upper and lower limits of operating temperature

5.1.1 Test purpose

Verify that the working temperature of the IC card meets the requirements.

5.1.2 Testing requirements

Under the condition of 0°C~50°C, the card should work normally without deformation and no obvious change in appearance.

5.1.3 Detection method

--The upper limit test of working temperature should be carried out in accordance with "Test Bd" or "Test Bb" in GB/T 2423.2, and the test time is 2 hours;

--The test of the lower limit of working temperature should be carried out in accordance with "Test Ad" or "Test Ab" in GB/T 2423.1, and the test time is 2 hours;

5.2 Surface printing compliance test

5.2.1 Test purpose

Verify that the IC card's printing pattern and text position, printing color difference, and printing fastness meet the requirements.

5.2.2 Testing requirements

--The position of the printed pattern and text should meet the relevant requirements of WS 543.2;

--Bar code and magnetic stripe should be able to be read correctly;

--The color difference between the test sample card and the standard sample card ab <=5.00;

--After.200 cycles of abrasion test, visually inspect the image, color, and characters of the card, and there should be no obvious changes.

5.2.3 Detection method

Use relevant testing equipment for testing.

5.3 Random characteristics of random numbers

5.3.1 Test purpose

Verify that the randomness of the random number generated by the user card random number generator meets the relevant security requirements.

5.3.2 Testing requirements

The randomness of the random number should conform to the frequency test, intra-block frequency test, run-length test, NIST SPECIAL PUBLICATION 800-22 Longest run test in a block, binary matrix test, discrete Fourier transform test, non-overlapping template matching test, overlapping template matching test, MAURER'S general statistical test, linear complexity test, continuous test, approximate entropy test, cumulative sum test, random drift test, random 15 requirements such as machine drift and variation test.

5.3.3 Detection method

Analyze the random number generated by the IC card.

5.4 User card COS detection

5.4.1 Basic requirements

To ensure the correctness of the user card function and the safety of its use, the user card COS function should comply with WS 543.2, WS 543.3, According to the requirements of WS 543.4, the carrier should be a chip that has been filed with the National Health and Family Planning Commission.

口Access. See WS 543.2 for the user card file structure.

5.4.2 Application function test

5.4.2.1 Reading card identification data area information

--Test purpose. verify that the user card can complete the basic data area of the card (MF\\DDF1\\EF05, MF\\DDF1\\EF06, MF\\DDF1\\EF07 and MF\\DDF1\\EF08).

--Testing requirements. It should meet the relevant requirements of 6.1.1 in WS 543.3-2017.

--Detection method. According to the process description in 6.1.1 of WS 543.3-2017, perform the card basic data area (MF\\DDF1\\EF05, MF\\DDF1\\EF06, MF\\DDF1\\EF07 and MF\\DDF1\\EF08) data read.

5.4.2.2 Write card identification data area information

--Test purpose. verify that the user card can complete the information update of the card's basic data area (MF\\DDF1\\EF07 and MF\\DDF1\\EF08) new.

--Testing requirements. It shall meet the relevant requirements of 6.1.2 in WS 543.3-2017.

--Detection method. According to the process description in 6.1.2 of WS 543.3-2017, perform the card basic data area (MF\\DDF1\\EF07 and MF\\DDF1\\EF08) data update.

5.4.2.3 Reading card identification data area information (read DF01 application data)

--Test purpose. verify that the user card can complete the identification data area (MF\\DDF1\\DF01\\EF05, MF\\DDF1\\DF01\\EF06, MF\\DDF1\\DF01\\EF07 and MF\\DDF1\\DF01\\EF08) information is read.

--Testing requirements. should meet the relevant requirements of 6.2.1 in WS 543.3-2017.

--Detection method. According to the process description in 6.2.1 of WS 543.3-2017, carry out the identification data area (MF\\DDF1\\DF01\\EF05, MF\\DDF1\\DF01\\EF06, MF\\DDF1\\DF01\\EF07 and MF\\DDF1\\DF01\\EF08) Data read.

5.4.2.4 Write card identification data area information (write DF01 application data)

--Test purpose. verify that the user card can complete the identification data area (MF\\DDF1\\DF01\\EF05, MF\\DDF1\\DF01\\EF06, MF\\DDF1\\DF01\\EF07 and MF\\DDF1\\DF01\\EF08) are updated.

--Testing requirements. It should meet the relevant requirements of 6.2.2 in WS 543.3-2017.

--Detection method. According to the process description in 6.2.2 of WS 543.3-2017, carry out the identification data area (MF\\DDF1\\DF01\\EF05, MF\\DDF1\\DF01\\EF06, MF\\DDF1\\DF01\\EF07 and MF\\DDF1\\DF01\\EF08) Data Update.

5.4.2.5 Reading card basic health information data area information (read DF02 application data)

--Test purpose. To verify that the user card can complete the basic health information data area (MF\\DDF1\\DF02\\EF05, MF\\DDF1\\DF02\\EF06, MF\\DDF1\\DF02\\EF07 and MF\\DDF1\\DF02\\EF08) information read.

--Testing requirements. It should meet the relevant requirements of 6.3.1 in WS 543.3-2017.

--Detection method. Perform basic health information data area according to the process description in 6.3.1 of WS 543.3-2017 (MF\\DDF1\\DF02\\EF05, MF\\DDF1\\DF02\\EF06, MF\\DDF1\\DF02\\EF07 and MF\\DDF1\\DF02\\EF08) Data read.

5.4.2.6 Write card basic health information data area information (write DF02 application data)

--Test purpose. To verify that the user card can complete the basic health information data area (MF\\DDF1\\DF02\\EF05, MF\\DDF1\\DF02\\EF06, MF\\DDF1\\DF02\\EF07 and MF\\DDF1\\DF02\\EF08) are updated.

--Testing requirements. It shall meet the relevant requirements in 6.3.2 of WS 543.3.

--Detection method. According to the process description in 6.3.2 of WS 543.3, carry out the basic health information data area (MF\\DDF1\\DF02\\EF05, MF\\DDF1\\DF02\\EF06, MF\\DDF1\\DF02\\EF07 and MF\\DDF1\\DF02\\EF08) data update.

5.4.2.7 Record hospitalization information (read and write DF03 application data)

--Test purpose. verify that the user card can complete the writing of hospitalization information, that is, the management data area (MF\\DDF1\\DF03\\EF05 and MF\\DDF1\\DF03\\EE01~EE03) information is updated.

--Testing requirements. It should meet the relevant requirements of 6.4.1 in WS 543.3-2017.

--Detection method. According to the process description of 6.4.1 in WS 543.3-2017, manage the data area (MF\\DDF1\\DF03\\EF05 and MF\\DDF1\\DF03\\EE01~EE03) data update.

5.4.2.8 Record outpatient information (read and write DF03 application data)

--Test purpose. verify that the user card can complete the writing of outpatient information, that is, the management data area (MF\\DDF1\\DF03\\EF06 and MF\\DDF1\\DF03\\ED01~ED05) information is updated.

--Testing requirements. It should meet the relevant requirements of 6.4.2 in WS 543.3-2017.

--Detection method. According to the process description of 6.4.2 in WS 543.3-2017, perform the management data area (MF\\DDF1\\DF03\\EF06 and MF\\DDF1\\DF03\\ED01~ED05) data update.

5.4.2.9 Withdrawal and reimbursement of hospitalization expenses (read and write DF03 application data)

--Test purpose. verify that the user card can complete hospitalization reimbursement, that is, the management data area (MF\\DDF1\\DF03\\EF05 and MF\\DDF1\\DF03\\EE01~EE03) information read and update.

--Testing requirements. It should meet the relevant requirements of 6.4.3 in WS 543.3-2017.

--Detection method. According to the process description of 6.4.3 in WS 543.3-2017, perform the management data area (MF\\DDF1\\DF03\\EF05 and MF\\DDF1\\DF03\\EE01~EE03) data read and update.

5.4.2.10 Outpatient expense extraction and reimbursement (read and write DF03 application data)

--Test purpose. verify that the user card can complete the outpatient expense reimbursement process, that is, the management data area (MF\\DDF1\\DF03\\EF06 and MF\\DDF1\\DF03\\ED01~ED05) information is updated.

--Testing requirements. It should meet the relevant requirements in 6.4.4 of WS 543.3-2017.

--Detection method. According to the process description in 6.4.4 of WS 543.3-2017, manage the data area (MF\\DDF1\\DF03\\EF06 and MF\\DDF1\\DF03\\ED01~ED05) data update.

5.4.3 Command function test

5.4.3.1 APPLICATION BLOCK command

--Test purpose. to verify the correct function of the APPLICATION BLOCK command.

--Testing requirements. It should meet the relevant requirements of 5.3.1 in WS 543.4-2017.

--Detection method.

1) If external authentication is not performed, the application lock operation is performed, and the card should return the status code '6982';

2) If the random number is not taken and the application is locked, the card should return the status code '6984';

3) If there is no MAC, perform the application lock operation, and the card should return the status code '6700' or '6987';

4) If the MAC data is wrong, perform the application lock operation and the card should return the status code '6988';

5) According to the relevant application description of WS 543.3, the application should be locked after the temporary lock operation is performed correctly;

6) Select the temporarily locked application, the card should return the status code '6283' (selected file is invalid), and return to FCI at the same time;

7) For temporarily locked applications, perform an application temporary lock operation, and the card should return the status code '6985';

8) Select the locked application, and access to the files under the application should be prohibited.

9) Select the locked application, except for random numbers, internal authentication, external authentication, permanent application lock, card lock, application Except for unlocking, no other commands can be executed.

10) For temporarily locked apps, perform permanent app lock operations, and the card should return the status code '9000'.

11) After the application is permanently locked, any operation performed on the application except for the card lock command should return an error status code '9303'.

5.4.3.2 APPLICATION UNBLOCK command

--Test purpose. to verify the correct function of the APPLICATION UNBLOCK command.

--Testing requirements. It should meet the relevant requirements of 5.3.2 in WS 543.4-2017.

--Detection method.

1) According to the related application description of WS 543.3, perform an application unlock operation on a temporarily locked application, and the application should be unlocked;

2) Select the unlocked application, the card should return the status code '9000' (selected file is valid), and return to FCI at the same time;

3) After the application is unlocked, the read and write operations on the data under the application should be successful;

4) To unlock the permanently locked application, the card should return the status code '9303';

5) For an unlocked application, perform an application unlock operation, and the card should return the status code '6985';

6) If the external authentication is not performed, and the application is unlocked, the card should return the status code '6982';

7) If the random number is not taken and the application is unlocked, the card should return the status code '6984';

8) There is no MAC, and the application is unlocked, the card should return the status code '6700' or '6987';

9) If the MAC data is wrong, perform the application unlock operation, and the card should return the status code '6988'.

5.4.3.3 CARD BLOCK command

--Test purpose. to verify the correct function of the CARD BLOCK command.

--Testing requirements. should meet the relevant requirements of 5.3.3 in WS 543.4-2017.

--Detection method.

1) According to the relevant application description of WS 543.3, lock the card, the card should be locked;

2) After the card is locked, all applications in the card become invalid, all commands cannot be executed, and the card returns status code '6A81';

3) The card is locked without external authentication, the card should be returned with the status code '6982';

4) If the random number is not taken and the card is locked, the card should return the status code '6984';

5) If there is no MAC, if the card is locked, the card should return the status code '6700' or '6987';

6) If the MAC data is wrong, perform the card lock operation and the card should return the status code '6988'.

5.4.3.4

--Test purpose. to verify the correct function of the EXTERNAL AUTHENTICATION command.

--Testing requirements. It should meet the relevant requirements of 5.3.4 in WS 543.4-2017.

--Detection method.

1) According to the relevant description of WS 543.3, the external authentication operation should be successful;

2) If the random number is not taken and the external authentication operation is performed, the card should return the status code '6984';

3) Lc is not '11', for external authentication operation, the card should return the status code '6700';

4) If the wrong key is used for external authentication, the card should return the status code '6A88';

5) Identify data errors and perform external authentication operations. The card should return the status code '63Cx';

6) If the external authentication fails 16 times, the card should return the status code '6983';

7) The key version data should be supported.

5.4.3.5 GET CHALLENGE command

--Test purpose. to verify the correct function of the GET CHALLENGE command.

--Testing requirements. should meet the relevant requirements of 5.3.5 in WS 543.4-2017.

--Detection method.

1) The card should support 8-byte random number acquisition;

2) Le is '00', send a random number command, the card should return the status code '6700';

3) Le is '04', send a random number command, the card should return the status code '6700';

5.4.3.6 Command

--Test purpose. verify that the command function is correct.

--Testing requirements. should meet the relevant requirements of 5.3.6 in WS 543.4-2017.

--Detection method.

1) According to the relevant description of WS 543.3, the internal authentication operation should be successful;

2) Lc is not '11', for external authentication operation, the card should return the status code '6700';

3) The key version data should be supported.

5.4.3.7 READ BINARY command

--Test purpose. to verify the correct function of the READ BINARY command.

--Testing requirements. should meet the relevant requirements of 5.3.7 in WS 543.4-2017.

--Detection method.

1) According to the relevant application description of WS 543.3, the MF\\DDF1\\DF03\\EE01~EE05 and MF\\DDF1\\DF03\\ED01~ED05 Read byte by byte, it should be successful;

2) According to the related application description of WS 543.3, the MF\\DDF1\\DF03\\EE01~EE05 and MF\\DDF1\\DF03\\ED01~ED05 the maximum return byte read should be successful;

3) Without external authentication, the file is read, the card should return the status code '6982';

4) If no file is selected, send this command and the card should return the status code '6986';

5) Read the data beyond the offset address, the card should return the status code '6B00';

6) Le = '00', read 256 bytes from the first byte to be read; if the file has arrived before reading 256 bytes for the last byte, all bytes starting from the first byte to be read will be read.

7) When Le is incorrect, the card should return the status code '6Cxx', and'xx' is the actual length;

8) Read the log file, the card should return the status code '6981'.

5.4.3.8 READ RECORD command

--Test purpose. to verify the correct function of the READ RECORD command.

--Testing requirements. should meet the relevant requirements of 5.3.7 in WS 543.4-2017.

--Detection method.

1) According to the relevant application description of WS 543.3, read all the record files with the record number, and it should be successful;

2) According to the relevant application description of WS 543.3, the variable length record file should be successfully read using the record identifier;

3) To read the fixed-length record file using the record identifier, the card should return the status code '6985';

4) Without external authentication, the file is read, the card should return the status code '6982';

5) If the file is not selected, read the file, and the card should return the status code '6986';

6) When Le is not equal to the record length or '00', the card should return the status code '6700';

7) When Le is equal to the record length or equal to '00', the card should return all data and status code;

8) Read the binary file, the card should return the status code '6981'.

5.4.3.9 SELECT command

--Test purpose. to verify the correct function of the SELECT command.

--Testing requirements. should meet the relevant requirements of 5.3.9 in WS 543.4-2017.

--Detection method.

1) Select all files in the card through the file identifier, the card should return the status code '9000';

2) Select the user card application environment (DDF1) in the card and its DF file by file name or AID, and the card should return the status code '9000';

3) Choose DDF or DF file, the card should return FCI information, and the format is correct;

4) When the data field is empty, the card should select the MF file;

5) The card should support partial file name selection;

6) When Lc is inconsistent with P1 and P2, the card should return the status code '6700';

7) When the selected file identifier or file name or AID does not exist, the card should return the status code '6A82'.

5.4.3.10 UPDATE BINARY command

--Test purpose. verify the function of UPDATE BINARY command is correct.

--Testing requirements. It should meet the relevant requirements of 5.3.10 in WS 543.4-2017.

--Detection method.

1) According to the related application description of WS 543.3, the MF\\DDF1\\DF03\\EE01~EE05 and MF\\DDF1\\DF03\\ED01~ ED05 updates byte by byte, it should be successful;

2) Without external authentication, the file is updated, the card should return the status code '6982';

3) If no file is selected, send this command, and the card should return the status code '6986';

4) If the offset address exceeds EF, the card should return the status code '6B00';

5) When Lc is empty, the card should return the status code '6700';

6) Update the record file, the card should return the status code '6981';

7) MAC error, the card should return the status code '6988';

8) MAC error 5 times, the card should temporarily lock the current application.

9) After the application is temporarily locked, all files under the application are invalid.

5.4.3.11 UPDATE RECORD command

--Test purpose. verify the function of UPDATE RECORD command is correct.

--Testing requirements. It should meet the relevant requirements of 5.3.11 in WS 543.4-2017.

--Detection method.

1) According to the relevant application description of WS 543.3, update the fixed-length record or variable-length record file with the record number, and it should be successful;

2) According to the relevant application description of WS 543.3, use the "previous record" to update the cycle record file, which should be successful;

3) Use the designated record number to update the circular record file, and the card should return the status code '6985';

4) Use "previous record" to update the fixed-length record or variable-length record file, and the card should return the status code '6985';

5) When updating fixed-length records or variable-length record files, the record number is wrong, and the card should return the status code '6A83' or '6A84';

6) When updating the variable length record file, the record identifier is incorrect, the card should return the status code '6A85';

7) When updating the variable length record file, if the record content is incorrect, the card should return the status code '6A85';

8) Without external authentication, the file is updated, the card should return the status code '6982';

9) If the file is not selected, update the file and the card should return the status code '6986';

10) When Lc is empty, the card should return the status code '6700';

11) Update the binary file, the card should return the status code '6981';

12) MAC error, the card should return the status code '6988';

13) MAC error 5 times, the card should temporarily lock the application;

14) After the application is temporarily locked, all files under the application are invalid.

5.4.3.12 WRITE RECORD command

--Test purpose. to verify the correct function of the WRITE RECORD command.

--Testing requirements. It should meet the relevant requirements of 5.4.2 in WS 543.4-2017.

--Detection method.

1) According to the relevant application description of WS 543.3, the management data area (MF\\DDF1\\DF03\\EF05 and MF\\DDF1\\DF03\\EF06) Use the record number to write "00", it should be successful;

2) Use the designated record number to update other fixed-length record files and circular record files, and the card sh...