Managing notifications in two-wheeled vehicles

Abstract

The present disclosure provides techniques for managing notifications in a two-wheeled vehicle (102) is disclosed. The system (104) includes a processor (202), a mode determination module (112, 210) to detect whether the vehicle (102) is in a drive mode or park mode, a receiving module (114, 212) to receive a notification from a rider's mobile device (108), and a transmitting module (116, 214) to send processed information to an infotainment dashboard (106). The notification, originating from an application on the mobile device (108), includes a payload of information. When the vehicle (102) is in drive mode, the receiving module (114, 212) processes the notification by generating a summary, to reduce distraction. The transmitting module (116, 214) transmits the summarized notification to a human-machine interface (HMI) of the infotainment dashboard (106), which is communicatively coupled to the mobile device (108) using wireless communication protocols.

Description

MANAGING NOTIFICATIONS IN TWO-WHEELED VEHICLES TECHNICAL FIELD

[0001] The present subject matter generally relates to vehicle safety and communication, and specifically to systems and methods for managing notifications on an electronic dashboard of the two-wheeled vehicles.BACKGROUND

[0002] Two-wheeled vehicles, including motorcycles, scooters, and mopeds, have been a popular mode of transportation for decades. These vehicles come in various forms, powered by either internal combustion engines (ICE) or electric motors. ICE-powered two-wheeled vehicles have been the traditional choice, offering long-range and quick refuelling capabilities. In recent years, however, electric two-wheeled vehicles have gained significant traction due to their environmental benefits, lower operating costs, and quieter operation.

[0003] Regardless of the propulsion system, riding a two-wheeled vehicle requires the operator to maintain constant balance, situational awareness, and precise control. These demands create inherent safety challenges, particularly when it comes to accessing mobile devices while riding. Unlike drivers of four-wheeled vehicles, who may have the flexibility to briefly glance at a screen or use in-vehicle infotainment dashboards, riders of two-wheeled vehicles typically cannot remove their hands from the handlebars or divert their attention from the road without compromising safety. Consequently, interacting with a mobile device while riding is not only hazardous but often prohibited by law.

[0004] In view of these challenges, the riders of the two-wheeled vehicles are generally advised not to use their mobile devices while riding. In emergency situations or when it is necessary to access information on their mobile devices, the riders are recommended to park their two-wheeled vehicle at a safe location before attempting to use their mobile devices. This ensures the safety of the rider, other road users, and pedestrians whileallowing the rider to address any urgent communications or information needs.BRIEF DESCRIPTION OF DRAWINGS

[0005] The detailed description is provided with reference to the accompanying figures, wherein:

[0006] Figure 1 illustrates an exemplary environment for managing notifications in a two-wheeled vehicle, in accordance with one implementation of the present subject matter;

[0007] Figure 2 illustrates a system for managing vehicle notifications, in accordance with one implementation of the present subject matter; and

[0008] Figure 3 illustrates an exemplary method for managing vehicle notifications in two-wheeled vehicle, in accordance with an example implementation of the present subject matter.

[0009] Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements. The figures are not necessarily to scale, and the size of some parts may be exaggerated to more clearly illustrate the example shown. Moreover, the drawings provide examples and / or implementations consistent with the description; however, the description is not limited to the examples and / or implementations provided in the drawings.DETAILED DESCRIPTION

[0010] Modem mobile devices, such as smartphones, have become an indispensable part of daily life, serving as multifunctional devices for communication, information access, entertainment, and productivity. The mobile devices offer a wide array of features, including voice calls, text messaging, email, social media access, navigation, and countless applications for various purposes. However, the use of a mobile device while operating any vehicle, especially, two-wheeled vehicles, poses significant safety risks and is often prohibited by law in many jurisdictions. This creates a complex challenge for riders who may need to stayconnected and informed about important communications while on the road, especially during longer commutes or work-related travel.

[0011] Riders of two-wheeled vehicles, such as motorcycles, scooters, and mopeds, increasingly rely on mobile devices for communication, navigation, scheduling, and access to a wide range of application-based services. However, operating a two-wheeled vehicle demands continuous manual control, balance, and attentiveness to the surrounding environment. These physical and cognitive demands make it inherently unsafe for riders to interact with mobile devices while the vehicle is in motion. Unlike four- wheeled vehicles that may support in-vehicle infotainment systems designed to present information with minimal distraction, two-wheeled vehicles typically lack advanced interfaces capable of facilitating safe, inmotion interaction with mobile content. As a result, riders either miss important notifications or engage in unsafe behaviours by attempting to check their mobile devices during transit.

[0012] Conventional infotainment dashboards available in modem twowheeled vehicles are generally limited to basic display functions, such as speed, battery status, or turn-by-turn navigation. These dashboards do not offer intelligent notification management features, such as filtering, prioritizing, or summarizing mobile alerts based on context. Moreover, they typically do not distinguish between different operational states of the vehicle, such as whether it is moving or stationary, when displaying notifications. Without operational context, the indiscriminate presentation of mobile notifications may lead to increased cognitive load or distraction, thereby compromising rider safety.

[0013] These limitations of the conventional infotainment dashboards highlight the need for a system specifically designed for two-wheeled vehicles that addresses the safety and usability limitations of existing approaches. Such a system should be capable of determining the operational mode of the vehicle and adapting the notification handling process based on the operational mode of the vehicle.

[0014] In an example embodiment of the present subject matter, techniques for managing notifications in a two-wheeled vehicle are described.

[0015] According to an example, a system for managing notification in the two-wheeled vehicle is provided. The system comprises a processor and a mode determination module coupled to the processor. The mode determination module is to determine an operational mode of the twowheeled vehicle in a drive mode or a park mode. The system further comprises a receiving module coupled to the processor. The receiving module is to receive a notification from a mobile device of a rider of the twowheeled vehicle, the notification being an electronic message, containing a payload of information. The notification originates from an application executing on the mobile device. The receiving module is to further process the information of the notification based on the operational mode. The processing comprises generating a summary of the information if the operational mode is determined to be the drive mode. Further, the system comprises a transmitting module coupled to the processor. The transmitting is to transmit, via the mobile device, the processed information for presentation on a human machine interface (HMI) of an infotainment dashboard of the two-wheeled vehicle in the drive mode. The infotainment dashboard is communicatively coupled to the mobile device of the rider.

[0016] By providing a notification management technique for the twowheeled vehicles that dynamically adapts the presentation of notifications based on the vehicle's operational mode, provides an improvement in the rider safety by ensuring that a rider's attention remains on the road, reducing the temptation and need to physically interact with a mobile device while riding. The continuous monitoring of the vehicle's operational mode allows for rapid adaptation to changing conditions, offering a more dynamic and responsive user experience. By generating concise summaries of notifications in drive mode and providing full content in park mode, the system enables more focused riding while keeping the user informed. Thisnot only improves connectivity by seamlessly integrating smartphone functionality, but it also provides a customizable experience, thereby providing enhanced safety, greater convenience, and improved overall user satisfaction.

[0017] The above techniques are further described with reference to Figure 1 to Figure 3. It should be noted that the description and the Figures merely illustrate the principles of the present invention along with examples described herein and should not be construed as a limitation to the present invention. It is thus understood that various arrangements may be devised that, although not explicitly described or shown herein, embody the principles of the present invention. Moreover, all statements herein reciting principles, aspects, and implementations of the present invention, as well as specific examples thereof, are intended to encompass equivalents thereof.

[0018] Figure 1 illustrates a schematic representation of a network environment 100 for managing notifications in a two-wheeled vehicle 102, in accordance with one implementation of the present subject matter. Examples of the two-wheeled vehicle 102 may include, but are not limited to, motorcycles, scooters, mopeds, electric bikes, or similar vehicles.

[0019] In an embodiment, the network environment 100 includes a system 104 configured to manage notifications in the two-wheeled vehicle 102. The system 104, in one example, may be implemented as a vehicular communication system hosted on a remote server, such as a cloud-based infrastructure implemented and / or maintained by the manufacturer of the two-wheeled vehicle 102. The vehicular communication system comprises integrated hardware and software components operable to process and deliver real-time notifications to the rider via the infotainment dashboard of the two-wheeled vehicle 102. The system is designed to enhance rider safety by intelligently managing notification delivery in a manner that minimizes rider distraction and maintains the rider’s visual and cognitive focus on the road during vehicle operation.

[0020] In one embodiment, the infotainment dashboard 106 may refer to a human machine interface (HMI) mounted on the two-wheeled vehicle 102, which may comprise one or more display screens, touch-sensitive surfaces, audio output modules, and user input mechanisms such as buttons, dials, or voice recognition components. The infotainment dashboard 106 may be operable to present a wide range of information to the rider, including, but not limited to, real-time vehicle diagnostics (e.g., speed, battery level, fuel status, engine temperature), GPS-based navigation data, connectivity status (e.g., device pairing status, signal strength), and rider communication alerts such as incoming calls, text messages, and application-based notifications. Examples of the infotainment dashboard 106 may include a built-in LCD or OLED console, a modular tablet-style display, or other embedded display technologies specifically designed for two-wheeled vehicles.

[0021] In one example, the system 104 may be accessed and interacted with through an electronic dashboard, such as an infotainment dashboard 106, installed in the two-wheeled vehicle 102. The infotainment dashboard 106 may serve as the primary user interface for displaying processed notifications and other vehicle-related information to the rider. The system 104 may communicate with the infotainment dashboard 106 via a mobile device 108 associated with and carried by the rider. The mobile device 108 may be configured to run one or more software applications or services that interface with the vehicular communication system to transmit, receive, and relay notification data to the dashboard.

[0022] In an example, the mobile device 108 may be any portable computing device capable of wireless or wired connectivity with the infotainment dashboard 106. Examples of the mobile device 108 may include, but are not limited to, a smartphone, tablet, smartwatch, fitness tracker, smart helmet, or any other wearable or handheld device equipped with communication capabilities. The connection between the mobile device 108 and the infotainment dashboard 106 may be established using variouswired or wireless communication protocols. Non-limiting examples of such protocols include Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, Wi-Fi Direct, Near Field Communication (NFC), or a Universal Serial Bus (USB) interface.

[0023] In one example, the mobile device 108 may execute a dedicated software application, hereinafter referred to as a "companion application," which is specifically configured to interface with the system 104. The companion application may facilitate communication between the mobile device 108 and the system 104, for example, over a network 110, to enable the reception, processing, and forwarding of alerts and system -generated notifications. The companion application may also support additional functionalities, such as user authentication, system configuration, notification filtering preferences, and secure data exchange between the rider and the system 104.

[0024] In an example, the network 110 may be a single network or a combination of multiple networks and may use a variety of different communication protocols. The network 110 may be a wireless or a wired network, or a combination thereof. Examples of such individual networks include, but are not limited to, Global System for Mobile Communication (GSM) network, Universal Mobile Telecommunications System (UMTS) network, Personal Communications Service (PCS) network, Time Division Multiple Access (TDMA) network, Code Division Multiple Access (CDMA) network, Next Generation Network (NON), Public Switched Telephone Network (PSTN). Depending on the technology, the network 110 may include various network entities, such as gateways, routers; however, such details have been omitted for the sake of brevity of the present description.

[0025] In an example, the mobile device 108 may also execute one or more third-party applications that are not part of the companion application but can generate user-facing notifications. Examples of such third-party applications may include, but are not limited to, messaging apps, social media platforms, calendar services, ride-sharing applications, or emailclients. Notifications generated by these third-party applications may be intercepted or accessed by the companion application, subject to user permissions and operating system constraints, and transmitted to the system 104 for processing.

[0026] In an example, the mobile device 108 may establish a communication link with the infotainment dashboard 106, either through the same companion application or through a separate dashboard-specific application configured to handle communication between the mobile device 108 and the infotainment dashboard 106. This communication may enable the infotainment dashboard 106 to display real-time notifications, system messages, or application alerts received from the system 104. In certain embodiments, the companion application and the dashboard application may operate in coordination, sharing context and data to enable seamless synchronization of rider notifications and configuration settings between the mobile device 108 and the infotainment dashboard 106.

[0027] In an example, the system 104 may be accessed directly through the infotainment dashboard 106 of the two-wheeled vehicle 102, without requiring an intermediary mobile device. In this configuration, the infotainment dashboard 106 may include a locally installed software application that is configured to communicate with the system 104 over the network 110. In such cases, the two-wheeled vehicle 102 may further include hardware and software components to support wireless communication, such as embedded communication modules compatible with protocols including, but not limited to, cellular networks, e.g., 4G, 5G, Wi-Fi, Bluetooth, or satellite communication, thereby enabling direct and seamless data exchange between the infotainment dashboard 106 and the system 1 O4.The locally installed application may operate as a native interface on the infotainment dashboard 106, enabling direct transmission and reception of data, including real-time notifications, alerts, and other communication signals generated by or relayed through the system 104. In such an embodiment, the infotainment dashboard 106 may function as aself-contained communication terminal that does not rely on a rider’s mobile device to access the system 104. This setup allows the infotainment dashboard 106 to independently retrieve and present notifications originating from various sources, including the rider’s cloud-linked accounts, third-party services, or the vehicular backend system, provided the necessary authentication and permissions are in place.

[0028] In an example, the system 104 may include a mode determination module 112. In one example, the mode determination module 112 is configured to determine an operational mode of the two-wheeled vehicle 102. The operational mode may indicate whether the vehicle is in a drive mode or a park mode. In one implementation, the drive mode may correspond to the vehicle being in motion, while the park mode may indicate that the vehicle is stationary, even though the engine or electrical system remains powered on. For example, the park mode may occur when the rider is waiting at a red traffic light, stopped at a railway crossing, or temporarily paused during a ride without switching off the ignition. In an example, the determination of park mode may be based on parameters such as zerowheel rotation detected via wheel speed sensors, a neutral or brake- engaged condition, or absence of throttle input for a predefined time interval, while the ignition or electrical system remains active.

[0029] In an example, the mode determination module 112 may determine the operational mode based on data received from one or more onboard sensors or electronic control units (ECUs), such as, but not limited to, speed sensors, accelerometers, gyroscopic sensors, or wheel rotation detectors. The determined mode may be used by the system 104 to control the manner in which notifications are processed and displayed.

[0030] In an embodiment, the system 104 may include a receiving module 114. In one example, the receiving module 114 may be configured to receive one or more notifications from the mobile device 108 associated with the rider of the two-wheeled vehicle 102. In one example, the notification may comprise an electronic message generated by a softwareapplication executing on the mobile device 108. Each notification may include a payload containing structured or unstructured information intended to alert or inform the rider. As explained previously, the software application generating the notification may be any of a variety of third-party applications installed on the mobile device 108. Non-limiting examples of such applications include social media platforms, messaging and email clients, navigation or mapping services, calendar applications, weather and news applications, ride-hailing or transportation services, fitness or health tracking tools, and other mobile or wearable applications capable of issuing system-level or user-specific notifications.

[0031] In an example, the receiving module 114 may be configured to adapted to detect, access, and ingest such notifications in real time or near real time, depending on device permissions and system configurations. The system 104 is designed to support the receipt and further handling of notifications from any such applications, thereby enabling a unified and context-aware notification management process suitable for use during twowheeled vehicle operation.

[0032] In an example, the receiving module 114 is further configured to process the information contained within the notification based on the operational mode of the two-wheeled vehicle 102. When the operational mode is determined to be the drive mode, the processing may include generating a condensed or summarized version of the notification content. This summary is designed to provide a concise and informative preview of the notification, minimizing rider distraction while ensuring the rider remains aware of important incoming information. In one implementation, the summary may be generated using Natural Language Processing (NLP) techniques, which may include language parsing, entity recognition, keyword extraction, and contextual prioritization to identify and retain only the most relevant portions of the original notification.

[0033] In an example, the summary may include selected key elements of the original notification, such as an icon or name of theoriginating application, the name or identifier of the sender, and a brief excerpt of the content. For example, in the drive mode, the summarized notification may look like, for example: : "2 New messages from WhatsApp - John Doe," without revealing the full message body. This enables the rider to stay informed without being required to visually or cognitively engage with detailed content while the vehicle is in motion. Depending on user preferences, the brief excerpt may include the first few words of a message, subject line of an email, or event title, carefully selected to balance informativeness and safety. By receiving such condensed information, the rider can make an informed decision on whether the message requires immediate attention, such as parking the vehicle to view and respond to an urgent notification.

[0034] In an embodiment, the system 104 may include a transmitting module 116. In one example, the transmitting module 116 is configured to transmit, via the mobile device 108, the processed information for presentation on a HMI of an infotainment dashboard 106 of the two-wheeled vehicle 102, particularly when the vehicle is operating in the drive mode. In one implementation, the transmitting module 116 may be operable to transmit the processed or summarized notification data via the mobile device 108 associated with the rider. The infotainment dashboard 106 may be communicatively coupled with the mobile device 108 using one or more short-range wireless communication protocols. Through this communication link, the processed notification data may be rendered on the HMI in a simplified, non-intrusive format suitable for quick rider awareness without diverting significant visual or cognitive attention from road navigation. The transmitting module 116 ensures that only context-appropriate information is transmitted and displayed, based on the determined operational mode and system preferences.

[0035] In an example, if the mode determination module 112 determines that the two-wheeled vehicle 102 is in the park mode, the transmitting module 116 may be configured to transmit the complete information payloadof the notification directly to the HMI of the infotainment dashboard 106 without applying any summarization or content reduction. In this mode, since the vehicle is stationary, the risk of rider distraction is significantly reduced, allowing the full content of the notification to be safely displayed. The transmitted information may include detailed text, images, links, or other interactive elements, depending on the capabilities of the infotainment dashboard 106 and the nature of the notification. This enables the rider to access the complete context of the communication or alert without needing to retrieve or interact with the mobile device 108.

[0036] In an example, the system 104 may also allow for user customization of how notifications are displayed in different modes. For example, the rider may be able to set priority levels for different applications or contacts, determining which notifications are shown as summaries in drive mode and which are held until the vehicle enters park mode.

[0037] Accordingly, the present subject matter enhances rider safety through intelligent notification management based on the operating mode of the vehicle which may be beneficial for two-wheeled vehicles where maintaining focus is crucial. The present invention allows for improving connectivity by allowing the riders to stay informed about important communications without physically interacting with their mobile devices while operating the vehicle. The system provides a customizable experience, enabling users to prioritize notifications from specific applications or contacts, and seamlessly integrates smartphone functionality with vehicle infotainment dashboard.It may be understood that concepts relating to managing notifications for a two-wheeled vehicles are not restricted to any specific propulsion system. The invention as described here may be applicable to both internal combustion engine (ICE) vehicles, which are powered by conventional fuels such as petrol or diesel, and electric vehicles (EVs), which utilize electric motors and a battery.

[0038] Figure 2 illustrates a system 104 for managing notifications in two-wheeled vehicles, according to an example implementation of the present subject matter. The system 104 implements a technical process for receiving, processing, and presenting notifications to a rider based on the operational mode of the two-wheeled vehicle 102, thereby minimizing distraction and enhancing rider safety. The system 104 as described herein addresses the technical limitations of conventional two-wheeled vehicular notification systems, which are often unable to differentiate between operational modes and may overwhelm the rider with excessive or irrelevant information while the vehicle is in motion.

[0039] As depicted in Figure 2, in an example implementation, the system 104 may include at least one processor 202 and a memory 204 coupled to the processor 202. In an example, the processor 202 may be implemented as microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. The memory 204 may include any computer-readable medium known in the art, including, for example, volatile memory (e.g., RAM), and / or non-volatile memory (e.g., EPROM, flash memory, etc.). The memory 204 may also be an external memory unit, such as a flash drive, a compact disk drive, an external hard disk drive, or the like.

[0040] Also, as depicted in Figure 2, in an example implementation, interface(s) 206 may be coupled to the processor 202. The interface(s) 206 may include a variety of software and hardware interfaces that allow interaction of the system 104 with other communication and computing devices, such as network entities, external repositories, and peripheral devices. The interface(s) 206 may also enable the coupling of components of the system 104 with each other. Further, in an example, the interface(s) 206 may couple the infotainment dashboard 106 to the system 104.

[0041] The system 104 may further include module(s) 208 and data 218. The module(s) 208 may be implemented as a combination of hardware andprogramming, for example, programmable instructions to implement a variety of functionalities of the module(s) 208. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the module(s) 208 may be executable instructions. Such instructions may be stored on a non-transitory machine-readable storage medium which may be coupled either directly with the system 104 or indirectly (for example, through networked means). In an example, the module(s) 208 may include a processing resource, for example, either a single processor or a combination of multiple processors, to execute such instructions. In the present examples, the non-transitory machine-readable storage medium may store instructions that, when executed by the processing resource, implement module(s) 208. In other examples, the module(s) 208 may be implemented as electronic circuitry.

[0042] The module(s) 208 may include the mode determination module 210, the receiving module 212, the transmitting module 214, and other module(s) 216. The other module(s) 216 may further implement functionalities that supplement functions performed by the system 104 or any of the module(s) 208. On the other hand, the data 218 serves, amongst other things, as a repository for storing data that may be fetched, processed, received, or generated by one or more of the module(s) 208 of the system 104. It may be further noted that information stored and available in the data 218 may be utilized by the module(s) 208 for performing various functions by the system 104. In an example, the data 218 may comprise vehicle mode data 220, notification data 222, and other data 224.

[0043] In an embodiment, the system may comprise a mode determination module 210 coupled to the processor 202. In an example, the mode determination module 202 is similar to ‘mode determination module 112’ as illustrated in Figure 1. The mode determination module 210 is to determine an operational mode of the two-wheeled vehicle. In an example, the mode determination module 210 classifies the operational state of thetwo-wheeled vehicle 102 into two distinct operational modes: drive mode and park mode. The drive mode is determined when the vehicle is in motion. Conversely, the park mode is determined when the vehicle is stationary, indicated by a zero-speed reading.

[0044] In an example, the park mode may remain active even when the vehicle’s ignition is turned off, provided that the HMI of the infotainment dashboard 106 remains powered and operational. Such scenarios may occur, for instance, when the rider has turned off the engine but is seated on the vehicle and interacting with the infotainment dashboard 106, or when the vehicle is parked and connected to an external power source for charging electronic systems. The park mode may also be active when the vehicle is stationary with the ignition off during activities such as refuelling, waiting for a passenger, or reviewing route information on the HMI before resuming travel. In these cases, the park mode enables full display of incoming notifications without the constraints applied in drive mode, allowing the rider to access complete message content or detailed application information without safety concerns.

[0045] In an example, to determine the operation mode of the vehicle, the mode determination module 116 may access data from various sensors of the two-wheeled vehicle 102, such as speedometer, GPS, accelerometer, engine status, and transmission status, to continuously analyse the current state of operation of the two-wheeled vehicle 102. As will be apparent, it is also possible that various information regarding the operational state of the two-wheeled vehicle 102 as sensed by the numerous sensors installed in the two-wheeled vehicle 102 may be communicated to the system 104 by the infotainment dashboard 106 from time to time. The system 104 may have up-to-date information about the two-wheeled vehicle 102 on a real-time or near real-time basis by implementing a push or pull mechanism for obtaining such information. Based on this data, mode determination module 210 classifies the mode of operation of the two-wheeled vehicle 102 into either drive mode or parkmode. In an example, the vehicle operational state data may be stored in data 218 of the system 104 as ‘vehicle mode data 220’, enabling the system 104 to access historical or current operational information for decisionmaking and processing tasks.

[0046] In an example, the system 104 may comprise a receiving module 212 coupled to the processor 202. In an example, the receiving module 212 is similar to the receiving module 114, as illustrated in Figure 1. The receiving module 212 is configured to receive one or more notifications from the mobile device 108 of a rider of the two-wheeled vehicle 102, the notification originating from an application executing on the mobile device 108. The notification may comprise an electronic message containing a payload of information, such as text, multimedia content, or event alerts, intended for the rider's attention.

[0047] In an example, the software application generating the notification can belong to a wide range of third-party or native applications installed on the mobile device 108. These may include, but are not limited to, social media applications, email clients, navigation and mapping applications, calendar or scheduling tools, weather information services, news aggregation platforms, ridesharing or transportation applications, fitness tracking applications, instant messaging services, banking or financial applications, e-commerce platforms, or any other software capable of generating user-specific notifications. The notification may carry diverse types of content such as text messages, multimedia files, hyperlinks, realtime alerts, reminders, promotional updates, or transactional confirmations. In an example, upon being received by the receiving module 212, the notification may be stored in the data 218 as part of notification data 222. This stored notification data may be utilized for subsequent processing, filtering, summarization, prioritization, or retrieval, depending on the operational mode of the two-wheeled vehicle 102 and user-defined preferences.

[0048] In an example, to enable the receiving module 212 to receive all notifications that are received on the rider’s mobile device 108, a coupling may be established between the companion application installed on the mobile device 108 and other applications executing on the mobile device 108 that are generating notifications, such as instant messaging, email, or social media applications. This may be facilitated through a one-time registration process, during which the rider’s mobile device is registered with the receiving module 212 and the rider provides explicit permission for the companion application to access notification content from selected third- party applications. In an example, the rider may selectively authorize access to notifications from specific messaging services (e.g., WhatsApp, SMS) while withholding access to other sources (e.g., email clients, social media applications) based on user-defined preferences. Upon completion of the registration and authorization process, the companion application may be configured to directly intercept notification payloads from the authorized third-party applications and transmit the corresponding data to the receiving module 212. In another example, the third-party application itself may be configured to transmit notification data directly to the receiving module 212 via an application programming interface (API) or equivalent communication interface. Such an arrangement enables the receiving module 212 to achieve notification while preserving rider control over data access and privacy through selective permission-based configuration.

[0049] In an example, the receiving module is to further process the information of the notification based on the operational mode. The processing comprises generating a summary of the information if the operational mode is determined to be the drive mode. This selective processing ensures that only essential information is presented to the rider while the vehicle is in motion, thereby reducing distraction.

[0050] As used herein, a “summary” refers to a condensed representation of the original notification that retains only key elements necessary for quick rider awareness, without displaying the full content. Thesummary of the information may comprise at least a name of the application from which the notification was generated and a name of the sender of the notification. In certain examples, the summary may also include a brief excerpt of the message content, such as the first few words of a text message, the subject of an email, or the title of a calendar event.

[0051] In operation, when the mobile device 108 receives a notification from an application, the mode determination module 210 evaluates the current operational mode of the two-wheeled vehicle 102. Based on this determination, the receiving module 212 may transmit the notification to the HMI of the infotainment dashboard 106 in a manner appropriate for the mode. For instance, in the drive mode, the receiving module 212 may generate a notification summary containing key elements such as the originating application name, the sender’s name, and a brief excerpt of the content. An example display on the HMI could be: “1 New Email - Work: Meeting rescheduled,” without revealing the complete email body. Conversely, in the park mode, the receiving module 212 may transmit the full content of the notification to the HMI, including the complete message text, any associated attachments, and available interactive elements, thereby allowing the rider to fully view and respond to the notification without compromising safety.

[0052] In an example, the system 104 may utilize Natural Language Processing (NLP) techniques to process the content of the notification and generate an appropriate summary. Such NLP techniques may include, but are not limited to, keyword extraction, named entity recognition (NER) to identify names of people, places, or organizations, text summarization algorithms to condense lengthy messages, sentiment analysis to detect urgency or emotional tone, and stop-word removal to filter out non-essential words. For instance, when processing an email notification, the system 104 may apply keyword extraction and NER to highlight the sender's name and subject line, while discarding verbose introductory text, thereby producing a concise and relevant summary for display on the HMI.

[0053] In an example, the system 104 may comprise a transmitting module 214 coupled to the processor 202. In an example, the transmitting module 214 is similar to the transmitting module 116, as illustrated in Figure 1. The transmitting module 214 is configured to transmit the processed information, via the mobile device 108, for presentation on the HMI of the infotainment dashboard 106 of the two-wheeled vehicle 102 when the operational mode is determined to be the drive mode. The infotainment dashboard 106 may be communicatively coupled to the rider’s mobile device through either a wired connection or wireless communication protocols. The wireless communication may be established using technologies such as, but not limited to, Bluetooth®, Wi-Fi Direct®, or Near Field Communication (NFC), ensuring reliable and low-latency data transfer for real-time notification display.

[0054] In an example, the receiving module 212 is further configured to cause the complete payload of a notification to be displayed on the HMI of the infotainment dashboard 106 when the mode determination module 210 identifies the operational mode of the two-wheeled vehicle 102 as the park mode. In this stationary state, the receiving module 212 enables presentation of the full message body, attached media files, timestamps, and complete conversation threads, thereby providing the rider with a comprehensive and interactive view of the notification. This configuration allows the rider to safely engage with the notification, such as responding to messages, viewing attachments, or dismissing alerts, without physically handling the mobile device. Additionally, by displaying the full notification content on the HMI, the system 104 equips the rider with sufficient context to determine whether further interaction, such as accessing a large file or performing a complex application-specific action, necessitates retrieving the mobile device for extended use.

[0055] In an example, the receiving module 212 may be further configured to filter incoming notifications based on one or more user-defined criteria, the criteria comprising at least one of: application-specific prioritylevels, sender contact information, and keywords present in the notification content. Such filtering enables user customization of notification display preferences, thereby allowing the rider to exercise granular control over how information is presented on the HMI. In an example, these preferences may be configured through a dedicated user interface accessible via a companion mobile application or, in park mode, directly through the infotainment dashboard 106. Riders may assign different priority levels to specific applications or individual contacts, with the receiving module 212 applying these rules in real time to determine whether a notification is displayed, summarized, or suppressed. This ensures that notification delivery is not limited to a fixed, pre-programmed behavior, but is instead dynamically adapted to the rider’s unique requirements and communication patterns, enabling only rider-approved alerts to appear in motion-sensitive conditions.

[0056] In an example, the receiving module 212 may assign higher priority to communication-oriented applications such as, but not limited to WhatsApp, Signal, or SMS messaging platforms, since notifications from such sources may represent direct, time-sensitive messages from family members, colleagues, or other important contacts. In contrast, lower priority may be assigned to applications that produce frequent but non-essential updates, such as social media platforms (e.g., Facebook, Instagram, X / Twitter), gaming applications, or promotional alerts from retail and food delivery services. The system 104 may process these predefined application-level preferences such that, in drive mode, only high-priority notifications are displayed in a summarized form while less critical alerts are temporarily suppressed until the two-wheeled vehicle 102 is in park mode. This approach reduces cognitive load and minimizes rider distraction while ensuring that time-critical messages are not missed during operation.

[0057] In an example, the receiving module 212 may further implement sender and content-based prioritization to refine notification handling. Regardless of the originating application, notifications from designated high-priority contacts, such as a spouse, parent, or workplace supervisor, may be automatically flagged for immediate delivery. Similarly, the receiving module 212 may be configured to analyze notification text for one or more rider-specified keywords, such as “emergency,” “urgent,” or “critical,” with any notification containing such terms being assigned high priority. In an example, this keyword detection may override lower application-level priority settings, ensuring that important alerts are surfaced even if the sender is not on the rider’s pre-approved list. This multi-layered prioritization strategy provides an additional safeguard against overlooking essential communications while the rider is in drive mode. By filtering notifications according to both predefined contacts and semantic content, the system 104 ensures that any alert appearing on the HMI in motion is both relevant and critical, thereby minimizing unnecessary cognitive distraction and supporting safer riding conditions.

[0058] In an example, the receiving module 212 may be enabled to implement sender and content-based prioritization based on user inputs. The user inputs may be provided during the afore-mentioned registration process.

[0059] Thus, by providing an intelligent, context-aware notification management technique, the system offers a significant advancement over existing technology. This system enhances rider safety by ensuring that a rider's attention remains on the road, reducing the temptation and need to physically interact with a mobile device while riding. The continuous monitoring of the vehicle's operational mode allows for rapid adaptation to changing conditions, offering a more dynamic and responsive user experience. By generating concise summaries of notifications in drive mode and providing full content in park mode, the system enables more focused riding while keeping the user informed. This not only improves connectivity by seamlessly integrating smartphone functionality but also provides a customizable experience, allowing riders to set their own notificationpriorities. Thereby, enhancing the safety, convenience, and overall user satisfaction.

[0060] Figure 3 illustrates a method 300 for managing notifications in a two-wheeled vehicle 102, according to an example of the present subject matter. Although the method 300 may be implemented in a variety of electronic devices, for ease of explanation, the present description of the method 300 is provided in the context of the above-described system 104. In an example, the method 300 may be implemented by a processor(s) or computing device(s) through any suitable hardware, non-transitory machine-readable instructions, or a combination thereof.

[0061] It may be understood that blocks of the method 300 may be performed by programmed computing devices. The blocks of the method 300 may be executed based on instructions stored in a non-transitory computer readable medium, as will be readily understood. The non- transitory computer readable medium may include, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.

[0062] Referring to Figure 3, at block 302, the method 300 comprises determining 302 an operational mode of the two-wheeled vehicle 102, the operational mode being indicative of the two-wheeled vehicle 102 being in a drive mode or a park mode. As explained previously, the drive mode refers to a state in which the vehicle is in motion or is otherwise deemed to be actively operated by the rider, such as when the vehicle speed exceeds a predefined threshold (e.g., 3 km / h), when the engine or motor is running and throttle input is detected, or when forward gear engagement is identified. In contrast, park mode refers to a stationary state of the vehicle, such as when the vehicle speed is zero. In some examples, park mode may remain active even if the vehicle’s ignition is switched off, provided that the infotainment dashboard’s HMI remains powered and capable of displaying notifications.

[0063] In an example, determining the operational mode comprises accessing data from at least one sensor associated with the two-wheeled vehicle 102. The data may include, but is not limited to, vehicle speed information obtained from a wheel speed sensor, GPS-derived positional and movement data, and engine or motor status obtained from the vehicle’s onboard control unit. In some examples, additional sensor inputs, such as gear position sensors, brake status sensors, or tilt angle data from an inertial measurement unit (IMU), may also be utilized to enhance accuracy. For instance, a sustained vehicle speed greater than a predefined threshold, combined with active engine status, may indicate drive mode, whereas zero speed over a predetermined period, combined with an inactive engine or deployed kickstand, may indicate park mode. This multi-parameter approach ensures reliable detection of the vehicle’s operational state, even in scenarios where a single sensor reading could be misleading due to environmental or mechanical factors.

[0064] At block 304, the method 300 comprises receiving 304, from a mobile device 108 of a rider of the two-wheeled vehicle 102, a notification, the notification being an electronic message containing a payload of information and originating from an application executing on the mobile device 108. In an example, this payload of information may include, for example, but not limited to textual content, metadata such as sender identification and message type, timestamps, geolocation tags, embedded media, hyperlinks, or structured data fields. The notification may be transmitted from the mobile device to the infotainment dashboard through a wired or wireless communication channel, such as Bluetooth or Wi-Fi Direct.

[0065] At block 306, the method 300 comprises processing 306 the information of the notification based on the operational mode. As previously described, the operational mode may be classified as either a drive mode, in which the vehicle is in motion, or a park mode, in which the vehicle is stationary. In the drive mode, the processing includes generating asummary of the information of the notification to minimize rider distraction and reduce cognitive load while operating the vehicle.

[0066] In an example, the generation of the summary may be performed using natural language processing (NLP) techniques to automatically identify and extract the most relevant portions of the notification content. Such NLP techniques may include, but are not limited to, keyword extraction to detect important terms, named entity recognition to identify people, places, or organizations, and text summarization algorithms to condense longer messages while preserving key meaning. By applying these NLP processes, the method ensures that the summary displayed to the rider is contextually meaningful, concise, and aligned with safety considerations, while avoiding irrelevant or redundant information that could otherwise distract the rider.

[0067] In an example, the summary may retain only the most essential elements of the payload, such as the name of the originating application, the sender’s name or identifier, and a brief excerpt or paraphrase of the content. The summarization may further omit non-critical details such as lengthy message bodies, large media attachments, or extended conversational history, ensuring that only high-priority, safety-compliant information is presented on the infotainment dashboard. In an example, when the operational mode is determined to be the park mode, the processing may involve retaining and formatting the complete payload information for display, including full message text, attachments, timestamps, and interactive elements, thereby enabling the rider to review and act upon the notification without operational safety concerns. The processing may also incorporate pre-determined filtering rules or priority levels, ensuring that even in summary form, the most relevant and timesensitive information is surfaced to the rider.

[0068] At block 308, the method 300 comprises transmitting 308, via the mobile device 108, the processed information for presentation on a HMI of an infotainment dashboard 106 of the two-wheeled vehicle 102 in the drivemode. As explained previously, the infotainment dashboard is communicatively coupled to the mobile device through either a wired connection or wireless communication protocols, such as Bluetooth, Wi-Fi Direct, or NFC, to ensure a reliable and low-latency transfer of data. This transmission step ensures that the processed information is delivered in real time, allowing the HMI to promptly update and display relevant content without delay. In an example, the transmitted data may incorporate data formatting and optimization techniques to ensure that the transmitted summary is compatible with the HMI’s display constraints, such as screen size, resolution, and available interaction capabilities, thereby improving readability and minimizing distraction.

[0069] In an example, the method 300 further comprises filtering the incoming notifications based on one or more user-defined criteria, including application-specific priority levels, sender contact information, and keywords present in the notification content. These preferences may be configured through a companion mobile application or, in park mode, directly via the infotainment dashboard, allowing the rider to tailor notification handling to their specific communication needs. The filtering process applies these rules in real time to determine whether a notification is displayed, summarized, or temporarily suppressed, ensuring that alerts presented in motion-sensitive conditions align with rider-approved priorities rather than fixed, pre-programmed settings.

[0070] In an example, the method 300 may further incorporate a multilayered prioritization by assigning higher importance to certain communication-oriented applications or designated contacts, while lowering priority for non-essential updates such as social media, gaming, or promotional alerts. Additionally, notifications containing rider-specified keywords, such as “emergency,” “urgent,” or “critical,” may be automatically elevated in priority regardless of their application source or sender. This approach ensures that time-sensitive messages are surfaced promptly in drive mode, while less critical alerts are deferred until the vehicle is in parkmode, thereby reducing cognitive load and minimizing distraction without compromising timely access to essential communications.

[0071] In some implementations, the method 300 may further include providing, via the HMI of the infotainment dashboard 106, interactive elements enabling the rider to respond to a received notification using a set of predefined quick-reply options and to dismiss or archive the notification. In an example, the quick-reply options may be contextually generated based on the content of the notification, allowing the rider to send short, relevant responses without the need for manual text input. The dismiss and archive functions enable efficient management of notifications, helping the rider clear or store them for later review.

[0072] Accordingly, the present subject matter provides a technique for managing vehicle notifications that enhances rider safety and convenience by intelligently managing smartphone notifications based on the operating mode of the vehicle. The present subject matter provides essential notifications without requiring physical interaction with the user device, reducing distractions while riding. The ability to display summarized or full notifications depending on whether the vehicle is in motion or parked ensures that riders stay connected without compromising safety, ultimately improving the overall riding experience.

[0073] Although implementations have been described in a language specific to structural features and / or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples for managing vehicle notifications for purposes such as presenting notifications received on a user device to a rider in a manner that enhances safety and user experience.

Claims

l / We Claim:

1. A system (104) for managing notifications in a two-wheeled vehicle (102), the system comprising: a processor (202); a mode determination module (112, 210), coupled to the processor (202), to determine an operational mode of the two-wheeled vehicle (102), the operational mode being indicative of the two-wheeled vehicle (102) in a drive mode or a park mode; a receiving module (114, 212), coupled to the processor (202), to: receive a notification from a mobile device (108) of a rider of the two-wheeled vehicle (102), the notification being an electronic message, containing a payload of information, the notification originating from an application executing on the mobile device (108); and process the information of the notification based on the operational mode, wherein the processing comprises generating a summary of the information if the operational mode is determined to be the drive mode, and a transmitting module (116, 214), coupled to the processor (202), to transmit, via the mobile device (108), the processed information for presentation on a human-machine interface (HMI) of an infotainment dashboard (106) of the two-wheeled vehicle (102) in the drive mode, the infotainment dashboard (106) being communicatively coupled to the mobile device (108) of the rider.

2. The system (102) as claimed in claim 1 , wherein the receiving module (114, 212) is further configured to cause the payload of information to be displayed on the HMI of the infotainment dashboard (106) when the operational mode of the two-wheeled vehicle (102) is the park mode.

3. The system (104) as claimed in claim 1 , wherein the mode determination module (112, 210) is configured to determine the operational mode of the two-wheeled vehicle (102) by accessing data from one or more sensors of the two-wheeled vehicle (102), the data including at least one or more of vehicle’s speed, GPS data, and engine status.

4. The system (104) as claimed in claim 1 , wherein the receiving module (114, 212) is further configured to filter notifications based on a user- defined criteria, the criteria comprising at least one of application priority levels, sender contact information, and keywords in the information within the notification.

5. The system (104) as claimed in claim 1 , wherein the summary of the information comprises at least a name of an application from which the notification was generated and a name of a sender of the notification.

6. A method (300) for managing notifications in a two-wheeled vehicle, the method comprising: determining (302) an operational mode of the two-wheeled vehicle (102), the operational mode being indicative of the two-wheeled vehicle (102) being in a drive mode or a park mode; receiving (304), from a mobile device (108) of a rider of the twowheeled vehicle (102), a notification, the notification being an electronic message containing a payload of information and originating from an application executing on the mobile device (108); processing (306) the information of the notification based on the operational mode, wherein the processing comprises generating a summary of the information if the operational mode is determined to be the drive mode; and transmitting (308), via the mobile device (108), the processed information for presentation on a human-machine interface (HMI) of aninfotainment dashboard (106) of the two-wheeled vehicle (102) in the drive mode, the infotainment dashboard (106) being communicatively coupled to the mobile (108) device of the rider.

7. The method (300) of claim 1 , further comprising displaying the payload of information on the HMI of the infotainment dashboard (106) when the operational mode is determined to be the park mode.

8. The method (300) of claim 1 , wherein the determining of the operational mode comprises accessing data from at least one sensor of the two-wheeled vehicle (102), the data comprising at least one of the vehicle’s speed, GPS data, and engine status.

9. The method (300) of claim 1 , wherein the processing of the information is further based on user-defined priority levels, the priority levels being set for at least one or more of a sender contact associated with the notification; keywords within the payload of information.

10. The method (300) as claimed in claim 6, further comprises providing, via the HMI of the infotainment dashboard (106), interactive elements, to reply to the notification using a set of predefined quick-reply options, and to dismiss or archive the notification.

Images