JP2003296506A - Electronic delivery system and electronic delivery method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an electronic delivery system and electronic delivery method capable of enhancing the reliability of an electronically delivered delivery slip. <P>SOLUTION: This electronic delivery system comprises a company A 1, a communication network 2 and a patent office B 3<SB>1</SB>connected to the company through the communication network 2. The processing control part 33 of the patent office B 3<SB>1</SB>changes the flag state to a requested state when request form data are transmitted from the company A 1. The processing control part 33 changes the flag state to a receipt read state when receipt data are stored. The processing control part 33 changes the flag state to a delivery slip forming state when the formation of delivery slip data is started. The processing part 33 changes the flag state to a delivery slip formed state when the delivery slip data are formed. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an electronic delivery system and an electronic delivery method, and more particularly to an electronic delivery system and an electronic delivery method for delivering a delivery note via a communication network.

[0002]

2. Description of the Related Art In recent years, with the widespread use of personal computers, in-house documents have been unified into specific software, and paper documents have been digitized to improve in-house work efficiency. As a part of such streamlining of business, electronic documents such as e-mails are also used in relationships with external companies that undertake specific business.

[0003]

By the way, the delivery note from another external company is sent as a paper document. In order to manage the delivery note electronically, it is necessary to input the contents of the delivery note, and it takes a lot of labor and time to manage the delivery note.

As for the delivery note, the construction of an electronic delivery system capable of delivering the delivery note through the communication network is under consideration. However, it is necessary to have a person in charge of another company perform the work of inputting the contents of the delivery note. For example, if you make a mistake in the input work, you can not proceed to the next task. Need to raise.

The present invention has been made in view of the above problems, and an object of the present invention is to provide an electronic delivery system and an electronic delivery method capable of improving the reliability of an electronic delivery note. Another object of the present invention is to provide an electronic delivery system and an electronic delivery method that can facilitate management of delivery notes.

[0006]

In order to achieve the above object, the electronic delivery system according to the first aspect of the present invention is
An electronic delivery system in which a requestee who submits a document or document data to a predetermined organization in response to a request from a requester is an electronic delivery system that electronically delivers delivery note data to the requester, and according to the creation status of the delivery note data, a flag of A flag state changing means for changing the state to at least requested, receipt taken, delivery note being created and delivery note being made, and when the flag state by the flag state change means indicates a requested state, When receipt data storage means for storing receipt data of a receipt indicating receipt of a document or document data from the predetermined institution, and when the flag status change means indicates that the receipt has been taken , A delivery note data creation start means for starting creation of delivery note data, and a flag state change means indicating that the delivery note data is being created First, the delivery note data creating means for creating delivery note data, and the delivery note data created by the delivery note data creating means when the flag state by the flag state changing means indicates the delivery note created state And a transmitting means for transmitting to the request source.

The flag state changing means changes the state of the flag to a requested state, for example, when the request form data of the request form indicating the request content from the request source is transmitted, and the receipt data is received. When the receipt data is stored by the storage means, the state of the flag is changed to a state in which the receipt has been taken in, and when the delivery note data creation start means starts producing the delivery note data, the state of the flag When the delivery note data is created by the delivery note data creating means, the state of the flag is changed to a state in which the delivery note has been created.

[0008] It is preferable that the flag state changing means changes the state of the flag to a state in which the delivery note has been prepared when all the submitted document data submitted to the predetermined organization is attached to the delivery note data. .

When the delivery means transmits the delivery note data to the request source, the flag state changing means changes the state of the flag to a delivered state, and the flag state changing means delivers the flag state. It is preferable to further include a bill preparing means for preparing a bill when the completed state is shown.

The electronic delivery method according to the second aspect of the present invention is an electronic delivery method in which a requester who submits a document or document data to a predetermined organization by request from a requester electronically delivers the delivery note data to the requester. A flag state changing step of changing the flag state into at least a requested state, a receipt fetched state, a delivery note preparing state, and a delivery note prepared state according to the preparation state of the delivery note data; A receipt data storing step of storing receipt data of a receipt showing receipt of a document or document data from the predetermined institution when the flag state indicates a requested state by the state changing step; and the flag state Starting the delivery note data creation step to start creating the delivery note data when the status of the flag indicates that the receipt has been taken in by the changing step When the flag status indicates the state of creating invoices by the flag state change step,
Delivery note data creation step to create delivery note data,
A transmission step of transmitting the delivery note data created in the delivery note data creation step to the requester when the flag state indicates that the delivery note has been created in the flag state changing step. And

In the flag state changing step, for example, when the request form request data indicating the request content from the request source is transmitted, the flag state is changed to a requested state, and the receipt data is changed. When the receipt data is stored in the storage step, the state of the flag is changed to a state in which the receipt has been taken in, and when the delivery note data creation start is started in the delivery note data creation start step, the state of the flag is changed. When the delivery note data is created in the delivery note data creating step, the state of the flag is changed to the delivery note created state.

In the flag state changing step, it is preferable to change the state of the flag to a state in which the delivery note has been created when all the submitted document data submitted to the predetermined organization is attached to the delivery note data. .

In the flag state changing step, when the delivery note data is transmitted to the requester in the transmitting step, the state of the flag is changed to a delivered state, and the flag state is delivered in the flag state changing step. Invoice creation step to create an invoice when showing the completed status,
It is preferable to further provide.

The program according to the third aspect of the present invention functions as an electronic delivery system in which a requestee who submits a document or document data to a predetermined institution by request from the requester electronically delivers the delivery note data to the requester. A program for causing a computer to change the state of the flag to at least requested, receipt accepted, delivery note in preparation, and delivery note preparation state according to the state of creation of the delivery note data. State change means, receipt data storage for storing receipt data of a receipt indicating receipt of a document or document data from the predetermined institution when the flag state indicates a requested state by the state change means Means, when the flag state is changed by the flag state changing means to indicate that the receipt has been taken in, the production of delivery note data is started. The delivery note data creation means for creating delivery note data when the flag state is changed by the flag state changing means and the flag state changing means changes the flag state by the delivery note data creating means. It is characterized in that it functions as transmission means for transmitting the delivery note data created by the delivery note data creating means to the request source when indicating the state that the delivery note has been created.

[0015]

BEST MODE FOR CARRYING OUT THE INVENTION (First Embodiment) An electronic delivery system and an electronic delivery method according to an embodiment of the present invention will be described below. In the present embodiment, a delivery note (delivery note information) regarding a predetermined procedure to the patent office performed by patent office B in response to a request from corporation A is delivered to corporation A requested via the communication network. The case will be described as an example.

FIG. 1 shows the configuration of the electronic delivery system.
As shown in FIG. 1, the electronic delivery system is connected via a communication network 2 and a company A1 that requests a patent office to perform a predetermined procedure to the patent office, and receives a request from the company A1. It is composed of a plurality of patent offices B3 ₁ and patent offices C3 ₂ to N3 _n that perform predetermined procedures at the patent office.

The company A1 has a computer 11 on the company A side.
Is provided. The company A side computer 11 includes a communication control unit 12, a processing control unit 13, a company A database 14, and a company A terminal 15.

The communication control unit 12 is composed of a predetermined communication device such as a router, and the company A side computer 11
And the communication network 2. Communication control unit 12
Under the control of the processing control unit 13
Various data (information) is transmitted and received via.

The process control unit 13 controls each unit of the company A side computer 11 and executes a predetermined operation program to realize each process described later. The processing control unit 13 also controls the communication control unit 12 to perform communication via the communication network 2. Furthermore, the processing control unit 13 is assumed to create predetermined image data.

The database 14 for company A is a database (DB) that stores various information related to the electronic delivery system carried out by company A. FIG. 2 shows the structure of the company A database 14. As shown in FIG. 2, the company A database 14 includes a user DB 141 and patent office information D.
B142, procedure information DB143, and history information DB14
4, request information DB 145, delivery note information DB 146
And an image information DB 147.

The user DB 141 is a database that stores information about a person in charge of the company A (company A side user). In the user DB 141, for example, as shown in FIG. 3, a record is created for each user ID that is user identification information, and each record stores information indicating the user name, affiliation, password, and the like. . The password registered here is a password for the user to log in to the electronic delivery system.

The patent office information DB 142 is a database that stores information about the patent offices to which the company A requests the procedure. The patent office information DB 142 is, for example,
As shown in FIG. 4, a record is created for each patent office number that is a number that identifies the patent office, and each record stores information indicating the patent office name, address / location, email address, etc. Has been done. Here, “patent office name and address” indicates the name and address / location of the patent office, and “mail address” indicates an e-mail address (E-mail address) used in each patent office. .

The procedure information DB 143 is a database for storing information on the procedure requested by the company A to the patent office. In the procedure information DB 143, for example, as shown in FIG. 5, there is a record for each “procedure name” which is the name of the procedure requested by the company A to the patent office (eg, patent application, application examination request, amendment, etc.). Each created record stores information about the procedure name, such as "procedure period" indicating the period during which the procedure can be performed.

The history information DB 144 is a database that stores information on the history of the case that is the subject of the procedure requested by the company A to the patent office. In the history information DB 144, for example, as shown in FIG. 6, a record is created for each “reference number” that is a number that identifies a case to be processed, and each record includes a patent office number and an application date. , Application number, application examination request date, etc. are stored. Here, the reason why the application examination request date of reference number: JP0001 in FIG. 6 is not stored is that the application examination request is not made for this case.

The request information DB 145 is a database for storing information on the contents of the procedure requested by the company A to the patent office. In the request information DB 145, for example, as shown in FIG. 7, a record is created for each request number, and in each record, the request date, requested patent office number, reference number (application number), request content, etc. Is stored. Here, in the “request content” column, information indicating the specific content of the request is recorded, for example, “procedure (application examination request, amendment, etc.) within a predetermined period”. .

The delivery note information DB 146 is a database for storing information regarding delivery notes delivered by the patent office. For example, as shown in FIG. 8, a record is created for each delivery number in the delivery note information DB 146, and each record has a delivery date, a patent office number, a request number, a reference number (application number), and a delivery content. , Etc. are stored.

The screen information DB 147 is a database that stores information that configures various screens displayed in each process described later, and stores images of various materials and various forms for generating these images. .

The company A terminal 15 is composed of, for example, a computer and a mobile terminal. Terminal 1 for company A
Reference numeral 5 is used by the person in charge of the company A to input procedure requests, input other operations, and display processing results.

[0029] The Patent Office B3 _1, is provided Patent Office B side computer 31. The computer 31 on the patent office B side includes a communication control unit 32 and a processing control unit 33.
Database 34 for patent office B and patent office B
And a terminal 35 for use.

The communication control unit 32 is composed of a predetermined communication device such as a router, and connects the patent office B side computer 31 and the communication network 2. The communication control unit 32 transmits and receives various information via the communication network 2 under the control of the processing control unit 33.

The processing control section 33 controls each section of the computer 31 on the patent office B side and executes a predetermined operation program to realize each processing described later.
The processing control unit 33 also controls the communication control unit 32 to perform communication via the communication network 2. Further, the processing control unit 33 is supposed to create predetermined image data.

The database 34 for patent office B is a database (DB) that stores various kinds of information regarding the electronic delivery system performed by patent office B. FIG. 9 shows the configuration of the patent office B database 34. As shown in FIG. 9, the patent office B database 34 includes the user DB 3
41, company information DB 342, request information DB 343
A history information DB 344, a receipt information DB 345,
The delivery note information DB 346, the billing DB 347, the image information DB 348, and the submission document DB 349 are provided.

The user DB 341 is a database that stores information about the person in charge of the patent office B (user on the patent office B side). In the user DB 341, for example, as shown in FIG. 10, a record is created for each user ID, and in each record, the user name, affiliation, password,
Information indicating such as is stored.

The company information DB 342 is a database that stores information about the company that requests the patent office B for the procedure (hereinafter referred to as the "client company"). Corporate information DB
In 342, for example, as shown in FIG. 11, a record is created for each company number assigned to each client company, and each record stores information indicating a company name, an address, a mail address, and the like. There is.

The request information DB 343 is a database for storing information on the contents of procedures requested by the company to the patent office B. In the request information DB 343, for example, FIG.
As shown in, a record is created for each request number, and each record stores information indicating the request date, company number, reference number (application number), request content, and the like.

The history information DB 344 is a database that stores information about the history of the case subject to the procedure requested by the company to the patent office B. In the history information DB 344, for example, as shown in FIG. 13, a record is created for each reference number, and each record stores information indicating a company number, an application date, an application number, an application examination request date, and the like. ing.

The receipt information DB 345 is a database that stores information relating to the receipt of the procedure performed by the patent office B at the patent office. In the receipt information DB 345, for example, as shown in FIG. 14, a record is created for each receipt number, and in each record, information indicating the receipt date, document name, reference number (application number), company number, etc. Is remembered.

The delivery note information DB 346 is a database that stores information about delivery notes to be delivered to the company. In the delivery note information DB 346, for example, as shown in FIG. 15, a record is created for each delivery number, and each record has a request number, a submitted document name, a reference number (application number), a submission date, a receipt number, Information indicating the document status, the attachment status, etc. is stored. Here, the "document status" indicates the status of the delivery note, and depending on the progress of the procedure, "requested", "receipt receipt taken", "delivery note in preparation", "delivery note preparation" , "Delivered", "invoicing in progress", etc. are displayed. "Attachment state" indicates the attachment state of the documents to be submitted to the delivery note, and "O" is displayed according to the state.
Information indicating “K”, “error”, etc. is recorded. In the delivery note information DB 346, upon receiving a request for a predetermined procedure from the company, the processing control unit 33 registers necessary information. Then, the processing control unit 33 creates delivery note information to which a document (file) to be submitted to the Patent Office can be attached.

The billing DB 347 is a database for issuing bills (billing information). In the billing DB 347, for example, as shown in FIG. 16, a record is created for each billing date, and in each record, the billing company name and address /
Information indicating the location, the amount of money, etc. is stored.

The image information DB 348 is a database that stores information that constitutes various screens displayed in each process described later, and stores images of various materials and various forms for generating these images. .

The submitted document DB 349 is a database for storing documents submitted by the Patent Office to the Patent Office. In the submission document DB 349, for example, as shown in FIG. 17, a record is created for each submission date, and each record stores information indicating a reference number, document name, attachment state, etc. and a submitted file. Here, the “document name” includes, for example, a specification, a drawing, an application to which an abstract is attached, a request for application examination, and the like. Further, in the “attachment status”, information indicating whether or not the submitted document is attached to the delivery note is recorded. Such information is, for example, HTML format information (HTML document). <Img in this HTML document
If there is a src => tag, the image file specified by this tag is stored in association with the HTML document. However, the information stored in the submitted document DB 349 is not limited to the information in the HTML format, and may be information in other formats that can exhibit the same function.

The terminal 35 for the patent office B is composed of, for example, a computer and a portable terminal. The patent office B terminal 35 is used by the person in charge of the patent office B to create delivery note information, input other operations, and display processing results.

[0043] has the same configuration as the Patent Office B3 ₁ also Patent Office C3 ₂ ~ Patent Office N3 _n, processing similar to that patent offices B3 ₁ is performed.

Next, an electronic delivery method using the electronic delivery system configured as described above will be described. In the present embodiment, for a predetermined patent application, the company A requests the patent office B to perform a predetermined procedure to the patent office, for example, request for application examination, and the patent office B makes a predetermined patent application. For example, a case will be described in which after the application examination request is submitted to the JPO, the delivery note information regarding the application examination request is delivered to the company A. First, a description will be given of how the company A requests the patent office B for a predetermined patent application, and requests the patent office to request an application examination.

(Advance Registration) In order for the person in charge of the company A (user on the company A side) to use the electronic delivery system, it is necessary to register in advance. Hereinafter, the pre-registration of the company A side user will be described.

The company A side user transmits information such as user name and affiliation from the company A terminal 15 to the processing control unit 13. Upon receiving the information such as the user name, the processing control unit 13 issues the user ID and the password, and transmits the user ID and the password to the company A terminal 15. Further, the processing control unit 13 registers the transmitted predetermined information, user ID and password in the user DB 141.

(Login) The user on the company A side can connect to the electronic delivery system by inputting the user ID and password transmitted in advance registration. The login to the electronic delivery system will be described below.

When a user on the company A side accesses the login screen from the terminal 15 for the company A, the processing control unit 13 causes
The process shown in the flowchart of 8 is started.

First, the processing control unit 13 reads a login page (information in HTML format) as shown in FIG. 19 from the image information DB 147 and transmits it to the company A terminal 15 for login to the company A terminal 15. The page is displayed (step S1). This page has an input field for entering a login name and password.

The user on the company A side inputs the login name and password on this screen and clicks "Send". When the user on the company A side inputs the login name and password and clicks “Send”, the input items are notified to the processing control unit 13.

In response to this notification, the processing control section 13 determines whether or not the input information is registered in the user DB 141 (step S2).

When the processing control section 13 determines that the user on the company A side is not registered (step S2; No),
Information (HTML document) of a registration guide page (not shown) is transmitted to the company A terminal 15 to display the registration guide page on the company A terminal 15 (step S3), and this processing is ended.

On the other hand, when the processing control section 13 determines that the user on the company A side is registered (step S2; Yes).
s), information on the menu page as shown in FIG. 20 (HT
(ML format information) is read from the image information DB 147 and transmitted to the company A terminal 15 to display a menu page on the company A terminal 15 (step S4), and this processing ends. On the menu page shown in FIG. 20, menu fields such as “Create Request Form” for creating a request form are arranged.

(Creation of Request Form) The user on the company A side is shown in FIG.
When "Request Form Creation" is clicked from the menu page shown in 0, the process control unit 13 starts the request form creation process shown in the flowchart of FIG.

First, the processing control unit 13 reads out the information (HTML format information) of the procedure page as shown in FIG. 22 from the image information DB 147 and transmits it to the company A terminal 15, and the company A terminal 15 receives it. A procedure page is displayed (step S11). The user on the company A side clicks the procedure for requesting, “request for application examination” in the present embodiment.

Next, the processing control section 13 determines whether or not a procedure has been selected (step S12). Processing control unit 1
If it is determined that the predetermined procedure has been selected (step S12; Yes), the history information DB 3 displays the history information DB as shown in FIG.
A list of cases (procedures for which an application examination request has not been made) selected from 144 is created, and this list is transmitted to the company A terminal 15. As a result, a list of matters for which the selected procedure is possible is displayed on the company A terminal 15 (step S13). On this screen, the user on the company A side requests the application examination request, for example, reference number:
JP0001 (application number: JP 2000-12XXX)
Select and click "Send".

Subsequently, the processing control section 13 determines whether or not a case for which an application examination request is requested has been selected (step S14). When the processing control unit 13 determines that a predetermined case has been selected (step S14; Yes), it creates a request form (request information) regarding the selected case (step S15).

Next, the processing control section 13 stores the created request information in the request information DB 145 (step S1).
6), transmitting to the patent office B side computer 31 via the communication control unit 12 and the communication network 2 (step S
17).

Company A to patent office B computer 3
1, reference number: JP0001 (application number: JP-A-200)
When the request information for the application examination request for 2-12 XXX) is transmitted, the processing control unit 33 registers the transmitted request information in the request information DB 343.

Further, the processing control section 33 informs the delivery note information D.
In B346, the name of the document requested by the company A to submit to the patent office B (in this embodiment, the application examination request form), reference number: JP0001 (application number: JP 2002-12XX)
X) is registered in advance.

At the patent office B, in response to a request from the company A, reference number: JP0001 (application number: JP-A-200)
For example, submit a request for application examination for 2-12 × xxx) to the JPO online. When the application examination request is submitted to the JPO online, the JPO sends the receipt to the patent office B.

Next, a method of using the electronic delivery system to create a delivery note from receipt information transmitted from the Patent Office will be described.

(Advance Registration) In order for the person in charge of the patent office B (user on the patent office B side) to use the electronic delivery system, it is necessary to register in advance. Hereinafter, pre-registration of the patent office B side user will be described.

The user on the patent office B side obtains information such as the user name and affiliation from the terminal 35 for the patent office B by the processing control unit 3.
Send to 3. Upon receiving the information such as the user name, the processing control unit 33 issues the user ID and password, and transmits the user ID and password to the patent office B terminal 35. Further, the processing control unit 33 registers the transmitted predetermined information, user ID and password in the user DB 341.

(Login) The patent office B side user can connect to the electronic delivery system by inputting the user ID and password transmitted in advance registration. The login to the electronic delivery system will be described below.

When the user on the patent office B side accesses the login screen from the terminal 35 for the patent office B, the processing control unit 33 starts the processing shown in the flowchart of FIG.

First, the processing control unit 33 reads a login page (HTML format information) as shown in FIG. 19 from the image information DB 348 and transmits it to the patent office B terminal 35, and the patent office B terminal. A login page is displayed on 35 (step S1). This page has an input field for entering a login name and password.

The user of the patent office B side displays on this screen
Enter your login name and password and click "Send". When the user of the patent office B side inputs the login name and password and clicks “Send”, the input items are notified to the processing control unit 33.

In response to this notification, the processing control section 33 determines whether or not the input information is registered in the user DB 341 (step S2).

When the processing control unit 33 determines that the user on the patent office B side is not registered (step S2; N).
o), the information (HTML document) of the registration guide page (not shown) is transmitted to the terminal 35 for the patent office B, and the patent office B
Display the registration guide page on the device terminal 35 (step S
3) The process ends.

On the other hand, when the processing control section 33 determines that the patent office B side user is registered (step S
2; Yes), the information of the menu page as shown in FIG. 24 (HTML format information) is read from the image information DB 347 and transmitted to the terminal 35 for patent office B, and the menu page is displayed on the terminal 35 for patent office B. (Step S
4) The process is finished.

(Method of creating delivery note from receipt information)
As described above, the reference number: JP0001 (application number: JP 20
When the request information for the application examination request for 02-12XXXXX) is transmitted, the processing control unit 33 stores the document name: application examination request form, reference number in the delivery note information DB 346 as shown in FIG. : JP0001 (application number: Japanese Patent Laid-Open No. 2002-2002)
-12xxx) is registered in advance.

Then, according to the patent office B, reference number:
JP0001 (application number: JP 2002-12XXX)
For example, when a request for examination of application is submitted to the patent office online, the receipt is sent from the patent office to the patent office B.

When the receipt is sent from the JPO, the user on the B side of the patent office connects to the electronic delivery system, and
Click "Create delivery note (receipt)" from the menu page as shown in 4 to perform the delivery note creation process. When the user on the patent office B side clicks "Create delivery note (receipt)", the processing control unit 33 starts the processing shown in the flowchart of FIG.

First, the processing control unit 33 determines whether or not the information on the receipt transmitted from the JPO is registered in the receipt information DB 345 (step S21). The processing control unit 33 determines that the information about the receipt is the receipt information DB.
If it is determined that it is not registered in 345 (step S
21; No), the user on the side of the patent office B is made to register the receipt information such as the receipt number, the receipt date, the application number (reference number) in the receipt information DB 345 (step S22).
On the other hand, when the processing control unit 33 determines that the information regarding the receipt is registered in the receipt information DB 345 (step S21; Yes), the process control unit 33 proceeds to step S23.

Next, the processing control section 33 determines the receipt information DB
It is determined whether or not a case matching the application number (reference number) registered in 345 is registered in the delivery note information DB 346 (step S23).

When the processing control unit 33 determines that the matching case is registered in the delivery note information DB 346 (step S23; Yes), the submission date and the receipt number are registered in the delivery note information DB 346 (step S23). S24). The receipt number is registered in the delivery note information DB 346 to prevent the delivery note from being re-created from the same receipt when the same receipt is mistakenly fetched and executed. Further, the processing control unit 33 changes the flag to “acceptance of receipt” as shown in FIG. 27 (step S25).
In this way, when the flag is changed to “receipt has been taken in”, it becomes possible to attach the JPO documents submitted to the JPO.

When the processing control unit 33 determines that the matching case is not registered in the delivery note information DB 346 (step S23; No), this case is determined as the delivery note information DB34.
6 is registered (step S26), and the process proceeds to step S24. In such a case, for example, a request for an application examination request may be made by telephone.

Next, the user on the side of the patent office B performs, for the delivery note information in which the receipt has been taken in, automatic submission document attachment processing for attaching a submission document to the delivery note information. This automatic submission document attachment processing will be described with reference to the flowchart in FIG.

The processing control unit 33 first displays a menu screen as shown in FIG. 24 (step S31). Here, when the "automatic attachment of delivered property" is clicked (step S32; Yes), as shown in FIG. 29, the delivery document D
"Preparing a delivery note" is set in the "Document status" column of B346 (step S33).

Subsequently, the processing control unit 33 causes the delivery document DB 3
After acquiring the receipt number information recorded in the record of No. 46, the receipt information DB 345 is accessed to obtain the receipt information corresponding to the receipt number (step S3).
4)

The processing control unit 33 further includes the submitted document DB 3
By accessing 49, it is searched whether or not there is submission document information (submission date, reference number, document name) that matches the receipt information acquired in step S34 (step S35). Here, if there is matching submitted document information (step S35; Yes).
In s), the submission document file recorded in the record of the submission document information is acquired and attached to the delivery note information (step S36). Here, HT of the submitted document file
When the <img src => tag is included in the ML document, the image file specified by this tag is associated with the submitted document file and attached to the delivery note information.

When the attachment of the submitted document file is completed, the processing control unit 33 sets "OK" in the "attachment state" column of the delivery document record as shown in FIG. 30 (step S37). This shows that the documents to be submitted were successfully attached to the delivery documents.

Next, the processing control unit 33 sends the submitted document DB 34.
6 is accessed, and "attached" indicating that the document has already been attached to the delivery document is set in the "attachment status" column corresponding to the submitted document attached in step S36 (step S3).
8).

As a result, the preparation of the delivery document has been completed, and therefore the processing control unit 33 sets the "document state" of the delivery record concerned to "preparation of delivery note" indicating completion of the delivery document. (Step S39), the process ends.
When the “delivery note has been created”, the delivery note can be transmitted (delivered) to the company A, and an invoice can be created after the transmission.

(Processing method for displaying processing screen when automatic attachment is not possible) On the other hand, when the receipt information and the submitted document information do not match (step S35; No), the processing control unit 33 executes the attachment error processing (step S40). Run. Here, because the submitted documents that should have been automatically attached could not be attached, the submission date, document name, application number, etc. may be erroneous (for example, a date different from the “submission date” entered in the document (eg, the next day It is assumed that the online procedure was performed)), so the user selects the target document. This attachment error processing will be described with reference to the flowchart shown in FIG.

The processing control unit 33, as shown in FIG.
After setting "error" in the "attachment status" column of the delivery note record (step S41), a document attachment error screen as shown in FIG. 33 is displayed (step S42).

On this document attachment error screen, the information recorded in the delivery note record is displayed and
Of the submitted document information recorded in the submitted document DB 349, a button ("Yes" and "No") for selecting whether to display the list screen of the submitted documents not yet attached to the delivery note is displayed. . The patent office B side user selects “Yes” or “No”.

Here, when "Yes" is selected, that is, when the list display of the unattached submitted documents is selected (step S43; Yes), the processing control unit 33 determines from the submitted document DB 349 that "attached state". “Unattached” is acquired and displayed as a list as shown in FIG. 34 (step S44).

On this screen, for each submitted document, for example,
A selection designating means such as a check box is arranged, and the patent office B side user checks the check box corresponding to the document to be attached from the list and designates the document to be attached (step S45). ; Ye
s), by selecting the "Attach" button (step S4
6; Yes) The submitted document is attached to the delivery note information (step S47).

The processing control unit 33 changes the "attachment state" of the delivery note record from "error" to "OK" (step S48), and further sets the "attachment state" of the delivery document record in the submission document DB 349. The process is changed to "attached" (step S49), and the process ends.

(Method of Manually Creating Delivery Note) Generally, the procedure to the JPO is carried out online, but the online procedure may not be possible depending on the working conditions of the office. In that case, documents may be submitted by mail. The process for attaching the documents submitted in a form other than the online form to the delivery note is as follows.

The user on the side of the patent office B clicks “Create delivery note (manual input)” from the menu page as shown in FIG. 24, and manually performs the process of importing the delivery article. When the “preparation of delivery note (manual input)” is clicked, the processing control unit 33 provides information (HTML format information) of the manual input page as shown in FIG. 35 to the image information DB 3
Read from 48 and send to terminal 35 for patent office B,
The page for manual input is displayed on the terminal 35 for the patent office B.

Here, the procedure classification is classified into, for example, application system, examination system, intermediate system, trial system, and the like. As an application system, there are procedures such as application and submission of a certificate regarding the exception of loss of novelty. As the examination system, there are procedures such as a request for application examination and a description of circumstances regarding accelerated examination. As an intermediate system, there are procedures such as written opinions and amendments to procedures. The umpire system has procedures for appeal requests and appeals.

The user of the patent office B side can
Enter the procedure classification, application number, and submission date to identify the property to be delivered. Next, the patent office B side user selects a document to be submitted by the patent office. First, the patent office B side user clicks “Search” in the documents submitted by the Japan Patent Office. Then, for example, as shown in FIG. 34, a list of the submitted documents which are not yet attached to the delivery note is displayed among the submitted documents. Here, since a predetermined procedure has been entered in the procedure classification, a list of documents submitted by the JPO corresponding to this procedure classification is displayed. The user of the patent office B side clicks “Attach” of the patent office submission document to be attached on this screen, and specifies the patent office submission document to be attached. As a result, the documents submitted by the JPO are attached to the delivered property. Then, the user at the patent office B side confirms, at the time of saving, whether the application number, the date of submission and the document name entered in the delivery note match the data in the attached file filed by the JPO. If they match, the work ends. If they do not match, an error message will be displayed, and the patent office B side user will
Create a delivery note again according to the content of this error message.

(Electronic Delivery Method to Company) It is possible to deliver to the company in a state where the flag is "preparation of delivery note". When the patent office B side user clicks "delivery" from the menu page as shown in FIG. 24, the processing control unit 3
3 via the communication control unit 32 and the communication network 2,
The delivery note is sent to the company A side computer 11. By this transmission, electronic delivery is made to the company A.

(Method of Creating Invoice) When the delivery note is sent to the company A, the processing control unit 33 changes the flag to "delivered". With the flag being "delivered", the patent office B side user can create an invoice. When the user of the patent office B side clicks "Create billing statement" from the menu page as shown in FIG. 24, the processing control unit 33 changes the flag to "Creating billing". The processing control unit 33 creates a bill from the information registered in the billing DB 347.

Here, regarding a specific company, for example,
When the parent document of the delivery note is opened, each item related to the charge calculation set when the company requests the patent office to submit the document is set. The patent office B side user changes each item when there is a change after the request, and details the reason for the change. As described above, when the billing statement is created, the billing statement in which the billing cost in which the fee is automatically calculated according to the set item is entered is created.

When the invoice is created, the user at the patent office B side clicks "Send invoice" from the menu page as shown in FIG. When “Send bill” is clicked, the processing control unit 33 sends a bill to the company A side computer 11 via the communication control unit 32 and the communication network 2. With this transmission, the invoice is sent to the company A.

(Merging of a plurality of delivery notes) For example, when a defect is found after the amendment is submitted and the amendment is submitted again, when a plurality of procedures are performed for different contents of one request on different days. , Multiple delivery notes will coexist. In such a case, a plurality of delivery notes can be merged.
The process of merging a plurality of delivery notes will be described below.

First, the user at the patent office B side prepares the first delivery note from the contents originally requested by the first submission date by the same processing as described above, and attaches the corresponding patent office submission document. . Next, when the user of the patent office B side wants to add the documents submitted by the JPO to the delivery note, the user on the side of the patent office B creates a second delivery note from the receipt in which the documents submitted by the Patent Office are added. Then, the patent office B side user attaches the documents submitted by the Patent Office to the second delivery note.

Then, the patent office B side user selects the first delivery note and the second delivery note to be merged,
Click "Merge" from the menu page as shown in FIG. When "Merge" is clicked, the processing control unit 3
Step 3 prepares the third delivery note and attaches the documents submitted by the JPO. Then, the processing control unit 33 creates a billing statement with the newly created third delivery note.

Here, since it is assumed that both the first delivery note and the second delivery note are created from the receipt, each delivery note can be treated as a different document. This is because when a delivery note is created from a receipt, it is checked whether the delivery note was created from the same receipt.
The same invoice and the documents submitted by the JPO do not exist. Therefore, the first delivery note and the second delivery note are different documents.

From the viewpoint of delivery note management, it is preferable to limit, for example, the case where the application numbers are the same, as the conditions that can be merged. Such merge processing can be performed for any number of cases, and the merged delivery note can be further merged.

To restore the original state (first delivery note and second delivery note) after merging, click "Cancel Merge" from the menu page as shown in FIG.
You can restore the original condition from the third delivery note. In this case, since the first delivery note and the second delivery note can be restored to their original state even if the third delivery note is unmerged, they are present as delivery notes.

The above description is for the case where the delivery note created from the receipt is used. However, one or both of the first delivery note and the second delivery note is a delivery note created manually. However, the merge process is possible.

As described above, according to the present embodiment, depending on the creation status of the delivery note data, the status of the flag has been requested, receipt has been taken, delivery note is being created, delivery note has been created, etc. If you change to the state and the state of the flag does not change,
The patent office B side user cannot perform the following processing. Therefore, the reliability of the electronic delivery note can be improved.

(Second Embodiment) Next, a second embodiment will be described. In this embodiment, the configuration of the electronic delivery system is different from that of the first embodiment. However, various processes such as the process of creating a delivery note are almost the same, and in this embodiment, the configuration of the electronic delivery system and the relationship between the processes will be mainly described. FIG. 36 is a diagram showing the relationship between the databases of the electronic delivery system according to the present embodiment.

As shown in FIG. 36, the electronic delivery system is composed of a company A51, a communication network 52, and a patent office B53. The company A51 stores an office request DB 54 that stores information about a request form for requesting a procedure from a patent office, and an examination request necessity evaluation workflow DB 5 that stores information about an application examination request necessity evaluation.
5, a patent common master DB 56 that stores information on charges for procedures, a billing statement DB 57 that stores billing statement data, a delivery DB 58 that stores delivery data, a fee list master and billing statement data, and an intermediate process. And an intermediate DB 59 for storing information regarding The electronic delivery system uses the office request DB 5 between the company A 51 and the patent office B 53 via the communication network 52.
4 and the delivery DB 58 and the intermediate DB 59 are configured to be able to send and receive information. The electronic delivery system is controlled by a server (not shown).

Next, the flow of the procedure (work flow) of the present embodiment will be described by taking as an example the case where the company A requests the patent office B for an application examination request. FIG. 37 is a flowchart for explaining the procedure processing of the electronic delivery system.

As shown in FIG. 37, the person in charge of examination request creates (displays) an office request form for an application examination request (step S51). The server stores the information regarding this request in the office request DB 54 and transmits the stored information to the patent office B.

The person in charge of the patent office B makes an application examination request to the JPO based on the sent information, and the delivery note is made from the information sent from the person in charge of examination request and the information on the receipt 60 from the JPO. Is created (step S52). Next, the person in charge of the patent office B imports the delivered article 61 (application examination request form) into the created delivery note (step S5).
3) Deliver the information about the delivery note in which the delivered article 61 is taken to the intellectual property of the company A (stored in the delivery DB by the server)
Yes (step S54). Information from the patent common master DB 56 is also stored in the delivery DB 58, these information is printed (step S67), and the submitted document 63 is output.

Subsequently, the person in charge of the patent office B determines whether or not the billing details need to be created (step S55), and if it is determined that it is not necessary (step S55; No), the process proceeds to step S57. If it is determined that it is necessary (step S55; Yes), a billing statement is created (step S56).

Next, the server determines whether or not the request data exists (step S57). If it is determined that the request data exists (step S57; Yes), the bill statement preparation data is stored in the bill statement DB 57. Yes (step S5
8). The server also stores it in the delivery DB 58. When the server determines that the request data does not exist (step S57; No), it outputs the existence check file (step S59) and stores it in the delivery check IN file (step S60).

Next, the server performs presence check processing (step S61) and stores it in the delivery check OUT file (step S62). Subsequently, the server performs existence check reflection processing (step S63) and determines whether or not the requested data exists (step S64). When the server determines that the request data exists (step S64; Yes), the process returns to step S58. When the server determines that the request data does not exist (step S64; No), the server transmits this information to the patent office B.

The person in charge of the patent office B displays a list of billing detail states (step S65) and determines whether or not to create a delivery note (step S66). When it is determined that the person in charge of the patent office B creates the delivery note (step S6)
6; Yes), the process returns to step S52. When the person in charge of the patent office B determines that the delivery note is not created (step S66; No), this processing ends.

Next, the flow (business flow) of the procedure of the electronic delivery system according to this embodiment will be described. Figure 38
FIG. 6 is a diagram for explaining a procedure process of the electronic delivery system according to the present embodiment.

As shown in FIG. 38, the person in charge of the company A51 uses the examination request necessity evaluation workflow DB 55 to
Performs the evaluation process for the necessity evaluation of application examination request. When making a request for application examination, the person in charge of the company A51 creates information on the request form for requesting the application examination request from the patent office B, and uses the office request DB 54 to make an online request.
Request patent examination B for application examination request. Here, it is also possible to request the application examination request from the patent office B by paper without using the office request DB 54.

The person in charge of the patent office B who accepted the project is
Create the necessary documents and request the patent office to examine the application online. Here, it is also possible to request an application examination from the JPO by mail. Next, the person in charge of the patent office B creates a delivery note from the procedure documents and the information on the receipt. Here, the person in charge of the patent office B may merge or cancel the merger of the delivery notes. Next, Patent Office B
The person in charge delivers (sends) information about the delivery note to the intellectual property of the company A. With the intellectual property, it is possible to output the submitted documents submitted to the JPO by printing the information regarding the received delivery note.

Further, the person in charge of the patent office B creates a billing statement, and transmits the information relating to the billing statement to the billing statement DB 57 of the company A by night batch, for example. After performing the existence check, the company A (server) performs automatic inspection or inspection by a person in charge of intellectual property, and executes billing processing.

When the person in charge of the company A51 makes a request for intermediate processing to the patent office B, the intermediate DB 59 is used to create information regarding the request form for requesting the intermediate processing to the patent office B, and the intermediate DB 59 is used. Online, Patent Office B
Ask for intermediate processing. Subsequent processing is the same as in the case of application examination request.

As described above, also by the electronic delivery system of the present embodiment, the delivery note is managed using the information regarding the delivery note sent to the company A, and the delivery note can be easily managed. .

The present invention is not limited to the above embodiment, and various modifications and applications are possible. For example, the system configuration and screen configuration can be changed as appropriate. Further, if the substantially same function can be realized, the processing procedure and the like can be appropriately changed.

In the above embodiment, the present invention has been described by taking as an example the case where the company A requests the patent office B to carry out the procedure for the patent office, but the present invention is not limited to this.
The request source (client) may be a case where the request destination requests a procedure for a predetermined organization such as a judiciary or an administrative organization.
The request source may be an individual as well as a corporation such as a company. There is a procedure agency as the request destination.

In the above embodiment, the status of the flag has been requested, receipt has been taken, delivery note is being created, delivery note has been created,
Although the present invention has been described by taking the case where it is delivered and changed during billing as an example, the present invention is not limited to this.
For example, the state of the flag may be changed to “requested”, “receipt taken”, “delivery in progress”, or “delivery in progress”. Also in this case, the reliability of the electronic delivery note can be improved.

[0126] All or part of the programs necessary for causing a computer or a group of computers to function as the above-mentioned system or to execute the above-mentioned steps are recorded on a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc. may be recorded and distributed.

[0127]

As described above, according to the present invention,
The delivery note can be easily managed.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of an electronic delivery system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of a company A database in FIG.

FIG. 3 is a diagram showing a configuration of a user database.

FIG. 4 is a diagram showing a configuration of a patent office information database.

FIG. 5 is a diagram showing a configuration of a procedure information database.

FIG. 6 is a diagram showing a configuration of a history information database.

FIG. 7 is a diagram showing a configuration of a request information database.

FIG. 8 is a diagram showing a configuration of a delivery note information database.

9 is a diagram showing a configuration of a database for patent office B in FIG. 1. FIG.

FIG. 10 is a diagram showing a configuration of a user database.

FIG. 11 is a diagram showing a configuration of a company information database.

FIG. 12 is a diagram showing a configuration of a request information database.

FIG. 13 is a diagram showing a configuration of a history information database.

FIG. 14 is a diagram showing a configuration of a receipt information database.

FIG. 15 is a diagram showing a configuration of a delivery note information database.

FIG. 16 is a diagram showing a configuration of a billing database.

FIG. 17 is a diagram showing a configuration of a submitted document database.

FIG. 18 is a flowchart illustrating a process executed by the electronic delivery server when logging in.

FIG. 19 is a diagram showing an example of a login page.

FIG. 20 is a diagram showing an example of a menu page.

FIG. 21 is a flowchart for explaining a request form creation process.

FIG. 22 is a diagram showing an example of a procedure page.

FIG. 23 is a diagram showing a list of cases not requested for application examination.

FIG. 24 is a diagram showing an example of a menu page.

FIG. 25 is a diagram showing an example of a delivery note information database.

FIG. 26 is a flowchart illustrating a delivery note creating process.

FIG. 27 is a diagram showing an example of a delivery note information database.

FIG. 28 is a flowchart for explaining an automatic attachment process of submitted documents.

FIG. 29 is a diagram for explaining an example of information recorded in the delivery note information database.

FIG. 30 is a diagram for explaining an example of information recorded in a delivery note information database.

FIG. 31 is a flowchart for explaining an attachment error process executed in the submitted document automatic attachment process shown in FIG. 28.

FIG. 32 is a diagram for explaining an example of information recorded in the delivery note information database.

33 is a diagram showing a display example of a document attachment error screen displayed in the attachment error processing shown in FIG. 31.

FIG. 34 is a diagram showing a display example of a non-attached document list screen displayed in the attachment error processing shown in FIG. 31.

FIG. 35 is a diagram showing an example of a manual input page.

FIG. 36 is a diagram showing a database relationship of the electronic delivery system according to the second embodiment of the present invention.

FIG. 37 is a flowchart for explaining a procedure process of the electronic delivery system.

FIG. 38 is a diagram for explaining the procedure processing of the electronic delivery system.

[Explanation of symbols]

1 Company A 2 Communication Network 3 ₁ Patent Office B 11 Company A Computer 12 Communication Controller 13 Processing Controller 14 Company A Database 15 Company A Terminal 31 Patent Office B Computer 32 Communication Controller 33 Processing Controller 34 Patent Office B Database 35 Terminal for Patent Office B

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Yuichi Jibiki             1-3-3 Nakamagome, Ota-ku, Tokyo Stocks             Company Ricoh (72) Inventor Katsuhiko Takahashi             2-11-1, Higashiueno, Taito-ku, Tokyo

Claims (9)

[Claims] 1. An electronic delivery system in which a requester who has submitted a document or document data to a predetermined organization in response to a request from a requester electronically delivers delivery note data to the requester, and According to the flag state changing means, the flag state changing means changes the flag state to at least requested, receipt received, delivery note in preparation, and delivery note preparation state. , The receipt data storage means for storing receipt data of the receipt indicating receipt of the document or the document data from the predetermined institution, and the flag state changing means indicating that the state of the flag is already received. When the status is indicated, the delivery note data creation start means for starting creation of delivery note data, and the flag state changing means for creating the delivery note A delivery note data creating means for creating delivery note data when the status indicates a medium state, and a delivery note data creating means when the flag state indicates that the delivery note has been created by the flag state changing means An electronic delivery system, comprising: a transmitting unit that transmits the received delivery note data to a request source. 2. The flag state changing means changes the state of the flag to a requested state when the request form data of the request form showing the request content from the request source is transmitted, and the receipt data When the receipt data is stored by the storage means, the state of the flag is changed to the receipt-acquired state, and when the delivery note data creation start means starts the production note data creation, the state of the flag is changed. 2. When the delivery note data creating means creates delivery note data, the state of the flag is changed to a state in which the delivery note has been created. Electronic delivery system described in. 3. The flag state changing means changes the state of the flag to a state in which a delivery note has been created when all the submitted document data submitted to the predetermined institution is attached to the delivery note data. The electronic delivery system according to claim 1 or 2, characterized in that. 4. The flag state changing means changes the state of the flag to a delivered state when the delivery note data is transmitted to the requester by the transmitting means, and the flag state changing means changes the flag state. The electronic delivery system according to any one of claims 1 to 3, further comprising an invoice creating unit that creates an invoice when indicates that the item has been delivered. 5. An electronic delivery method in which a requestee who has submitted a document or document data to a predetermined organization in response to a request from a requester electronically delivers the delivery note data to the requester, and the status of creation of the delivery note data According to the flag state changing step, the flag state changing step changes the flag state to at least requested, receipt accepted, delivery note in preparation, and delivery note preparation state, and the flag state has been requested by the flag state change step. , A receipt data storage step of storing receipt data of a receipt indicating receipt of a document or document data from the predetermined institution, and the flag state change step indicating that the state of the flag has already been received. When the status is indicated, the delivery note data creation start step of starting delivery note data creation and the flag state change step When the flag state indicates that the delivery note is being created, a delivery note data creating step for creating delivery note data, and when the flag state by the flag state changing step indicates a delivery note already created state, An electronic delivery method, comprising: a delivery step of transmitting the delivery note data created in the delivery note data creation step to a request source. 6. In the flag state changing step, when request data of a request form showing request contents from the request source is transmitted, the flag state is changed to a requested state, and the receipt data is changed. When the receipt data is stored in the storing step, the state of the flag is changed to a state in which the receipt has been taken in, and when the creation of the delivery note data is started in the step of starting the delivery note data creation, the state of the flag is changed. 6. When the delivery note data is created in the delivery note data creating step, the flag state is changed to a delivery note created state. Electronic delivery method described in. 7. The flag state changing step changes the state of the flag to a state in which a delivery note has been created when all the submitted document data submitted to the predetermined organization is attached to the delivery note data. The electronic delivery method according to claim 5 or 6, characterized in that. 8. In the flag state changing step, when the delivery note data is transmitted to the requester in the transmitting step, the flag state is changed to a delivered state, and the flag state changing step is performed. The electronic delivery system according to any one of claims 5 to 7, further comprising an invoice creating step of creating an invoice when indicates a delivered state. 9. A program for causing a requestee, who has submitted a document or document data to a predetermined organization in response to a request from a requester, to function as an electronic delivery system for electronically delivering delivery note data to the requester. , Flag state changing means for changing the state of the flag to at least requested, receipt accepted, delivery note in preparation, and delivery note preparation state according to the production status of the delivery note data, by the flag state change means A receipt data storage unit that stores receipt data of a receipt indicating that a document or document data is received from the predetermined institution when the flag state indicates a requested state; A delivery note data creation start means for starting creation of delivery note data when the status indicates that the receipt has been imported; Delivery note data creating means for creating delivery note data when the flag state indicates that the delivery note is being created; when the flag state indicates that the delivery note has been created by the flag state changing means A program for functioning as a sending means for sending the delivery note data created by the delivery note data creating means to a request source.