DESC:FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)

SYSTEM AND METHOD FOR TRANSMISSION OF NOTIFICATION MESSAGES IN A COMMUNICATION NETWORK

Jio Platforms Limited, an Indian company, having registered address at Office -102, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

The following specification particularly describes th e invention and the manner in which it is to be performed.
TECHNICAL FIELD
[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for managing transmission of notification messages to various application platforms in a communication environment. The present disclosure further relates to a system and a method for receiving the notification messages in the communication environment.
BACKGROUND OF THE INVENTION
[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.
[0003] In the realm of wireless communication and networking environments, a sudden increase in number and types of web and mobile applications has revolutionized the way one or more users interact with user devices. With advent of Internet of Things (IoT) and increasing integration of technology into our day-to-day life, need for an efficient and seamless communication channel has become more crucial than ever. One key aspect of user engagement and interaction with different application platforms is timely processing and pushing of notification messages across the application platforms.
[0004] To this end, notification systems play a pivotal role in keeping users informed about relevant updates, events, and activities within applications and enabling seamless transmission of alerts, updates, and the messages or notifications across the different application platforms. In various applications such as enterprise systems, web applications, mobile applications, and the like, notifications serve as a means to deliver personalized content, important announcements, reminders, and alerts directly to the user devices, thereby enhancing user experience and ensuring seamless communication between the applications and the users.
[0005] However, there remains a notable challenge in providing a unified and efficient mechanism for delivering the notification messages across the different application. For instance, an enterprise manages a web application and a mobile application, and both the web application and the mobile application require real time notification. If a user receives an important security alert on a user device (for instance, mobile phone) but not on the web browser, or if an update notification arrives at different times on different devices, it can cause confusion and impact the user experience.
[0006] Traditionally, the web applications rely on browser-based push notification services, while the mobile applications use platform specific messaging services. Since both the web applications and the mobile applications operate independently, conventional notification systems utilize separate notification engines for triggering the notification messages to the web applications and the mobile applications. This not only increases development and maintenance efforts but also results in redundant workflows. Every notification is to be sent separately to web and mobile users, leading to unnecessary duplication and higher operational costs.
[0007] Another limitation associated with the conventional notification systems is inconsistency in message synchronization across the different platforms. Since web and mobile notifications are triggered separately, the notification messages may not be delivered at same time to both platforms. The lack of synchronization causes discrepancies in user experience particularly in cases where notifications contain time sensitive information, such as security alerts or real time status updates. The inability to ensure consistent and simultaneous delivery of notifications across the different application platforms leads to operational inefficiencies.
[0008] Further, use of separate notification engines for sending or delivering the notification messages required additional resources, leading to inefficiencies in notification management and resource utilization.
[0009] Additionally, security and authentication challenges present another significant limitation associated with the conventional notification systems. Since separate authentication mechanisms are required for the different application platforms, implementation of a secure notification transmission has become more complex. The use of multiple authentication protocols has increased risk of unauthorized access, message interception, and data leakage. A unified authentication approach is required to enhance security of notification delivery while maintaining compliance with privacy standards.
[0010] Therefore, to overcome aforementioned challenges and limitations associated with the conventional notification systems, there lies a need for a system and a method that utilizes a common notification engine to facilitate seamless notification transmission across multiple application platforms.
SUMMARY
[0011] The following embodiments present a simplified summary to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
[0012] According to an aspect of the present disclosure, disclosed herein is a method for managing transmission of notification messages in a communication environment. The method comprises receiving, by a reception module from one or more user devices, one or more requests to register one or more applications, with a cloud-based messaging service. Furthermore, the method comprises registering, by an execution module, the one or more applications with the cloud-based messaging service upon receiving the one or more requests and transmitting, by a data processing module to the one or more user devices, a registration token received from the cloud-based messaging service. The registration token corresponds to an identifier associated with each application of the one or more applications. Thereafter, the method comprises composing, by the data processing module, one or more notification messages upon transmitting the registration token to the one or more user devices and generating, by the data processing module, message metadata corresponding to the one or more notification messages. The method further comprises transmitting, by the data processing module via the cloud-based messaging service, the one or more notification messages and the message metadata to the registered one or more applications based on a state of the one or more user devices. The state of the one or more user devices corresponds to an online state or an offline state.
[0013] In one or more implementations, each request of the one or more requests includes authentication credentials associated with the corresponding user device. The authentication credentials are used by the cloud-based messaging service to validate the corresponding user device for registering the one or more applications.
[0014] In one or more implementations, the registration token corresponding to each of the registered one or more applications is unique.
[0015] In one or more implementations, the one or more notification messages include at least one of a text-based alert, a multimedia message, a system generated update, a real time status notification, an event triggered alert, a security warning, an application update message, or a personalized user prompt. Each notification message of the one or more notification messages is configured with a priority level and a predefined delivery mechanism. The predefined delivery mechanism is selected based on at least one of user preferences, network conditions, and availability of the one or more user devices.
[0016] In one or more implementations, the message metadata includes at least one of a message identifier of the one or more notification messages, a timestamp indicating a time of notification message generation, a priority level defining an urgency of the notification message, a sender identifier, a notification message type classification, an expiration time for a notification message validity, and encryption details for secure transmission of the notification message.
[0017] In one or more implementations, for transmitting the one or more notification messages to the one or more applications, the method comprises determining, by the data processing module, whether the one or more user devices are in the online state, or the offline state based on a current network status. The method further comprises sending, by the data processing module, the one or more notification messages, and the message metadata to the one or more applications upon the determination that the one or more user devices are in the online state.
[0018] In one or more implementations, the method comprises storing, by the data processing module, the one or more notification messages in a buffer queue upon the determination that the one or more user devices are in the offline state. The method further comprises sending, by the data processing module, the one or more notification messages, and the message metadata to the one or more applications when the one or more user devices transitions from the offline state to the online state.
[0019] According to another aspect of the present disclosure, a system for managing transmission of notification messages in a communication environment is disclosed. The system comprises a reception module, an execution module, and a data processing module. The reception module is configured to receive, from one or more user devices, one or more requests to register one or more applications, installed on the one or more user devices, with a cloud-based messaging service. The execution module is configured to register the one or more applications with the cloud-based messaging service upon receiving the one or more requests. The data processing module is configured to transmit, to the one or more user devices, a registration token received from the cloud-based messaging service and compose one or more notification messages upon transmitting the registration token to the one or more user devices. The registration token corresponds to an identifier associated with each application of the one or more applications. The data processing module is further configured to generate message metadata corresponding to the one or more notification messages and transmit, via the cloud-based messaging service, the one or more notification messages and the message metadata to the registered one or more applications based on a state of the one or more user devices. The state of the one or more user devices corresponds to an online state or an offline state.
[0020] In one or more implementations, for transmitting the one or more notification messages to the one or more applications, the data processing module is configured to determine whether the one or more user devices are in the online state, or the offline state based on a current network status and send the one or more notification messages, and the message metadata to the one or more applications upon the determination that the one or more user devices are in the online state.
[0021] In one or more implementations, the data processing module is configured to store the one or more notification messages in a buffer queue upon the determination that the one or more user devices are in the offline state and send the one or more notification messages, and the message metadata to the one or more applications when the one or more user devices transitions from the offline state to the online state.
[0022] According to a further aspect of the present disclosure, a method for receiving notification messages in a communication environment is disclosed. The method comprises sending, via a communication unit of one or more user devices, one or more requests to register one or more applications with a cloud-based messaging service. The method further comprises receiving, by an acquisition unit of the one or more user devices, a registration token from the cloud-based messaging service via a data processing module of a server processor, and receiving, by the acquisition unit from the cloud-based messaging service, one or more notification messages and message metadata corresponding to the one or more notification messages based on a state of the one or more user devices. The registration token corresponds to a unique identifier associated with the one or more applications. The state of the one or more user devices corresponds to an online state or an offline state.
[0023] In one or more implementations, the method comprises controlling, by a processing unit of the one or more user devices, a display interface of the one or more user devices to display the one or more notification messages.
[0024] According to another aspect of the present disclosure, a User Equipment (UE) for receiving notification messages in a communication environment is disclosed. The UE comprises a communication unit and an acquisition unit. The communication unit is configured to send one or more requests to register one or more applications with a cloud-based messaging service. The acquisition unit is configured to receive, from the cloud-based messaging service via a data processing module of a server processor, a registration token, and receive, from the cloud-based messaging service via the data processing module of the server processor, one or more notification messages and message metadata corresponding to the one or more notification messages based on a state of the one or more user devices. The registration token corresponds to a unique identifier associated with the one or more applications. The state of the one or more user devices corresponds to an online state or an offline state.
[0025] In one or more implementations, the UE comprises a processing unit configured to control a display interface of the UE to display the one or more notification messages.
BRIEF DESCRIPTION OF DRAWINGS
[0026] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.
[0027] FIG. 1 illustrates a communication environment for transmission of notification messages between various entities via a communication network, in accordance with an embodiment of the present disclosure.
[0028] FIG. 2 illustrates a block diagram depicting a server of the communication environment, in accordance with an embodiment of the present disclosure.
[0029] FIG. 3 illustrates a block diagram depicting a user device (or User Equipment (UE)) of the communication environment, in accordance with an embodiment of the present disclosure.
[0030] FIG. 4 illustrates a block diagram depicting various components of a processor of the server, in accordance with an embodiment of the present disclosure.
[0031] FIG. 5 illustrates a flowchart depicting a method for managing transmission of notification messages in the communication environment, in accordance with an embodiment of the present disclosure.
[0032] FIG. 6 depicts a flowchart depicting a method for receiving the notification messages in the communication environment, in accordance with an embodiment of the present disclosure.
[0033] FIG. 7 illustrates a schematic architecture diagram depicting a computing system, in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION OF THE INVENTION
[0034] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.
[0035] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.
[0036] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments”. Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations”.
[0037] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”
[0038] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.
[0039] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.
[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.
[0041] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.
[0042] The present invention relates to a system and a method for managing transmission of notification messages to various application platforms in a communication environment. The present disclosure further relates to a system and a method for receiving the notification messages in the communication environment.
[0043] An aspect of the present disclosure is to provide a unified notification engine that can deliver the notification messages seamlessly to client applications including both web-based applications and mobile applications, thereby improving users experience.
[0044] Another aspect of the present disclosure is to provide a system and a method that can eliminate need for separate notification triggers for the web-based applications and the mobile applications, thereby improving efficiency and reducing complexity of a notification management process.
[0045] Yet another aspect of the present disclosure is to provide a system and a method that can enable transmission of the notification messages and enhance cross-platform compatibility by facilitating customizable notification settings.
[0046] A further aspect of the present disclosure is to provide a system and a method that can generate and transmit the notification messages along with message metadata, including message identifiers, timestamps, priority levels, and encryption details, to enhance security and message tracking.
[0047] Another aspect of the present disclosure is to provide a system and a method that can facilitate authentication and validation of user devices during application registration with a cloud-based messaging service to prevent unauthorized access.
[0048] A further aspect of the present disclosure is to provide a scalable and flexible architecture that can be integrated with multiple messaging platforms and services to support diverse communication needs.
[0049] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.
[0050] A User Equipment (UE) corresponds to a communication device used by an end user. The UE may include smartphones, tablets, Internet of Things (IoT) devices, laptops, other wireless terminals, and the like devices capable of connecting to a communication network.
[0051] A client application refers to a software application installed on a UE that registers with a cloud-based messaging service to receive notification messages.
[0052] A messaging server or a server in context of the present disclosure refers to a centralized server responsible for managing, processing, and transmitting the notification messages between a cloud-based messaging service and registered UEs.
[0053] A cloud-based messaging service refers to a remote platform that is capable of delivering push notifications, or the like to registered client applications using standard messaging protocols, ensuring scalable and real time message distribution.
[0054] A communication network or a network corresponds to a communication medium (e.g., Long Term Evolution (LTE), Fifth Generation (5G), Wireless Fidelity (Wi-Fi), private enterprise networks, or the like) that facilitates data exchange between a messaging server, UEs, clients, and cloud-based messaging services.
[0055] A client device corresponds to a computing device (for e.g., workstation, server, embedded system, or the like) that may interact with a messaging server to initiate or manage notifications.
[0056] A notification message corresponds to a structured message containing alerts, updates, system generated messages, user specific prompts, or the like delivered from a messaging server to registered to UEs via a cloud-based messaging service.
[0057] Message metadata corresponds to additional data associated with a notification message. The message metadata may include a message identifier, a timestamp, a message priority level, a sender identifier, encryption details, a message expiration time, and the like, used for tracking, security, and optimized delivery of the notification message.
[0058] A message identifier corresponds to a unique identifier assigned to each notification message, facilitating message tracking and deduplication across network elements.
[0059] A message priority level refers to a classification parameter defining urgency of a notification message, including high priority messages, which are to be delivered immediately (for e.g., security alerts, emergency notifications, and the like), medium priority messages, which are processed with moderate urgency (for e.g., system updates), and low priority messages which are to be delivered as per network availability or user preferences (for e.g., promotional messages).
[0060] A notification type classification corresponds to a categorization of notification messages based on their function, including text-based alerts, multimedia notifications, system warnings, security advisories, event triggered alerts, and the like.
[0061] A message expiration time refers to a predefined validity period for a notification message, after which the notification message is discarded if undelivered, preventing network congestion and outdated notifications.
[0062] A message delivery mechanism refers to a mechanism for transmitting notification messages, and is selected based on network conditions, user preferences, or Service Level Agreements (SLAs). The message delivery mechanism may include real time push notifications, polling, deferred notifications, store and forward, and the like.
[0063] In the context of the present disclosure, a push notification refers to a mechanism where a cloud-based messaging service actively sends notification messages to a UE without requiring the UE to initiate a request.
[0064] A polling mechanism refers to an alternative to push notifications where a UE periodically queries a messaging server for pending notification messages when in an online state.
[0065] A registration token corresponds to a unique identifier assigned to a client application upon successful registration with a cloud based messaging service, enabling secure and targeted notification message delivery.
[0066] Authentication credentials refer to security related information (for e.g., device certificates, API keys, encrypted tokens, or the like) used to validate a UE and allow message reception.
[0067] A device identifier corresponds to a unique identifier (for e.g., IMEI, UUID, etc.) associated with a UE to track device registration and authentication.
[0068] A buffer queue refers to a temporary storage mechanism on a messaging server for holding notification messages when a UE is in an offline state, ensuring deferred message transmission upon the transition of the UE to an online state.
[0069] A network state in the context of the present disclosure, refers to a current network status of a UE by assessing whether the UE is in an online state (connected to a network) or an offline state (disconnected from the network) before transmission of notification messages.
[0070] An online state of the UE in context of the present disclosure, refers to a condition where the UE is actively connected to a network and is capable of receiving notification messages in real time.
[0071] An offline state of the UE in context of the present disclosure, corresponds to a condition where the UE is temporarily disconnected from a network, preventing immediate reception of notification messages.
[0072] Encryption details correspond to security attributes associated with a notification message, including encryption type, key exchange mechanism, digital signatures, and the like, ensuring secure transmission of the notification message.
[0073] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 7, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.
[0074] FIG. 1 illustrates a communication environment 100 for transmission of the notification messages between various entities via a communication network 120 (hereinafter may also be referred to as a “network 120”), in accordance with an embodiment of the present disclosure. The embodiment of the communication environment 100 shown in FIG. 1 is for illustration only. In particular, the communication environment 100 corresponds to a messaging environment. Other embodiments of the communication environment 100 may be used without departing from the scope of this disclosure.
[0075] The communication environment 100 may include a server 110 (hereinafter may also be referred to as a “messaging server 110”), the network 120, a cloud-based messaging service 130, user devices 140 (hereinafter may be collectively referred to as a “user device 140” or “User Equipments (UEs) 140”, or a “UE 140”), and client(s) 150.
[0076] The server 110 communicates with each of the cloud-based messaging service 130, the user devices 140, and the client(s) 150 via the network 120. The server 110 functions as a centralized entity responsible for managing transmission of the notification messages. The server 110 is configured to receive message requests from the clients 150, process the message requests, and forward the notifications to respective user devices 140 via the cloud-based messaging service 130. The server 110 may include modules for composing notification messages, generating message metadata, handling authentication, and determining optimal delivery mechanisms based on device availability and network conditions.
[0077] The network 120 enables message transmission and communication between components of the communication environment 100. The network 120 may correspond to one of an Internet, a proprietary Internet Protocol (IP) network, or other data network. The network 120 may include wired and/or wireless networks. For example, the network 120 may include a cellular network for e.g., a Fifth Generation (5G) network, a Long-Term Evolution (LTE) network, a Third Generation (3G) network, a Code Division Multiple Access (CDMA) network, etc.), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.
[0078] The cloud-based messaging service 130 corresponds to a platform or services that facilitates delivery of the notification messages to the user devices 140 without requiring direct device to device connections. The cloud-based messaging service 130 transmits the notification messages to the applications. The cloud-based messaging service 130 is configured to handle notification transmission, device registration management, message queuing, reliability mechanisms, to ensure notification message delivery. The server 110 interacts with the cloud-based messaging service 130 to route notifications to intended user devices. The cloud-based messaging service 130 may further send the registration token corresponding to registered client applications.
[0079] The cloud-based messaging service 130 enables optimized routing of the notification messages by determining best notification delivery mechanisms based on availability of the user devices 140, network conditions, and message priority settings. The cloud-based messaging service 130 ensures that the notification messages are transmitted securely to the user devices 140 by integrating authentication mechanisms, encryptions, and access controls. The cloud-based messaging services 140 offers cross platform compatibility and application independence i.e., the cloud-based messaging service 130 is configured to support a wide range of user devices including mobile devices such as smartphones, tablets, etc., web-based devices such as desktop computers, laptops, etc.), ensuring that the notification messages are delivered irrespective of the device type or operating system. The cloud-based messaging service 130 is designed to communicate with any application, whether it is a mobile application, web-based application, or a cloud-based enterprise solution, eliminating the need for application-specific notification implementations.
[0080] In one or more embodiments, applications may either be applications installed on the user devices 140 to communicate with the server 110. The user device(s) 140 may correspond to computing devices capable of receiving the notification messages. The user device(s) 140 may include mobile devices such as smartphones, tablets, IoT devices, smartwatches, and the like, and web-based devices such as the laptops, desktop computers, workstations, and the like. Each user device may communicate with the cloud-based messaging service 130 to receive push notifications sent by the server 110.
[0081] The clients 150 correspond to backend applications, web services, or enterprise systems that require real time messaging functionality. The clients 150 may represent interfaces that run on the user devices 140 to communicate with the server 110. The clients 150 may correspond to web browsers or a program requesting data from software applications running on the user devices 140. The clients 150 function as intermediaries between the user devices 140 and the cloud-based messaging service 130. The clients 150 are responsible for handling communication requests, managing message interactions, and facilitating seamless notification delivery between the back-end infrastructure and registered applications. The clients 150 do not represent the applications themselves but rather serve as communication interfaces that enable efficient data exchange.
[0082] Although FIG. 1 illustrates one example of the communication environment 100, various changes may be made to FIG. 1. For example, the communication environment 100 may include any number of user devices and servers in any suitable arrangement. Further, in another example, the communication environment 100 may include any number of components in addition to the components shown in FIG. 1. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.
[0083] FIG. 2 illustrates a block diagram depicting the server 110 of the communication environment 100, in accordance with an embodiment of the present disclosure.
[0084] The server 110 includes a device interface management module 112, an application interface management module 114, a communication interface 116, a processor 118, and a memory 122.
[0085] The device interface management module 112 manages communication between the server 110 and the user devices 140 in case where each of the user devices 140 is configured to receive push notification messages. The device interface management module 112 may further keep track of whether a user of each of the user devices 140 opted for receiving certain types of notifications messages or not. When a notification message needs to be sent, the device interface management module 112 determines or find out which user devices are configured to receive the notification message based on device settings and makes sure the notification message is sent only to those user devices that are configured to receive the notification message. The device interface management module 112 may also determine whether the notification messages were sent successfully to prevent any unauthorized access.
[0086] The application interface management module 114 streamlines a process of sending notification messages to the user devices 140. The application interface management module 114 may help in optimizing the communication interface 116 between the server 110 and the user devices 140 and thus ensures efficient and reliable delivery of the notification messages from the server 110 to the client applications (web-based and mobile applications) on the user devices 140. The application interface management module 114 supports a plurality of communication protocols, including Hypertext Transfer Protocol (HTTP), Message Queuing Telemetry Transport (MQTT) protocol, among others, enabling seamless integration between the server 110 and the user devices 140. The application interface management module 114 may also facilitate transformation of the notification messages into various formats compatible with the user devices 140 to ensure uniformity and consistency in delivery and presentation of the notification message.
[0087] The communication interface 116 may allow transmission and reception of data between the server 110 and the network 120. The communication interface 116 may include a transmitter, a receiver, and a single or a plurality of transmit antennas electrically coupled to the transmitter and the receiver. The communication interface 116 may include an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 116 is configured to communicate internally with internal hardware components. The communication interface 116 may be further configured to communicate with external devices via the network 120.
[0088] The communication interface 116 may be configured to enable the server 110 to communicate with various entities of the communication environment 100 via the network 120. Examples of the communication interface 116 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and/or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a Radio Frequency (RF) transceiver, one or more amplifiers, a Coder-Decoder (CODEC) chipset, a Subscriber Identity Module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication interface 116 may include any device and/or apparatus capable of providing wireless or wired communications between the server 110 and various other entities of the communication environment 100.
[0089] The processor 118 is configured to execute programs and other processes stored in the memory 122. The processor 118 is further configured to store data in the memory 122 and fetch the data from the memory 122 as required by an execution process. The processor 118 may also be coupled to a network interface that may allow the server 110 to communicate with other devices or systems over a network. The network interface may support communications over any suitable wired or wireless connection(s). The processor 118 may further include a plurality of processors, including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU).
[0090] The memory 122 stores a set of instructions required by the processor 118 of the server 110 for controlling its overall operations. Specifically, the memory 122 stores a microservices framework (not shown in FIG. 2). The microservices framework represents individual services for specific tasks, such as handling requests and processing data. The microservices framework within the memory 122 allows the server 110 to break down entire operations of the server 110 into smaller, independent services that may be developed, deployed, and scaled independently. Each of the microservices framework may adhere to a well-defined Application Programming Interface (API).
[0091] A part of the memory 122 may include a Random Access Memory (RAM), a Cache memory, or a Read Only Memory (ROM). Further, the memory 122 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of Electrically Programmable Memories (EPROM) or Electrically Erasable and Programmable Memories (EEPROM). In addition, the memory 122 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory 122 is non-movable. In some examples, the memory 122 may be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in the RAM or cache). The memory 122 may be an internal storage unit or an external storage unit of the server 110, cloud storage, or any other type of external storage.
[0092] FIG. 3 illustrates a block diagram depicting the user device 140 (hereinafter may also be referred to as a User Equipment (UE) 140 of the communication environment 100, in accordance with an embodiment of the present disclosure.
[0093] The user device 140 include the mobile devices such as smartphones, tablets, IoT devices, smartwatches, and the like, and web-based client devices such as laptops, desktop computers, workstations, and the like. The user device 140 may include a communication unit 142, an acquisition unit 144, a device processor 146, and a device memory 148.
[0094] The communication unit 142 may include antennas, Radio Frequency (RF) transceivers, a transmit processing circuitry, and a receive processing circuitry. The communication unit 142 enables communication between the user device 140 and external systems such as the server 110 and the cloud-based messaging service 130. The communication unit 142 supports mobile communication protocols (for e.g., LTE, 5G, Wi-Fi, and the like) for wireless devices, and internet-based communications for the web applications through HTTP, or other APIs. The communication unit 142 is configured to support handling of real time push notifications using protocols like cloud messaging, web push APIs, or the like. The communication unit 142 is further configured to send requests to register applications (web-based or mobile applications) with the cloud-based messaging service 130 and maintain a seamless connection with the server 110 for efficient message receipt.
[0095] The acquisition unit 144 is configured to receive, from the cloud-based messaging service 130 via the processor 118 of the server 110, a registration token. The registration token corresponds to a unique identifier associated with the applications. The acquisition unit 144 is further configured to receive, from the cloud-based messaging service 130 via the processor 118 of the server 110, the notification messages and message metadata corresponding to the notification messages based on a state of the user device 140. The state of the user device 140 corresponds to an online state or an offline state.
[0096] The device processor 146 (may also be referred to as a processing unit 146) may include one or more processors, microcontrollers, responsible for executing instructions stored in the device memory 148. The device processor 146 enables various functionalities such as processing received notification messages from the server 110, executing the web-based applications or the mobile applications that allows the users to manage the notification messages. The device processor 146 is further configured to perform authentication and verification of the notification messages using security credentials and optimized power and resource consumption to ensure efficient processing of the notification messages.
[0097] The device memory 148 includes volatile and non-volatile memory components such as the RAM, the ROM, flash storage, or secure storage modules. The device memory 122 is responsible for storing application data, the notification messages, and configuration settings. The device memory 148 is further configured to cache received notification messages to improve performance and enable offline access. The device memory 148 is configured to store the authentication credentials security tokens and encryption keys.
[0098] FIG. 4 illustrates a block diagram depicting various components of the processor 118 of the server 110, in accordance with an embodiment of the present disclosure.
[0099] The processor 118 may include units/modules selected from any of a reception module 118-1, an execution module 118-2 and a data processing module 118-3. The processor 118 may include, but are not limited to, other modules such as a generation module, an analytics module, a monitoring module, and the like. Each of the modules of the processor 118 may be communicatively connected to one another.
[0100] In an implementation, the processor 118, using the acquisition module 118-1, is configured to receive, receive, from the user devices 140, the requests to register the applications with the cloud-based messaging service 130.
[0101] The processor 118, using the execution module 118-2 is configured to register the applications with the cloud-based messaging service 130 upon receiving the requests. Each request of the requests includes the authentication credentials associated with the corresponding user device. The authentication credentials are used by the cloud-based messaging service 130 to validate the corresponding user device for registering the applications.
[0102] The processor 118, using the data processing module 118-3, is configured to transmit, to the user devices 140, the registration token received from the cloud-based messaging service 130, and compose the notification messages upon transmitting the registration token to the user devices 140. The registration token corresponds to the identifier associated with each application of the applications. The registration token corresponding to each of the registered applications is unique. In an implementation, the notification messages include at least one of a text-based alert, a multimedia message, a system generated update, a real time status notification, an event triggered alert, a security warning, an application update message, or a personalized user prompt. Each notification message of the notification messages is configured with a priority level and a predefined delivery mechanism. The predefined delivery mechanism is selected based on at least one of user preferences, network conditions, and availability of the user devices 140.
[0103] The processor 118, using the data processing module 118-3, is further configured to generate the message metadata corresponding to the notification messages and transmit, via the cloud-based messaging service 130, the notification messages and the message metadata to the registered applications based on the state of the user devices 140. The state of the user devices 140 corresponds to the online state or the offline state. In an implementation, the message metadata includes at least one of a message identifier of the notification messages, a timestamp indicating a time of notification message generation, a priority level defining an urgency of the notification message, a sender identifier, a notification message type classification, an expiration time for a notification message validity, and encryption details for secure transmission of the notification message.
[0104] In an implementation, for transmitting the notification messages to the applications, the processor 118 using the data processing module 118-3 is configured to determine whether the user devices 140 are in the online state, or the offline state based on the current network status, and send the notification messages, and the message metadata to the applications upon the determination that the user devices 140 are in the online state.
[0105] The processor 118, using the data processing module 118-3, is configured to store the notification messages in a buffer queue upon the determination that the user devices 140 are in the offline state. Furthermore, the processor 118, using the data processing module 118-3 is configured to send the notification messages, and the message metadata to the applications when the user devices 140 transitions from the offline state to the online state.
[0106] FIG. 5 illustrates a flowchart depicting a method 500 (hereinafter may also be interchangeably referred to as a “process 500”) for managing transmission of the notification messages in the communication environment 100, in accordance with an embodiment of the present disclosure. The method 500 comprises a series of operation steps indicated by blocks 502 through 516. Although the method 500 shows example blocks of steps 502 to 516, in some embodiments, the method 500 may include additional steps, fewer steps or steps in different order than those depicted in FIG. 5. In other embodiments, the steps 502 to 516 may be combined or may be performed in parallel. The method 500 starts at block 502.
[0107] At block 502, In an implementation, the acquisition module 118-1 of the processor 118 receives, from the user devices 140, the requests to register the applications with the cloud-based messaging service 130.
[0108] At block 504, the execution module 118-2 of the processor 118 registers the applications with the cloud-based messaging service 130 upon receiving the requests and initiation of the application registration processes on the user devices 140. Each of the application registration processes includes user device identification, authentication, and the like. Each request of the requests includes the authentication credentials associated with the corresponding user device.
[0109] At block 506, the data processing module 118-3 of the processor 118 transmits, to the user devices 140, the registration token received from the cloud-based messaging service 130. The registration token serves as a unique identifier that authenticates the applications on the user device 140 with the cloud-based messaging service 130. The registration token ensures that only authorized applications receive the notification messages, preventing unauthorized access or misuse. Further, since each registration token is uniquely associated with a particular application instance, the cloud-based messaging service 130 can precisely route the notification messages to the correct destination. This eliminates need for complex lookups and ensuring that the notification messages are delivered to the intended applications without errors. Moreover, in cases where multiple applications on the same user device are registered for notifications each application receives a distinct registration token. This prevents message conflicts and ensures that the notification messages are directed to the right application instance.
[0110] At block 508, the data processing module 118-3 of the processor 118 composes the notification messages upon transmitting the registration token to the user devices 140. The notification messages correspond to structured data packets generated by the server 110 and delivered to the user devices 140 via the cloud-based messaging service 130 or direct communication channels. The notification messages contain message metadata, content, and delivery parameters to ensure accurate and timely delivery. The notification messages are composed by defining the message title, body, optional multimedia content, interactive elements, and the like. The composition of the notification messages involves structuring, formatting, and preparing the message content before transmission. This process ensures that the notification messages are relevant, properly formatted, and ready for delivery to the intended user device 140.
[0111] The data processing module 118-3 may gather raw data required for composing the notification message. The data sources may include user activity logs, system generated alerts, external APIs, or predefined message templates. The data processing module 1183 may further organize the extracted data into a structured format the message format may include plain text, multimedia (images, audio, video), or interactive elements such as clickable links or action buttons. The message content is encrypted to ensure secure transmission and prevent unauthorized access. Before transmission, the notification message is packaged with the message metadata including the message identifier, timestamp, operation details, and center information. The final composed message is then ready for transmission to the user devices 140.
[0112] The registration token corresponds to the identifier associated with each application of the applications. The registration token corresponding to each of the registered applications is unique. In an implementation, the notification messages include at least one of the text-based alert, the multimedia message, the system generated update, the real time status notification, the event triggered alert, a security warning, the application update message, or personalized user prompts. Each notification message of the notification messages is configured with the priority level and the predefined delivery mechanism. The predefined delivery mechanism is selected based on at least one of user preferences, network conditions, and availability of the user devices 140.
[0113] At block 510, the data processing module 118-3 of the processor 118 generates the message metadata corresponding to the notification messages. In an implementation, the message metadata includes at least one of the message identifier of the notification messages, the timestamp indicating the time of notification message generation, the priority level defining the urgency of the notification message, the sender identifier, the notification message type classification, the expiration time for the notification message validity, and the encryption details for secure transmission of the notification messages.
[0114] At block 512, the data processing module 118-3 of the processor 118 determines whether the user devices 140 are in the online state based on the current network status. Upon the determination that the user devices 140 are in the online state, the method 500 proceeds to block 516 and to block 514 upon the determination that the user devices 140 are in the offline state. The determination involves continuous monitoring, periodic status checks, or real-time network event tracking. The user device 140 continuously communicates with the server 110 and the cloud-based messaging service 130 via the communication unit 142 over the network 120. The monitoring is done to check whether the connection is persistent, i.e., the user devices 140 maintain an active connection (long polling, etc.) or intermittent i.e., the user devices 140 maintain network connection periodically (e.g., polling mechanisms, push notification services).
[0115] At block 514, the data processing module 118-3 of the processor 118 stores the notification messages in the buffer queue and wait till the user devices 140 transitions from the offline state to the online state. The data processing module 118-3 determines whether to immediately send the notification messages or wait until the user devices 140 becomes available. The data processing module 118-3 periodically checks the network status of the user devices 140. When the user devices 140 becomes online, the flow of the method 500 proceeds to block 516. However, of the user devices 140 remains offline beyond a predefined period, the notification messages may be discarded.
[0116] At block 516, the data processing module 118-3 of the processor 118 transmits, via the cloud-based messaging service 130, the notification messages and the message metadata to the registered applications.
[0117] FIG. 6 depicts a flowchart depicting a method 600 for receiving the notification messages in the communication environment 100, in accordance with an embodiment of the present disclosure. The method 600 comprises a series of operation steps indicated by blocks 602 through 606. Although the method 600 shows example blocks of steps 602 to 606, in some embodiments, the method 600 may include additional steps, fewer steps or steps in different order than those depicted in FIG. 6. In other embodiments, the steps 602 to 606 may be combined or may be performed in parallel. The method 600 starts at block 602.
[0118] At block 602, the communication unit 142 of the user device 140 sends the requests to register the applications with the cloud-based messaging service 130.
[0119] At block 604, the acquisition unit 144 of the user device 140 receives, from the cloud-based messaging service 130 via the processor 118 of the server 110, the registration token. The registration token corresponds to the unique identifier associated with the applications.
[0120] At block 606, the acquisition unit 144 of the user device 140 receives, from the cloud-based messaging service 130 via the processor 118 of the server 110, the notification messages and the message metadata corresponding to the notification messages based on the state of the user devices 140. The state of the user devices 140 corresponds to the online state or the offline state.
[0121] FIG. 7 illustrates a schematic architecture diagram depicting a computing system 700, in accordance with an embodiment of the present disclosure. The computing system 700 includes a network 702 (similar to network 120 of FIG. 1), a network interface 704, a processor 706 (similar in functionality to the processor 118 of FIG. 2), an Input/Output (I/O) interface 708 and a non-transitory computer readable storage medium 710 (hereinafter may also be referred to as the “storage medium 710” or the “storage media 710”, similar to the memory 122 of FIG. 2).
[0122] The network interface 704 includes wireless network interfaces such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA) or wired network interfaces such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers-864 (IEEE-864).
[0123] The processor 706 may include various processing circuitry and communicate with the storage medium 710 and the I/O interface 708. The processor 706 is configured to execute instructions stored in the storage medium 710 and to perform various processes. The processor 706 may include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, the CPU, the AP, the dedicated processor, or the like, the graphics-only processing unit such as the GPU, the microcontroller, the FPGA, the programmable logic device, the discrete hardware component, or any combination thereof. The processor 706 may be configured to execute computer-readable instructions 710-1 stored in the storage medium 710 to cause the server 110 to perform various functions.
[0124] The storage medium 710 stores a set of instructions i.e., computer program instructions 710-1 (hereinafter may also be referred to as instructions 710-1) required by the processor 706 for controlling its overall operations and a microservices framework 710-2.
[0125] The storage media 710 may include an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like. For example, the storage media 710 may include, but are not limited to, hard drives, floppy diskettes, optical disks, ROMs, RAMs, EPROMs, EEPROMs, flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more embodiments, the storage media 710 includes a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk-Read/Write (CD-R/W), and/or a Digital Video Disc (DVD).
[0126] In one or more implementations, the storage medium 710 stores computer program code configured to cause the computing system 700 to perform at least a portion of the processes and/or methods. Accordingly, in at least one implementation, the computing system 700 performs the method for managing the transmission of the notification messages in the communication network.
[0127] Embodiments of the present disclosure have been described above with reference to flowchart illustrations of methods and systems according to embodiments of the disclosure, and/or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and/or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed method.
[0128] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer-readable memory or memory devices (for example, the memory 122 or the storage medium 710) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions 710-1 stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).
[0129] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 118 or the processor 706) to perform one or more functions as described herein. The instructions 710-1 may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.
[0130] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments may include providing the system and the method, that enables sending the notification messages seamlessly to the client applications across different application platforms including the web-based applications and the mobile applications, thereby improving the users’ experience. A further potential advantage of the one or more embodiments disclosed herein may include eliminating the need for the separate notification triggers for the web-based applications and the mobile applications, thereby improving efficiency and reducing complexity of the notification management process. Another noteworthy advantage of the present disclosure may include but not limited thereto, enhanced cross-platform compatibility and customizable notification settings thereby improving end users experience. The customizable notification settings allow the users to tailor their notification experience based on personal preferences, device conditions, and contextual factors. The customizable notification settings enable control over notification message type, the priority levels, message delivery mechanisms, timing, and filtering to enhance the user experience and avoid unnecessary interruptions.
[0131] Another potential advantage offered by the embodiments of the present disclosure may include providing a system and a method that is capable of generating and transmitting the notification messages along with message metadata, including the message identifiers, the timestamps, the priority levels, and the encryption details, to enhance security and message tracking.
[0132] A yet another potential advantage offered by the embodiments of the present disclosure may include providing a system and a method that facilitates the authentication and the validation of user devices during application registration with the cloud-based messaging service to prevent unauthorized access.
[0133] Another noteworthy advantage offered by the embodiments of the present disclosure may include providing the scalable and flexible architecture that can be integrated with multiple messaging platforms and services to support diverse communication needs.
[0134] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.
[0135] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.
[0136] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.
LIST OF REFERENCE NUMERALS
[0137] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:
100 - Communication Environment/Environment
110 – Messaging Server/Server
112 – Device Interface Management Module
114 – Application Interface Management Module
116 – Communication Interface
118 – Processor(s)/Server Processor(s)
118-1 – Reception Module
118-2 – Execution Module
118-3 – Data Processing Module
120 – Communication Network/Network
122 – Memory/Server Memory
130 – Cloud-based messaging service
140 – User Device/User Equipment (UE)
142 – Communication Unit
144 – Acquisition Unit
146 – Device Processor(s)
148 – Device Memory
150 – Client
500 – Method for managing transmission of notification messages
600 – Method for receiving the notification messages
700 - Computing System
702 – Network
704 - Network interface
706 – Processor
708 – I/O Interface
710 - Storage Medium
710-1 – Instructions
710-2 – Microservices framework
,CLAIMS:We Claim:

1. A method (500) for managing transmission of notification messages in a communication environment (100), the method (500) comprising:
receiving, by a reception module (118-1) from one or more user devices (140), one or more requests to register one or more applications, with a cloud-based messaging service (130);
registering, by an execution module (118-2), the one or more applications with the cloud-based messaging service (130) upon receiving the one or more requests;
transmitting, by a data processing module (118-3) to the one or more user devices (140), a registration token received from the cloud-based messaging service (130), wherein the registration token corresponds to an identifier associated with each application of the one or more applications;
composing, by the data processing module (118-3), one or more notification messages upon transmitting the registration token to the one or more user devices (140);
generating, by the data processing module (118-3), message metadata corresponding to the one or more notification messages; and
transmitting, by the data processing module (118-3) via the cloud-based messaging service (130), the one or more notification messages and the message metadata to the registered one or more applications based on a state of the one or more user devices (140), wherein the state of the one or more user devices (140) corresponds to an online state or an offline state.

2. The method (500) as claimed in claim 1, wherein each request of the one or more requests includes authentication credentials associated with the corresponding user device, the authentication credentials being used by the cloud-based messaging service (130) to validate the corresponding user device for registering the one or more applications.

3. The method (500) as claimed in claim 1, wherein the registration token corresponding to each of the registered one or more applications is unique.

4. The method (500) as claimed in claim 1, wherein the one or more notification messages include at least one of a text based alert, a multimedia message, a system generated update, a real time status notification, an event triggered alert, a security warning, an application update message, or a personalized user prompt, and wherein each notification message of the one or more notification messages is configured with a priority level and a predefined delivery mechanism, the predefined delivery mechanism being selected based on at least one of user preferences, network conditions, and availability of the one or more user devices (140).

5. The method (500) as claimed in claim 1, wherein the message metadata includes at least one of a message identifier of the one or more notification messages, a timestamp indicating a time of notification message generation, a priority level defining an urgency of the one or more notification message, a sender identifier, a notification message type classification, an expiration time for the one or more notification messages, and encryption details for secure transmission of the one or more notification messages.

6. The method (500) as claimed in claim 1, wherein for transmitting the one or more notification messages to the one or more applications, the method (500) comprises:
determining, by the data processing module (118-3), whether the one or more user devices (140) are in the online state, or the offline state based on a current network status; and
sending, by the data processing module (118-3), the one or more notification messages, and the message metadata to the one or more applications upon the determination that the one or more user devices (140) are in the online state.

7. The method (500) as claimed in claim 6, comprising:
storing, by the data processing module (118-3), the one or more notification messages in a buffer queue upon the determination that the one or more user devices (140) are in the offline state; and
sending, by the data processing module (118-3), the one or more notification messages, and the message metadata to the one or more applications when the one or more user devices (140) transitions from the offline state to the online state.

8. A system (110) for managing transmission of notification messages in a communication environment (100), the system comprising:
a reception module (118-1) configured to receive, from one or more user devices (140), one or more requests to register one or more applications with a cloud-based messaging service (130);
an execution module (118-2) configured to register the one or more applications with the cloud-based messaging service (130) upon receiving the one or more requests; and
a data processing module (118-3) configured to:
transmit, to the one or more user devices (140), a registration token received from the cloud-based messaging service (130), wherein the registration token corresponds to an identifier associated with each application of the one or more applications;
compose one or more notification messages upon transmitting the registration token to the one or more user devices (140);
generate message metadata corresponding to the one or more notification messages; and
transmit, via the cloud-based messaging service (130), the one or more notification messages and the message metadata to the registered one or more applications based on a state of the one or more user devices (140), wherein the state of the one or more user devices (140) corresponds to an online state or an offline state.

9. The system (110) as claimed in claim 8, wherein each request of the one or more requests includes authentication credentials associated with the corresponding user device, the authentication credentials being used by the cloud-based messaging service (130) to validate the corresponding user device for registering the one or more applications.

10. The system (110) as claimed in claim 8, wherein the registration token corresponding to each of the registered one or more applications is unique.

11. The system (110) as claimed in claim 8, wherein the one or more notification messages include at least one of a text based alert, a multimedia message, a system generated update, a real time status notification, an event triggered alert, a security warning, an application update message, or a personalized user prompt, and wherein each notification message of the one or more notification messages is configured with a priority level and a predefined delivery mechanism, the predefined delivery mechanism being selected based on at least one of user preferences, network conditions, and availability of the one or more user devices (140).

12. The system (110) as claimed in claim 8, wherein the message metadata includes at least one of a message identifier of the one or more notification messages, a timestamp indicating a time of notification message generation, a priority level defining an urgency of the notification message, a sender identifier, a notification message type classification, an expiration time for a notification message validity, and encryption details for secure transmission of the notification message.

13. The system (110) as claimed in claim 8, wherein for transmitting the one or more notification messages to the one or more applications, the data processing module (118-3) is configured to:
determine whether the one or more user devices (140) are in the online state, or the offline state based on a current network status; and
send the one or more notification messages, and the message metadata to the one or more applications upon the determination that the one or more user devices (140) are in the online state.

14. The system (110) as claimed in claim 13, wherein the data processing module (118-3) is configured to:
store the one or more notification messages in a buffer queue upon the determination that the one or more user devices (140) are in the offline state; and
send the one or more notification messages, and the message metadata to the one or more applications when the one or more user devices (140) transitions from the offline state to the online state.

15. A method (600) for receiving notification messages in a communication environment (100), the method (600) comprising:
sending, via a communication unit (142) of one or more user devices (140), one or more requests to register one or more applications with a cloud-based messaging service (130);
receiving, by an acquisition unit (144) of the one or more user devices (140), a registration token from the cloud-based messaging service (130) via a data processing module (118-3) of a server processor (118), wherein the registration token corresponds to a unique identifier associated with the one or more applications; and
receiving, by the acquisition unit (144) from the cloud-based messaging service (130), one or more notification messages and message metadata corresponding to the one or more notification messages based on a state of the one or more user devices (140), wherein the state of the one or more user devices (140) corresponds to an online state or an offline state.

16. The method (600) as claimed in claim 15, comprising controlling, by a processing unit (146) of the one or more user devices (140), a display interface of the one or more user devices (140) to display the one or more notification messages.

17. A user device (140) for receiving notification messages in a communication environment (100), the user device (140) comprising:
a communication unit (142) configured to send one or more requests to register one or more applications with a cloud-based messaging service (130); and
an acquisition unit (144) configured to:
receive, from the cloud-based messaging service (130) via a data processing module (118-3) of a server processor (118), a registration token, wherein the registration token corresponds to a unique identifier associated with the one or more applications; and
receive, from the cloud-based messaging service (130) via the data processing module (118-3) of the server processor (118), one or more notification messages and message metadata corresponding to the one or more notification messages based on a state of the one or more user devices (140), wherein the state of the one or more user devices (140) corresponds to an online state or an offline state.

18. The user device (140) as claimed in claim 17, comprising a processing unit (146) configured to control a display interface of the user device (140) to display the one or more notification messages.