protocol

1.dashboard configuration of protocol stack is not feasible because every layer setup
needs info about the previous layer and next layer
2.alternative is to do the setup within a layers context
3.when in the context it sets up the next layer , depth layers can be returned back

android graphics

1.graphics system is based on pipeline
2.A-->B-->rendering
3.in android there is the concept of surfaces,layers
4.its kind of stack arrangement where we see things that are on top
5.a layer can have multiple surfaces and multiple windows
6.a surface gets pushed to hardware for rendering

protocol state machine

below are some state handling scenarios
1.before sending connection request, complete comes
2.before connection request pending, complete comes
3.without a previous connection, connection reconfiguration comes
4.without a previous connection, close comes
5.without sending a connection request accept or reject comes

baseline for some of the in/out requests, checking of states are mandatory
some of them passes through this first layer, another layer of checking


sometimes state transition calls are synchronous
1.nas connection request may call rrc connection request and wait till it is completed
before changing its state

work flow

1.total work progress should follow the ratio of 80/20
2. 80 on abstract level -- tgt
3. 20 on paper -- code