Sign In to Follow Application
View All Documents & Correspondence

System And Method For Successful Process Automation

Abstract: The present disclosure relates to a system(s) and method(s) for enabling success execution of a process automation. The method comprises receiving an instruction to execute a process automation and executing an assessment of the process automation. The assessment comprises the assessment comprises, obtaining a characteristic associated with a process automation, configuring a check based on the characteristics; and computing a probability of success of a process automation based on execution of the check. The method further comprises executing the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
19 March 2019
Publication Number
14/2019
Publication Type
INA
Invention Field
ELECTRICAL
Status
Email
ip@legasis.in
Parent Application
Patent Number
Legal Status
Grant Date
2024-04-15
Renewal Date

Applicants

HCL Technologies Limited
A-9, Sector - 3, Noida 201 301, Uttar Pradesh, India

Inventors

1. SURAPARAJU, Rajesh Babu
HCL Technologies Limited, No 602/3 Elcot Economic Zone, Medavakkam High Road, Sholinganallur, Chennai - 600119, Tamil Nadu, India
2. PONAKALA, Suresh Naidu
HCL Technologies Limited, Avance Business Hub, Tower H08, Phoenix Infocity Pvt. Ltd, Madhapur, Hyderabad - 500081, Telangana, India
3. MEKALA, Durga Prasad
HCL Technologies Limited, Avance Business Hub, Tower H08, Phoenix Infocity Pvt. Ltd, Madhapur, Hyderabad - 500081, Telangana, India
4. MADHAVAN PILLAI, Hareendran
HCL Technologies Limited, No 602/3 Elcot Economic Zone, Medavakkam High Road, Sholinganallur, Chennai - 600119, Tamil Nadu, India

Specification

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[001] The present application does not claim priority from any patent application.
TECHNICAL FIELD
[002] The present disclosure in general relates to the field of process automation. More particularly, the present subject matter relates to a system and a method for enabling success execution of a process automation.
BACKGROUND
[003] Nowadays, process automation, involving automation of manual activities performed by IT engineers, is dependent on successful execution of BOTs/use cases. Typically, these BOTs accept inputs from various sources like file systems, mails, databases, other applications etc., perform operations typically performed by engineers manually and provide the necessary output thereby completing the activity. Successful execution of the bots is critical to ensure that there are no process breakdowns due to failed executions.
[004] The execution of these bots involves various dependencies like input information, hardware, software, system configurations and system resources. There are multiple scenarios of failure or malfunction of deployed BOT/use case execution, due to unavailability of inputs, required resources, dependent applications. While adequate conditions are incorporated into these BOTs at the time of development to ensure all pre-requisites, required dependencies, system resources and configurations are in place, there are a significant number of situations that occur at the time of execution that have an impact on the successful execution of the BOT. Some examples of situations are a) Unavailability of resources, which may have been consumed by other executions, b) Lack of dependent software applications, which may have stopped or not accessible due to various reasons, c) Changed or missing configurations due to the outcome of other systems, d) Impact by system performance degrade, e) Periodic update of OS and dependency software.
SUMMARY
[005] Before the present system and a method for enabling success execution of a process automation are described, it is to be understood that this application is not limited to a particular system, systems, and methodologies described, as there can be multiple possible embodiments, which are not expressly illustrated in the present disclosures. It is also to be understood that the terminology used in the description is for the purpose of describing the particular implementations, versions, or embodiments only, and is not intended to limit the scope of the present application. This summary is provided to introduce aspects related to a system and a method for enabling success execution of a process automation. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[006] In one embodiment, a method for enabling success execution of a process automation is disclosed. In the embodiment, the method comprises receiving an instruction to execute a process automation and executing an assessment of the process automation. In one example, the assessment comprises obtaining a characteristic associated with a process automation and configuring a check based on the characteristics. The check comprises a list of activities to be executed. In the example, the characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes, Further, the first set of attributes comprises critical attributes and the second set comprises a non-critical attribute. Further, the assessment comprise computing a probability of success of a process automation based on execution of the check. The method further comprises executing the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.
[007] In one embodiment, a system for enabling success execution of a process automation may be disclosed. The system comprises a memory and a processor coupled to the memory, further the processor may be configured to execute programmed instructions stored in the memory. In the embodiment, the system may receive an instruction to execute a process automation and execute an assessment of the process automation. Further the assessment comprises obtaining a characteristic associated with a process automation, configuring a check based on the characteristics and computing a probability of success of a process automation based on execution of the check. In one example, the check comprises a list of activities to be executed. Further, the characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes. Furthermore, the first set of attributes comprises critical attributes and the second set comprises a non-critical attributes. The system executes the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.
BRIEF DESCRIPTION OF DRAWINGS
[008] The foregoing detailed description of embodiments is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present subject matter, an example of construction of the present subject matter is provided as figures; however, the present subject matter is not limited to the specific method and system disclosed in the document and the figures.
[009] The present subject matter is described in detail with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer various features of the present subject matter.
[0010] Figure 1 illustrates a network implementation of a system for enabling success execution of a process automation, in accordance with an embodiment of the present subject matter.
[0011] Figure 2 illustrates and embodiment of the system for enabling success execution of a process automation, in accordance with an embodiment of the present subject matter.
[0012] Figure 3 illustrates a method for enabling success execution of a process automation, in accordance with an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0013] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Although any system and method for enabling success execution of a process automation , similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the exemplary, system and method for enabling success execution of a process automation are now described.
[0014] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments for enabling success execution of a process automation. However, one of ordinary skill in the art will readily recognize that the present disclosure for enabling success execution of a process automation is not intended to be limited to the embodiments described, but is to be accorded the widest scope consistent with the principles and features described herein.
[0015] As described, generally, at the time of deployment of the bots, one-time verification can be carried to make sure all pre-requisites are in place including required resources availability, with all configuration checks. While this is ok to ensure static dependencies are verified, run time dependencies are difficult to predict and handle and trying to handle all such scenarios will lead to bloated bots which are not desirable. Bots typically automate manual transactions automation involving medium to large volume transactions processing. These applications would contain complex business logic, data processing, integration of external services and data base systems. For successful execution of deployed applications requires, all dependent applications are running and integration points needs to be configured and up and running properly. Even handling checks in application level, may cause data integrity issues sometimes, which requires manual intervention to take corrective action to get proper execution state. This involves significant effort and various integration checks to get correct execution state, for handling a) Data base access issues: May due to server down, database locks, timeout due to continues data grown b) Port conflict issues: Unknowingly port configuration to other applications during install, system re-start also may cause to ports may occupied by other applications c) IP and host name changes: Due to dynamic internet protocol bindings, internet protocol changes would affect external server/services access d) Dependent applications availability: Any temporary downtimes including automatic upgrade of dependent applications may cause failure of application executions, which may require changes based on upgrades e) System resources availability like memory, CPU, storage f) Network congestion impacting data transfer rates.
[0016] In one embodiment, the present subject matter relates to successful process automation i.e. bot execution ready-ness, to make sure all pre-requisites, required configurations, required resources availability, dependent applications and services existence with access checks for success full execution of desired software application/use case. This is done by identifying and monitoring the characteristics of dependent resources and correlating them to the success or failure of executions of the bot using machine learning algorithm which uses classification model. In one example, any of suitable classification algorithm can be depending on characteristics data. In one example, each characteristic can be considered as input feature to draw some conclusion from the input values (i.e. each characteristic value/result) provided for training. It can be used to predict for new results data. Further, the subject matter predicts the success probability of a BOT execution and by alerting stakeholders or delaying the execution of the bot till a favourable environment is available for execution, increasing the successful execution rates of bots.
[0017] In one embodiment, a system performs continues assessment of bot/use case execution process, to determine the application/use case to run for subsequent executions. So that, necessary actions and corrections for successful execution may be taken. Also analyse past execution logs to consider for further execution checks to suggest appropriate corrective actions. The system performs 1) Checking the all pre-requisites availability. 2) Checking required configurations. 3) Checking required resources availability. 4) Checking dependent applications and services existence. 5) Accessibility checks of any dependent applications and services, for successful execution of desired software bot/use case.
[0018] In one example, the assessment can be done by analysing the bot/use case characteristics, which are causing execution result if it’s successful or failure. The execution process is characterized by multiple attributes, which can be required for process execution. These attributes/features can be considered to process the model and predict whether the execution will be successful or not. Attributes/features required for bot/use case execution would be as snapshot, the more of the attributes in the model, would provide more accuracy in the prediction. For example, some of attributes are System CPU, System Memory, Storage, Available ports, Access rights, Network transmission rate, Firewall settings, Data requirements, Files and Folders availability, Database availability and connectivity, Services availability3rd party or dependent applications availability and connectivity, Required configurations existence, License checks, Etc.
[0019] Further, in one embodiment, subject matter suggests a technique to use monitoring engine to perform the assessment of bot/use case execution. In the technique, assessment repository would be defined with required characteristics and the checks for the required characteristics in may be Configured. Further, all the checks may be executed based on the configuration. Further, a prediction of success may be computed based on the execution. Subsequently, a report may be generated with predicted result and notify to take corrective actions if required. In one example, all checks results of the characterized attributes/features may be utilized for next assessment prediction.
[0020] Exemplary embodiments for discussed above may provide certain more advantages. Further, in the subsequent description, embodiments of the present subject along with the advantages are explained in detail with reference to the Figures 1 to Figure 3.
[0021] Referring now to Figure 1, embodiment of a network implementation 100 of a system 102 for enabling success execution of a process automation is disclosed. Although the present subject matter is explained considering that the system 102 is implemented on a server 110, it may be understood that the system 102 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, and the like. In one implementation, the system 102 may be implemented in a cloud-based environment. It will be understood that multiple users may access the system 102 through one or more user device or applications residing on the user device 104-1….104-N. Examples of the user device may include, but are not limited to, a portable computer, a personal digital assistant, a handheld system, and a workstation. The system 102 may be communicatively coupled to server 110 through a network 106.
[0022] In one implementation, the network 106 may be a wireless network, a wired network or a combination thereof. The network 106 may be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 106 may be either a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), Secure File Transfer Protocol (SFTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another.
[0023] In one embodiment, a system 102 for enabling success execution of a process automation may be disclosed. The system 102 comprises a memory and a processor coupled to the memory, further the processor may be configured to execute programmed instructions stored in the memory. In the embodiment, the system 102 may receive an instruction to execute a process automation and execute an assessment of the process automation. Further the assessment may comprise obtaining a characteristic associated with a process automation, configuring a check based on the characteristics and computing a probability of success of a process automation based on execution of the check. In one example, the check comprises a list of activities to be executed. Further, the characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes. Furthermore, the first set of attributes comprises critical attributes and the second set comprises a non-critical attributes. The system may executes the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.
[0024] Referring now to figure 2, an embodiment of the system 102 for enabling success execution of a process automation is illustrated in accordance with the present subject matter. The system 102 may include at least one processor 202, an input/output (I/O) interface 204, and a memory 206. The at least one processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any systems that manipulate signals based on operational instructions. Among other capabilities, at least one processor 202 may be configured to fetch and execute computer-readable instructions stored in the memory 206.
[0025] The I/O interface 204 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 204 may allow the system 102 to interact with the user directly or through the user device 104. Further, the I/O interface 204 may enable the system 102 to communicate with other computing systems, such as web servers and external data servers (not shown). The I/O interface 204 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 204 may include one or more ports for connecting a number of systems to one another or to another server.
[0026] The memory 206 may include any 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 memory 206 may include modules 208 and data 210.
[0027] The modules 208 may include routines, programs, objects, components, data structures, and the like, which perform particular tasks, functions or implement particular abstract data types. In one implementation, the module 208 may include a receiving module 212, a configuration module 214, a computation module 216, an execution module 220, and other modules 224. The other modules 224 may include programs or coded instructions that supplement applications and functions of the system 102.
[0028] The data 210, amongst other things, serve as a repository for storing data processed, received, and generated by one or more of the modules 208. The data 210 may also include a system data 226, and other data 228. In one embodiment, the other data 228 may include data generated as a result of the execution of one or more modules in the other module 224.
[0029] In one implementation, a user may access the system 102 via the I/O interface 204. The user may be registered using the I/O interface 204 in order to use the system 102. In one aspect, the user may access the I/O interface 204 of the system 102 for obtaining information, providing inputs, configuring or implementing the system 102.
[0030] In one embodiment, the receiving module 212 may receive an instruction to execute a process automation. In one example, the instruction may be predefined and received at a particular time or upon a trigger. In one example, construe an instruction when a message is sent by a customer from contact us page on a website. In the said example, the process automation may be to input all the data received from the contact ups page in to a system with in an organization. Further, the receiving module 212 may store instruction in the system data 226.
[0031] In the embodiment, the configuration module 214 may obtain a characteristic associated with a process automation. In one example, the characteristic may comprise historic data associated with historical execution of the process automation. In one other example, the characteristic may comprise a first set of attributes and a second set of attributes. Further, the first set of attributes may comprise critical attributes and wherein the second set comprises a non-critical attributes. Referring to the example of the process automation of data entry, first set of attributes may be accesses to the internal system, the second set may be the system memory.
[0032] In one there example, the configuration module 214 may identify a characteristic. Further, the configuration module 214 may store the characteristic in the system data 226. In one example, the characteristic may comprise multiple attributes, which can be required for process execution, this would be defined as snapshot.
[0033] In the embodiment, upon obtaining, the configuration module 214 may configure a check based on the characteristics. In one example, the check comprises a list of activities to be executed. Further, the configuration module 214 may store check in system data 226.
[0034] In the embodiment, further to configuration, a computation module 216 may compute a probability of success of a process automation based on execution of the check. Further, the computation module 216 may store the mapped data in the system data 226.
[0035] In the embodiment, upon computing, an execution module 220 execute the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation. In one example, execution module 220 may generate an alert if the probability of success is below a predefined threshold. In other example, execution module 220 delay an execution of the process automation when the probability of success is below a predefined threshold till the probability of success is above the predefined threshold
[0036] Exemplary embodiments for enabling success execution of a process automation discussed above may provide certain advantages. Though not required to practice aspects of the disclosure, these advantages, without limitation, are the following.
[0037] Some embodiments of the system and the method enable successful execution of process automation.
[0038] Some embodiments of the system and the method enable identification of any issues related to an issues in execution of process automation.
[0039] Referring now to figure 3, a method 300 for enabling success execution of a process automation using a system 102, is disclosed in accordance with an embodiment of the present subject matter. The method 300 for enabling success execution of a process automation using a system 102 may be described in the general context of device executable instructions. Generally, device executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, and the like, that perform particular functions or implement particular abstract data types. The method 300 for enabling success execution of a process automation using a system 102 may also be practiced in a distributed computing environment where functions are performed by remote processing systems that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage systems.
[0040] The order in which the method 300 for enabling success execution of a process automation using a system 102 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 300 for enabling success execution of a process automation using a system 102 may be considered to be implemented in the above-described system 102.
[0041] At block 302, an instruction to execute a process automation is received. In one embodiment, the receiving module 212 may receive an instruction to execute a process automation. Further, the extraction module 212 may store the instruction in the system data 226.
[0042] At block 304, an assessment of the process automation may be executed. In one example, the assessment may comprise obtaining a characteristic associated with a process automation, configuring a check based on the characteristics and computing a probability of success of a process automation based on execution of the check. The characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes, the first set of attributes comprises critical attributes and the second set comprises a non-critical attributes. In one embodiment, the configuration module 214 obtain a characteristic associated with a process automation, configuring a check based on the characteristics. Further, the computation module 216 may compute probability of success of a process automation based on execution of the check the extraction module 214 and store the probability of success of a process automation in the system data 226.
[0043] At block 306, executing the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation. In one embodiment, the execution module 220 may. Further, the identification module 214 may executing the process automation, if the probability of success is above a predefined threshold and store execution data in system data 226.
[0044] Although implementations for methods and systems for enabling success execution of a process automation have been described in language specific to features, system and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods for enabling success execution of a process automation described. Rather, the specific features and methods are disclosed as examples of implementations for enabling success execution of a process automation.

Claims:1. A method for enabling success execution of a process automation, wherein the method comprising:
receiving, by a processor, an instruction to execute a process automation;
executing, by the processor, an assessment of the process automation, wherein the assessment comprises:
obtaining, by the processor, a characteristic associated with a process automation, wherein the characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes, wherein the first set of attributes comprises critical attributes and wherein the second set comprises a non-critical attributes;
configuring, by the processor, a check based on the characteristics, wherein the check comprises a list of activities to be executed; and
generating, by the processor, a probability of success of a process automation based on execution of the check; and
executing, by the processor, the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.

2. The method of claim1 further comprises identifying, by a processor, the characteristic

3. The method of claim1 further comprises generating, by the processor, alert if the probability of success is below a predefined threshold.

4. The method of claim1 further comprises delaying, by the processor, an execution of the process automation when the probability of success is below a predefined threshold till the probability of success is above the predefined threshold.

5. A system for enabling success execution of a process automation, wherein the system comprising:
a memory; and
a processor coupled to the memory, wherein the processor is configured to execute program instructions stored in the memory for:
receiving an instruction to execute a process automation;
executing an assessment of the process automation, wherein the assessment comprises:
obtaining a characteristic associated with a process automation, wherein the characteristic comprises historic data associated with the execution of the process automation, a first set of attributes and a second set of attributes, wherein the first set of attributes comprises critical attributes and wherein the second set comprises a non-critical attributes;
configuring a check based on the characteristics, wherein the check comprises a list of activities to be executed; and
computing a probability of success of a process automation based on execution of the check; and
executing the process automation, if the probability of success is above a predefined threshold, thereby enabling success execution of a process automation.

6. The system of claim1 further comprises identifying the characteristic

7. The system of claim1 further comprises generating alert if the probability of success is below a predefined threshold.

8. The system of claim1 further comprises delaying an execution of the process automation when the probability of success is below a predefined threshold till the probability of success is above the predefined threshold.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 201911010698-FORM 4 [16-12-2024(online)].pdf 2024-12-16
1 201911010698-IntimationOfGrant15-04-2024.pdf 2024-04-15
1 201911010698-STATEMENT OF UNDERTAKING (FORM 3) [19-03-2019(online)].pdf 2019-03-19
2 201911010698-IntimationOfGrant15-04-2024.pdf 2024-04-15
2 201911010698-PatentCertificate15-04-2024.pdf 2024-04-15
2 201911010698-REQUEST FOR EXAMINATION (FORM-18) [19-03-2019(online)].pdf 2019-03-19
3 201911010698-PatentCertificate15-04-2024.pdf 2024-04-15
3 201911010698-Proof of Right [15-02-2024(online)].pdf 2024-02-15
3 201911010698-REQUEST FOR EARLY PUBLICATION(FORM-9) [19-03-2019(online)].pdf 2019-03-19
4 201911010698-Written submissions and relevant documents [09-02-2024(online)].pdf 2024-02-09
4 201911010698-Proof of Right [15-02-2024(online)].pdf 2024-02-15
4 201911010698-POWER OF AUTHORITY [19-03-2019(online)].pdf 2019-03-19
5 201911010698-Written submissions and relevant documents [09-02-2024(online)].pdf 2024-02-09
5 201911010698-FORM-9 [19-03-2019(online)].pdf 2019-03-19
5 201911010698-Correspondence to notify the Controller [19-01-2024(online)].pdf 2024-01-19
6 201911010698-FORM-26 [19-01-2024(online)].pdf 2024-01-19
6 201911010698-FORM 18 [19-03-2019(online)].pdf 2019-03-19
6 201911010698-Correspondence to notify the Controller [19-01-2024(online)].pdf 2024-01-19
7 201911010698-US(14)-HearingNotice-(HearingDate-25-01-2024).pdf 2024-01-11
7 201911010698-FORM-26 [19-01-2024(online)].pdf 2024-01-19
7 201911010698-FORM 1 [19-03-2019(online)].pdf 2019-03-19
8 201911010698-CLAIMS [30-04-2022(online)].pdf 2022-04-30
8 201911010698-FIGURE OF ABSTRACT [19-03-2019(online)].jpg 2019-03-19
8 201911010698-US(14)-HearingNotice-(HearingDate-25-01-2024).pdf 2024-01-11
9 201911010698-CLAIMS [30-04-2022(online)].pdf 2022-04-30
9 201911010698-COMPLETE SPECIFICATION [30-04-2022(online)].pdf 2022-04-30
9 201911010698-DRAWINGS [19-03-2019(online)].pdf 2019-03-19
10 201911010698-COMPLETE SPECIFICATION [19-03-2019(online)].pdf 2019-03-19
10 201911010698-COMPLETE SPECIFICATION [30-04-2022(online)].pdf 2022-04-30
10 201911010698-DRAWING [30-04-2022(online)].pdf 2022-04-30
11 201911010698-DRAWING [30-04-2022(online)].pdf 2022-04-30
11 201911010698-FER_SER_REPLY [30-04-2022(online)].pdf 2022-04-30
11 abstract.jpg 2019-04-29
12 201911010698-FER_SER_REPLY [30-04-2022(online)].pdf 2022-04-30
12 201911010698-OTHERS [30-04-2022(online)].pdf 2022-04-30
12 201911010698-Proof of Right (MANDATORY) [12-08-2019(online)].pdf 2019-08-12
13 201911010698-OTHERS-200819.pdf 2019-08-23
13 201911010698-OTHERS [30-04-2022(online)].pdf 2022-04-30
13 201911010698-FER.pdf 2021-11-01
14 201911010698-Correspondence-200819.pdf 2019-08-23
14 201911010698-FER.pdf 2021-11-01
14 201911010698-Proof of Right [13-10-2021(online)].pdf 2021-10-13
15 201911010698-FORM 13 [09-07-2021(online)].pdf 2021-07-09
15 201911010698-POA [09-07-2021(online)].pdf 2021-07-09
15 201911010698-Proof of Right [13-10-2021(online)].pdf 2021-10-13
16 201911010698-FORM 13 [09-07-2021(online)].pdf 2021-07-09
16 201911010698-POA [09-07-2021(online)].pdf 2021-07-09
17 201911010698-POA [09-07-2021(online)].pdf 2021-07-09
17 201911010698-Proof of Right [13-10-2021(online)].pdf 2021-10-13
17 201911010698-Correspondence-200819.pdf 2019-08-23
18 201911010698-FER.pdf 2021-11-01
18 201911010698-OTHERS-200819.pdf 2019-08-23
18 201911010698-Correspondence-200819.pdf 2019-08-23
19 201911010698-OTHERS [30-04-2022(online)].pdf 2022-04-30
19 201911010698-OTHERS-200819.pdf 2019-08-23
19 201911010698-Proof of Right (MANDATORY) [12-08-2019(online)].pdf 2019-08-12
20 201911010698-FER_SER_REPLY [30-04-2022(online)].pdf 2022-04-30
20 201911010698-Proof of Right (MANDATORY) [12-08-2019(online)].pdf 2019-08-12
20 abstract.jpg 2019-04-29
21 abstract.jpg 2019-04-29
21 201911010698-DRAWING [30-04-2022(online)].pdf 2022-04-30
21 201911010698-COMPLETE SPECIFICATION [19-03-2019(online)].pdf 2019-03-19
22 201911010698-COMPLETE SPECIFICATION [19-03-2019(online)].pdf 2019-03-19
22 201911010698-COMPLETE SPECIFICATION [30-04-2022(online)].pdf 2022-04-30
22 201911010698-DRAWINGS [19-03-2019(online)].pdf 2019-03-19
23 201911010698-CLAIMS [30-04-2022(online)].pdf 2022-04-30
23 201911010698-DRAWINGS [19-03-2019(online)].pdf 2019-03-19
23 201911010698-FIGURE OF ABSTRACT [19-03-2019(online)].jpg 2019-03-19
24 201911010698-US(14)-HearingNotice-(HearingDate-25-01-2024).pdf 2024-01-11
24 201911010698-FORM 1 [19-03-2019(online)].pdf 2019-03-19
24 201911010698-FIGURE OF ABSTRACT [19-03-2019(online)].jpg 2019-03-19
25 201911010698-FORM 1 [19-03-2019(online)].pdf 2019-03-19
25 201911010698-FORM 18 [19-03-2019(online)].pdf 2019-03-19
25 201911010698-FORM-26 [19-01-2024(online)].pdf 2024-01-19
26 201911010698-Correspondence to notify the Controller [19-01-2024(online)].pdf 2024-01-19
26 201911010698-FORM 18 [19-03-2019(online)].pdf 2019-03-19
26 201911010698-FORM-9 [19-03-2019(online)].pdf 2019-03-19
27 201911010698-FORM-9 [19-03-2019(online)].pdf 2019-03-19
27 201911010698-POWER OF AUTHORITY [19-03-2019(online)].pdf 2019-03-19
27 201911010698-Written submissions and relevant documents [09-02-2024(online)].pdf 2024-02-09
28 201911010698-POWER OF AUTHORITY [19-03-2019(online)].pdf 2019-03-19
28 201911010698-Proof of Right [15-02-2024(online)].pdf 2024-02-15
28 201911010698-REQUEST FOR EARLY PUBLICATION(FORM-9) [19-03-2019(online)].pdf 2019-03-19
29 201911010698-PatentCertificate15-04-2024.pdf 2024-04-15
29 201911010698-REQUEST FOR EARLY PUBLICATION(FORM-9) [19-03-2019(online)].pdf 2019-03-19
29 201911010698-REQUEST FOR EXAMINATION (FORM-18) [19-03-2019(online)].pdf 2019-03-19
30 201911010698-IntimationOfGrant15-04-2024.pdf 2024-04-15
30 201911010698-REQUEST FOR EXAMINATION (FORM-18) [19-03-2019(online)].pdf 2019-03-19
30 201911010698-STATEMENT OF UNDERTAKING (FORM 3) [19-03-2019(online)].pdf 2019-03-19
31 201911010698-STATEMENT OF UNDERTAKING (FORM 3) [19-03-2019(online)].pdf 2019-03-19
31 201911010698-FORM 4 [16-12-2024(online)].pdf 2024-12-16

Search Strategy

1 201911010698E_29-10-2021.pdf

ERegister / Renewals

3rd: 16 Dec 2024

From 19/03/2021 - To 19/03/2022

4th: 16 Dec 2024

From 19/03/2022 - To 19/03/2023

5th: 16 Dec 2024

From 19/03/2023 - To 19/03/2024

6th: 16 Dec 2024

From 19/03/2024 - To 19/03/2025

7th: 10 Mar 2025

From 19/03/2025 - To 19/03/2026