JP5370791B2 - Pension interface and system in intellectual property database - Google Patents

Abstract

A method and system for integrating management of intellectual property assets with management of annuity instructions for patent grants and pending patent applications. An intellectual property asset management application is integrated with an asset management application through a third application. Communication conduits are configured in communication with the applications in the form of queues and schedulers to facilitate communicating instructions among the applications. Web services are employed as a communication medium to send instructions among the applications.

Description

  The present invention relates to an interface between two applications through a web service. More particularly, the present invention relates to interfacing an annuity application to an asset management application.

  A patent is an exclusive right granted to the inventor by the government to make, use or sell the invention for a limited number of years. A common basis for authorization is the disclosure of the invention. All licensed regular patents and many industrial design patents require periodic maintenance payments to maintain the license itself. In the United States, maintenance costs for regular patents are not pensions, and currently there are no maintenance costs for design patents. However, in most other countries, regular patents are subject to a pension, also known as a renewal fee. Such renewal fees are required even while the patent has a pending state that precedes the issuance of the license itself.

  As the patent portfolio expands, so does the maturity of pensions and the complexity of managing payments. There are services available to help manage these assets to ensure that deadlines are not overlooked, and to reduce the costs associated with managing regular maintenance costs as well as payments.

  Another aspect of the management of intellectual property assets relates to the management of pending applications and invention disclosures. A variety of tools are available for its management, but all of them employ some form of calendar that records deadlines and notifies agents and patent attorneys of such deadlines. Computer-based applications have been developed that employ that kind of management in the electronic environment. As technology evolves, so do management applications, which are now available in a web-based format accessible through commonly available browser applications.

  However, the management of intellectual property assets and the management of regular maintenance costs remain largely separate. In other words, such applications are not integrated so that the management application can also track the deadlines associated with the periodic maintenance cost (s). Accordingly, it is desirable to employ technological advances that enhance the management of intellectual property assets, including the communication of data between management application (s) and asset management services.

  The present invention includes a transparent interface between an annuity management system and an asset management system.

  In a first aspect of the invention, a computer system method is provided that includes a first computer having a first processor in communication with a first memory module, and a first application in communication with the first processor. . The first application is directed to the docking of intellectual property assets. A second computer is provided with a second processor that communicates with the second memory module and data storage, and a second application that communicates with the second processor. The second application is directed to managing pension data for intellectual property assets. A manager is provided that is local to the first computer, communicates with the first application via a local communication protocol, and communicates with the second application via a web service. The manager synchronizes data between the pension and the asset management system via the manager and a web service.

  In another aspect of the invention, an interface method is provided for coupling pension data processing to management of intellectual property assets. A first application is provided that is directed to the docking of intellectual property assets, and a second application is provided that is directed to managing pension data for the intellectual property assets. The second application communicates with the first application. The manager is connected to the first application and the second application through the web service, and provided to synchronize the pension data of the second application and the intellectual property asset of the first application through the web service. Is done.

  Other features and advantages of the present invention will become apparent from the following detailed description, which is presently preferred embodiments of the invention, taken in conjunction with the accompanying drawings.

  The drawings referred to herein form a part of this specification. The features illustrated in the drawings are meant to be illustrative of some embodiments of the invention rather than all embodiments of the invention, unless expressly indicated otherwise. Opposite implications cannot be made in any other way.

Prior art block diagram illustrating a client communicating with a server running an annuity management application Prior art block diagram illustrating a client communicating with a server running an asset management application Block diagram illustrating a server running an annuity management application communicating with a server running an asset management application Flow chart illustrating the start of the extraction process in an asset management application Flowchart illustrating the process of sending an extraction request via a third application Flow chart illustrating the retrieval of an approval file sent by an annuity management application Flowchart illustrating the process of sending payment instructions from the asset management application to the annuity management application Flowchart illustrating the transmission of instructions via a third application Flow chart illustrating the retrieval of information from an annuity management application

  As will be readily appreciated, the components of the invention generally described herein and illustrated in the drawings can be arranged and designed in a wide variety of different configurations. Accordingly, the detailed description of the apparatus, system, and method embodiments of the present invention given in the drawings below is not intended to limit the scope of the claimed invention, but is merely selected It is merely representative of this embodiment.

  The functional units described in this specification are labeled as application (s) and / or manager (s). Any of these functional units can be implemented in a programmable hardware device such as a field programmable gate array, a programmable logic array, a programmable logic device, or the like. Functional units can also be implemented in software for execution by various types of processors. The functional unit of the executable code being identified includes, for example, one or more physical or logical blocks of computer instructions and can be organized as, for example, an object, procedure, function, or other construct. Nevertheless, the managers and / or executable parts of the application that are identified need not be physically clustered, but conversely, they contain different kinds of instructions that are stored in different locations and are logical When coupled together, they may constitute functional units to achieve their stated purpose.

  In fact, an executable code manager or functional unit can be a single instruction or multiple instructions, distributed across different code segments, distributed among different applications, and even several May even be distributed across different memory devices. Similarly, operational data may be identified and illustrated within the manager and / or application, and may be embodied in any suitable form and organized in any suitable type of data structure. be able to. Operational data may be collected as a single data set or distributed across different locations, including across different storage devices, and at least partially present on the system or network as an electronic signal There is also.

  Throughout this specification, references to “selected embodiment”, “one embodiment”, or “an embodiment” refer to specific features, structures, or characteristics described in connection with that embodiment, It is meant to be included in at least one embodiment of the invention. Thus, references to “selected embodiment”, “in one embodiment”, or “in an embodiment” appearing in various places throughout this specification are not necessarily referring to the same embodiment. .

  Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of managers, applications, etc., to provide a thorough understanding of embodiments of the present invention. However, one of ordinary skill in the relevant art will recognize that the invention may be practiced without one or more of those specific details, or with other methods, components, materials, etc. . In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the invention.

  The illustrated embodiments of the invention will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The following description is intended to be exemplary only and merely illustrates certain selected embodiments of devices, systems, and processes consistent with the present invention as claimed herein. Yes.

[Overview]
Integration of the patent annuity management system with the patent asset management system is enabled through a third application. In one embodiment, this third application runs locally to the server running the asset management application. The third application serves as a conduit between the patent pension system and the asset management system that synchronizes the data in the asset management system with the pension data maintained by the pension management system. This third application communicates pension payment information to the asset management system. In this way, users can make payment decisions through the asset management system, including electronically sending instructions to the pension management system and maintaining a record of all instructions for a given update. become.

[Technical details]
In the following description of embodiments, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It will be understood that other embodiments may be utilized as structural changes may be made without departing from the scope of the present invention.

  FIG. 1 is a prior art block diagram (100) of a computer system provided with a patent annuity system. The patent pension system manages the entire pension process from decision-making to expense allocation. As shown, the server (102) is provided with a processing unit (104) that communicates with the memory (108) across the bus (106), which may be referred to herein as a processor. . Server (102) is shown as communicating with a data storage medium (110) employed to store patent maintenance cost information. A second application (112) is provided locally to the server (102) and communicates with the processing unit (104). The second application (112) serves as an interface for managing maintenance cost information stored in the storage medium (110). In one embodiment, a client machine (120) is provided to communicate with the server (102). The client machine (120) includes a processing unit (124) that communicates with the memory (128) across the bus (126). In addition, the client machine (120) is provided with an input device (130) and a visual indicator (132). The client machine (120) performs communication with the server (102), more specifically, communication with the second application (112) through a local connection or across a network interface. Thus, patent maintenance cost information is maintained locally with respect to the server and can be accessed via a client machine communicating with the server.

  FIG. 2 is a prior art block diagram (200) of a computer system provided with an asset management system. The asset management system provides detailed management of active patents as well as pending patent applications. The user shall make a case history, documents, electronically read copies of notices from the JPO, drafts, and disclosure of the invention, assignee, inventor, status of the invention, date memorandum, notice from the JPO You can check the maturity date, final date, filing, etc. However, the asset management system does not allow the user to determine or make payments for annuity payments. As shown, the server (202) is provided with a processing unit (204) that communicates with the memory (208) across the bus (206), which may be referred to herein as a processor. . Server (202) is shown as communicating with a data storage medium (210) employed to store asset management data. A first application (212) is provided locally to the server (202) and communicates with the processor (204). The application (212) serves as an interface for managing asset management data stored in the storage medium (210). In one embodiment, a client machine (220) is provided to communicate with the server (202). The client machine (220) includes a processing unit (224) that communicates with the memory (228) across the bus (226). In addition, the client machine (220) is provided with an input device (230) and a visual indicator (232). The client machine (220) performs communication with the server (202), more specifically, communication with the first application (212) through a local connection or across a network interface. Therefore, asset management data is held locally with respect to the server and can be accessed via a client machine communicating with the server.

  1 and 2 illustrate a client that can separately access maintenance cost and asset management data. However, none of the systems shown in FIGS. 1 and 2 provide communication between a server managing maintenance cost information and a server responsible for asset management information. More specifically, each of the prior art systems individually treats the asset management system or patent annuity system as a separate unit, but these two dissimilar systems are integrated or otherwise It does not include hardware and / or software tools for sharing data between them. Modify the system to include additional elements to facilitate data sharing. FIG. 3 is a block diagram (300) of a computer system that supports integration of an asset management system and a patent annuity system. As shown, the first server (302) is provided with a processing unit (304) that communicates with the memory (308) across the bus (306), which is referred to as a processor here. Sometimes. Server (302) is shown as communicating with a data storage medium (310) employed to store asset management data. In one embodiment, the data storage medium (310) may be arranged as an independent server. A first application (312) is provided locally to the server (302) and communicates with the processor (304). The application (312) serves as an interface for managing asset management data stored in the storage medium (310). In one embodiment, a client machine (320) is provided to communicate with the server (302). The client machine (320) includes a processing unit (324) that communicates with the memory (328) across the bus (326). In addition, the client machine (320) is provided with an input device (330) and a visual indicator (332). The client machine (320) communicates with the first server (302), more specifically with the application (312) through a local connection or across a network interface.

  The second server (360) is shown as communicating with a data storage medium (370) employed to store maintenance cost data. As in the case of the first server (302), the second server (360) includes a processing unit (364) that communicates with the memory (368) across the bus (366). A second application (380) for managing pension data is provided locally to the server (360). The second application (380) manages the asset management data in the storage medium (370).

  A third application (340) is provided locally to the first server (302) to facilitate communication between the patent annuity application (312) and the asset management application (380). The third application (340) serves as a conduit between the patent annuity application and the asset management application. In addition to the third application (340), two queues (342) and (344) are provided to support the interface of the third application with the first application (312). These queues are in the form of an extraction queue (342) and an instruction queue (344). The extraction queue (342) is activated by the first application (312) to extract data from the storage medium (370) that communicates with the second application (380) local to the pension system server (380). Communicate the request to the third application. An extraction request is a request for pension payment information for an approved patent or pending patent application. Details of this extraction will be described later using a flowchart illustrating an example of the flow of extraction communication. The instruction queue (344) forwards communication to the third application (340) regarding the authority to submit payments for the maintenance cost of the managed asset. Details of the instruction queue will be described later with reference to a flowchart showing an example of the instruction communication flow. For each of the queues (342) and (344), the data communication is unidirectional from the first application (312) to the third application (340). Accordingly, the first application (312) communicates with the third application (340) through these queues and the messages stored therein.

  In addition, the first application (312) can communicate the extracted data (346) and payment instruction data to the third application (340). The third application (340) communicates approval data, instruction status, pension events, and renewal date (348) to the first application.

  As shown in FIG. 3, the third application (340) is provided as an interface between the first application (312) and the second application (380). The third application (340) is separated from the asset management application. More specifically, the third application (340) functions as an interface between the asset update service and the asset management service. There are four core elements supported by the third application (340), including sending an extraction job, receiving an approval job, sending an instruction job, and receiving a package job. Each of these four core elements is described in FIGS. A scheduler (350) is employed to facilitate communication between the third application (340) and the asset management application (312). The scheduler (350) is a program that drives the third application (340). In one embodiment, the scheduler is an in-memory application that does not retain any knowledge of activity between executions. Thus, the scheduler (350) is provided in communication with the third application (340) and supports communication with the first application (312).

  As mentioned above, there are four core elements supported by the third application. FIG. 4 is a flowchart (400) illustrating by way of example a process for initiating job extraction from a first application to a third application. A scheduler is employed to prompt the first application to insert a scheduled extraction job into the extraction queue (402). Following step (402), it is determined whether the first application is seeking manual transmission of one or more data extraction jobs to the extraction queue (404). If it is an affirmative response, the process proceeds to a waiting period elapse (406) for the user to send the extraction job (s) to the extraction queue. Conversely, if the response to the determination in step (404) is negative or after completion of step (406), the first application creates an extraction request for pension payment information related to the active asset. (408) and the insertion of an extraction request into the extraction queue (410) follows. Thus, the process of inserting an extraction job into the extraction queue can be performed manually or in an automated manner without human involvement.

  After the job is inserted into the extraction queue, the job needs to be processed. FIG. 5 is a flowchart (500) illustrating an example of the extraction job processing by the third application. As indicated above, a scheduler can be employed to facilitate reexamination of extraction and instruction queues on a regular basis. Based on the time interval, the scheduler sends a message to the third application indicating that the third application needs to check the extraction queue (502). It then determines whether there are any pending extraction requests in the extraction queue (504). If the response to the decision in step (504) is negative, feedback continues to the scheduler that waits for the next time interval to expire and checks the extraction queue. Conversely, if the response to the decision in step (504) is affirmative, the third application pulls the extraction request from the queue (506), and the extraction request is local to the pension management service for processing. Followed by sending to the second application (508). In one embodiment, the extraction request is communicated to the second application via a web service. Web services are software systems designed to support interoperable machine-to-machine interactions across a network. Web services are often internet-based application program interfaces (APIs) that can be accessed over a network such as the Internet and run on a remote system that hosts the requested service. However, the present invention should not be limited to web service communications because other forms of communication protocols may be employed. Following step (508), a determination is made as to whether other extraction requests are in the extraction queue (510). If the response to the decision in step (512) is affirmative, feedback to step (506) continues. Conversely, when the response to the determination at step (510) is negative, feedback to step (502) continues. Accordingly, the third application periodically reviews the extraction queue for one or more extraction requests.

  When the extraction request is removed from the queue, it is transferred to a second application local to the annuity management data storage. FIG. 6 is a flowchart (600) illustrating an example of tracking the receipt of a request by a second application. The scheduler provides a prompt to determine the status of receipt of the extraction request to the third application on a regular basis (602). Following the prompt from the scheduler, the third application initiates a call to the second application and requests an approval file indicating receipt of the extraction request (604). Thereafter, it is determined whether the second application is in a position to transmit the approval file (606). In one embodiment, the second application may not be prepared to send the authorization file. If, in step (606), it is determined that the second application is not in a position to send acknowledgment to the third application, the third application waits for the set time interval (608) and then Return to step (602). Conversely, if the response to the determination in step (606) is affirmative, transmission (610) of the approval file to the third application continues, and then to the first application local to the asset management application. Proceed to transfer approval file (612). Thus, the third application bridges communication between the first application and the second application with respect to the extracted information.

  After the first application obtains the extracted information from the second application via the third application, the first application enters a position to make a decision related to the payment of a known annuity deadline. FIG. 7 is a flowchart (700) illustrating by way of example the logical flow for communicating annuity payment decision from the asset management application to the annuity management application. Initially, a user in communication with the asset management application makes a decision regarding payment of an annuity (702). Thereafter, a determination is made whether the decision made there is final (704). If it is determined that the decision is not final but merely preliminary, the process returns to step (702) until the final decision is reached. Conversely, if the response to the determination in step (704) is affirmative, the insertion of annuity payment instructions into the instruction queue by the first application continues (706). As shown in FIG. 3, the instruction queue is a conduit, whereby the first application communicates payment instructions to the third application.

  FIG. 8 is a flowchart (800) illustrating by way of example how the payment instructions inserted into the queue at step (706) are communicated to the pension management system. In a manner similar to the extraction queue, the scheduler periodically reminds the third application to check the instruction queue and thereby check for instructions inserted into the queue by the first application (802). Following step (802), a determination is made whether there are instructions in the queue (804). When the response to the determination in step (804) is negative, it is an indication that the queue is empty. The third application then waits for the set time interval (806) and then returns to step (802). Conversely, if the response to the determination in step (804) is affirmative, then the third application continues to retrieve instruction details from the communication inserted in the instruction queue (808). The third application subsequently sends a payment instruction to the second application local to the pension management system (810). Accordingly, communication regarding the pension instructions between the third application and the second application follows a path similar to that of the extraction information job described above with reference to FIG.

  After the instructions are communicated to the pension management system, the asset management system needs to receive a payment confirmation. FIG. 9 is a flowchart (900) illustrating an exemplary process followed by the first application of the asset management system to poll the pension management system. As shown in FIG. 8, the scheduler is employed to limit the asset management system to periodic polling of schedules. In step (902), the scheduler sends a communication to the third application indicating that it can start the polling process. The third application polls the second application of the pension management system for newer data than the previous communication (904). Although recognized in this field, the latest information on polling data may not be generated frequently. Thereafter, it is determined whether the annuity management system includes this new data (906). If the response to the decision in step (906) is negative, wait (908) continues for a predefined time interval, followed by feedback to step (902). However, if the response to the determination in step (906) is affirmative, polling data transmission from the pension management system to the asset management system continues. More specifically, this transmission includes updates on updated information (910), status on instructions for annuity payments (912), and payment process status (914). All data sent to the third application is then transferred to the first application. In one embodiment, polling data is communicated from the annuity management system to a third application local to the asset management system through a web service.

  As shown in FIGS. 3-9, all communication between an application local to the asset management system and an application local to the annuity management system occurs via web services. However, the present invention need not be limited to this single type of communication transmission. In one embodiment, other transmission tools may be employed that replace or augment web service transmission.

  Implementations that fall within the scope of the invention may include products that include program storage means encoded with program code. Such program storage means can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, such program storage means may be RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage or other magnetic storage device, or other desired program code. Any medium that can be used for storing means and accessible by a general purpose or special purpose computer can be included. Combinations of the above should also be included within the scope of program storage means.

  The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of computer readable media include storage media such as semiconductor or solid state memory, magnetic tape, removable computer diskette, random access memory (RAM), read only memory (ROM), fixed magnetic disk, flash drive, and optical disk. .

  A data processing system suitable for storing and / or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory, mass storage, and cache memory that are employed during the actual execution of program code, and the cache memory must be taken from the mass storage during execution. Provide temporary storage of at least some program code to reduce the number of code searches.

  Input / output or I / O devices (including but not limited to keyboards, displays, pointing devices, etc.) can either be coupled directly to the system or coupled through an intermediary I / O controller. . Network adapters can also be coupled to the system to allow the data processing system to be coupled to other data processing systems or remote printers or storage devices through a dedicated or public intermediary network.

  A software implementation may take the form of a computer program product accessible from a computer-usable or computer-readable medium that provides program code for use by or with a computer or any instruction execution system.

  An interface is provided that facilitates and enables automated information exchange between the pension management system and the asset management system. By adopting a schedule with this interface, the need for human interaction is alleviated if not all removed together. While particular embodiments of the present invention have been described herein for purposes of illustration, it will be appreciated that various modifications can be made without departing from the spirit and scope of the invention. In particular, in one embodiment, a web service can be employed as a medium for communication between the third application and the patent asset management application, and the third application can be embedded locally in the patent annuity application. . Similarly, in another embodiment, the third application can be embedded on a third server that is remote to both the patent asset management application and the patent annuity application. The third application communicates with both of the remaining applications through a network connection, and the web service is employed as a medium for communication between the third application, the patent asset management application, and the patent annuity application. . Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.

Claims (24)

A first server having a first processor in communication with a first data storage medium storing intellectual property asset data;
A first application serving as an interface for the first storage and communicating with the first processor, the first application being directed to the docking of intellectual property assets;
A second server having a second processor in communication with a second data storage device storing pension data;
A second application serving as an interface for the second storage medium and communicating with the second processor, the second application being directed to managing pension data for intellectual property assets; ,
The local to the first server, and communicates with the first application via the local communication protocol, a third application that communicates with the second application via a web service, instructions And communicating pension information received from the first application to the second application and a corresponding pension related to information received from the second application to the first application. A third application making a request to
Each of the pensions for the instructions, the request, and the corresponding pension for the information that is accessible by the first and third applications are stored before they are communicated to the first or second application. Multiple queues
A scheduler in communication with the third application, wherein for the third application, a pension for the instruction, the request, and a corresponding pension for the information from the plurality of queues, the first application and A scheduler that prompts one of the second applications to periodically release;
Computer system with The computer system according to claim 1,
A computer system further comprising a local extraction queue for the first computer and receiving an extraction request from the first application. A computer system according to claim 2,
The third application transmits the extraction request to the second application via the web service ,
Computer system requirements that have a said extraction request to search for the pension information. A computer system according to claim 3,
The third application receives an approval file from the second application and communicates the approval file to the first application ;
Computer system that pension relating to the information having a the approval file. A computer system according to claim 4,
The approval file is a computer system that confirms reception of extraction by the second application. The computer system according to claim 1,
Further comprising a local instruction queue for the first computer for receiving annuity payment instructions from the first application ;
Computer system pension relating to the instructions to have the said pension payment instructions. The computer system according to claim 6,
The third application is a computer system that transmits the annuity payment instruction to the second application via the web service. The computer system according to claim 7,
The third application is a computer system that receives an approval file containing confirmation of annuity payment from the second application and communicates the approval file to the first application. The computer system according to claim 1,
The computer system wherein the first application communicates a polling query to the second application and receives the current status of pension data for the selection of intellectual property assets. A computer system according to claim 9,
The computer system wherein the current status of the pension data includes an update on pension update data information for selection of the intellectual property asset. A computer system according to claim 9,
The computer system includes processing instruction status data including status relating to processing of annuity instructions received by the second application. A computer system according to claim 9,
The polling query is a computer system that includes status updates regarding the status of annuity payments for selection of the asset. A processor linking a first data storage medium used to store intellectual property data to a first application, wherein the first application is directed to the docking of intellectual property assets When,
The processor linking a second data storage medium used to store pension data to a second application, wherein the second application is allocated to managing pension data for intellectual property assets. The steps directed,
The processor communicates pensions for instructions using a third application, pension information received from the first application to the second application, and from the second application to the first application. Making a request to retrieve a corresponding pension for received information, wherein the third application communicates with the first application via a local communication protocol, and via a web service Communicating with a second application;
The processor stores each of the pensions for the instruction, the request, and the corresponding pension for the information in a plurality of queues before they are communicated to the first or second application. The plurality of queues being accessible by the first and third applications;
The processor uses the scheduler to obtain a pension for the instruction, a request for the instruction, and a corresponding pension for the information from the plurality of queues for the third application. Prompting one of the applications to release periodically,
Having an interface method. 14. An interface method according to claim 13, comprising:
An interface method for receiving an extraction request from the first application through a local extraction queue for the first application. 15. The interface method according to claim 14, wherein
The third application communicates the extraction request to the second application via the web service ;
Interface method request that have a said extraction request to search for the pension information. 16. The interface method according to claim 15, comprising:
The third application receives an approval file from the second application and communicates the approval file to the first application ;
Interface how pension relating to the information having a the approval file. The interface method according to claim 16, comprising:
The interface method, wherein the approval file includes data confirming receipt of the extraction by the second application. 14. An interface method according to claim 13, comprising:
A local instruction queue for the first computer to receive annuity payment instructions from the first application ;
An interface method wherein the pension for the instruction comprises the pension payment instruction . 19. An interface method according to claim 18, comprising:
An interface method in which the third application communicates the pension payment instruction to the second application via the web service. 20. An interface method according to claim 19, comprising:
An interface method wherein the third application receives an approval file containing a confirmation of annuity payment from the second application and communicates the approval file to the first application. 14. An interface method according to claim 13, comprising:
An interface method for communicating a polling query from the first application to the second application to receive a current status of pension data for selection of intellectual property assets. The interface method according to claim 21, wherein
An interface method wherein the current status of the pension data includes an update on pension update data information for selection of the intellectual property asset. The interface method according to claim 21, wherein
The interface method wherein the polling query includes processing instruction status data including a status relating to processing of annuity instructions received by the second application. The interface method according to claim 21, wherein
The interfacing method wherein the polling query includes status updates regarding the status of annuity payments for selection of the asset.

Images