diff --git a/components/app/hamburger-menu.vue b/components/app/hamburger-menu.vue index ff6f4a8bc..07aaddcbb 100644 --- a/components/app/hamburger-menu.vue +++ b/components/app/hamburger-menu.vue @@ -151,6 +151,19 @@ function transformNavigation(navItems: any[], isChild = false): MenuItem[] { }) } + // A `link` in the folder's .navigation.yml overrides the generated path (e.g. an anchor on another page) + if (isChild && item.link) { + return { + label: item.title, + path: item.link, + children: null, + onClick: () => { + router.push(item.link) + isOpen.value = false + } + } + } + return { label: item.title, path: item.path, diff --git a/components/app/menus.vue b/components/app/menus.vue index 1cc5373e5..343458d2c 100644 --- a/components/app/menus.vue +++ b/components/app/menus.vue @@ -176,10 +176,18 @@ const filteredNavigation = computed(() => interface MenuItem { label: string path?: string + link?: string children?: MenuItem[] | null } const processNavigationItem = (navItem: any, isRoot = true): MenuItem => { + // A `link` in the folder's .navigation.yml overrides the generated path (e.g. an anchor on another page) + if (navItem.link) { + return { + label: navItem.title, + path: navItem.link + }; + } if (navItem.children?.length === 1) { const singleChild = navItem.children[0]; return { @@ -200,7 +208,7 @@ const menuData = computed(() => ({ // Helper: Check if a menu item (or one of its children) is active const isActive = (item: MenuItem): boolean => { - if (item.path && item.path === route.path) { + if (item.path && item.path.split('#')[0] === route.path && (!item.path.includes('#') || item.path === route.fullPath)) { return true } if (item.children && item.children.length > 0) { diff --git a/content/80.about/8005.index.md b/content/80.about/8005.index.md index 93f7964ea..9b48e05dc 100644 --- a/content/80.about/8005.index.md +++ b/content/80.about/8005.index.md @@ -5,16 +5,34 @@ navigation: false layout: web icon: flat-color-icons:about --- -# ABOUT +# ABOUT OMA + +The **Open Mobile Alliance (OMA)** is a **non-profit Standards Development Organization (SDO)** with a long history in mobile and **Internet of Things (IoT)** technology. Think of OMA as a **specifications factory**: industry-leading companies bring their ideas and talent to build **market-accelerating standards** that let products and services **interoperate seamlessly across fixed and mobile wireless networks**. + +Our **working group-driven, efficient and agile process** balances the need for industry consensus with the **fast and accurate creation** of specifications and other technical documentation. + +::ShAlert +Learn more about Open Mobile Alliance (OMA) and how we work to advance global standards. +Find answers to common questions in our FAQ or reach out to our team for support and membership inquiries. +We’re here to help you navigate OMA standards and get involved. +:: +## IDEA MACHINE + +Members come to OMA to work together in a transparent environment where companies of all shapes and sizes contribute on an equal footing to the next generation of wireless and IoT standards. At OMA, good ideas are valued, and high-quality technical outputs are completed, validated at [**OMA TestFests**](/oma-events/test-events), and released to the market for use across sectors such as *utilities, smart cities, industrial IoT, healthcare, and automotive that make up today's connected world. + +## HOME OF LWM2M + +OMA is home to the industry-leading **[LightweightM2M (LwM2M)](/specifications/lwm2m)** protocol and the **[OMNA LwM2M Registry](/specifications/registries)**, where market-leading corporations and small start-ups alike come together to build the next generation of IoT. + +OMA has steadily expanded IoT interoperability by bringing complementary initiatives under its roof. In **2018**, it integrated the **IPSO Alliance**, adding **IPSO Smart Objects** for standardized data models and **semantic interoperability**. In **2025**, it welcomed **uCIFI®**, extending OMA's reach with **vendor-neutral data models** that work across **LoRaWAN, NB-IoT, and mesh networks**. Together, these enable **smart, scalable IoT solutions** for utilities, smart cities, and beyond. + ::ShAlert -Learn more about **Open Mobile Alliance (OMA)** and how we work to advance global standards. -Find **answers to common questions** in our **FAQ** or **reach out to our team** for support and membership inquiries. -We’re here to **help you navigate OMA standards and get involved**. +**Want to shape the next generation of IoT standards?** [Join OMA](/join) or [explore our working groups](/groups/wg). :: ::ShMultiColumn --- -cols: 5 +cols: 4 --- :::ShMicroCard @@ -24,7 +42,7 @@ cols: 5 #icon: dark:saturate-[450%] #coverImage: opacity-[30%] dark:opacity-[45%] layout: teaser - coverImage: /images/about/about-part-1.png + coverImage: /images/about_4/about_4-part-1.jpg icon: mdi:scale-balance urlWrapper: /about/policies title: | @@ -41,7 +59,7 @@ cols: 5 ui: teaser: layout: teaser - coverImage: /images/about/about-part-2.png + coverImage: /images/about_4/about_4-part-2.jpg icon: mdi:certificate-outline urlWrapper: /about/ipr/ title: | @@ -58,7 +76,7 @@ cols: 5 ui: teaser: layout: teaser - coverImage: /images/about/about-part-3.png + coverImage: /images/about_4/about_4-part-3.jpg icon: mdi:handshake-outline urlWrapper: /about/liaisons title: | @@ -75,24 +93,7 @@ cols: 5 ui: teaser: layout: teaser - coverImage: /images/about/about-part-4.png - icon: mdi:help-circle-outline - urlWrapper: /about/faq - title: | - FAQ - subtitle: | - Answers to Common Questions - text: | - Find quick answers to frequently asked questions about **OMA standards, membership, and processes**. - --- - ::: - - :::ShMicroCard - --- - ui: - teaser: - layout: teaser - coverImage: /images/about/about-part-5.png + coverImage: /images/about_4/about_4-part-4.jpg icon: mdi:email-outline urlWrapper: /about/contact title: | @@ -104,4 +105,187 @@ cols: 5 --- ::: -:: \ No newline at end of file +:: + + +## FREQUENTLY ASKED QUESTIONS + +Answers to common questions about the **Open Mobile Alliance (OMA)**, **LightweightM2M (LwM2M)**, **OMA test events**, **LwM2M for utilities**, and the **uCIFI® data model**. + + +::ShAlert +Frequent asked questions about **OMA**. +:: + +::ShFaq +--- +ui: + header: + wrapper: "font-bold text-xl mb-4" + title: "text-2xl" + wrapper: "border p-4" + inner: "mb-2" + question: "cursor-pointer text-blue-500" + answer: "text-gray-700" + divider: "border-t my-2" +qas: + - q: "What is the Open Mobile Alliance (OMA)?" + a: | + The Open Mobile Alliance (OMA) is a non-profit Standards Development Organization that develops open, interoperable specifications for mobile and IoT. OMA is responsible for the development and maintenance of the LightweightM2M (LwM2M) protocol and the OMNA LwM2M Registry. + - q: "Who can join OMA, and how?" + a: | + Companies of all sizes — from large corporations to start-ups, as well as utilities and other organizations deploying IoT — can join OMA and take part in its working groups. See [Join OMA](/join) for membership options, or contact [membership@omaorg.org](mailto:membership@omaorg.org). + - q: How does OMA develop its specifications? + a: | + Specifications are developed in OMA's [working groups](/groups/wg) through an open, member-driven process. Drafts are validated in multi-vendor test events before being released to the market. Governance is set out in the [OMA Bylaws](/documents/Website/Membership/OMA-Reference-2024-0002-Bylaws.pdf) and [IPR Policy](/documents/Website/Membership/Member_IPRGuidelines.pdf). +--- +:: + +::ShAlert +Frequent asked questions about **LightweightM2M (LwM2M)**. +:: + +::ShFaq +--- +ui: + header: + wrapper: "font-bold text-xl mb-4" + title: "text-2xl" + wrapper: "border p-4" + inner: "mb-2" + question: "cursor-pointer text-blue-500" + answer: "text-gray-700" + divider: "border-t my-2" +qas: + - q: "What is LwM2M?" + a: | + OMA LightweightM2M is a device management protocol designed for sensor networks and the demands of a machine-to-machine (M2M) environment. + - q: "Relationship betweem OMA, and LightweightM2M (LwM2M) Protocol" + a: | + Open Mobile Alliance (OMA) is a standards organization focused on developing open, interoperable mobile services enablers. OMA is responsible for the development and maintenance of the Lightweight M2M (LwM2M) protocol. The LwM2M protocol is one of the key specifications produced by OMA. It serves as a standard for device management and communication in the Internet of Things (IoT), particularly for constrained devices with limited resources. By providing the LwM2M protocol, OMA enables efficient, secure, and interoperable management of IoT devices, ensuring consistency and compatibility across various devices and platforms. +--- +:: + +::ShAlert +This section aims to provide an overview of what is an **OMA Test Events**, and what you can expect out of the Event. +:: + +::ShFaq +--- +ui: + header: + wrapper: "font-bold text-xl mb-4" + title: "text-2xl" + wrapper: "border p-4" + inner: "mb-2" + question: "cursor-pointer text-blue-500" + answer: "text-gray-700" + divider: "border-t my-2" +qas: + - q: "What is an OMA Specification Validation Event (SVE)?" + a: | + OMA SVEs are designed to achieve a number of goals, including: + * Ensuring the quality of OMA specifications. + * Enabling vendors to verify and test the interoperability of their product implementations in a multi-vendor environment. + * Provide a peer-to-peer networking environment for participants. + SVEs are held in a confidential and secure testing environment where companies can bring their Client or Server implementation(s) based on an OMA Enabler to test in multiple multi-vendor combinations. These events are open to both OMA member and non-member companies. + - q: "When is the next SVE?" + a: | + See section [Test Event](/oma-events/test-events){ target="_blank"}. + There are 1 to 2 TestFest events held per year. These events are hosted in a variety of locations and venues throughout North America, Europe, and Asia. Registration fees are per implementation (engineers are free to attend) and vary based on the expenses estimated to cover the event. If you are interested in hosting a TestFest at your company’s facility, please contact our [staff](/about/contact){ target="_blank"}. +--- +:: + +::ShAlert +**LwM2M for Utilities**: Explore how the **LightweightM2M (LwM2M) protocol** addresses key challenges in **device management, security, and scalability** for utilities. This FAQ section covers **implementation strategies, security measures, and real-world use cases** to help you make informed decisions. +:: + +::ShFaq +--- +ui: + header: + wrapper: "font-bold text-xl mb-4" + title: "text-2xl" + wrapper: "border p-4" + inner: "mb-2" + question: "cursor-pointer text-blue-500" + answer: "text-gray-700" + divider: "border-t my-2" +qas: + - q: "What is OMA LwM2M Protocol, and how does it benefit utility meter management?" + a: | + LightweightM2M (LwM2M) is an open and efficient protocol designed to simplify device management in the Internet of Things (IoT) and utility management sectors. It offers several benefits for utility meter management, including secure device management, real-time monitoring, remote updates, enhanced security, and significant cost reduction. + - q: "What utility pain points does LwM2M address?" + a: | + LwM2M effectively addresses various utility pain points, including secure device management to prevent unauthorized access and cyber threats, network connectivity monitoring for maintaining consistent communication, and regulatory compliance for adherence to changing regulations. It also mitigates challenges related to modem firmware management, data privacy, scalability, operational efficiency, and downtime minimization. + - q: "Reducing OPEX: How does LwM2M contribute to reducing operating costs for utilities?" + a: | + LwM2M reduces operating costs through various means, including automated secure device onboarding, authentication, and access control, which minimizes labor costs. It also enhances security, reducing operational disruptions and cybersecurity expenses. Additionally, it automates tasks, reduces manual interventions, provides proactive issue identification, and facilitates compliant updates, all of which contribute to substantial cost savings. + - q: "Benefits to Utilities: What are some key LwM2M services that benefit utility management?" + a: | + LwM2M offers several key services that benefit utility management, such as secure onboarding for authorized device deployment, authentication and encryption for secure communication, automation for minimizing labor costs, insights for proactive issue identification and remote diagnostics, and support for compliant firmware and software updates. + - q: "LwM2M Objects: What are LwM2M Objects, and how do they lower operating costs for utilities?" + a: | + LwM2M Objects are standardized components that enhance operational efficiency in utility management. They contribute to cost reduction by ensuring device authenticity, streamlining software and SIM card management, and fine-tuning LTE connectivity parameters. These Objects empower utilities to make informed choices, reduce manual intervention, and improve data quality, all of which lead to lower operating costs. + - q: "LwM2M Future in Utilities: How does LwM2M contribute to the future of utility management?" + a: | + LwM2M plays a pivotal role in shaping the future of utility management by offering efficient, secure, and cost-effective solutions. It allows utilities to adapt to evolving technologies, streamline operations, meet regulatory requirements, and deliver reliable services, ensuring a sustainable and efficient future for the utility sector. + - q: "Standardization Efforts: Where can I find more information about LwM2M and its standardization?" + a: | + For more detailed information about LwM2M and its standardization, you can refer to the official [OMNA LwM2M Registry](/specifications/registries){ target="_blank" }. This registry provides comprehensive details about LwM2M Objects and their functionalities. + - q: "Real-Word Examples: Are there real-world examples of utilities benefiting from LwM2M adoption?" + a: | + Yes, LwM2M has been successfully adopted by utility organizations worldwide. Its implementation has led to significant improvements in device management, cost reduction, security enhancement, and overall operational efficiency. Real-world case studies and success stories are available to showcase the tangible benefits of LwM2M in utility management. See OMNA LwM2M Registry. + - q: "Where to Find More Info: Where can utilities access further resources and support for LwM2M adoption?" + a: | + Utilities can access further resources and support for LwM2M adoption through industry associations, online forums, LwM2M documentation, technology providers, and standards organizations like the Open Mobile Alliance. These sources provide valuable information, guidance, and collaboration opportunities for utilities embarking on their LwM2M journey. + - q: "Get Starting: How can utilities get started with implementing LwM2M in their operations?" + a: | + "Implementing LwM2M in your utility organization typically involves working with technology partners or adopting LwM2M-compliant devices and solutions. It's essential to consult with experts in IoT and utility management to plan and execute a successful LwM2M integration that aligns with your organization's specific needs and objectives. See our Product Listing pages." +--- +:: + +::ShAlert +**The uCIFI Data Model FAQ:**Get insights into how the **uCIFI Data Model** enables **data interoperability and seamless integration** for **smart city and utility IoT deployments**. Explore the most frequently asked questions to understand its capabilities and benefits. +:: + +::ShFaq +--- +qas: + - q: "Are there Synergies between uCIFI® and other standards?" + a: | + The goal of uCIFI® is to bring solutions to existing market pains, particularly to provide a unified data model to Smart City and Smart Energy applications that require long-range device-to-device communication. To do so, uCIFI® shall not reinvent the wheel but will work hand in hand with other consortia and initiatives including OMA, Wi-SUN, FIWARE, LoRaWAN, TALQ, Zhaga and D4i: + + - **FIWARE:**: the uCIFI® data model is the equivalent of Fiware device profiles but on constrained networks, while Fiware models are designed to run only on IT servers and based on JSON and NGSI RESTful that can’t be transported on LPWAN low bandwidth networks. + + - **LoRaWAN**: uCIFI® shall provide a unified data model for LoRa devices to be interoperable and easy to integrate in central management software. + + - **Wi-SUN**: the Smart City Working Group will specify an application stack on top of Wi-SUN mesh to extend smart city devices interoperability and capabilities to a higher level. + + - **TALQ** is a protocol based on HTTP and RESTful interfaces, offering interoperability at central management software layers. uCIFI is designed to complement TALQ: while TALQ offers interoperability at the central software layers, but does not provide interoperability between TALQ gateways, the uCIFI initiative standardizes application layers in the gateways and node, enabling interoperability and avoiding vendor lock-in. uCIFI and TALQ data models can be mapped through dedicated sofware layers, to further simplify integration and end to end interoperability. + + - q: "How does it position vis-à-vis existing wireless technologies?" + a: | + Cities and Utilities need a variety of wireless networks to support their needs. LPWAN networks may be fine for battery-based devices, particularly when device-to-device is not needed and data bandwidth is limited to few kilobytes per second. The main issue with such open LPWAN networks is the lack of standardization for data format. Each device supplier uses proprietary data payload that only vendors can decode, which results into cities being dependent from vendor’s proprietary cloud systems to do the data translation. On such LPWAN networks, uCIFI® shall provide a standardized data model/data payload that vendors can use freely to unlock these networks and drastically reduce vendor’s dependence in smart city applications. + + When higher bandwidth or device-to-device communication is needed (e.g. dynamic outdoor lighting, demand/response in smart metering), Wi-SUN wireless mesh may be required. The uCIFI® Alliance develops an open source smart city Application Layer on top of mesh networks which are standardized by the Wi-SUN Alliance up to the transport layer. + - q: "What are the verticals included in the data model?" + a: | + This uCIFI® data model defines standard attributes for almost 50 smart city & utility object types including streetlight controllers, electrical cabinet controllers, water & gas meters, water pressure & quality meters, environmental sensors, parking place detectors, traffic counters, city information panels and more. + In addition, relevant effort has been recently made to standardize a complete and feature-rich Schedule Framework to allow autonomous device operation, reacting to both time based and sensor based events, supporting various standalone and device-to-device scenario. The uCIFI® data model is designed to be extendable with vendor-specific objects and attributes. + + - q: "Does uCIFI data model apply globally?" + a: | + The uCIFI® unified data model shall apply to any standardized LPWAN network, regardless of wireless spectrum and technologies. + + - q: "How can interoperability be assured?" + a: | + One of the goals of the Smart City Working Group is to create a testing and validation framework that vendors and cities may be able to use to assure adherence to the data model and proper implementation. In addition, vendors may join the numerous Plug Fest events being periodically organized by OMA to let implementors meet and cross validate their products. + + - q: "How long will the data model be supported?" + a: | + The uCIFI® data model does not have any predetermined time limit. + + In case of extensions, backward compatibility is always considered as a priority, and LwM2M versioning further helps to ensure that no ambiguity would occur when working with multiple versions of the same object. +--- +:: diff --git a/content/80.about/8040.faq/.navigation.yml b/content/80.about/8040.faq/.navigation.yml index c8d9ce519..73057e496 100644 --- a/content/80.about/8040.faq/.navigation.yml +++ b/content/80.about/8040.faq/.navigation.yml @@ -1 +1,2 @@ -title: FAQ \ No newline at end of file +title: FAQ +link: /about#frequently-asked-questions diff --git a/public/images/about_4/about_4-part-1.jpg b/public/images/about_4/about_4-part-1.jpg new file mode 100644 index 000000000..305a33fe4 Binary files /dev/null and b/public/images/about_4/about_4-part-1.jpg differ diff --git a/public/images/about_4/about_4-part-2.jpg b/public/images/about_4/about_4-part-2.jpg new file mode 100644 index 000000000..1766720c3 Binary files /dev/null and b/public/images/about_4/about_4-part-2.jpg differ diff --git a/public/images/about_4/about_4-part-3.jpg b/public/images/about_4/about_4-part-3.jpg new file mode 100644 index 000000000..a3a022b93 Binary files /dev/null and b/public/images/about_4/about_4-part-3.jpg differ diff --git a/public/images/about_4/about_4-part-4.jpg b/public/images/about_4/about_4-part-4.jpg new file mode 100644 index 000000000..788c39e40 Binary files /dev/null and b/public/images/about_4/about_4-part-4.jpg differ