FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR SENDING ONE OR MORE TEMPLATE-BASED MESSAGES ON OCCURRENCE OF AN EVENT”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR SENDING ONE OR MORE TEMPLATE-BASED MESSAGES ON OCCURRENCE OF AN EVENT
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to subscription management systems. More particularly, embodiments of the present disclosure relate to a method and a system for sending one or more template-based messages on occurrence of an event.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Subscription is purchase of a service or offer or plan by a user from a marketplace. Subscription lifecycle is collection of events associated with a subscription that is purchased by a user. For example, subscription lifecycle can include events like creation, updation, pausing, termination etc. A vendor offers a service or a plan or an offer to a user in marketplace. A template-based email is an email sent on occurrence of an event during subscription lifecycle and is based on a template that can be configured by a vendor in subscription engine module.
[0004] When a user buys any plan/offer/service, a vendor is required to send template- based email for various events that happens during subscription lifecycle. In conventional approaches, each vendor (selling in marketplace) would have its own notification engine configured to receive triggers for each event of subscription lifecycle and send a template-based email for said event. As a result, in conventional approaches, marketplace or subscription engine module has to interface with several notification engines, which is resource intensive, costly and inefficient approach for sending template-based emails. Moreover, each vendor can have their own template which said vendor intends to send at different events, which can be different for each vendor. Existing approaches to sending template-based email were inflexible to cater needs of each vendor. Furthermore, for any new template to be introduced it is needed to define template specific requirement and that too with static content and requires code change in the existing code base.

[0005] Hence, there exists a need to provide a method and system for sending one or more template-based messages on occurrence of an event.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for sending one or more template-based messages on occurrence of an event. The method comprises sending, by a scheduler module to a subscription engine module, a trigger related to an occurring event. The method further comprises determining, by the subscription engine module, a target message template and a time to dispatch of a final message related to the occurring event, based on the trigger received from the scheduler module. The target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, or a new real-time configured message template configured by a vendor module. The method further comprises sending, by the subscription engine module to a mediator server, a set of details of one or more customers, and the final message, for sending to the one or more customers. The method further comprises sending, by the mediator server, the final message to the one or more customers.
[0008] In an exemplary aspect of the present disclosure, prior to the determining, by the subscription engine module, the target message template, the method comprises configuring, by the vendor module on the subscription engine module, a new message template in real-time for the occurring event.
[0009] In an exemplary aspect of the present disclosure, the method further comprises storing, by the vendor module in a storage unit, the configured new message template in real-time for the occurring event.
[0010] In an exemplary aspect of the present disclosure, the method further comprises configuring, by the vendor module, one or more message templates for one or more events. The method further comprises storing, by the vendor module in a storage unit, the configured one or more message templates for the one or more events, in the set of one or more pre-defined message templates.

[0011] In an exemplary aspect of the present disclosure, the one or more pre-defined message templates and the new real-time configured message template are based on one of: a mark-up format and a plain text format.
[0012] In an exemplary aspect of the present disclosure, prior to the sending, by the mediator server, the final message to the one or more customers, the method comprises displaying, by a user interface, a user-configurable settings related to a message template of the final message.
[0013] Another aspect of the present disclosure may relate to a system for sending one or more template-based messages on occurrence of an event. The system comprises a scheduler module configured to send, to a subscription engine module, a trigger related to an occurring event. The subscription engine module is connected at least with the scheduler module and the subscription engine module configured to determine a target message template and a time to dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module. The target message template is one of: a pre-defined message template selected from a set of one or more pre¬defined message templates, and a real-time configured message template configured by a vendor module. The subscription engine module is further configured to send, to a mediator server, a set of details of one or more customers, and the final message, for sending to the one or more customers. The mediator server is configured to send the final message to the one or more customers.
[0014] Another aspect of the present disclosure may relate to a first user device for sending one or more template-based messages on occurrence of an event. The first user device comprising scheduler module configured to send, to a subscription engine module, a trigger related to an occurring event, The subscription engine module configured to determine a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module. The target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a real-time configured message template configured by a vendor module. The subscription engine module is further configured to send, to a mediator server, a set of details of one or more customers, and the final message, for sending to the one or more customers. The mediator server configured to send the final message to the one or more customers.
[0015] Another aspect of the present disclosure may relate to a second user device for receiving one or more template-based messages on occurrence of an event, the second user device comprising a memory, and a processor coupled to the memory. Further, the processor is configured to transmit to a system, a trigger related to an occurring event, and receive from the system, the final message based on

the trigger. Further, the final message is determined based on determining, by the system, a target
message template and a time for dispatch of a final message related to an occurring event, based on the
trigger received from the scheduler module, wherein the target message template is one of: a pre-defined
message template selected from a set of one or more pre-defined message templates, and a new real-
5 time configured message template configured by a vendor module.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for sending one or more template-based messages on occurrence of an event, the instructions include executable code which, when executed by a one or more units of a
10 system, causes: scheduler module of the system to send, to a subscription engine module, a trigger
related to an occurring event. Further, the instructions include executable code, which when executed causes the subscription engine module of the system to determine a target message template and a time to dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module, wherein the target message template is one of: a pre-defined message template
15 selected from a set of one or more pre-defined message templates, and a real-time configured message
template configured by a vendor module. Further, the instructions include executable code, which when executed causes the subscription engine module of the system to send, to a mediator server, a set of details of one or more customers, and the final message, for sending to the one or more customers. Further, the instructions include executable code, which when executed causes the mediator server of
20 the system to send the final message to the one or more customers.
OBJECTS OF THE INVENTION
[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein
25 satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for sending one or more template-based messages on occurrence of an event.
30 [0019] It is another object of the present disclosure to provide a solution that enables creation and
configuration of template email as per subscription life cycle which comprises events like creation, updation, pausing, termination etc.
[0020] It is yet another object of the present disclosure to provide a solution that enables sending same
35 template or a different template for different offer/service/plans sold by a vendor.
5

[0021] It is yet another object of the present disclosure to provide a solution that allows configuring templates using either a coding language or as a plain text.
[0022] It is yet another object of the present disclosure to provide a solution that obviates the need of
5 a vendor to integrate vendor notification engine with subscription engine module.
[0023] It is yet another object of the present disclosure to provide a solution that is efficient, cost-effective, less resource intensive and maintenance friendly.
10 [0024] It is yet another object of the present disclosure to provide a solution that allows vendors to
change the configured templates on the fly.
[0025] It is yet another object of the present disclosure to provide a solution that obviates requirement of expertise to change codebase of the notification templates or system. 15
DESCRIPTION OF THE DRAWINGS
[0026] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like
20 reference numerals refer to the same parts throughout the different drawings. Components in the
drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled
25 in the art that disclosure of such drawings includes disclosure of electrical components or circuitry
commonly used to implement such components.
[0027] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features
of the present disclosure may be implemented in accordance with exemplary implementation of the
30 present disclosure.
[0028] FIG. 2 illustrates an exemplary block diagram of a system for sending one or more template-based messages on occurrence of an event, in accordance with exemplary implementations of the present disclosure. 35
[0029] FIG. 3 illustrates a method flow diagram for sending one or more template-based messages on occurrence of an event in accordance with exemplary implementations of the present disclosure.
6

[0030] FIG. 4 illustrates another exemplary method flow diagram [400] for sending one or more template-based messages on occurrence of an event, in accordance with exemplary implementations of the present disclosure. 5
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
10
[0032] In the following description, for the purposes of explanation, various specific details are set forth in order 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 may each be used independently of one another or with any
15 combination of other features. An individual feature may not address any of the problems discussed
above or might address only some of the problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is not intended to limit the
scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary
20 embodiments will provide those skilled in the art with an enabling description for implementing an
exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0034] Specific details are given in the following description to provide a thorough understanding of
25 the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments
may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
30 [0035] Also, it is noted that individual embodiments may be described as a process which is depicted
as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in
35 a figure.
7

[0036] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example,
instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited
by such examples. In addition, any aspect or design described herein as “exemplary” and/or
“demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or
5 designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of
ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
10
[0037] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a
15 (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated
Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
20
[0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
25 user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a
general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are
30 required to implement the features of the present disclosure.
[0039] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable
medium including any mechanism for storing information in a form readable by a computer or similar
machine. For example, a computer-readable medium includes read-only memory (“ROM”), random
35 access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices
or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
8

[0040] As used herein “interface” or “user interface refers to a shared boundary across which two or
more separate components of a system exchange information or data. The interface may also be referred
to a set of rules or protocols that define communication or interaction of one or more modules or one
5 or more units with each other, which also includes the methods, functions, or procedures that may be
called.
[0041] All modules, units, components used herein, unless explicitly excluded herein, may be software
modules or hardware processors, the processors being a general-purpose processor, a special purpose
10 processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors,
one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
15 [0042] As used herein the transceiver unit include at least one receiver and at least one transmitter
configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0043] As discussed in the background section, the current known solutions have several shortcomings.
20 The present disclosure aims to overcome the above-mentioned and other existing problems in this field
of technology by providing method and system for sending one or more template-based messages on occurrence of an event. The present solution encompasses sending of a trigger related to an occurring event, based on which a target message template and a time for dispatch of a final message related to the occurring event is decided. Further the present solution encompasses that a set of details of one or
25 more customers and the final message for sending to the one or more customers are transmitted to a
mediator server and thereafter the mediator server sends the final message to the one or more customers.
[0044] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation
30 of the present disclosure. In an implementation, the computing device [100] may also implement a
method for sending one or more template-based messages on occurrence of an event utilising the system. In another implementation, the computing device [100] itself implements the method for sending the one or more template-based messages on occurrence of the event using one or more units configured within the computing device [100], wherein said one or more units are capable of
35 implementing the features as disclosed in the present disclosure.
9

[0045] The computing device [100] may include a bus [102] or other communication mechanism for
communicating information, and a processor [104] coupled with bus [102] for processing information.
The processor [104] may be, for example, a general-purpose microprocessor. The computing device
[100] may also include a main memory [106], such as a random-access memory (RAM), or other
5 dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed
by the processor [104]. The main memory [106] also may be used for storing temporary variables or
other intermediate information during execution of the instructions to be executed by the processor
[104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104],
render the computing device [100] into a special-purpose machine that is customized to perform the
10 operations specified in the instructions. The computing device [100] further includes a read only
memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
[0046] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided
15 and coupled to the bus [102] for storing information and instructions. The computing device [100] may
be coupled via the bus [102] to a display [112], such as a Cathode Ray Tube (CRT), Liquid Crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command
20 selections to the processor [104]. Another type of user input device may be a cursor controller [116],
such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
25
[0047] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing
30 device [100] in response to the processor [104] executing one or more sequences of one or more
instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry
35 may be used in place of or in combination with software instructions.
10

[0048] The computing device [100] also may include a communication interface [118] coupled to the
bus [102]. The communication interface [118] provides a two-way data communication coupling to a
network link [120] that is connected to a local network [122]. For example, the communication interface
[118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a
5 modem to provide a data communication connection to a corresponding type of telephone line. As
another example, the communication interface [118] may be a local area network (LAN) card to provide
a data communication connection to a compatible LAN. Wireless links may also be implemented. In
any such implementation, the communication interface [118] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of
10 information.
[0049] The computing device [100] can send messages and receive data, including program code,
through the network(s), the network link [120] and the communication interface [118]. In the Internet
example, a server [130] might transmit a requested code for an application program through the Internet
15 [128], the ISP [126], the Host [124], the local network [122], and the communication interface [118].
The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0050] Referring to FIG. 2, an exemplary block diagram of a system [200] for sending one or more
20 template-based messages on occurrence of an event is shown, in accordance with the exemplary
implementations of the present disclosure. The system [200] comprises at least one vendor module
[202], at least one scheduler module [204], at least one subscription engine module [206] and at least
one mediator server [208]. Also, all of the components/ units of the system [200] are assumed to be
connected to each other unless otherwise indicated below. As shown in the figures all units shown
25 within the system [200] should also be assumed to be connected to each other. Also, in FIG. 2 only a
few units are shown, however, the system [200] may comprise multiple such units or the system [200]
may comprise any such numbers of said units, as required to implement the features of the present
disclosure. Further, in an implementation, the system [200] may be present in a user device to implement
the features of the present disclosure. The system [200] may reside wholly or partially in a server. In
30 yet another implementation, the system [200] may be in connection with the server.
[0051] The system [200] is configured to send one or more template-based messages on occurrence of an event, with the help of the interconnection between the components/units of the system [200].
35 [0052] Further, in accordance with the present disclosure, it is to be acknowledged that the
functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is
11

recognized that various configurations and combinations thereof are within the scope of the disclosure.
The functionality of specific units as disclosed in the disclosure should not be construed as limiting the
scope of the present disclosure. Consequently, alternative arrangements and substitutions of units,
provided they achieve the intended functionality described herein, are considered to be encompassed
5 within the scope of the present disclosure.
[0053] In order to send one or more template-based messages on occurrence of an event, the scheduler module [204] is configured to send to a subscription engine module [206], a trigger related to an occurring event. The one or more template-based messages include but not limited to electronic mails,
10 push notification, and/or electronic messages (e.g. SMS) etc. The event includes but not limited to
creation, updation, pausing, and/or termination of a subscription, a offers, free trails, discount coupons and any other like such events that may be appreciated by a person skilled in the art as within the scope of the present disclosure. For example, a user had purchased a subscription A and upon termination of the subscription, the scheduler module [204] sends to the subscription engine module [206], the triggers
15 related to occurrence of a termination event.
[0054] As used herein, the “subscription engine module [206]” may refer to a server that manages the entire lifecycle of subscriptions for the one or more customers. Further, the subscription engine module [206] may communicate with one or more content platforms to provision and enable consumption of
20 content and enables the one or more customers to set up recurring events and manage their subscriptions.
The subscription engine module [206] may serve as a central hub for subscription management, communicating with the one or more customers through various communication channels such as web applications, mobile applications, integration Application Programming Interfaces (APIs), a webhooks. Furthermore, the subscription engine module [206] may utilise one or more protocols for
25 communication as a Hypertext Transfer Protocol (HTTP), a web services (WS), a Representational State
of Resource (REST), Events protocol over TCP (Transmission Control Protocol) connector.
[0055] As used herein, the “trigger” may refer to a pre-defined action that is automatically executed in response to an occurring of a specific event, such as a creation event, an updation event, a pause event,
30 or a termination event of a particular subscription. Further, the trigger may be associated with a
template-based message, which can be in the form of electronic mails, push notifications, electronic messages (e.g. SMS), or other types of notifications. Further, when the specific event occurs, the trigger is activated, and the corresponding message is sent to the designated recipient, such as a user or a system module.
35
[0056] Furthermore, in an exemplary implementation of the present disclosure, triggers may be used to automate communication and workflows based on specific events related to subscription lifecycle,
12

such as a subscription creation trigger to send a welcome message to a corresponding user, a
subscription updation trigger to notify the corresponding user of changes to their subscription, a
subscription pausing trigger to inform the corresponding user of the pause and any necessary next steps,
a subscription termination trigger to send a termination notification and potentially offer renewal
5 options, and any other such like trigger that may be appreciated by a person skilled in the art as within
the scope of the present disclosure.
[0057] The subscription engine module [206] is connected at least with the scheduler module [204], and the subscription engine module [206] configured to determine a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204]. The target message template is one of a pre-defined message template selected from a set of one or more pre-defined message templates, and a real-time configured message template configured by a vendor module [202]. For example, the subscription engine module [206] decides the target message template (such as updation message template) and a time to send the final message according to the decided target message template related to the occurring event (such as updation event), based on the trigger received from the scheduler module [204].
[0058] The present disclosure encompasses that prior to the deciding, by the subscription engine
module [206], the target message template, the vendor module [202] is configured to configure, on the
20 subscription engine module [206], a new message template in real-time for the occurring event. For
example, the vendor module [202] may configure the new message template in real-time for occurring event such as pause event.
[0059] The present disclosure encompasses that the one or more pre-defined message templates and the new real-time configured message template are based on one of a mark-up format and a plain text format. For example, the one or more pre-defined message templates and the new real-time configured message template may be generated either through the mark-up format (such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS)) or the plain text format (Short Message Service (SMS)).
[0060] The present disclosure encompasses that the vendor module [202] is configured to store, in a storage unit [210], the configured new message template in real-time for the occurring event.
[0061] The present disclosure encompasses that the vendor module [202] is configured to configure
35 one or more message templates for one or more events. The vendor module [202] further configured to
store, in the storage unit [210], the configured one or more message templates for the one or more events, in the set of one or more pre-defined message templates.
13

[0062] The present disclosure encompasses that the system [200] further comprising a user interface
[212], wherein prior to the mediator server [208] sending the final message to the one or more
customers, the user interface [212] is configured to display a user-configurable settings related to a
5 message template of the final message. The user-configurable settings include but not limited to time,
date, frequency, and/or location, user(s), message preview, etc. The present disclosure encompasses that the mediator server [208] is an intermediary server or proxy server that acts as an intermediary between the one or more customers/clients and other servers.
10 [0063] The subscription engine module [206] is further configured to send to the mediator server [208],
a set of details of the one or more customers, and the final message (e.g., email or message or notification), for sending to the one or more customers. The set of details of the one or more customers include but not limited to name, phone number, IP address, email, shipping address, order ID, product name, quantity, and/or price etc.
15
[0064] The mediator server [208] is then configured to send the final message to the one or more customers.
[0065] For example, a vendor configures one or more dynamic templates or utilizes one or more pre-
20 defined template for one or more events such as updation, deletion, pausing. The scheduler module
[204] triggers the subscription engine module [206] about an event. Thereafter, the subscription engine
module [206] decides a template to be used from the one or more dynamic template or the one or more
pre-defined template and time for dispatch of the final message (i.e. final mail). Further the subscription
engine module [206] sends a set of user details which are one or more details of one or more recipients
25 along with the final message (i.e. final email) to the mediator server [208]. Thereafter, the mediator
server [208] sends the final message to the customer/recipients which is generated as per the one or
more dynamic templates, or the one or more pre-defined templates decided by the subscription engine
module [206].
30 [0066] Referring to FIG. 3, an exemplary method flow diagram [300] for sending one or more
template-based messages on occurrence of an event, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
35
[0067] At step [304], the method comprises sending, by a scheduler module [204] to a subscription engine module [206], a trigger related to an occurring event. The one or more template-based messages
14

include but not limited to electronic mails, and/or electronic messages. The event includes but not limited to creation, updation, pausing, and/or termination of a subscription. For example, a user had purchased a subscription A and upon termination of the subscription, the scheduler module [204] sends to the subscription engine module [206], the triggers related to occurrence of a termination event. 5
[0068] At step [306], the method comprises deciding, by the subscription engine module [206], a target
message template and a time for dispatch of a final message related to the occurring event, based on the
trigger received from the scheduler module [204]. The target message template is one of: a pre-defined
message template selected from a set of one or more pre-defined message templates, and a new real-
10 time configured message template configured by a vendor module [202]. For example, the subscription
engine module [206] decides the target message template (such as updation message template) and a
time to send the final message related to the occurring event (such as updation event), based on the
trigger received from the scheduler module [204].
[0069] The present disclosure encompasses that wherein prior to the deciding, by the subscription engine module [206], the target message template, the method comprises configuring, by the vendor module [202] on the subscription engine module [206], a new message template in real-time for the occurring event. For example, the vendor module [202] may configure the new message template in real-time for occurring event such as pause event.
[0070] The present disclosure encompasses that the method further comprising configuring, by the vendor module [202], one or more message templates for one or more events. The method further comprises storing, by the vendor module [202] in a storage unit [210], the configured one or more message templates for the one or more events, in the set of one or more pre-defined message templates.
[0071] The present disclosure encompasses that the one or more pre-defined message templates or the new real-time configured message template are based on one of: a mark-up format and a plain text format. For example, the one or more pre-defined message templates and the new real-time configured message template may be generated either through the mark-up format (such as HTML, CSS) or the plain text format (SMS).
[0072] The present disclosure encompasses that the method further comprising storing, by the vendor module [202] in a storage unit [210], the configured new message template in real-time for the occurring event. 35
15

[0073] At step [308], the method comprises sending, by the subscription engine module [206] to a mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers. The set of details of one or more customers include but not limited to name, email, shipping address, order ID, product name, quantity, and/or price etc.
[0074] The present disclosure encompasses that prior to the sending, by the mediator server [208], the final message to the one or more customers, the method comprises displaying, by a user interface [212], a user-configurable settings related to a message template of the final message. The user-configurable settings include but not limited to time, date, frequency, and/or location etc.
[0075] At step [310], the method comprises sending, by the mediator server [208], the final message to the one or more customers.
[0076] The method [300] terminates at step [312].
[0077] Referring to FIG. 4, another exemplary method flow diagram [400] for sending one or more template-based messages on occurrence of an event, in accordance with exemplary implementations of the present disclosure is shown. The method [400] depicted in FIG. 4 may be implemented by using the system [200]. At step S1, a subscription lifecycle is processed. For example, the subscription lifecycle is processed to extract one or more events such as creation, pausing, termination via the subscription engine module [206]. Thereafter, at step S2, an email template is created which is based on the subscription lifecycle and lastly at step S3, a dynamic email template with a set of custom parameters (such as time, frequency, location, date) is dispatched via the mediator server [208].
[0078] The present disclosure may relate to a first user device for sending one or more template-based messages on occurrence of an event. The first user device comprising scheduler module [204] configured to send to a subscription engine module [206], a trigger related to an occurring event. The subscription engine module [206] configured to decide a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204]. The target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a real-time configured message template configured by a vendor module. The subscription engine [206] module is further configured to send to a mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers. The mediator server [208] configured to send the final message to the one or more customers.

[0079] The present disclosure may relate to a second user device for receiving one or more template-based messages on occurrence of an event, the second user device comprising a memory, and a processor coupled to the memory. Further, the processor is configured to transmit to a system [200], a trigger related to an occurring event, and receive from the system [200], the final message based on the trigger. Further, the final message is determined based on determining, by the system [200], a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204], wherein the target message template is one of: a pre¬defined message template selected from a set of one or more pre-defined message templates, and a new real-time configured message template configured by a vendor module [202].
[0080] The present disclosure may relate to a non-transitory computer readable storage medium storing instructions for sending one or more template-based messages on occurrence of an event, the instructions include executable code which, when executed by a one or more units of a system [200], causes: scheduler module [204] of the system [200] to send, to a subscription engine module [206], a trigger related to an occurring event. Further, the instructions include executable code, which when executed causes the subscription engine module [206] of the system [200] to decide a target message template and a time to dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204], wherein the target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a real-time configured message template configured by a vendor module. Further, the instructions include executable code, which when executed causes the subscription engine module of the system to send, to the mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers. Further, the instructions include executable code, which when executed causes the mediator server [208] of the system to send the final message to the one or more customers.
[0081] As is evident from the above, the present disclosure provides a technically advanced solution for sending one or more template-based messages on occurrence of an event. The present solution provides one or more custom notification templates which maybe configured as per a subscription life cycle. Further the present solution permits to preview one or more user-configurable settings related to a message template of the final message before dispatching to one or more customers. The present solution also provides configuring of the templates using either the mark-up format or the plain text format. Also, through the present solution, there is no need to integrate an external engine (i.e. notification engine) with the subscription engine, which makes the present solution more efficient, cost-effective, less resource intensive and maintenance friendly. Further, the present solution may be used

by the vendor without any additional requirement of expertise. Hence, the present solution provides flexibility and scalability requirements of the vendor within a marketplace ecosystem.
[0082] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method [300] for sending one or more template-based messages on occurrence of an event,
the method comprising:
- sending, by a scheduler module [204] to a subscription engine module [206], a trigger related to an occurring event;
- determining, by the subscription engine module [206], a target message template and a time for dispatch of a final message related to the occurring event, based on the trigger received from the scheduler module [204],
wherein the target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a new real-time configured message template configured by a vendor module [202];
- sending, by the subscription engine module [206] to a mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers; and
- sending, by the mediator server [208], the final message to the one or more customers.
2. The method [300] as claimed in claim 1, wherein prior to the determining, by the subscription
engine module [206], the target message template, the method comprises:
- configuring, by the vendor module [202] on the subscription engine module [206], a new
message template in real-time for the occurring event.
3. The method [300] as claimed in claim 2, the method further comprising:
- storing, by the vendor module [202] in a storage unit [210], the configured new message
template in real-time for the occurring event.
4. The method [300] as claimed in claim 3, the method further comprising:
- configuring, by the vendor module [202], one or more message templates for one or more events; and
- storing, by the vendor module [202] in the storage unit [210], the configured one or more message templates for the one or more events, in the set of one or more pre-defined message templates.

5. The method [300] as claimed in claim 4, wherein the one or more pre-defined message templates and the new real-time configured message template are based on one of: a mark-up format and a plain text format.
6. The method [300] as claimed in claim 1, wherein prior to the sending, by the mediator server [208], the final message to the one or more customers, the method comprises:
- displaying, by a user interface [212], a user-configurable settings related to a message
template of the final message.
7. A system [200] for sending one or more template-based messages on occurrence of an event,
the system [200] comprising:
- a scheduler module [204] configured to:
o send, to a subscription engine module [206], a trigger related to an occurring event;
- the subscription engine module [206] connected at least with the scheduler module [204],
the subscription engine module [206] configured to:
o determine a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204],
wherein the target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a new real¬time configured message template configured by a vendor module [202];
o send, to a mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers; and
- the mediator server [208] configured to:
o send the final message to the one or more customers.
8. The system [200] as claimed in claim 7, the system comprising the vendor module [202],
wherein prior to the determining, by the subscription engine module [206], the target message
template, the vendor module [202] is configured to:
- configure, on the subscription engine module [206], a new message template in real-time
for the occurring event.
9. The system [200] as claimed in claim 8, the vendor module [202] is configured to:
- store, in a storage unit [210], the configured new message template in real-time for the
occurring event.
10. The system [200] as claimed in claim 9, the vendor module [202] is configured to:

- configure one or more message templates for one or more events; and
- store, in the storage unit [210], the configured one or more message templates for the one or more events, in the set of one or more pre-defined message templates.

11. The system [200] as claimed in claim 10, wherein one of the one or more pre-defined message templates and the new real-time configured message template are based on one of: a mark-up format and a plain text format.
12. The system [200] as claimed in claim 7, the system [200] further comprising a user interface [212], wherein prior to the mediator server [208] sending the final message to the one or more customers, the user interface [212] is configured to:
- display a user-configurable settings related to a message template of the final message.
13. A first user device for sending one or more template-based messages on occurrence of an event,
the first user device comprising:
- a scheduler module [204] configured to:
o send, to a subscription engine module [206], a trigger related to an occurring event;
- the subscription engine module [206] configured to:
o determine a target message template and a time for dispatch of a final message related to an occurring event, based on the trigger received from the scheduler module [204],
wherein the target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a new real¬time configured message template configured by a vendor module [202];
o send, to a mediator server [208], a set of details of one or more customers, and the final message, for sending to the one or more customers; and
- the mediator server [208] configured to:
o send the final message to the one or more customers.
14. A second user device for receiving one or more template-based messages on occurrence of an
event, the second user device comprising:
- a memory; and
- a processor coupled to the memory, wherein the processor is configured to: o transmit to a system [200], a trigger related to an occurring event, and o receive from the system [200], a final message based on the trigger,
wherein the final message is determined based on:

▪ determining, by the system [200], a target message template and a time for dispatch
of a final message related to an occurring event, based on the trigger received from a scheduler module [204],
wherein the target message template is one of: a pre-defined message template selected from a set of one or more pre-defined message templates, and a new real-time configured message template configured by a vendor module [202].