Another explanation:
https://www.ericsson.com/research-blog/robust-scrambling-nb-iot-broadcast-channels/
Another explanation:
https://www.ericsson.com/research-blog/robust-scrambling-nb-iot-broadcast-channels/
@andre-rodenburg said in Change of scrambling parameter:
Will the new manual be ready before tuesday?
Btw, why did you decide to implement the new scrambling feature?Good luck!
Hey Andre,
It is necessary for the next generations nb-iot chipsets. Later on, it will not be possible to switch scrambling off anymore.
You can find more details regarding CR 354 and CR 338 here:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&versionId=52094&release=189
Hi all! We have decided to not to divide the change in 3 regions and 3 nights.
Change will be done during the night of tuesday 17 april to wednesday 18 april.
Hey Adriaan! Dat is gek. Dat heeft niet met de library te maken dacht ik. Die zit namelijk al op jouw module.
@techniek , heb jij een idee?
Bijna…
Zodra wij UDP berichten supporten op ons netwerk. Of nu al als je deze CoAp library werkend krijgt op je module: https://github.com/otheruse/NeulMessenger
Hey @withthegrid! Cool to hear from you.
That’s because you are one of the very early access users. Before 2018 we didn’t have the IoT T-Mobile portal and Device Registration Tool yet. I will send you a direct message with the credentials.
Just like you, Sodaq has an application in our IoT-network. Before Sodaq provided you the device, they registrered the IMEI number in their application.
That means that there is a double registration of the same IMEI in our IoT-network. Hence, our network is not showing the data of the IMEI to anyone. Because there are two people now who claim to be the owner of the same IMEI.
Just checked, but the RawData device profile was already attached to your application.
Do you have a Sodaq device? If yes, did you ask Sodaq to unregister your IMEI number in their application?
We finally have some new dates for the upgrade on our radio network.
After this upgrade you’ll need to change some config parameters on your devices to match the new RAN version:
AT+NCONFIG=CR_0354_0338_SCRAMBLING,TRUE
AT+NCONFIG=CR_0859_SI_AVOID,TRUE
Or (new syntax)
AT+NCONFIG=“CR_0354_0338_SCRAMBLING”,“TRUE”
AT+NCONFIG=“CR_0859_SI_AVOID”,“TRUE”
The network change schedule is based on 3 regions:
North = 16 April
Mid = 17 April
South = 18 April
We will share a detailed map next week!
Yeap, that’s right. The Neul Messaging Protocol (NMGS) is not supported anymore on these modules. However, there are two solutions:
By the way! Did you try it with our without scrambling? Scrambling should be switched off.
AT+NCONFIG=CR_0354_0338_SCRAMBLING,FALSE
Hi @voske65 thanks for sharing this informations here and it was nice to meet you yesterday!
I’ve reached out to the heroes from our terminal testing team and radio access network and will get back to you soon
Yeap!! This was the problem. Thank you for the heads up @Andre-Rodenburg! Really appreciate it
@TCS, can you please try again?
Waardevol deze info!
Nog even voor de zekerheid: je hebt nu getest met SARA N211 02B-00, correct?
En welke firware versie staat er nu op?
That’s great news. Support for UDP passtrough is scheduled on our roadmap (apologies, only in Dutch). We aim to support UDP passtrough before the summer. However, if you are ready around the end of this month, we can test it on our PoC environment.
Please keep us posted!
Helemaal correct! Uit mijn hoofd weet ik alleen wel dat de BG96 geen Non-IP ondersteunt. Maar wellicht niet relevant voor jouw use case en needs!
@andre-rodenburg Thanks
Ben heel benieuwd naar de resultaten met nieuwe firmware. Hoor het graag!
Zou je mij aub in een pm kunnen laten weten vanaf welk adres en postcode je test? Dan weet ik zeker dat we naar de juiste cell kijken!
If I understand your question correctly: yes, this should be possible. with Long Periodic TAU: https://forum.iot.t-mobile.nl/topic/41/power-saving-met-nb-iot/
@Jasper @Richard-Marijs @Eric-Barten @ericbarten
Do you know when we will support Long Periodic TAU?
In ieder geval wel omtrent energieconsumptie. Maar ik ben heel benieuwd naar welke functionaliteiten en wat voor performance je precies op zoek bent. Let me know!
Wij hebben het probleem niet (meer). We hebben op dit moment onze apparatuur al ruim 240 uur in deep sleep mode (zonder dat het na 2 uur disconnect dus).
Maar @Andre-Rodenburg en @felixdonkers feit dat jullie het nog wel hebben zit dan denk ik toch in een combi van device - firmware - parameters op ons radio netwerk.
Zouden jullie kunnen aangeven
Hoor het graag!
Is er tijdens die RSRP ‘0’ dan ook helemaal geen coverage en/of network attach @felixdonkers ?
Interessante info!