VM.PL Software House’s Post

This was one of the more difficult case studies I've enjoyed describing 😅, but the project was very interesting 😎. It involved many VM.PL Software House senior developers with a wealth of knowledge and experience in IoT, edge computing, cloud computing, and many other areas. Thank you Rafał Peno, for your incredible help in this #content creation😊 They created an industrial PC for a German client that integrates router and #IoT Edge functions to enable remote control of the system 🖥️. It also requires a high-security standard for devices that are not connected to the network or should be protected by an independent firewall 🔒. In addition to this, the device fleet #software (OEM) was built to be hyper-secure so that no one but the owner could access it 🔐, and at the same time, it could integrate with multiple devices 🔄. What were the different stages of implementation and the results of this project? Keep reading 👇

𝐈𝐧𝐝𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐞 𝐃𝐚𝐲, 𝐅𝐢𝐫𝐦𝐰𝐚𝐫𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭, 𝐚𝐧𝐝 𝐈𝐨𝐓: 𝐅𝐢𝐧𝐝𝐢𝐧𝐠 𝐏𝐚𝐫𝐚𝐥𝐥𝐞𝐥𝐬 𝐢𝐧 𝐅𝐫𝐞𝐞𝐝𝐨𝐦 𝐚𝐧𝐝 𝐈𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐨𝐧 🇮🇳 As we celebrate Independence Day, it’s a great opportunity to reflect on the concept of freedom—not just in our national context but also in the technologies we develop, particularly in the realms of firmware development and IoT 1. 𝐈𝐧𝐝𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐞 𝐚𝐧𝐝 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲: Just as Independence Day symbolizes the freedom to choose our path as a nation, agnostic firmware/software development represents the freedom to choose the best platforms and technologies without being locked into a single ecosystem. In IoT, this flexibility allows us to create solutions that are adaptable, scalable, and capable of integrating with a wide range of devices and protocols. 2. 𝐈𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐑𝐞𝐬𝐢𝐥𝐢𝐞𝐧𝐜𝐞: The fight for independence required innovative thinking, resilience, and the ability to adapt to changing circumstances. Similarly, in IoT and firmware development, innovation is key. By adopting an agnostic approach, we build systems that are resilient to change—whether it's evolving standards, emerging technologies, or new security challenges. This resilience ensures our solutions remain robust and future-proof. 3. 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐚𝐧𝐝 𝐒𝐨𝐯𝐞𝐫𝐞𝐢𝐠𝐧𝐭𝐲: Just as a nation must protect its sovereignty, IoT systems must be secure to protect data and maintain trust. Agnostic firmware/software development allows for consistent and strong security protocols across various platforms, ensuring that the entire system remains secure, much like how a nation safeguards its borders. 4. 𝐕𝐢𝐬𝐢𝐨𝐧 𝐟𝐨𝐫 𝐭𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞: Independence Day is not just a commemoration of the past but a vision for a brighter future. In the same way, developing agnostic firmware/software and IoT solutions is about building technology that stands the test of time. 5. 𝐍𝐚𝐭𝐢𝐨𝐧𝐚𝐥 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐚𝐧𝐝 𝐓𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐢𝐜𝐚𝐥 𝐏𝐫𝐨𝐠𝐫𝐞𝐬𝐬: Just as national independence set the stage for economic and social progress, technological independence drives innovation and growth in the tech industry. By adopting agnostic firmware/software development practices, we foster an environment where innovation thrives, unencumbered by the limitations of proprietary platforms. This approach not only accelerates development cycles but also enables rapid prototyping and deployment of cutting-edge solutions. As we celebrate the spirit of independence, let’s also embrace the freedom, resilience, and foresight that agnostic firmware/software development brings. It’s this technical independence that empowers us to build secure, adaptable, and future-ready solutions. 𝑯𝒂𝒑𝒑𝒚 𝑰𝒏𝒅𝒆𝒑𝒆𝒏𝒅𝒆𝒏𝒄𝒆 𝑫𝒂𝒚 ! 🇮🇳 #IndependenceDay #IoT #FirmwareDevelopment #EmbeddedSystems #Innovation #TechFreedom #iotplatform

🎤 why Interoperability Testing Required 5G(ORAN): 🔸 While the move to open RAN offers numerous benefits for MNOs, making it work means adopting rigorous testing requirements. 🔸 A few years ago, it was sufficient to simply test an Evolved Node B (eNB) as a complete unit in accordance with 3GPP requirements. 🔹 But the introduction of the open RAN and distributed RANs change the equation, requiring testing each component of the RAN in isolation for conformance to the standards and testing combinations of components for interoperability. 🎤 FH tests focused on the M-Plane IOT: 🔸 Start-up (O-RU start-up from the power-on of O-RU to the availability of service). 💠 Fronthaul M-Plane Architectural options 🔸 Hierarchical model: The O-RU is entirely managed by one O-DU (sudo) using a NETCONF based M-Plane interface. 🎤 Procedure: M-Plane start up test 🎤 M-plane IOT Test: 🔸 Netconf Client 🔸 By default, Netconf server running at O-RU is listening on port #830. 🔸 Following is the command used at netopeer2-cli to connect to the O-RU   $ netopeer2-cli   > connect --host <o-ru-ip-address> --port 830 --login root                        Interactive SSH Authentication Type your password:                        Password: admin123 💠 RPC execution 🔸 Following is the command to execute RPCs from netopeer2-cli:   > user-rpc --file <file.xml> --timeout 120 👉 Transport layer initialization 👉 RU calls home to NETCONF client (TCP connection establishment) 💠 Pre - Requisites: O1_MPLANE_CONN_METHOD=CALLHOME        Set below mentioned fields in /o1_config.cfg file on the O-RU side   O1_MPLANE_CONN_METHOD=CALLHOME NETCONF_CONNECTION_PROTOCOL=SSH   Set the DU IP address in /o_ran_transport.cfg ODU_IPADDRESS=<DU_IP_ADDERESS>  🔸 Restart the O-RU to make the above configuration changes effective.  🔸 Start netopeer2-cli on Linux terminal on Netconf client side:   $ netopeer2-cli > listen netopeer2-cli Give listen to establish CALLHOME session in NETCONF client 👉 SSH/TLS Secure connection establishment 👉 Initial process of NETCONF Subscribe for each stream XML to subscribe to NETCONF stream.  <create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">    <stream>NETCONF</stream> </create-subscription> 👉 Supervision of NETCONF connection 👉 Retrieval of O-RU information and Additional configuration O-DU sends <rpc><get><filter=”subtree”> to get each yang module listed in ietf-yang-library.yang in O-RU, for example ietf-hardware augmented by o-ran-hardware O-RU responds with <rpc-reply><data> for each yang module per <rpc><get> O-DU sends <rpc><edit-config> to each configurable yang module for additional configuration to O-RU whenever it is necessary O-RU responds with <rpc-reply><ok/> 👉 Software management

🚀 Top 5 Benefits of Using Microsoft .NET 8 As technology evolves, so do the tools we use to build robust and scalable applications. .NET 8 is here, and it’s packed with features designed to enhance performance, security, and developer productivity. Here are the top 5 benefits of using .NET 8 for your business applications: 1. Enhanced Performance: .NET 8 brings significant performance improvements across the board. Faster runtime, optimized memory management, and reduced latency mean your applications will run smoother and handle more concurrent users effortlessly. 2. Improved Security: With .NET 8, security is a top priority. Enhanced authentication mechanisms, better encryption support, and improved vulnerability management ensure your applications are secure and compliant with industry standards. 3. Advanced Cloud Integration: .NET 8 offers seamless integration with cloud services, making it easier to build, deploy, and manage cloud-native applications. Leverage the power of Azure and other cloud platforms to scale your applications and take advantage of advanced cloud capabilities. 4. Unified Development Platform: .NET 8 provides a unified development platform that supports multiple languages and frameworks. Whether you’re working with C#, F#, or VB.NET, you can build applications for web, mobile, desktop, and IoT devices using a single, cohesive platform. 5. Developer Productivity: .NET 8 comes with a host of new tools and features aimed at boosting developer productivity. Enhanced debugging, hot reload, improved diagnostics, and streamlined workflows make it easier and faster to develop high-quality applications. Embrace the future of application development with .NET 8 and unlock new levels of performance, security, and productivity for your business. #DotNet8 #SoftwareDevelopment #Performance #Security #CloudIntegration #DeveloperProductivity #BusinessApplications #Microsoft #TechInnovation

Configuration and connection to MQTT broker NB-IoT Part #3 https://lnkd.in/d-74zubW #Embeddedsystems #Firmware #Internetofthings #IoT #WizzDev #NBIoT #LTEM

🌟 Choose Node.js When: Your team already has strong Node.js expertise. You need custom security solutions tailored to your specific requirements. The application can leverage specialized security libraries to enhance protection. Ideal For: 🛠️🛠️ Real-time web applications 🚀 Microservices architecture 🔗 IoT development 🌐 Cross-platform desktop applications 🖥️ 🔒 Choose .NET for Enhanced Security: Robust security features and strongly-typed languages are essential for your project. You require seamless integration with Windows security features. Your application benefits from mature and battle-tested security frameworks. Perfect For: 🛠️🛠️ Enterprise-level applications 🏢 Complex computations and data processing 📊 Windows desktop and mobile applications 📱💻 Integrations with Microsoft tools and services 🛠️

The Twelve-Factor Thing Day 5: Cloud-Proxied web RPC This is one where the symbiotic relationship between a connected device and its trusted cloud service can really shine. It's not uncommon for an embedded device to require real-time synchronous calls to web services, 3rd party or otherwise. One device might need to fetch predicted utility load and energy prices in a product's location and change its operating mode in response. Another might need to publish data that is mission-critical and time-sensitive, like an alert when a machine is operating beyond a safety threshold. URLs, keys, and credentials for these services should never be compiled into the firmware of or stored in the flash of an embedded device. Instead, the embedded device should need nothing more than the name of a remote endpoint, like "releaseTheHounds," which maps to a key in the managed cloud solution service. The service maps that name to the URL, keys or secrets needed and operates as a transparent proxy to the ultimate destination, sending the request, and delivering the response to the connected device. It's safe, it's secure and it has the added benefit of allowing the endpoints themselves to change in the cloud service if they need to be updated, without necessitating an OTA firmware update. Read more at https://lnkd.in/ghhucx8c #12FactorThing #IoT #IIoT #ConnectedProducts

Using FlowFuse is simply the best way to deploy #nodered. Here are the reasons: - 📌 You can #manage Node-Red #instances from a centralized #system. FlowFuse works like a #DevOps system for Node-Red. - 💻 The Node-Red instances can run on the #server or #remote #devices. This lets you #deploy, #update, or back up remote Node-Red instances from FlowFuse. - 🔐 FlowFuse offers #security by default. It comes with an #NGINX reverse #proxy. When you deploy FlowFuse, a #certificate is generated for the #domain name you are using. And, of course, you need users and passwords to access FlowFuse and its Node-Red instances. - 🚀 Last but not least, FlowFuse is easy to deploy. You can use one of the preconfigured VMs in Digital Ocean to have FlowFuse running in minutes. Note 1: In case you don't have a Digital Ocean account, I'm leaving you a link in the first command with a USD 200 credit to use for two months. 😉 Note 2: You need a valid domain name to run FlowFuse in this way. Also, you have to point a couple of "A" DNS records to the IP of your VM. 🌎 #iot #iiot #data #platform #pipeline #lowcode #node

Developing an embedded software architecture is no longer about thinking in a single domain. Here are four domains you must consider to develop a successful architecture: 1) The Privilege Domain Many developers write all their code in privilege mode, but that’s a mistake! Carefully consider how the privileged and unprivileged domains should be managed. 2) The Security Domain Security requires isolation. An embedded architect must consider what code can be left in the application-rich domain and which should be isolated into a security domain. 3) The Execution Domain Many devices today have multiple cores, and it is important to carefully consider which pieces of the architecture should run on which core. 4) The Cloud Domain Even though a system might be embedded, it likely talks to the cloud. What pieces of the overall product architecture should run on-target, and what can be offloaded to the cloud? If you carefully consider these domains, you’ll architect a system that is not only flexible and scalable but also efficient. #embedded #programming #embedsys #arm #IoT

#Linux #TPM #OpenSource "World’s First TPM 2.0 with Open-Source Software Stack Cuts Down Security Integration Efforts in Industrial, Automotive and IoT Applications . . . . Trusted Platform Modules (TPM) enable secured remote software updates, disc encryption, and user authentication. They are important for connected industrial, automotive, and other embedded devices. To further facilitate seamless integration in Linux-based systems, Infineon Technologies AG now provides its OPTIGA TPM 2.0 solution with a comprehensive TSS* host software implementing the latest FAPI standard. Infineon has developed the open-source software jointly with Intel Corporation and Fraunhofer Institute for Secure Information Technology SIT. By using Infineon’s plug-and-play OPTIGA TPM 2.0, IoT system integrators can improve the security of connected products. Per the company, software integration with TSS-FAPI does not require specific skills in low-level security specifications and reduces source code development by a factor of up to 16. Manufacturers can accelerate the process for certifying their industrial devices according to the IEC 62443 standard for industrial applications, which requires hardware-based safety from level 4 upwards. The FAPI specification has been released recently as an international standard by the Trusted Computing Group (TCG). The specification is implemented in the TSS stack 1 together with the associated tools and plug-ins. The TSS stack is open-source software, which allows seamless integration of the TPM 2.0 in Linux-based systems. This includes the support of typical Linux software for device authentication, data encryption, software updates, and remote device management."