WO2021255754A1

WO2021255754A1 - A method and system for scheduling a reminder in a calendar

Info

Publication number: WO2021255754A1
Application number: PCT/IN2021/050581
Authority: WO
Inventors: Saurabh CHAUDHARI
Original assignee: Chaudhari Saurabh
Priority date: 2020-06-16
Filing date: 2021-06-15
Publication date: 2021-12-23

Abstract

The present invention discloses a method (400) for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment. The method includes electronically receiving (401) reminder scheduling request in the calendar and plurality of inputs from the third party. The method includes verifying (402) the plurality of inputs of the third party from a list. The method then includes identifying (403) a category of the third party based on plurality of categories pre-defined in the list. The method also includes taking (404) predefined action based on the identified category of the third party.

Description

DESCRIPTION

Title of the Invention:

A METHOD AND SYSTEM FOR SCHEDULING A REMINDER IN A CALENDAR

A) TECHNICAL FIELD

[001] The disclosed subject matter relates generally to the field of calendaring system in a computing device. More particularly, the present disclosure relates to a system and method for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment.

B) BACKGROUND OF INVENTION

[002] Today’s busy life schedule makes us forget many deadlines assigned to our children for homework, assignments, or exams related things from school. Remembering important events and meetings is a cumber some and challenging task for a user amidst the number of tasks the user needs to perform. As is evident, it is a common practice to schedule reminders for the important events.

[003] Most of the times it feels very terrified to remind a forgetful person repeatedly to complete the discussed or given task and this happens when the completion of that task is very important. According to a research, it is found that reminding someone repeatedly to complete a task by calling consumes much more time of the day.

[004] It is also observed that, many unknown person schedules reminders without any reason using reminder scheduling/sharing systems and platforms which disturbs scheduled routines. Also taking decisions on the each and every received reminder waste our time and may distract us from our ongoing work.

[005] Many times family members, office colleagues, educational institutes, unknown people need to assign tasks to be done which may be important. They may assign a task by using available internet based network. However, internet connectivity may be non- accessible often and may lead the user to miss receipt of otherwise necessary reminders in real-time. For example, during traveling because of internet issue or dis-connectivity problems, these reminder request may not be processed and received, thereby leading the user to miss many important deadlines/events. Therefore, a method and system is required that overcomes the problems of the prior arts as mentioned above.

C) OBJECTS OF INVENTION

[006] The primary object of the invention is to provide a system and method for scheduling event reminder for self and other user or users having network connected computing device or devices.

[007] Another object of the present invention is to provide a secure, easy, and efficient method for user to receive, process and to take decisions on received event reminder(s) irrespective of the fact whether computing device is connected to the internet or cellular network.

[008] Yet another object of the present invention is to enables communication and delivery of the event reminder details scheduled by third party to the user at his/her computing device even when computing device of user is not connected to the internet.

[009] These and other objects and advantages of the embodiments herein will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings.

D) SUMMARY OF INVENTION

[010] This summary is provided to introduce a selection of concepts in a simplified format that are further described in the detailed description of the invention. This summary is not intended to identify key or essential inventive concepts of the invention, nor is it intended for determining the scope of the invention.

[011] The present disclosure provides a method and system for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment.

[012] In an embodiment, the present invention discloses a method for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment. The method includes electronically receiving reminder scheduling request in the calendar and plurality of inputs from the third party. The method includes verifying the plurality of inputs of the third party from a list. The method then includes identifying a category of the third party based on plurality of categories pre-defined in the list. The method also includes taking predefined action based on the identified category of the third party. Further, method includes detecting internet connectivity status of the reminder receiving user to interact and to sending notifications as per status.

[013] In another embodiment, the present invention discloses a system for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment. The system includes an interface module, a verification module, a memory module, a processing module, and a notification module. The interface module electronically receives reminder scheduling request in the calendar and plurality of inputs from the third party. Then the verification module verifies the plurality of inputs of the third party from a list which stored in a server. Thereafter, the verification module identifies a category of the third party based on plurality of categories pre-defined in the list by interacting with the server. The processing module takes predefined action based on the identified category of the third party. Further, an internet status detection module at the server determines if the computing device of the user is connected to the internet. Lastly, the notification module based on the information received from the internet status detection module at the server sends a notification to the user as well as the third party about the status of the reminder scheduling request i.e., if the request is accepted or rejected via internet network or cellular network.

[014] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

E) BRIEF DESCRIPTION OF DRAWINGS

[015] The other objects, features and advantages will occur to those skilled in the art from the following description of the preferred embodiment and the accompanying drawings in which:

[016] FIG. 1 illustrates a block diagram of distributed computing environment, according to one or more embodiment of the present invention;

[017] FIG. 2 illustrates a block diagram of a computing device, according to one or more embodiment of the present invention;

[018] FIG. 3 illustrates a block diagram of a server, according to one or more embodiment of the present invention; [019] FIG. 4 illustrates a flow diagram of a method for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment, according to one embodiment of the present invention;

[020] FIG. 5 illustrates a flow diagram of an example embodiment of a method for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment, according to one embodiment of the present invention; and

[021 ] FIG. 6 illustrate a flow diagram of an example embodiment of a method for sharing scheduled event reminder or reminders with other user or users, according to another embodiment of the present invention. [022] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present disclosure. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein. F) DETAILED DESCRIPTION OF DRAWINGS

[023] In the following detailed description, a reference is made to the accompanying drawings that form a part hereof, and in which the specific embodiments that may be practiced is shown by way of illustration. The embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments and it is to be understood that the logical, mechanical and other changes may be made without departing from the scope of the embodiments. The following detailed description is therefore not to be taken in a limiting sense.

[024] FIG. 1 illustrates a block diagram of distributed computing environment, according to one or more embodiment of the present invention. As illustrated, an environment comprising of end users 104, computing devices 103, a network 101 , and at least one server 102.

[025] In an embodiment, the computing device 103 may include but are not limited to, a personal digital assistant, a smart phone, personal computer, a mobile station, computing tablet, a handheld device, an internet enabled calling device, an internet enabled calling software, a telephone, a mobile phone, a digital processing system, and the like.

[026] In an embodiment, the network 101 may include but is not limited to, internet, optical network, an Ethernet, a wireless local area network (WLAN), or a wide area network (WAN), a WIFI communication network e.g., the wireless high speed internet, or a combination of networks, a cellular service such as a 3G, 4G (e.g., LTE, mobile WiMAX) or 5G cellular data service, wired cables and the like without limiting the scope of the present disclosure. The network 101 allows connection between computing device or devices 103 of users 104 to communicate with each other through at least one server 102.

[027] In an embodiment, the user or users 104 uses valid login credentials in the computing device 103 through user interface module 304. The login credentials may include but not limited to, a login ID, and user ID, a password, a pin number, and the like. Further, each of the end user 104 provides data which includes but not limited to login credentials, personal details such as contact number, email id or unique alphanumeric ID etc., a scheduled list of event reminders, a blocked user ID list, a favorite user ID list, which is stored in a memory of the computing device 103 and is synced with the at least one server 102 through the network 101 .

[028] FIG. 2 and FIG. 3 illustrates a block diagram of a computing device 103 and server 102 respectively, according to one or more embodiment of the present invention. As illustrated, the computing device 103 comprises a memory 301 , a processor 302, a user interface module 304, a verification module 305, a processing module 306, and a notification module 303. The memory 301 , the processor 302, the user interface module 304, the verification module 305, and the notification module 303, and the processing module 306, may communicate with each other over the communication path (bus) 101. The components of a system 300 may be stored in a computing device 103 in the form of an application. The computing device 103 communicates with the server 102 through the network 101 .

[029] In another embodiment as illustrated in Figure 3, the server 102 comprises a memory 301 , a processor 302, a verification module 305, a processing module 306, an internet status detection module 307 and a notification module 308. The memory 301 , the processor 302, the verification module 305, the internet status detection module 307 and the notification module 308, and the processing module 306, may communicate with each other over the communication path (bus) 101 . [030] In an embodiment, the processor 302 can be a single processing unit or a number of units, all of which could include multiple computing units. The processor 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. A processor 302 may be a general purpose processor, an application specific integrated circuit (ASIC), a FPGA (Field Programmable Gate Array), a RISC (Reduced Instruction Set Controller) processor, an integrated circuit, or the like. There may be a single core, multiple cores, or more than one processor. Among other capabilities, the processor 302 is configured to fetch and execute computer-readable instructions and data stored in the memory 301 .

[031] In an embodiment, the memory 301 may include any non-transitory computer- readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The data stored in the memory 301 of computing device 103 of each end user 104, is synchronized with the server 102 through network 101.

[032] In an embodiment, the user interface module 304 comprises components essential to interact with user such as display or touch sensible display, alpha numeric keyboard, speaker, vibrating device, mike and the like.

[033] In an embodiment, the verification module 305, the processing module 306, the internet status detection module 307, notification module 303 of computing device 103 and the notification module 308 of a server 102 amongst other things, include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types. The verification module 305, the processing module 306, the internet status detection module 307, notification module 303 of computing device 103 and the notification module 308 of a server 102 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulate signals based on operational instructions.

[034] Further, the verification module 305, the processing module 306, the internet status detection module 307, notification module 303 of computing device 103 and the notification module 308 of a server 102 may be implemented in hardware, instructions executed by at least one processing unit, for e.g., the processor 302, or by a combination thereof. The processing unit 306 may comprise a computer, a processor, a state machine, a logic array and/or any other suitable devices capable of processing instructions. The processing unit 306 may be a general-purpose processor which executes instructions to cause the general-purpose processor to perform operations or the processing unit may be dedicated to performing the required functions. In some example embodiments, the verification module 305, the processing module 306, the internet status detection module 307, notification module 303 of a computing device 103 and the notification module 308 of a server 102 may be machine-readable instructions (software, such as web-application, mobile application, program, etc.) which, when executed by a processor/processing unit, perform any of the described functionalities.

[035] In an embodiment, the computing device 103 of a user is connected to the internet, optical network, an Ethernet, a wireless local area network (WLAN), or a wide area network (WAN), or a WIFI communication network e.g., the wireless high-speed internet, or a combination of networks is verified by the internet status detection module 307.

[036] In an embodiment, when the internet status detection module 307 in the server 102 detects the computing device 103 of the user is not connected to internet, then it triggers the notification module 308 which then sends the details of reminder scheduling request received from the third party of either of the favorite, general and unknown category to the user through text massage over the cellular network.

[037] In an embodiment, the notification module 308 of the server 102 communicates with the processing module 306 and based on the action taken by the user 104 or by a processing module 306, the notification module 308 notifies the third party as well as the user 104. The notification module 308 of the server 102 sends notification to the third party and the user 104 through cellular network and/or internet. If the computing device 103 of the user 104 found connected to the internet then, the notification module 308 of the server 102 sends notification to the computing device 103 of the user 104 through internet, if not then through cellular network.

[038] In an embodiment, the user electronically receives reminder scheduling request in the calendar and plurality of inputs from the third party via server 102. Then the verification module 305 verifies the plurality of inputs of the third party from a list which is synced and stored in the memory module 301 of a server 102. Thereafter, the verification module 305 of the server 102 identifies a category of the third party based on plurality of categories pre-defined in the list. The processing module 306 of a server 102 takes predefined action based on the identified category of the third party. The internet status detection module 307 at the server 102 detects whether the computing device 103 of the user is connected to the internet or Wi-Fi or optical network, an Ethernet, a wireless local area network (WLAN), or a wide area network (WAN), a WIFI communication network e.g., the wireless high-speed internet or not. If the computing device 103 of user is found connected to the internet, then the scheduled list of event is updated in the computing device 103 of the user, or the server 102 interacts with the user through the user interface module 304 and notification module 303 of the computing device 103. If the computing device 103 of the user 104 is not connected to the internet, then the notification module 308 of a server 102 sends notification comprising event details to the user 104 over cellular network, through but not limited to text massage.

[039] In an embodiment, the plurality of inputs from the third party include: event date, event time, event details, event name, event type, location, user ID of a user or user(s) for whom event reminder is to be schedule or with whom event reminder(s) is to be shared.

[040] In an embodiment, the list comprises contact details known to the user, scheduled list of event reminders and the plurality of categories include favourite, blocked, general and unknown.

[041] In an embodiment, the processing module 306 takes at least one of the predefined actions of:

• accepting the reminder scheduling request from the third party of the favourite category,

• rejecting the reminder scheduling request from the third party of the blocked category, and

• requesting the user to accept or reject or modify the reminder scheduling request from the third party of the general category and unknown category.

[042] In an embodiment, after the processing module 306 takes predefined action of accepting the reminder scheduling request from the third party of any of the plurality of categories, updates the scheduled list of event reminders in the computing device 103 of the user 104, then an alarm is fixed for that particular date and time in the computing device 103 of a user 104 according to time zone of a user 104.

[043] FIG. 4 illustrates a flow diagram of a method 400 for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment, according to one embodiment of the present invention. At step 401 , the method 400 includes electronically receiving reminder scheduling request in the calendar and plurality of inputs from the third party at server. At step 402, the method 400 includes verifying the plurality of inputs of the third party from a list at server. At step 403, the method 400 then includes identifying a category of the third party based on plurality of categories pre-defined in the list at server. At step 404, the method 400 includes taking predefined action based on the identified category of the third party at server. At step 405, the method 400 includes detecting the internet connection status of the computing device of the user at the server. At step 406, the method 400 also includes notifying both third party and user.

[044] In an embodiment, the plurality of inputs from the third party include: event date, event time, event details such as event name, event type, event location, and user ID of a user or user(s) for whom event reminder is to be schedule or with whom event reminder is to be share.

[045] In an embodiment, the list comprises contact details known to the user, scheduled list of event reminders and the plurality of categories include favourite, blocked, general and unknown.

[046] In an embodiment, the predefined action includes:

[047] Further, if the third party is of unknown category and the user accepts or rejects or modifies the reminder scheduling request, then the user is requested to add the third party in any of favourite, blocked or general category.

[048] In an embodiment, if a verification module 305 determines that the date and time of a shared or a scheduled reminder from the third party of any of the favorite, general and unknown category is already blocked, then the notification module 308 of the server 102 notifies accordingly to the third party.

[049] In an embodiment, after taking predefined action of accepting the reminder scheduling request from the third party of any of the plurality of categories, an alarm is fixed for that particular date and time in the computing device 103 of the user.

[050] In an exemplary embodiment, when a user electronically receives reminder scheduling request in the calendar and plurality of inputs from the third party via server 102, then the verification of plurality of inputs of the third party is performed to identify a category of the third party based on plurality of categories pre-defined in the list. According to the identified category of the third party, a predefined action is taken by server 102. Thereafter, the server 102 updates the scheduled event reminder list in network 101 connected computing device 103 of user as per action taken by server 102 or user itself. Lastly, an alarm is fixed for a particular date and time regarding the reminder scheduling request in the computing device 103 of the user 104. As the verification helps in shortlisting the appropriate reminders for communication, a signaling and processing overhead is reduced. As mentioned before, the verification may be performed interchangeably at client and server.

[051] With respect to FIG. 1 , FIG. 2, FIG 3 and FIG. 5, an example embodiment is illustrated via flow diagram of a method for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment, according to one embodiment of the present invention. As shown, an event reminder scheduling user 104A schedules reminder of particular event for event reminder receiving user or users 104B.

[052] At step 502, verifying login credentials of event reminder scheduling user 104A through network connected computing device. At step 504, receiving inputs from the event-reminder scheduling user 104 such as event date, event time, event name, place, and user ID(s) of event reminder receiving user or users 104B at server 102. At step 506, verifying if User ID of the event-reminder scheduling user 104A is in favourite user ID list and blocked user ID list of each event-reminder receiving user 104B at server 102. At step 508, determining if event-reminder scheduling user 104A is a blocked user listed by event-reminder receiving user or users 104B. If yes, then at step 510, then notifying rejection of event-reminder to the event reminder scheduling user 104A, using internet, wifi or cellular network. If no, then at step 512, determining if event-reminder scheduling user 104A is a favourite user listed by event-reminder receiving user or users 104B. If yes, then at step 516, scheduling of event reminder in computing device of event- reminder receiving user or users 104B and notification of the same is delivered to event- reminder scheduling user 104A, using internet, wifi or cellular network after determining if the computing device is connected to the internet or not. If no, then at step 514, event- reminder receiving user 104B decides whether to schedule received event-reminder or reject it after receiving notification. In case, at step 518, Event-reminder receiving user 104B rejects received event-reminder, then at step 520, notifying rejection of event- reminder to event reminder scheduling user 104A using internet, wifi or cellular network after determining if the computing device is connected to the internet or not. Otherwise, at step 516 is followed. Lastly, an alarm is fixed for that particular date and time of the event in the computing device 103 of an event-reminder receiving user 104B for the accepted event reminder according to time zone of an event-reminder receiving user 104B. [053] With respect to FIG. 1 , FIG. 2 and FIG. 6, an example embodiment is illustrated via flow diagram of a method for sharing scheduled event reminder or reminders with other user or users, according to another embodiment of the present invention. As shown, an event reminder sharing method wherein an event reminder sharing user 104C shares reminder or reminders from own scheduled list of event reminders with other end user or users i.e. event reminder receiving user or users 104B.

[054] At step 602, verifying login credentials of event reminder sharing user 104C. At step 604, Selecting event reminders from the list of scheduled event reminders to be share, and receiving user ID(s) of event-reminder receiving user or users 104B from event reminder sharing user 104C. At step 606, verifying User ID of event reminder or reminders sharing user 104C in favourite user ID list and blocked user ID list of each event-reminder receiving user 104B at server. At step 608, determining if event-reminder sharing user 104C is blocked user listed by event-reminder receiving user or users 104B. If yes, then at step 610, notifying rejection of event-reminder to event reminder sharing user 104C, using internet, wifi or cellular network after determining if the computing device is connected to the internet or not. If no, then at step 612, determining if event- reminder sharing user 104C is favourite user listed by event-reminder receiving user or users 104B. If yes, then at step 614, scheduling of event reminder in computing device of event-reminder receiving user or users 103B and notification of the same will be delivered to event-reminder sharing user 104C, using internet, wifi or cellular network after determining if the computing device is connected to the internet or not. If no, then at step 616, event-reminder receiving user 104B decides whether to schedule received event- reminder or reject it after receiving notification. At step 618, if event-reminder receiving user 104B rejects received event-reminder, then at step 620, notifying rejection of event- reminder to event reminder sharing user 104C using internet, wifi or cellular network after determining if the computing device is connected to the internet or not. Otherwise, follow step 614. Lastly, an alarm is fixed for that particular date and time of the event in the computing device 103 of an event-reminder receiving user 104B for the accepted event reminder according to time zone of an event-reminder receiving user 104B.

[055] The present disclosure allows event reminder scheduling user to schedule event reminder for event reminder receiving user or users through easiest and efficient way by means of network connected computing device(s).

[056] The present disclosure allows event reminder receiving user to block user ID(s) of particular user or users giving troubles.

[057] The present disclosure allows event reminder scheduling user to schedule event reminders for event reminder receiving user or users without their permission only if an user ID of event reminder scheduling user is listed as favorite user ID by event reminder receiving user or users.

[058] The present disclosure allows event reminder scheduling user to share event reminders from the list of scheduled event reminders with event reminder receiving user or users through network connected computing device(s).

[059] The present invention provides the following advantages by enabling:

• a system to categorize and manage event reminder scheduling and sharing users;

• a computing device to take decision related to shared/ scheduled event reminder or reminders efficiently, which saves human hours;

• a system to take decision on received event reminders from third party, along with that a system which can take decision on received event reminders from a third party even when a computing device of event reminder receiving user is not connected to the internet;

• a system allowing verification at server helps in shortlisting the appropriate reminders for communication, which reduced a signaling and processing overhead;

• a system which interacts with computing device of an event reminder receiving user to deliver details of scheduled calendar event even when a computing device of a user is not connected to an internet.

[060] It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims.

[061] 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.

[062] The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. [063] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component.

Claims

im:

1 . A method (400) for scheduling a reminder in a calendar of a user by a third party in a distributed computing environment, the method comprising: electronically receiving (401) reminder scheduling request in the calendar and plurality of inputs from the third party; verifying (402) the plurality of inputs of the third party from a list; identifying (403) a category of the third party based on plurality of categories pre-defined in the list; and taking (404) predefined action based on the identified category of the third party.

2. The method (400) as claimed in claim 1 , the method further comprising at least one of: determining (405) if computing device of the user is connected to internet and sending (406) notification to the user and third party of the predefined action via the internet network; or determining (405) if computing device of the user is not connected to internet and sending (406) notification to the user and third party of the predefined action via the cellular network.

3. The method (400) as claimed in claim 1 , wherein the plurality of inputs from the third party includes but not limited to event date, event time, event details, event type, location, user ID(s) of a user or user(s) for whom event reminder is to be scheduled.

4. The method (400) as claimed in claim 1 , wherein the list comprises contact details known to the user, scheduled list of event reminders, and the plurality of categories include but not limited to favourite, blocked, general and unknown.

5. The method (400) as claimed in claim 1 , wherein the predefined action comprising: accepting the reminder scheduling request from the third party of the favourite category; rejecting the reminder scheduling request from the third party of the blocked category; and requesting the user to accept or reject or modify the reminder scheduling request from the third party of the general category and unknown category.

6. The method (400) as claimed in claim 5, wherein if the third party is of unknown category and the user accepts or rejects or modifies the reminder scheduling request: requesting the user to add the third party in any of favourite, blocked, general category of the plurality of categories.

7. A system (300) for scheduling a reminder in a calendar of a user (104) by a third party in a distributed computing environment, the system (300) comprising: an interface module (304) configured to electronically receive reminder scheduling request in the calendar and plurality of inputs from the third party; a verification module (305) configured to verify the plurality of inputs of the third party from a list, stored in a memory module (301) in synchronization with a server (102); the verification module (305) configured to identify a category of the third party based on plurality of categories pre-defined in the list; and a processing module (306) configured to take predefined action based on the identified category of the third party.

8. The system (300) as claimed in claim 7, further comprising: an internet status detection module (307) at the server configured to determine if the computing device of the user is connected to the internet or not; a notification module (308) configured to send notification to the third party and the user via internet network or cellular network based on the determination of the internet connection status detection module (307) in communication with the server (102); and a network module (101 ) configured to establish connection between the interface module, the verification module, the processing module, the internet status detection module and notification module.

9. The system (300) as claimed in claim 7, wherein the plurality of inputs from the third party includes but not limited to event date, event time, event details, event type, location, user ID(s) of a user or user(s) for whom event reminder is to be schedule.

10. The system (300) as claimed in claim 7, wherein the list in the memory (301 ) comprises contact details known to the user, scheduled list of event reminders, and the plurality of categories include but not limited to favourite, blocked, general and unknown.

11 . The system (300) as claimed in claim 7, wherein the processing module (306) is configured to take at least one of the predefined actions of: accepting the reminder scheduling request from the third party of the favourite category; rejecting the reminder scheduling request from the third party of the blocked category; and requesting the user to accept or reject or modify the reminder scheduling request from the third party of the general category and unknown category.

12. The system (300) as claimed in claim 10, wherein if the third party is of unknown category and the user accepts or rejects or modifies the reminder scheduling request, the processing module is configured to take at least one of the predefined actions of: requesting the user to add the third party in any of favourite, blocked, general category of the plurality of categories.