Bug #1836: Re-Synchronization does not work as described in sysmousim-manual - pySim - Open Source Mobile Communications

Custom queries

all-by-project

Actions

Copy link

Bug #1836

closed

Re-Synchronization does not work as described in sysmousim-manual

Added by wirelesss over 7 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

High

Assignee:

wirelesss

Category:

Target version:

Start date:

11/03/2016

Due date:

% Done:

100%

Spec Reference:

Description

As per received information from our customer in RT# 6830, Re-Synchronization does not work as described in https://www.sysmocom.de/downloads/sysmousim-manual.pdf
Issue has been reproduced and log file attached.

Package: libosmocore
Version: 0.9.3.20

Files

re-sync_4.log	re-sync_4.log	2.11 KB		wirelesss, 11/03/2016 04:02 PM
re-sync_2.log	re-sync_2.log	2.14 KB		wirelesss, 11/04/2016 05:35 PM
re-sync_5_APDUs.log	re-sync_5_APDUs.log	6.91 KB	Log file with sent/received APDUs	wirelesss, 11/28/2016 10:56 AM
resync_succ.log	resync_succ.log	7.53 KB	Log file	wirelesss, 12/05/2016 12:39 PM

History
Notes
Property changes

Actions

Copy link

Updated by wirelesss over 7 years ago

File deleted (~~re-sync.log~~)

Actions

Copy link

Updated by wirelesss over 7 years ago

File re-sync_4.log re-sync_4.log added

Actions

Copy link

Updated by wirelesss over 7 years ago

File re-sync_2.log re-sync_2.log added

Actions

Copy link

Updated by laforge over 7 years ago

Assignee set to wirelesss

please escalate this further and try to get a response on why it behaves this way.

Actions

Copy link

Updated by laforge over 7 years ago

Priority changed from Normal to High

Actions

Copy link

Updated by laforge over 7 years ago

Project changed from Cellular Network Infrastructure to SIM card related Projects

Actions

Copy link

Updated by laforge over 7 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by wirelesss over 7 years ago

File re-sync_4.log added
File re-sync_5_APDUs.log re-sync_5_APDUs.log added

Ticket #138 has been created in the customer support portal of the manufacturer.
Related log files where re-synchronization issue has been reproduced are enclosed as log files.

Actions

Copy link

Updated by wirelesss over 7 years ago

% Done changed from 10 to 30

Actions

Copy link

#10

Updated by wirelesss over 7 years ago

File deleted (~~re-sync_4.log~~)

Actions

Copy link

#11

Updated by wirelesss over 7 years ago

File resync_succ.log resync_succ.log added
% Done changed from 30 to 40

As per TS 33.102 release 11, Annex C, "Management of sequence numbers which are not time-based" and in regards to the generation of sequence numbers the following parameter values are suggested for reference:

Length of IND in bits = 5

for the verification of sequence numbers in the USIM:
Length of the array: a = 32

In our case value 3 has been used which is low and does not satisfy requirement related to Length of IND in bits.

When using higher value (i.e. 64) successful re-synchronization is performed. Please see attached resync_succ.log file.

Actions

Copy link

#12

Updated by wirelesss over 7 years ago

% Done changed from 40 to 50

This update comes as an addition to the above mentioned comment and for the sake of clarity.

A SQN value higher than the one determined by the AUTS procedure must be used as input to osmo-auc-gen to generate a new authentication quintuples (-s parameter).

The SQN value has to be such one that at least causes a changes of bit 2 ⁵ or bit 6.
Please refer to 3GPP TS 33.102 Release 11, annex C. 3.2, "Management of sequence numbers which are not time-based", where the following parameter values are suggested for reference:

Length of IND in bits = 5
Length of the array: a = 32

The last one relates to verification of sequence numbers in the USIM. Minimum value that satisfies the requirements is a value that is achieved by applying incremental step of 32.

Actions

Copy link

#13

Updated by wirelesss over 7 years ago

% Done changed from 50 to 80

Chapter 6.2.4 Re-Synchronization in sysmoUSIM User manual has been edited in accordance with 3GPP TS 33.102 Release 11, annex C. 3.2, "Management of sequence numbers which are not time-based. Our customer has been informed accordingly.

Actions

Copy link

#14