> So the spec says, ME PDN ACT can come even for an implicit context
> activation request associated with CGATT, which is the case with EPS.
> For 3G, if this happens (ME PDN ACT) for UE initiated activation of
> context, then the cid is already set with CGDCONT.
> For EPS this can happen for default context, where cid is not set with
> CGDCONT, but is in the range as returned by CGDCONT.
> Here the cid issue, because cid is managed by ofono and is never
> communicated to modem. Probably to avoid sending too many CGDCONT's
> during startup. or is it something else?
> I thought the default context activation will come to TE as NW ACT, with
> a cid not in range of CGDCONT.
Exactly so the idea to avoid any issue was to call ofono_gprs_set_cid_range from the
driver with a range which doesn't include the CID used for initial EPS context.
Normaly we know from the modem vendor which CID will be used for the initial EPS
For instance if +CGDSCONT=? Is returning 1-25 as range then we call
ofono_gprs_set_cid_range with 2-25 as range assuming that CID 1 will be used for the
initial EPS context.
Ok so you are assuming that cid 1 will be always used for
context, and so this is work around for the issue.
Instead we could also expect it to have a unique id.
I still feel that the default context should be a NW initiated context
and will have a unique cid.
Also why can't the context id management be done in modem instead of ofono?