GB2550406A - Method and system for managing time-based task - Google Patents

Abstract

A method and system for managing a time-based task comprises; populating a database with intellectual property (IP) related data, the data comprising a first deadline date and a deadline type; calculating a second deadline based on the first deadline; sending a request for a service based on the first deadline type; receiving a service description related to the request; executing a communication using the received service description; and performing the time-based task by the second deadline. The IP related data may be patent data, and the service request may be made to service providers to make an equivalent application or make a complete application to replace a provisional application. The service providers may make multiple approvals about the service request, and a service allocator (which may be a patent attorney) may select a particular service provider. The deadline type may be one of a critical deadline, an important deadline and a follow-up deadline. A third deadline may also be determined.

Description

METHOD AND SYSTEM FOR MANAGING TIME-BASED TASK TECHNICAL FIELD

[001] The present disclosure relates generally to managing tasks and resources for doing such tasks; and more specifically, to a method and a system for managing a time-based task, such as tasks associated with intellectual property services.

BACKGROUND

[002] The management of intellectual property rights (or services) like patents, trademarks, and so forth, is generally a lengthy and a continuous process. Often, an individual or an enterprise seeking protection of intellectual property rights engages the services of a patent attorney or patent agent to secure the intellectual property rights at a patent office. In the process, the attorney or agent prepares and files the requisite paperwork at the patent office.

[003] The documentation lifecycle to secure and maintain intellectual property rights requires many tasks to be performed at regular intervals and therefore involves a considerable amount of communication between the attorney and the patent office. Predominantly, the tasks involved in the process of managing intellectual property rights are preparation of the application, filing of the application, response to examination report and maintenance of the application. Moreover, depending on the nature of the tasks, the patent office may specify a date, such as a deadline, making such tasks as time-based tasks which the attorney is required to complete before such deadline. Therefore, such tasks may require special attention because of associated deadline, and it may be desirable for the attorney to seek assistance from a third party service provider to perform such time-based task before the deadline.

[004] Presently, there exist ways in which third party service providers may try to pro-actively offer their assistance to attorneys. For example, the third party service providers may use marketing letters, Client Relationship Management (CRM) systems, and so forth, to contact attorneys. The known ways to offer assistance (by the service providers to the attorneys) are typically based on the information available in public domain, and such assistance may not take care of time-based tasks for which the attorneys may require assistance. Also, the known ways to offer assistance are not flexible enough to accommodate the time-based tasks having very critical deadlines (such as close deadlines or immovable deadlines). For example, if due to any reason, the attorney forgets or very lately realizes about such time-based tasks, in such instances, the known ways to offer assistance may not be effective to attend to such time-based tasks.

[005] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks associated with managing resources for doing time-based tasks.

SUMMARY

[006] The present disclosure seeks to provide a method for managing a time-based task.

[007] The present disclosure also seeks to provide a system for managing a time-based task.

[008] In one aspect, an embodiment of the present disclosure provides a method for managing a time-based task, the method comprising - populating a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task; - calculating a second deadline based on the first deadline; - sending a request for a service based on the deadline type; - receiving a service description related to the request; - making a communication using the received service description; and - performing the time-based task by the second deadline.

[009] In another aspect, an embodiment of the present disclosure provides a system for managing a time-based task, the system comprising - at least one communication device associated with at least one service allocator; - at least one communication device associated with at least one service provider; and - a server communicably coupled to the at least one communication device of the at least one service allocator and the at least one service provider, wherein the server is configured to - populate a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task, - calculate a second deadline based on the first deadline, - send a request for a service based on the deadline type, - receive a service description related to the request, - make a communication using the received service description, and - perform the time-based task by the second deadline.

[0010] Embodiments of the present disclosure substantially eliminate or at least partially address the aforementioned problems in the prior art, and enables an efficient management of resources for doing time-based tasks.

[0011] Additional aspects, advantages, features and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative embodiments construed in conjunction with the appended claims that follow.

[0012] It will be appreciated that features of the present disclosure are susceptible to being combined in various combinations without departing from the scope of the present disclosure as defined by the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the present disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.

[0014] Embodiments of the present disclosure will now be described, by way of example only, with reference to the following diagrams wherein: FIG. 1 is a schematic illustration of a system for managing a time-based task, in accordance with an embodiment of the present disclosure; FIG. 2 is an illustration of operational steps of the system (of FIG. 1), in accordance with an embodiment of the present disclosure; FIG. 3 is an illustration of operational steps of the system (of FIG. 1), in accordance with another embodiment of the present disclosure; FIG. 4 is a schematic illustration of a user interface rendered on a communication device associated with a service allocator, in accordance with an embodiment of the present disclosure; and FIG. 5 is an illustration of steps of a method for managing a time-based task, in accordance with an embodiment of the present disclosure.

[0015] In the accompanying drawings, an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent. A non-underlined number relates to an item identified by a line linking the non-underlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing.

DETAILED DESCRIPTION OF EMBODIMENTS

[0016] The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognize that other embodiments for carrying out or practicing the present disclosure are also possible.

[0017] In one aspect, an embodiment of the present disclosure provides a method for managing a time-based task, the method comprising - populating a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task; - calculating a second deadline based on the first deadline; - sending a request for a service based on the deadline type; - receiving a service description related to the request; - making a communication using the received service description; and - performing the time-based task by the second deadline.

[0018] In another aspect, an embodiment of the present disclosure provides a system for managing a time-based task, the system comprising - at least one communication device associated with at least one service allocator; - at least one communication device associated with at least one service provider; and - a server communicably coupled to the at least one communication device of the at least one service allocator and the at least one service provider, wherein the server is configured to - populate a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task, - calculate a second deadline based on the first deadline, - send a request for a service based on the deadline type, - receive a service description related to the request, - make a communication using the received service description, and - perform the time-based task by the second deadline.

[0019] In an embodiment, the at least one communication device associated with the at least one service allocator and the at least one service provider include, but are not limited to, a smart phone, a tablet, a laptop, a desktop computer and a personal digital assistant.

[0020] In an embodiment, the term "service allocator" used herein relates to a person (such as an attorney or an agent) engaged by a client (such as an individual inventor, a group of inventors or an enterprise) to handle procedures associated with obtaining intellectual property rights for the client. Specifically, the service allocator communicates with the client, and acquires work or tasks (related to securing intellectual property rights) from the client. Thereafter, completes the work or tasks himself/herself or takes assistance of a service provider (explained in greater detail herein later).

[0021] In an embodiment, the communication device associated with the at least one service allocator may be configured to include an Intellectual Property management module (hereinafter referred to as 'IP management module'). The term "IP management module" may relate to a software or a combination of a software and a hardware, used by the service allocator for managing intellectual property tasks at his/her end for his/her client. In one embodiment, the IP management module may be a Microsoft word document or a Microsoft excel sheet including the intellectual property related data, otherwise IP management module may be a (customer relationship management) CRM system including the intellectual property related data.

[0022] In one embodiment, the IP management module may be stored on a server. In such instance, the communication device may comprise an access module to access the IP management module on the communication device from the server.

[0023] In one embodiment, the term "service provider" used herein relates to an entity having expertise in performing tasks associated with intellectual property services. Further, the service provider may be a company or a person capable of providing such services, i.e. performing time-based tasks associated with management of intellectual property rights. For example, the service provider may be capable of providing services, such as reminding a service allocator regarding performance of the time-based task; and providing deliverable (to the service allocator) associated with such time-based task, which is explained in greater detail herein later.

[0024] The system of the present disclosure further comprises a server. The server is communicably coupled to the at least one communication device of the at least one service allocator and the at least one communication device of the at least one service provider through a communication network. In present embodiment, the server is configured to include a service module, which may be associated with the at least one service provider. The service module is also associated with the at least one service allocator. Specifically, the IP management module and the service module are collectively configured to manage the time-based tasks associated with intellectual property services. In one embodiment, the service module may be stored in the communication device of the service allocator (instead of the server).

[0025] In an embodiment, the network used to communicably couple the at least one communication device associated with the at least one service allocator, the at least one communication device associated with the at least one service provider, and the server, includes, but is not limited to, Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks (MANs), Wireless LANs (WLANs), Wireless WANs (WWANs), Wireless MANs (WMANs), the Internet, second generation (2G) telecommunication networks, third generation (3G) telecommunication networks, fourth generation (4G) telecommunication networks, and Worldwide Interoperability for Microwave Access (WiMAX) networks.

[0026] In operation, the service allocator populates and/or enters intellectual property related data in the communication device associated with the service allocator. The communication device associated with the service allocator is configured to be connected to an aforementioned network. In an embodiment, the service allocator may receive the intellectual property related data from an intellectual property office.

[0027] In an embodiment, the term "intellectual property related data" may include information such as an attorney docket number, inventor details (such as, a name, an address, a citizenship and so forth), a title, an application type (such as a provisional or a non-provisional in case of patents), an entity size (such as, a micro entity, a small entity and a large entity), a subject matter type (such as design, utility and so forth), a priority information, communication details (such as an email id), attorney details (such as, a name, a registration number, an address, a contact number and so forth), an application as filed, information about preliminary amendments, a filing receipt, signed documents (such as an oath and declaration form) and so forth. Also, the intellectual property data includes all dates (or timelines) associated with any task to be performed for managing the intellectual property services.

[0028] In another embodiment, intellectual property related data may also comprise applications related to a new content against which an intellectual property protection is sought. For example, the new content includes a non-provisional patent application prepared on the basis of a provisional patent application, a design patent application, a trademark application and so forth.

[0029] In an embodiment, the IP management module (stored in the communication device associated with the service allocator) is configured to share the entire or a part of the intellectual property related data, through the network, to the server. Further, the server (or service module) may accordingly be configured to populate a database of the server with such intellectual property related data.

[0030] In an embodiment, the service module (stored in the server) may be configured to populate a database with an intellectual property related data comprising at least a first deadline date and a deadline type, associated with a time-based task.

[0031] In an embodiment, the server is configured to provide an access, to the intellectual property related data populated by the service allocator, to the at least one service provider. Specifically, the server is configured to provide the access of the intellectual property related data to the at least one service provider by registering the at least one service provider with the server. For example, the at least one service provider may register using service provider details (name, ID, passwords) with the help of the service module.

[0032] In an embodiment, the term "time-based task" used herein relates to any task or activity which is initiated and completion of such activity is time bound. In the present embodiment, the term "time-based tasks" are associated with tasks related to securing and managing intellectual property services or rights. In another embodiment, the time-based task may include communication with an examiner or communication with a third party, for example, a client.

[0033] In one embodiment, the time-based task may include a reminder for performing such time-based task. The reminder may be in form of a notification email or a notification message for performing the time-based task. For example, the reminder may include a notification related to filing a complete patent application based on a provisional application thereof, or a notification related to filing a PCT (Patent Cooperation Treaty) patent application based on a complete patent application.

[0034] In another embodiment, the time-based task comprises deliverable associated with such time-based task. For example, the deliverable may include but is not limited to forms associated with the intellectual property related data, applications associated with the intellectual property related data, and responses to shortcomings associated with the forms and the applications.

[0035] In an embodiment, the forms associated with intellectual property related data include standard forms which may contain aforementioned intellectual property related information. For example, the forms include, but are not limited to, an application filing form, a response filing form, a fee form, a patent office record updation form, and so forth. In an embodiment, the applications may be related to a new content against which an intellectual property protection is sought. For example, the new content includes a non-provisional patent application prepared on the basis of a provisional patent application, a design patent application, a trademark application and so forth. In an embodiment, the responses to shortcomings associated with the forms and the applications comprise making corrections of errors made while filing such forms, for example, correcting the spellings, correcting the address and so forth. Further, responses to shortcomings associated with the forms and the applications may also include responses to an office action or an examination report.

[0036] According to an embodiment, the time-based task may be associated with a deadline, i.e. a latest time or a date for completing and/or doing a time-based task. Further, there may be multiple deadlines associated with a time-based task, i.e. due to lengthy and continuous nature of tasks related to securing and maintaining intellectual property rights.

[0037] In an embodiment, multiple deadlines associated with a time-based task may differ in nature and therefore have different deadline types. Typically, a deadline type may be at least one of a critical deadline, an important deadline and a follow-up deadline. For example, a critical deadline may be a non-extendable deadline, for example, a 12 month deadline for filing of a non provisional patent application from a date of filing of a provisional patent application. Further, an important deadline may or may not be extendable, for example, a deadline for payment of fee. Moreover, a follow-up deadline may be an internal deadline used by an individual or an organization for monitoring the progress of tasks related to securing and maintaining intellectual property rights.

[0038] According to an embodiment, the server (or the service module stored on the server) is configured to calculate a second deadline based on the first deadline. The server is configured to analyze the intellectual property related data (i.e. the first deadline date and a deadline type, associated with a time-based task) to calculate the second deadline. In an example, the second deadline (based on the first deadline) may be calculated using an algorithm. For example, while filing a non-provisional application from a provisional application, the first deadline may be considered as 12 months from the priority date of the provisional application, whereas the second deadline may be calculated as 9 months from the priority date of the provisional application. In the present embodiment, the second deadline is earlier than the first deadline. In other words, the second deadline acts as safety check to meet the first deadline. For example, the second deadline acts a reminder for doing any time-based task having the first deadline.

[0039] According to one embodiment, after calculation of the second deadline, the server is configured to wait for a pre-determined time (i.e. till the arrival of the second deadline). Thereafter, the server may send a reminder to the at least one service allocator and/or to the at least one service provider regarding the second deadline.

[0040] According to another embodiment, the IP management module (communicably coupled to the service module) may be also configured to wait for the pre-determined time and thereafter send a reminder to the at least one service allocator and and/or to the at least one service provider.

[0041] In an embodiment, the pre-determined time for which the server (or the service module) is configured to wait may be less than the predetermined time for which the IP management module is configured to wait. In other words, the server (or the service module stored on the server) is configured to send the reminder earlier than the IP management module. For example, the server may be configured to send the reminder to the at least one service allocator and/or to the at least one service provider after 8 months from a priority date (in case of conversion of a provisional application to a non-provisional application), whereas the IP management module is configured to send at least one re-reminder to the at least one service allocator after 9 months from the priority date.

[0042] In an embodiment, the at least one service provider, on receiving the intellectual property related data, analyses the received data. Further, the server (or the service module) is configured to form a request for a service based on the deadline type (associated with the received data). Specifically, the at least one service provider registered with the server forms the request for the service based on the deadline type.

[0043] In an embodiment, a "request for service" refers to a proposal for performing a particular service related to a time based task. In an example, the "request for service" may include request for filing a complete application (for a provisional application), filing a patent cooperation treaty (PCT) application (for a complete application) or national-phase filing in various jurisdiction. Further, the "request for service" also includes information regarding timeline and service charges to be proposed by the service provider.

[0044] In an embodiment, after formation of the request for service, the at least one service provider sends the request for service to the service allocator via the server (or the service module). In an embodiment, such request for service may be in the form of a letter, multimedia content, an email, rendered content on communication devices, and so forth.

[0045] In an embodiment, the server (and/or IP management module) is configured to provide a rendered content to the service allocator (based on the request for service). For example, the rendered content may include a deadline reminder, a case number, intellectual property related data for the case number, and a request for a service based on the deadline type. In an embodiment, the rendered content further includes at least one button to make communication between the service allocator and at least one service provider. For example, a buttons can be used to make communication regarding PCT application filing, another button can be used to make communication regarding Europe application filing, and another button can be used to make communication regarding Chinese filing and so forth. In an embodiment, the rendered content also includes a button for instructing the at least one service provider, by the service allocator, to contact a client directly.

[0046] In an embodiment, after receiving the request the service allocator may then accept or reject the request, and accordingly the at least one service provider may wait for the approval of the request.

[0047] In another embodiment, the IP management module is configured to collect the service request from the service provider, and forward the request to an in-house Intellectual Property Rights (IPR) council for performing the time-based task.

[0048] In an embodiment, after receiving the request for service, if the service allocator approves the request, the service allocator prepares a service description related to the request. The service description may include instructions given by the service allocator to the at least one service provider for carrying out the time-based task. For example, the service description includes, but is not limited to, an instruction regarding a portion of or an entire time-based task to be performed, a service fee provided by the service allocator to the service provider for carrying out the time-based task and so forth.

[0049] In one embodiment, after preparation of the service description, the service allocator sends the service description to the server. The server accordingly may be configured to receive the service description related to the request for a service, and the at least one service provider may then access the server to receive the service description related to the request.

[0050] The server is further configured to make a communication using the received service description. In an embodiment, the communication is a back and forth communication between the at least one service allocator and the at least one service provider. The communication comprises approval for the request for the service. Specifically, the at least one service provider acknowledges the acceptance or rejection of performing the time-based task (i.e. whether or not the service provider can perform the time-based task) based on the service description provided by the service allocator. In an embodiment, the at least one service provider can communicate with the service allocator for negotiating the timeline and the service fee (decided by the service allocator).

[0051] In an embodiment, making the communication comprises receiving multiple approvals, from multiple service providers, based on the received service description. Specifically, the service allocator may receive the request for a same service from the multiple service providers. In such instance, the service allocator selects a service provider from the multiple service providers, which may be based on bidding. For example, the service providers may bid for providing the services to the service allocator, and the service allocator may select an appropriate service provider with the most suitable bid (meeting timeline and service charges specified by the service allocator).

[0052] The server is further configured to perform the time-based task by the second deadline. Specifically, the at least one service provider performs/executes the time-based task by the second deadline using the received service description, i.e. the service provider may send reminder for performing the time-based task, and/or may send the deliverable associated with the time-based task. Moreover, the at least one service provider may send an acknowledgement to the service allocator about completion of the time-based task.

[0053] In an embodiment, the server (or the service module) is further configured to calculate a third deadline based on the performed time-based task. Specifically, if the time-based task is associated with multiple timelines, the time-based task may be associated with multiple deadlines. For example, if the time-based task has been completed by the second deadline the third deadline may be calculated to complete the time-based task. A particular example for such time-based task may include responding to an examination report (issued by the patent office), which includes multiple deadlines (having different types, such as critical, important, and follow-up).

[0054] In an embodiment, the service allocator upon completion of the time-based task may update the IP management module regarding completion of such time-based task. Accordingly, the service allocator may clear the reminders/re-reminders from the IP management module. Alternatively, the IP management module may be configured to automatically clear the reminders/re-reminders on its own based on the received update from the service allocator.

[0055] In another embodiment, the IP management module is further configured to update the server (or the service module) regarding completion of the time-based task. The server (or the service module) is then configured to clear the reminders from its database based on the received update from the IP management module.

[0056] The present disclosure provides a method and system for managing a time-based task such as a task involved in a documentation lifecycle to secure and maintain intellectual property rights. The method and system described in the present disclosure enables in sharing of intellectual property related information, which is typically unavailable in public domain, between service allocators and service providers. Therefore, the sharing of information related to the time-based task facilitates timely management of resources for completion of the task before a deadline. Further, the method and system of the present disclosure are flexible enough to accommodate the time-based tasks having critical deadlines, such as close deadlines or immovable deadlines. Moreover, the method and system of the present disclosure enables in clearing reminders/re-reminders after completion of the time-based tasks, and thereby reducing communication load to the service allocator.

DETAILED DESCRIPTION OF THE DRAWINGS

[0057] Referring to FIG. 1, illustrated is a schematic illustration of a system 100 for managing a time-based task, in accordance with an embodiment of the present disclosure. The system 100 comprises at least one communication device, such as a communication device 102, associated with at least one service allocator, such as a service allocator 104. Further, the system 100 also comprises at least one communication device, such as a communication device 106, associated with at least one service provider, such as a service provider 108. The system 100 further comprises a server 110 communicably coupled to the communication device 102 and the communication device 106 via a communication network 112. As shown, the communication device 102 includes an IP management module 114 and the server 110 includes a service module 116.

[0058] Referring to FIG. 2, illustrated are operational steps 200 of a system, such as the system 100 of FIG. 1, for managing a time-based task, in accordance with an embodiment of the present disclosure. At step S 2.1, the IP management module 114 is populated with an intellectual property related data by the service allocator 104. The intellectual property related data includes at least a first deadline date and a deadline type, associated with the time-based task. At step S 2.2, entire or a part of the intellectual property related data populated in the IP management module 114 is replicated to a service module 116. At step S 2.3, a second deadline is calculated based on the first deadline by the IP management module 114. Similarly, at step S 2.4, a second deadline is calculated based on the first deadline by the service module 116. At step S 2.5, a request for a service based on the deadline type, is sent by the service module 116 to the service allocator 104. At step S 2.6 communications are made between the service allocator 104 and the service provider 108. For example, a service description related to the request is received by the service provider 108 from the service allocator 104. Further, a communication is made between the service allocator 104 and the service provider 108 using the received service description,

i.e. approval of the request based on the service description. At step S

2.7, the time-based task is performed at the second deadline. At step S 2.8, the IP management module 114 is updated regarding completion of the time-based task by the service allocator 104. At step S 2.9, the service module 116 is also updated regarding the completion of the time-based task by the IP management module 114.

[0059] Referring to FIG. 3, illustrated are operational steps 300 of a system, such as the system 100 of FIG. 1, for managing a time-based task, in accordance with another embodiment of the present disclosure. In the present embodiment, the IP Management module 306 also possesses inherent properties of a service module (such as the service module 116 shown in FIGS. 1 and 2). At step S 3.1, the IP Management module 306 is populated with an intellectual property related data by the service allocator 302. The intellectual property related data comprises at least a first deadline date and a deadline type, associated with a time-based task. At step S 3.2, the intellectual property related data is analysed and a second deadline is calculated based on the first deadline by the IP Management module 306. At steps S 3.3 and S 3.4, the IP Management module 306 requests information from a first and second service provider 310, 320. The information includes a request for service based on intellectual property related data. The requests for services received in steps S 3.3 and S 3.4 by the IP management module 306 from multiple service providers, may be for a same service (or for different services). At step S 3.5, a communication related to approvals for services from multiple service providers, is received by the service allocator 302. At step S 3.6, the selection of a service provider from multiple service providers is performed by the service allocator 302, and a service is ordered from the service allocator 302 to the second service provider 320.

[0060] Referring to FIG. 4, illustrated is a schematic illustration of a user interface 400 rendered on a communication device (such as the communication device 102, shown in FIG. 1) associated with a service allocator (such as the service allocator 104, shown in FIG. 1), in accordance with an embodiment of the present disclosure. As shown, the user interface 400 includes rendered content (related to the intellectual property related data), such as a deadline reminder, a case number, intellectual property related data for the case number, and a request for a service based on the deadline type. The user interface 400 also includes buttons 402, 404, and 406 to make communication between the service allocator (such as the service allocator 104, shown in FIG. 1) and the service provider (such as the service provider 108, shown in FIG. 1). For example, in FIG. 4, the button 402 can be used to make communication regarding patent cooperation treaty (PCT) application filing, the button 404 can be used to make communication regarding Europe (EP) application filing, and the button 406 can be used to make communication regarding Chinese (CN) filing. The user interface 400 also includes a button (Sell) 408 which allows the service allocator to establish a direct contact between the service provider and a client.

[0061] Referring to FIG. 5, illustrated are steps of a method 500 for managing a time-based task, in accordance with an embodiment of the present disclosure. Specifically, the method 500 illustrates the steps of managing the time-based task, explained in conjunction with FIGS. 1-4. At step 502, a database is populated with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task. At step 504, a second deadline is calculated based on the first deadline. At step 506, request for a service based on the deadline type is sent. At step 508, a service description related to the request is received. At step 510, a communication is made using the received service description. At step 512, the time-based task is performed at the second deadline.

[0062] The steps 502 to 512 are only illustrative and other alternatives can also be provided where one or more steps are added, one or more steps are removed, or one or more steps are provided in a different sequence without departing from the scope of the claims herein. For example, the method 500 further comprises providing access, to the intellectual property related data populated by a service allocator, to at least one service provider. Also, the method 500 comprises selecting a service provider from the multiple service providers by the service allocator. The method 500 also comprises forming the request for the service based on the deadline type.

[0063] Modifications to embodiments of the present disclosure described in the foregoing are possible without departing from the scope of the present disclosure as defined by the accompanying claims. Expressions such as "including", "comprising", "incorporating", "have", "is" used to describe and claim the present disclosure are intended to be construed in a nonexclusive manner, namely allowing for items, components or elements not explicitly described also to be present. Reference to the singular is also to be construed to relate to the plural.

Claims (15)

1. A method for managing a time-based task, the method comprising populating a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task; calculating a second deadline based on the first deadline; sending a request for a service based on the deadline type; receiving a service description related to the request; making a communication using the received service description; and performing the time-based task by the second deadline.

2. A method according to claim 1, further comprising providing access, to the intellectual property related data populated by a service allocator, to at least one service provider.

3. A method according to claim 2, wherein making the communication comprises receiving multiple approvals, from multiple service providers, based on the received service description.

4. A method according to claim 3, further comprising selecting a service provider from the multiple service providers by the service allocator.

5. A method according to any of the preceding claims, further comprising forming the request for the service based on the deadline type.

6. A method according to any of the preceding claims, wherein the time-based task comprises - reminder for performing the time-based task; and - deliverable associated with the time-based task.

7. A method according to claim 6, wherein the deliverable comprises - forms associated with the intellectual property related data; - applications associated with the intellectual property related data; and - responses to shortcomings associated with the forms and the applications.

8. A method according to claim 1, wherein the communication comprises approval for the request for the service.

9. A method according to any of the preceding claims, wherein the deadline type comprises at least one of a critical deadline, an important deadline and a follow-up deadline.

10. A method according to any of the preceding claims, further comprising calculating a third deadline based on the performed time-based task.

11. A system for managing a time-based task, the system comprising at least one communication device associated with at least one service allocator; at least one communication device associated with at least one service provider; and a server communicably coupled to the at least one communication device of the at least one service allocator and the at least one service provider, wherein the server is configured to - populate a database with an intellectual property related data, comprising at least a first deadline date and a deadline type, associated with the time-based task, - calculate a second deadline based on the first deadline, - send a request for a service based on the deadline type, - receive a service description related to the request, - make a communication using the received service description, and - perform the time-based task by the second deadline.

12. A system according to claim 11, wherein the time-based task comprises - reminder for performing the time-based task, and - deliverable associated with the time-based task.

13. A system according to claim 12, wherein the deliverable comprises - forms associated with the intellectual property related data, - applications associated with the intellectual property related data, and - responses to shortcomings associated with the forms and the applications.

14. A system according to any of the claims 11, 12 or 13, wherein the deadline type comprises at least one of a critical deadline, an important deadline and a follow-up deadline.

15. A system according to any of the preceding claims, wherein multiple service providers provide multiple approvals based on the received service description, and the service allocator selects a service provider from the multiple service providers.