-
Notifications
You must be signed in to change notification settings - Fork 3k
cellular: eps ciot optimization network support check #8709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@mirelachirica Please review |
Can you fix please? |
@@ -198,6 +200,7 @@ class AT_CellularNetwork : public CellularNetwork, public AT_CellularBase { | |||
nsapi_ip_stack_t _ip_stack_type; | |||
int _cid; | |||
Callback<void(nsapi_event_t, intptr_t)> _connection_status_cb; | |||
Callback<void(Supported_Network_Opt)> _ciot_network_support_cb; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would include "opt" in the name of the callback _ciotopt_network_support_cb or _ciot_opt_network_support_cb.
@@ -55,6 +55,7 @@ class CellularNetwork : public NetworkInterface { | |||
optimization. */ | |||
SUPPORTED_UE_OPT_MAX | |||
}; | |||
typedef Supported_UE_Opt Supported_Network_Opt; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about one type which doesnt have UE or network in the name of the values and it could be used bithe as UE and network values? Like:
enum CIoT_Opt {
CIOT_OPT_NO_SUPPORT
CIOT_OPT_CONTROL_PLANE
....
* @param preferred_opt Preferred CIoT EPS optimizations. | ||
* @param network_support_cb This callback will be called when network optimisation support is known |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when network CIoT optimisation support
_ciot_network_support_cb(supported_network_opt); | ||
} | ||
} | ||
|
||
nsapi_error_t AT_CellularNetwork::get_ciot_optimization_config(Supported_UE_Opt &supported_opt, | ||
Preferred_UE_Opt &preferred_opt) | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This API name should be changed to indicate that this will return UE ciot optimizations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a getter for the Network's ciot optimization is needed. Some flag/member to be set in urc_cciotopti()?
|
||
/** Get Network CIoT optimizations. | ||
* | ||
* @param supported_opt Supported CIoT EPS optimizations. CIOT_OPT_MAX will be returned, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
supported_opt -> supported_network_opt Network supported CIoT EPS optimizations.....
Could you still have 2 commits only? One for astyle fixes and one for the "cellular: ciot eps optimization support". Now there is a third commit which has both kind changes. |
That is not true. My mistake. Still the CIoT optimization changes better be in one commit than split in two commits which are not functional/logical splits. |
@TeemuKultala Mind rebasing so that we can get CI started? |
/morph build |
Build : SUCCESSBuild number : 3657 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 3264 |
@ARMmbed/mbed-os-maintainers note: This one still needs a maintainer review |
The best to avoid suprised, can you rebase on top of master to update travis config (this would error with the new config). This still needs to be addressed here, please update the code |
I fail to find how this is breaking and why it is breaking. Please explain in the commit (the first commit that is the most important should be expanded). My/our expectation for even functionality change is to have at least one paragraph in the commit message to introduce the change (it's not few lines fix). |
-added an API for checking network eps ciot optimization support -renamed the API for getting the UE parameters -the API for setting the UE parameters includes now a callback, which will be called once network support for eps ciot optimization is known
Is this breaking, how? |
Preferred_UE_Opt preferred_opt) = 0; | ||
virtual nsapi_error_t set_ciot_optimization_config(CIoT_Supported_Opt supported_opt, | ||
CIoT_Preferred_UE_Opt preferred_opt, | ||
Callback<void(CIoT_Supported_Opt)> network_support_cb) = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@0xc0170: I assume is breaking because of this change and the one from line 278 bellow, renaming
get_ciot_optimization_config ->get_ciot_ue_optimization_config
@AnttiKauppila that's marked as a breaking change, we are committed to maintaining backward compatibility. Is this necessary, can we not massage it so it doesn't break the public APIs? |
Changing the enum values are also a breaking change, CIoT_ was added, was there a name clash of some sort @TeemuKultala? If we don't change the namings and modify that added callback to be a pointer (defaulting to NULL) then this would be a minor break and would be fine for 5.11. |
@AnttiKauppila The support enum was previously referring to UE values, but is now used for both network and UE values, and therefore more common name taken into use. The preferred enum changed to be consistent with the supported enum. CCIOTOPTI is a Rel-14 feature, so most likely there are few, if any, users for this API |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new feature which is needed in 5.12. This is breaking a functionality which was not even working fully earlier and therefore the "breaking" thing is not critical here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CI started |
Test run: SUCCESSSummary: 4 of 4 test jobs passed |
This needs to go to a feature branch |
This is the feature branch PR: #8979 |
Closing since #8979 already came in. |
Description
CCIOTOPTI URC handler added, tested with unittests, no HW support currently available to test with
Pull request type