Bug #5036
closed
ns2: add support for BSS SNS procudures (e.g. adding a bind to a SNS on the BSS)
Added by lynxis about 3 years ago.
Updated over 2 years ago.
Description
When adding a new bind to a SNS, the SNS fsm must do procedures to inform the SGSN about the new binds/endpoint.
- Status changed from New to In Progress
- Priority changed from Urgent to High
- Status changed from In Progress to Stalled
- % Done changed from 0 to 40
- Status changed from Stalled to New
lynxis wrote:
I'm waiting for SNS SGSN patches.
merged now., uns-stalling
- Status changed from New to In Progress
- % Done changed from 40 to 50
I've reimplemented the change weight procedure with a different approach.
2x ttcn3 test case succeed now.
Next step is the ADD + DEL procedure. I've also a simpler approach for them now.
I've created 2x ttcn cases for sns_add and sns_del.
sns_add succeed, sns del not yet.
also add/del need more testcases and also unitest for the race and corner cases.
I've reconsidered my implementation and did it in a different way.
Also the ttcn3 test cases went some review and there is a new proposal in gerrit.
The last missing part is the SGSN side. The procedure work also for the SGSN side, but there are the following tasks left:
- ttcn3 test cases
- terminate the SNS connection similiar as of GPRS_SNS_EV_REQ_SELECT_ENDPOINT
- % Done changed from 50 to 80
- Status changed from In Progress to Feedback
- % Done changed from 80 to 90
- Status changed from Feedback to Stalled
until refcount handled. The SNS code has recursion problems.
- Status changed from Stalled to Closed
- % Done changed from 90 to 100
Also available in: Atom
PDF
