JP2007269461A - Sent article receiving service management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable management of a sent article received by a person receiving the sent article for a user and transferring it to an actual address of the user. <P>SOLUTION: In the receiving service management server 1, the actual address and a virtual address are registered regarding the respective users while making them relevant to individual discrimination information. When the virtual address and sender's name or name are inputted to an input device, information regarding the sent article is registered in a sent article list table. The user performs access to the receiving service management server 1 from an own user terminal 2 to set a transfer flag for designating transferring to himself or a cancellation flag for designating cancellation. Thereafter, the receiving service management server 1 investigates information of the sent article registered in the sent article list table, instructs transferring of the sent article corresponding to the information to a person in charge regarding the information of the sent article set with the transfer flag, and instructs mind of the sent article corresponding to the information to a person in charge regarding the information of the sent article set with the cancellation flag. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention is used for managing a service for receiving a delivery for a specific user sent to his / her address on behalf of the user and transferring the address to the user by changing the destination. It relates to a delivery receipt agent management device.

  In recent years, as the value of personal information has been recognized, there have been many incidents and disputes of misusing personal information. Therefore, the momentum of personal information protection has increased, and companies that use personal information are obliged to properly use personal information by the Personal Information Protection Law. Consciousness is not to disclose personal information to others.

  For example, the address and name of personal information have not been considered to be confidential information, but for example, through stalker damage problems, reform scam problems, and bank transfer scam problems. It has been recognized that it should not be disclosed to others. Therefore, when answering company questionnaires, applying for sweepstakes, purchasing goods through mail order, etc., there are an increasing number of citizens who want to keep their address as low as possible.

  Also, as a general rule, you cannot refuse to receive mail that reaches your home. As a result, there is a problem that even if a large number of unnecessary direct mails that are only dust are sent from a stranger, they must be received. Due to the deregulation of the postal service, since the postal service has been monopolized by private carriers, such problems can be transported not only by mail but by private carriers. This can also occur.

  In addition, since there are many carriers that carry the package, if the package cannot be received due to the absence, the carrier that carried the package is identified, and the contact person specified by the carrier There is a problem in that the procedure is troublesome because the carrier has to contact in the manner specified by the carrier. In addition, it is necessary to wait for re-delivery at home at an unconventional time period that each carrier accepts, or otherwise go to each carrier's sales office to collect multiple packages and go around There's a problem.

  An object of the present invention is to enable a user who is a recipient of a mailed item or the like to receive a package without disclosing the home address to the sender. It is to provide a delivery receipt agent management apparatus that enables a provider that provides a service to receive a package and forward it to the user's address to manage the received package according to the service.

  The delivery receipt agent management device devised to solve the above-described problem is described with a virtual address including a character string indicating the address of a specific building and identification information of a user who is a recipient. A delivery receipt agent management device used to manage a delivery sent to the building and received on behalf of the other party, and for each user, identification information and First storage means for storing the real address in association with each other, and the identification information of the user who is the sending partner included in the virtual address written in the delivery received on behalf of the agent by being operated by the operator, and its Input means for inputting delivery information comprising sender identification information; second storage means for storing the delivery information input by the input means for each delivery; and second storage means For each delivery information stored in the delivery information, an actual address corresponding to the identification information of the user included in the delivery information is read from the first storage means, and the delivery corresponding to the delivery information is stored in the actual delivery information. An instruction means for outputting an instruction to transfer to an address is provided.

  According to the present invention configured as described above, the user stores his / her own real address in the first storage means in association with his / her identification information, and sets the destination of his / her address to another person. When it is necessary to disclose, instead of disclosing its own real address, a virtual address including its own identification information and the address of the specific building may be disclosed to the other person. That is, if the other person describes this virtual address in the delivery addressed to the user, the post office worker or delivery company's delivery person looks at the address of the specific building in the virtual address and identifies this delivery address. Will be delivered to the building. For the delivery delivered to a specific building in this way, the delivery information (at least the user identification information in the virtual address, the sender identification information, etc.) by the person in charge of the service provider (operator) Is input to the input means and stored in the second storage means. Then, immediately after this storage, or at the timing of visiting at regular intervals, the user identification information in each delivery information stored in the second storage means is read out, and the user identification information is stored in correspondence with this identification information. 1. A delivery corresponding to the delivery information is sent to the real address stored in the storage means. As a result, the user does not need to disclose the actual information to others, and thus the personal information is protected. In addition, even when sent items are sent from a plurality of senders, the collected items are collected in one place, so that the user can receive the sent items in a batch.

  According to the delivery receipt agent management apparatus of the present invention configured as described above, each user does not have to tell the sender the address of the home by the user who is the recipient of the delivery such as mail. , You will be able to receive your personal delivery.

  Hereinafter, based on the drawings, a proxy receipt management server 1 which is an embodiment of a delivery receipt agency management device according to the present invention will be described. The following embodiment shows an example in which the proxy receipt management server 1 is operated by an ISP (Internet Service Provider) that provides Internet-related services.

(Virtual address)
First, the concept of “virtual address” used in the present embodiment will be described. This “virtual address” is a concept that is contrasted with a “real address” that means an address where the recipient of the package actually receives the package, and each use is as if it is in the building of the ISP that operates the proxy receipt management server 1. The address is recognized as if there is a space where the person resides or works (equivalent to a virtual address including a character string indicating the address of a specific building and identification information of the user who is the recipient). Specifically, information for identifying a virtual space dedicated to the user is added to the address of the ISP. Here, an e-mail address is used in view of the current situation where it is recognized as human identification information. A post office worker or a delivery person who saw the virtual address written in the sent article looks at the ISP address in the virtual address, and determines that the ISP building at this address is the building where the destination space exists. Recognize and throw the shipment into the outermost mailbox allowed for outsiders in the building (this mailbox may be provided for each user's email address) . Or hand over the delivery to the person in charge at the counter. Thereafter, the person in charge of the ISP inputs the part of the e-mail address in the virtual address described in the delivery received on behalf of the sender as described above to the proxy receipt management server 1 and manages this proxy receipt management. According to the instruction based on the management executed by the server 1, it is discarded or a label indicating the real address output by the proxy receipt management server 1 is attached and transferred.

(System configuration)
FIG. 1 shows a circuit configuration of a proxy receipt management server 1 according to the present embodiment, and a plurality of user terminals 2 that can access the proxy receipt management server 1 through the Internet N and make various settings and inquiries (FIG. 1). 1 is a block diagram showing only one unit in FIG.

  First, the user terminal 2 is a normal personal computer having an Internet N connection function, and includes a display 21, a CPU 22 for executing a browser program, and an input device 23.

  Next, the proxy receipt management server 1 is operated by an ISP and is actually composed of a plurality of computers connected through a LAN (not shown). In order to simplify the explanation, FIG. Is illustrated as a single computer. In other words, the proxy receipt management server 1 includes a CPU 10, a RAM 11, a display 12, an input device 13, a communication interface 14, a disk device 15, and a printer 19 that are connected to each other via a bus B.

  The CPU 10 is a processing device that reads a program and executes various processes according to the program. The RAM 11 is a main storage device that provides a work area for the CPU 10 to perform processing and control. The input device 13 is a man-machine interface operated by a person in charge of the ISP to input various commands and data to the CPU 10 (corresponding to input means). The display 12 is a display device on which an input screen is displayed or a processing result of the CPU 10 is displayed when a person in charge of the ISP performs an input operation using the input device 13. The communication interface 14 is a communication adapter that is connected to the Internet N and performs data communication according to a communication protocol such as TCP / IP (corresponding to communication means). Based on the print data generated by the CPU 10, the printer 19 prints the real address of the addressee of the delivery on the label (corresponding to the instruction means).

  The disk device 15 is a storage device such as a hard disk or an optical (magneto-optical) disk, and stores various data and various programs 16 (corresponding to first to fourth storage means).

  The program 16 stored in the disk device 15 is requested in accordance with the OS (Operating System) executed by the CPU 10 for controlling each hardware of the proxy receipt management server 1 and the HTTP request message from the user terminal 2. The CGI program executes the processed processing and responds to the result, or the WWW server program that reads the requested Web content from the disk device 15 and responds, and the data processing for the proxy reception service together with the OS and the WWW server. Application programs such as various CGI programs to be executed by the CPU 10 are included.

  The various data stored in the disk device 15 includes a user database 17 and other table groups 18.

  FIG. 2 is a table showing the data structure of the user database 17. As shown in FIG. 2, the user database 17 is provided for each user who has concluded a service supply contract (for example, Internet connection service, paid content providing service, etc.) with the ISP operating the proxy receipt management server 1. In addition, a record in which the user information is registered is held. Each record is included in a “user ID” field in which the ID of the corresponding user is described, a “user password” field in which a password combined with the ID is described, and a virtual address of the user. "Virtual address" field in which an e-mail address (user identification information) is described, and when setting to notify the fact using e-mail when the delivery addressed to the virtual address is received by proxy A “notification mail flag” field in which a flag is set, a “name” field in which the name of the user is described, a “real address” field in which the real address of the user is described, and between the user and the ISP "Card number" field that describes the card number of the credit card specified for use in the settlement of service supply contracts From the "email address" field of e-mail address of the user is described, it is configured. The portion storing the user database 17 in the disk device 15 corresponds to first storage means for storing the identification information and the real address in association with each other for each user.

  As the other table group 18, in this embodiment, a delivery list table, a white list sender table, a white list condition table, a SPAM list sender table, and a SPAM list condition table are prepared.

  The sent item list table is a master for managing the sent items sent to the ISP building and received on behalf of the ISP because the virtual address is described. The virtual address flag is set in the user database 17. It is prepared for each user. FIG. 3 is a table showing the data structure of the delivery list table. As shown in FIG. 3, the number of deliveries (number of deliveries) registered in the delivery list table is registered in the header portion of the delivery list table. Further, the main body of the delivery list table is composed of a plurality of columns for registering delivery information for each delivery. That is, each column describes a “code” field in which a serial number for uniquely identifying a shipment registered in the column is described, and the name or name (sender identification information) of the sender of the shipment. “Sender” field, flag “1” indicating that the delivery should be sent to the original destination (transfer flag specifying that the delivery should be transferred to the user who is the recipient), and discarding Flag “−1” (discard flag designating that the shipment should be discarded) or “flag” field in which “0” indicating pending is set, the type of the shipment (ie, “ "Postcard", "Seal" or "Parcel"), and a "virtual address" field describing the virtual address as the destination of the shipment Has been . The part storing the delivery list table in the disk device 15 corresponds to second storage means for storing delivery information of each delivery (in a format in which a transfer flag or a discard flag can be set).

  The white list sender table is a sender (white list sender) that, as a general rule, will send a mail sent from it to the original destination regardless of the flag value registered in the mail list table. Is a table in which the name of the sender (identification information of the sender to be collectively transferred to the user) is registered in advance, and is prepared for each user for which the virtual address flag is set in the user database 17. . FIG. 4 is a table showing the data structure of the white list sender table. As shown in FIG. 4, the number of senders registered in the white list sender table is registered in the header portion of the white list sender table. The main body of the white list sender table is composed of a plurality of columns for registering individual white list senders. That is, each column describes a “white list sender” field in which a sender number for uniquely identifying a white sender registered in the column is described, and the name or name (sender identification information) of the white list sender. The “name” field is configured. The portion of the disk device 15 that stores the white list sender table corresponds to third storage means in which the identification information of the sender of the items to be collectively transferred to the user is registered in advance for each user.

  The white list condition table is a table that defines in detail the conditions for sending a delivery to the original user of each white list sender registered in the white list sender table (FIG. 4). It is prepared for each user whose virtual address flag is set in the database 17. FIG. 5 is a table showing the data structure of the white list condition table. As shown in FIG. 5, the main body of the white list condition table is composed of a plurality of columns for registering individual white list senders. That is, each column has a “white list sender” field in which a sender number for uniquely identifying a white sender registered in the column is described, and when the type of a delivery from the white sender is a postcard, Character string (type information) “0x00f0” which means that it should be sent to the sender, and character string (type information) “0x00f0” which means that it should be sent to the original sender when the type of the shipment is sealed , Character string (type information) “0x0f00” which means that it should be sent to the original sender when the type of delivery is a parcel, and to be sent to the original sender when the type of delivery is other "0xf000", a character string that means, and a "condition" field that contains a character string "0" that means that it should be sent to the original sender (no condition) regardless of the type of delivery Is composed of ing. The combination of the white list sender table and the white list condition table corresponds to the third storage means in which the combination conditions of the sender identification information and the type information regarding the delivery to be transferred to the user for each user are registered in advance. To do.

  Regardless of the value of the flag registered in the delivery list table, the SPAM sender table is basically a sender (SPAM) that will be discarded without sending it to the original destination. This is a table in which the name of the sender) (identification information of the sender of the delivery to be discarded) is registered, and is prepared for each user whose virtual address flag is set in the user database 17. FIG. 6 is a table showing the data structure of the SPAM sender table. As shown in FIG. 6, the number of senders registered in the SPAM sender table is registered in the header portion of the SPAM sender table. The main body of the SPAM sender table is composed of a plurality of columns for registering individual SPAM senders. That is, each column describes a “SPAM sender” field in which a sender number for uniquely identifying a SPAM sender registered in the column, and a name or name (sender identification information) of the SPAM sender are described. It consists of a “name” field. The part storing the SPAM sender table in the disk device 15 corresponds to the fourth storage means in which the sender identification information of the items to be discarded for each user is registered in advance.

  The SPAM condition table is a table that defines in detail the conditions for discarding a delivery for each SPAM sender registered in the SPAM sender table (FIG. 6), and a virtual address flag is set in the user database 17. It is prepared for each user. FIG. 7 is a table showing the data structure of the SPAM condition table. As shown in FIG. 7, the main body of the SPAM condition table is composed of a plurality of columns for registering individual SPAM senders. That is, each column is discarded when the type of the delivery from the SPAM sender is a “SPAM sender” field in which the sender number for uniquely identifying the SPAM sender registered in the column is described. A character string (type information) “0x000f” that means something to be done, a character string (type information) “0x00f0” that means to be discarded when the type of the shipment is a sealed letter, and the type of the shipment is a parcel Character string (type information) "0x0f00" meaning that should be discarded in case of the case, character string (type information) "0xf000" meaning that it should be discarded if the type of the shipment is any other It consists of a “condition” field in which a character string “0” is written, which means that it should be discarded regardless of conditions (no condition). The combination of the SPAM sender table and the SPAM condition table corresponds to a fourth storage unit in which the combination conditions of the sender identification information and type information for the delivery to be discarded for each user are registered in advance.

(processing)
Next, processing executed by the CPU 10 of the proxy receipt management server 1 according to the program 16 will be described based on the flowcharts of FIGS. 8 to 14 and the screen examples of FIGS. 15 to 34.

  First, a setting process executed for a user who has signed a contract for providing various services with an ISP to receive a proxy receipt service will be described with reference to FIG. This setting process is triggered by the reception of an HTTP request message designating the URL of the setting screen from any user terminal 2.

  After the start, in the first S001, the CPU 10 displays the setting screen shown in FIG. 15 on the display 21 of the user terminal 2 (transmits HTML data for displaying the setting screen to the user terminal 2). This setting screen includes a “Register” button 30, and in the HTML data for displaying this, when the “Register” button 30 is operated, a message to that effect is sent to the proxy receipt management server 1. The setting to send to is incorporated.

  The proxy receipt management server 1 waits for the message to be received in S002, terminates the setting process when timed out without receiving, and executes the authentication process in S003 when the message is received before the time-out. That is, the CPU 10 displays an authentication screen including an ID entry field 31, a password entry field 32, and a “Next” button 33 on the display 21 of the user terminal 2 as shown in FIG. In the HTML data for displaying the authentication screen, when the “next” button 33 is operated, the character strings written in the ID entry field 31 and the password entry field 32 are respectively displayed to the browser. A setting to be transmitted to the proxy receipt management server 1 as a password is incorporated. Upon receipt of this message, the proxy receipt management server 1 checks whether the combination of ID and password in the received message is registered in the user database 17 on the hard disk 15, and if not registered, this setting process is performed. finish. On the other hand, if the combination of the ID and password is registered in the user database 17, it is determined that the authentication is successful, and the process proceeds to S004.

  In S <b> 004, the CPU 10 displays the virtual address registration screen shown in FIG. 17 on the display 21 of the user terminal 2. In this virtual address registration screen, the real address and e-mail address described in the record including the ID authenticated in S003 in the user database 17 are described, respectively, and the “change address” button 34 and “ A “register” button 35 is included. In the HTML data for displaying the virtual address registration screen, a setting to make the displayed address rewritable when the “change address” button 34 is operated, and a “register” button When 35 is operated, a setting for transmitting a message (including a rewritten address) to register a virtual address to the proxy receipt management server 1 is incorporated.

  The proxy receipt management server 1 waits for the message to be received in S005, terminates the setting process when timed out without receiving, and receives the message before the time-out, and in S006, the address after rewriting in the message Only when the real address in the user database 17 corresponding to the ID authenticated in S003 is changed with the address after rewriting, the process proceeds to S007.

  In S007, the proxy receipt management server 1 sets the virtual address flag to “1” in the record including the ID authenticated in S003 in the user database 17, and sets the ISP address and the mail address in the record. A virtual address is generated by combining, and this virtual address is written in the “virtual address” field of the record.

  In next S 008, the proxy receipt management server 1 displays the notification mail setting screen shown in FIG. 18 on the display 21 of the user terminal 2. In the notification mail setting screen, a “set” button 36 that is operated when a setting is made to notify by e-mail when the ISP receives a delivery, and “not set” that is operated when the setting is not performed. A button 37 is included. The HTML data for displaying the notification mail setting screen incorporates a setting for sending a message including a parameter corresponding to the button 36, 37 to the proxy receipt management server 1 when each button 36, 37 is operated. ing.

  The proxy receipt management server 1 waits for the reception of the message in the next S009, and if the message includes a parameter corresponding to the “set” button 36, the proxy reception management server 1 is authenticated in S003 in S010. If the notification mail flag in the record including the ID is set to “1” and the parameter corresponding to the “not set” button 37 is not included in the message, the ID authenticated in S003 in S011 The notification mail flag in the record including “” is reset to “0”. In any case, the proxy receipt management server 1 proceeds with the process to S012.

  In S012, the proxy receipt management server 1 displays the white list setting screen shown in FIG. 19 on the display 21 of the user terminal 2. In this white list setting screen, the information of each white list sender registered in the white list sender table (FIG. 4) and the white list condition table (FIG. 5) is listed and the white list sender information is newly added. And a list 38 that can delete or change information of an existing white list sender, a “register” button 39 and a “cancel” button 40 are included. This list 38 can be scrolled infinitely in the vertical direction, and each row corresponds to an individual white list sender, and each column is in order from the left side, the sender number, name or name, and condition of the white list sender. It corresponds. The HTML data for displaying the white list setting screen includes a setting for transmitting a message including the contents described in the list 38 to the proxy receipt management server 1 when the “registration” button 39 is operated, and When the “Cancel” button 40 is operated, a setting for sending a message to that effect to the proxy receipt management server 1 is incorporated.

  The proxy receipt management server 1 waits for the reception of the message in the next S013, and when the message is received, advances the processing to S014.

  In S014, the proxy receipt management server 1 advances the process to S015 as it is when the received message includes a message indicating that the “Cancel” button 40 has been operated. On the other hand, when the contents of the list 38 (white list setting information) are included in the received message, the white list sender table (FIG. 4) and the white list condition table (FIG. 5) are changed according to the contents. Update. In other words, if the existing whitelist sender information is deleted or changed in the list 38, the proxy receipt management server 1 deletes or changes the whitelist sender information from these tables (FIGS. 4 and 5). If new white list sender information is added to the list 38, the new white list sender information is added to these tables (FIGS. 4 and 5). Thereafter, the proxy receipt management server 1 advances the process to S015.

  In next S015, the proxy receipt management server 1 displays the SPAM setting screen shown in FIG. 20 on the display 21 of the user terminal 2. In this SPAM setting screen, information on each SPAM sender currently registered in the SPAM sender table (FIG. 6) and SPAM condition table (FIG. 7) is enumerated, and SPAM sender information is newly added or existing information is added. A list 41 on which the SPAM sender information can be deleted or changed, a “Register” button 42 and a “Cancel” button 43 are included. The list 41 can be scrolled infinitely in the vertical direction, and each row corresponds to an individual SPAM sender, and each column corresponds to the sender number, name or name, and condition of the SPAM sender in order from the left side. ing. The HTML data for displaying the SPAM setting screen includes a setting for transmitting a message including the contents described in the list 41 to the proxy receipt management server 1 when the “registration” button 42 is operated, and When the “Cancel” button 43 is operated, a setting for sending a message to that effect to the proxy receipt management server 1 is incorporated.

  The proxy receipt management server 1 waits for the reception of the message in the next S016, and proceeds to S017 when receiving the message.

  In S017, the proxy receipt management server 1 advances the process to S018 as it is when the received message includes the fact that the “Cancel” button 43 has been operated. On the other hand, if the contents of the list 41 are included in the received message, the SPAM sender table (FIG. 6) and the SPAM condition table (FIG. 7) are updated with the contents. That is, if the existing SPAM sender information is deleted or changed in the list 41, the proxy receipt management server 1 deletes or changes the SPAM sender information from these tables (FIGS. 6 and 7). When new SPAM sender information is added in the list 41, the new SPAM sender information is added to these tables (FIGS. 6 and 7). Thereafter, the proxy receipt management server 1 advances the process to S018.

  In S018, the proxy receipt management server 1 displays an end screen shown in FIG. 21 on the display 21 of the user terminal 2. Thereafter, the user terminal 2 ends this setting process.

  Next, when the person in charge of the ISP receives a delivery with any virtual address registered in the user database 17 from a post office worker or a delivery company's delivery agent, the input device 13 is used. A delivery receipt process executed by inputting a predetermined command will be described with reference to FIG.

  In first S101 after the start of the delivery receipt process, the proxy receipt management server 1 displays the input screen shown in FIG. On this input screen, a sender name text box 44 for writing the sender name written in the delivery received on behalf of the agent, a virtual address text box 45 for writing a virtual address written as a destination on the delivery, and the sending A pull-down list box 46 for selecting the type of the item from postcards, parcels, sealed letters, and the like, and a “Register” button 47 are included.

  In next step S102, the proxy receipt management server 1 waits for the “registration” button 47 to be operated in a state where character strings are set in the respective columns 44 to 46. When the “registration” button 47 is operated in a state where character strings are set in the respective columns 44 to 46, the proxy receipt management server 1 sends the sender name, Accepted as virtual information and input as type (corresponds to input means). In S103, a code is issued for the delivery. At this time, the proxy receipt management server 1 may print out from the printer 19 a label indicating the code as a barcode. In that case, the person in charge affixes the printed label on the surface of the received delivery. In this way, the person in charge can easily find the delivery from the warehouse even if the delivery is to be transferred or discarded in a later procedure.

  In the next step S104, the proxy receipt management server 1 uses the sender name, virtual address, type and the code issued in step S103 input in step S102 as the delivery information in the delivery list table (FIG. 3). ). At this time, “0” indicating suspension is initially set in the “flag” field. After completion of S104, the proxy receipt management server 1 completes this delivery receipt process.

  Next, a mail notification process is performed to search for information on the newly registered delivery in the delivery list table (FIG. 3) and to notify the user who is the destination of the new delivery by e-mail. This will be described with reference to FIG.

  This mail notification process starts periodically. Then, in the first step S201 after the start, the proxy receipt management server 1 newly displays in the delivery list table (FIG. 3) whether or not there is a delivery that has arrived after the previous mail notification processing. The check is made based on whether or not the delivery information is registered. When there is no newly arrived delivery (when no delivery information is newly registered), the proxy receipt management server 1 ends the mail notification process. On the other hand, when there is a newly arrived delivery (when delivery information is newly registered), the proxy receipt management server 1 executes a loop process of S202 to S205.

  In the first step S202 after entering this loop process, the proxy receipt management server 1 specifies one new delivery information from the delivery list table (FIG. 3).

  In the next S203, the proxy receipt management server 1 checks the notification mail flag included in the delivery information specified in S202. If the notification mail flag is set to “1”, the proxy receipt management server 1 searches the user database 17 for a mail address corresponding to the virtual address in the information of the delivery in S204, A mail arrival notification mail is transmitted to the mail address (corresponding to an electronic mail transmitting means). FIG. 23 shows a screen image when the mail arrival notification mail is opened. As shown in FIG. 23, in the delivery arrival notification mail, a URL link 48 (contents of delivery information including the identification information of the user concerned) is displayed in a list corresponding to a later-described delivery disposal process (CGI). Link information to screen data to be executed). When S204 is completed, the proxy receipt management server 1 advances the process to S205.

  On the other hand, if the notification mail flag included in the information of the delivery specified in S202 is “0”, the proxy receipt management server 1 advances the process to S205 as it is.

  In S205, the proxy receipt management server 1 checks whether or not the processing from S202 onward has been executed for the information of all new deliverables in the delivery list table (FIG. 3). Then, if all the new delivery information in the delivery list table (FIG. 3) has not yet been completed, the proxy receipt management server 1 returns the process to S202. On the other hand, when the processing from S202 onward is completed for all new delivery information in the delivery list table (FIG. 3), the proxy receipt management server 1 ends this mail notification process. .

  Next, for each delivery registered in the delivery list table (FIG. 3), a disposal processing for instructing disposal or transfer to the destination user for the person in charge of the ISP is shown in FIG. This will be described with reference to FIG.

  In this sending waste disposal process, when the user who has received the sending arrival notification mail operates the URL link 48 in the mail, the user operates the input device 23 of his / her user terminal 2. Thus, the process starts from S301 with the reception of the message (request) transmitted from the user terminal 1 as a trigger. In addition, it automatically starts from S304 by an interrupt that occurs periodically.

  In S304, the proxy receipt management server 1 executes an authentication process. That is, the CPU 10 displays an authentication screen including an ID entry field 49, a password entry field 50, and a “Next” button 51 on the display 21 of the user terminal 2 as shown in FIG. In the HTML data for displaying the authentication screen, when the “next” button 51 is operated, the character strings written in the ID entry field 49 and the password entry field 50 are respectively displayed to the browser. A setting to be transmitted to the proxy receipt management server 1 as a password is incorporated. Upon receiving this message, the proxy receipt management server 1 checks whether the combination of ID and password in the received message is registered in the user database 17 on the hard disk 15, and if not registered, the process is interrupted. . On the other hand, if the combination of the ID and password is registered in the user database 17, the process proceeds to S302 on the assumption that the authentication is successful.

  In S302, the proxy receipt management server 1 generates HTML data for displaying the delivery list screen shown in FIG. 25 (screen data for displaying the contents of the delivery information including the user identification information), This HTML data is transmitted to the requesting user terminal 2, and a delivery list screen is displayed on the display 21 (corresponding to list response means). This delivery list screen is a list that lists the senders and types of all delivery items addressed to the user authenticated in S301. That is, the proxy receipt management server 1 reads out from the user table 17 the virtual address (that is, the virtual address of the requesting user) corresponding to the ID authenticated in S301. Then, the delivery list table (FIG. 3) is searched using this virtual address as a search key, and the sender name and type described in each column including the virtual address are called. Then, the combination of the read sender and type is incorporated into the HTML data so as to be listed. The sent item list screen further includes a plurality of “ship button” 52, “white” button 53, “SPAM” 54, and “discard” button 55 corresponding to the information (sender and type) of each sent item. In addition, a “white list setting” button 57, a “SPAM setting” button 58 and an “end” button 59 are included. Further, in the HTML data for displaying the delivery list screen, when each button 52 to 55 is operated, the type of the operated button 52 to 55 and the delivery associated with the button are displayed. Settings for sending a message including parameters to the proxy receipt management server 1 (link information for sending a request for setting a transfer flag to the delivery information for each delivery, and for each delivery. If the “white list setting” button 57, “SPAM setting” button 58 and “end” button 59 are operated, the operation is performed. The setting including transmitting a message including a parameter indicating the type of the buttons 57 and 58 to the proxy receipt management server 1 is included.

  In step S303, the proxy receipt management server 1 that has received one of the messages cooperates with the message transmission source user terminal 2 (the CPU 22 that executes the browser) to execute a delivery disposal information acquisition process. That is, when any “ship” button 52 is operated, the proxy receipt management server 1 displays the shipping screen shown in FIG. 26 on the display 21 of the user terminal 2. This shipping screen includes a “ship” button 60. When the “ship” button 60 is operated, the proxy receipt management server 1 displays the shipping list screen (FIG. 25). The “flag” field in the column in the delivery list table (FIG. 3) including the delivery code (parameter in the message) corresponding to the operated “ship” button 52 is set to “1” (flag 27), a completion screen shown in FIG. 27 is displayed on the display 21 of the user terminal 2. This completion screen includes a “return to list” button 61. When this “return to list” button 61 is operated, the delivery list screen shown in FIG. 25 is displayed on the display of the user terminal 2. 21 is displayed again.

  In addition, when any “discard” button 55 is operated on the delivery list screen, the proxy receipt management server 1 displays the discard screen shown in FIG. 28 on the display 21 of the user terminal 2. This shipping screen includes a “discard” button 62. When this “discard” button 62 is operated, the proxy receipt management server 1 displays the dispatch list on the shipment list screen (FIG. 25). The “flag” field in the column in the delivery list table (FIG. 3) including the code (parameter in the message) of the delivery corresponding to the operated “discard” button 55 is set to “−1” ( 29), a completion screen shown in FIG. 29 is displayed on the display 21 of the user terminal 2. This completion screen includes a “return to list” button 63. When this “return to list” button 63 is operated, the proxy receipt management server 1 displays the delivery list screen shown in FIG. Is redisplayed on the display 21 of the user terminal 2.

  Further, when any “white” button 53 is operated on the delivery list screen, the proxy receipt management server 1 displays the white list setting screen shown in FIG. 30 on the display 21 of the user terminal 2. . This white screen setting screen displays each condition (parcel, envelope, letter, etc.) in the white list condition table (FIG. 5) for the sender of the delivery corresponding to the “white” button 53 operated on the delivery list screen (FIG. 25). Four check boxes 62 for selecting whether or not to register postcards and others) and a “set” button 63 are included. When the “set” button 63 is operated, the proxy receipt management server 1 sends a unique transmission for the name or name if the sender is not registered in the white list sender table (FIG. 4). A person number is assigned, and the name or famous place and the sender number are associated with each other and registered in the white list sender table (FIG. 4). In addition, the type of the shipment corresponding to the check box 62 checked at that time is registered in the white list condition table (FIG. 5) in association with the sender number associated with the name or name of the sender. To do. If none of the check boxes 62 are checked, the proxy receipt management server 1 makes the white list sender unconditional in order to unconditionally transfer the shipment due to being a white list sender. In addition to registering in the table (FIG. 4), the character string “0” indicating unconditional is registered in the whitelist condition table (FIG. 5) in association with the sender number associated with the name or name of the sender. To do. Thereafter, the proxy receipt management server 1 displays a completion screen shown in FIG. 31 on the display 21 of the user terminal 2. This completion screen includes a “return to list” button 64. When this “return to list” button 64 is operated, the proxy receipt management server 1 sends a delivery list screen shown in FIG. Is redisplayed on the display 21 of the user terminal 2.

  When any “SPAM” button 54 is operated on the delivery list screen, the proxy receipt management server 1 displays a SPAM setting screen shown in FIG. 32 on the display 21 of the user terminal 2. In the SPAM setting screen, for each sender of the delivery corresponding to the “SPAM” button 54 operated on the delivery list screen (FIG. 25), each condition (parcel, sealed letter, postcard, Four check boxes 65 for selecting whether or not to register “others” and a “set” button 66 are included. When the “set” button 66 is operated, the proxy receipt management server 1 determines that the sender is unique to the name or name unless the sender is registered in the SPAM sender table (FIG. 6). Numbers are assigned, and these names or sights and sender numbers are associated with each other and registered in the SPAM sender table (FIG. 6). Further, the type of the delivery corresponding to the check box 65 checked at that time is registered in the SPAM condition table (FIG. 7) in association with the sender number associated with the name or name of the sender. . If none of the check boxes 65 are checked, the proxy receipt management server 1 makes the SPAM sender table (in order to unconditionally discard the delivery due to being a SPAM sender). In addition to registration in FIG. 6), the character string “0” indicating uncondition is registered in the SPAM condition table (FIG. 7) in association with the sender number associated with the name or name of the sender. Thereafter, the proxy receipt management server 1 displays a completion screen shown in FIG. 33 on the display 21 of the user terminal 2. This completion screen includes a “return to list” button 67. When this “return to list” button 67 is operated, the proxy receipt management server 1 sends a delivery list screen shown in FIG. Is redisplayed on the display 21 of the user terminal 2.

  When the “white list setting” button 57 is operated on the delivery list screen, the proxy receipt management server 1 displays the white list batch setting screen shown in FIG. 34 on the display 21 of the user terminal 2. . The white list batch setting screen includes a deletion check box 68 and a white list that are checked to exclude each sender listed on the delivery list screen from being registered in the white list sender table (FIG. 4). Four condition check boxes 69 for selecting whether to register each condition (parcel, sealed letter, postcard, etc.) in the condition table (FIG. 5), a “change setting” button 70 and a “return” button 71 is included. When the “return” button 71 is operated, the proxy receipt management server 1 displays the delivery list screen shown in FIG. 25 on the user terminal 2 without updating each table (FIGS. 4 and 5). Are redisplayed on the display 21. On the other hand, when the “change setting” button 70 is operated, the proxy receipt management server 1 sends information on the sender whose deletion check box 68 is checked from the whitelist sender table (FIG. 4). Are deleted, and a column including the same sender number as the deleted column is deleted from the white list condition table (FIG. 5). For a sender whose deletion check box 68 is not checked, if the information is registered in the white list sender table (FIG. 4), the sender number in the information in the white list condition table (FIG. 5) is displayed. The condition in the record to be included is changed according to whether or not each condition check box 69 is checked. If the information is not registered in the white list sender table (FIG. 4), the sender number is assigned to the sender, and the name or name of the sender and the sender number are associated with each other and the white list sender is associated. While registering in the table (FIG. 4), the sender number and the conditions corresponding to the checked condition check boxes 69 are associated with each other and registered in the white list condition table (FIG. 5). Thereafter, the proxy receipt management server 1 displays a completion screen shown in FIG. 35 on the display 21 of the user terminal 2. This completion screen lists the senders registered in the respective updated tables (FIGS. 4 and 5) and the conditions for the batch transfer, and includes a “return” button 72. When the “return” button 72 is operated, the proxy receipt management server 1 redisplays the delivery list screen shown in FIG. 25 on the display 21 of the user terminal 2.

  When the “SPAM setting” button 58 is operated on the delivery list screen, the proxy receipt management server 1 displays the SPAM collective setting screen shown in FIG. 36 on the display 21 of the user terminal 2. In this SPAM collective setting screen, each of the senders listed on the delivery list screen (FIG. 25) is deleted check boxes 73, which are checked to exclude them from being registered in the SPAM sender table (FIG. 6). Four condition check boxes 74 for selecting whether to register each condition (parcel, sealed letter, postcard, etc.) in the SPAM condition table (FIG. 7), a “change setting” button 75, and “return” A button 76 is included. When the “return” button 76 is operated, the proxy receipt management server 1 displays the delivery list screen shown in FIG. 25 on the user terminal 2 without updating each table (FIGS. 6 and 7). Are redisplayed on the display 21. On the other hand, when the “change setting” button 75 is operated, the proxy receipt management server 1 stores information on the sender whose deletion check box 73 is checked from the SPAM sender table (FIG. 6). The registered column is deleted, and a column including the same sender number as the deleted column is deleted from the SPAM condition table (FIG. 7). For a sender whose deletion check box 73 is not checked, if the information is registered in the SPAM sender table (FIG. 6), a record including the sender number in the information in the SPAM condition table (FIG. 7). The inside condition is changed according to whether or not each condition check box 49 is checked. If the information is not registered in the SPAM sender table (FIG. 6), the sender number is assigned to the sender, and the name or name of the sender and the sender number are associated with each other in the SPAM sender table ( 6), the sender number and the conditions corresponding to the checked condition check boxes 74 are associated with each other and registered in the SPAM condition table (FIG. 7). Thereafter, the proxy receipt management server 1 displays a completion screen shown in FIG. 37 on the display 21 of the user terminal 2. This completion screen lists the senders registered in the updated tables (FIGS. 6 and 7) and their batch disposal conditions, and includes a “return” button 77. When the “return” button 77 is operated, the proxy receipt management server 1 redisplays the delivery list screen shown in FIG. 25 on the display 21 of the user terminal 2.

  On the other hand, when the “end” button 59 is operated on the delivery list screen, the proxy receipt management server 1 ends the delivery disposal information acquisition process and advances the process to S304.

  In S304, the proxy receipt management server 1 checks whether or not one or more sender information is registered in the white list sender table (FIG. 4). If no sender information is registered, the proxy receipt management server 1 advances the process to S311. On the other hand, when the information of one or more senders is registered, the loop processing from S305 to S310 is executed.

  In the first step S305 after entering this loop process, the proxy receipt management server 1 identifies one delivery from the delivery list table (FIG. 3).

  In next step S306, the proxy receipt management server 1 checks whether or not the sender of the delivery registered in the delivery list table (FIG. 3) is registered in the white list sender table (FIG. 4). . If it is not registered, the proxy receipt management server 1 advances the process to S310. Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 advances the process to S310 as it is.

  On the other hand, if the sender of the delivery is registered in the white list sender table (FIG. 4), the proxy receipt management server 1 is registered in the delivery list table (FIG. 3) in S307. The type of the sent item matches with any of the conditions registered in the white list condition table (FIG. 5) corresponding to the sender number of the sender of the sent item, or the condition is unconditional. Check whether or not. If the type of the delivery does not match any of the conditions registered in the white list condition table (FIG. 5) corresponding to the sender number of the sender of the delivery, the proxy receipt management server 1 advances the process to S310 as it is.

  On the other hand, in the case where the type of the delivery matches or is unconditional with any of the conditions registered in the white list condition table (FIG. 5) corresponding to the sender number of the sender of the delivery. In S308, the proxy receipt management server 1 displays the real address, name and code registered in the user database 17 corresponding to the virtual address of the delivery registered in the delivery list table (FIG. 3). The printer 19 causes the printer to print out the destination label, and notifies the person in charge of an instruction to transfer the delivery to the real address of the destination user (corresponding to an instruction unit). This notification is performed, for example, by transmitting a message or an electronic mail to a terminal dedicated to the person in charge. Upon receiving the notification, the person in charge searches for the actual delivery using the code printed on the destination label and attaches the destination label to the delivery. In order to simplify this work, for example, it is conceivable to configure the system as follows.

  That is, a handy POS terminal having a communication function, a barcode reader, and a printer is prepared, and print data is transmitted to the handy POS terminal in S308. Then, the print data received by the handy POS terminal is stored in association with the code, and the person in charge uses the bar-coded code pasted on the surface of the package stored in the warehouse as the handy POS terminal. When the print data corresponding to the code is stored in the POS terminal, the print data is printed on a label by the printer. Then, the person in charge affixes the printed / output label on the surface of the delivery and sends it out.

  After completion of S308, the proxy receipt management server 1 advances the process to S309.

  In S309, the proxy receipt management server 1 deletes the delivery information of the delivery from the delivery list table (FIG. 3). After completion of S309, the proxy receipt management server 1 advances the process to S310.

  In S310, the proxy receipt management server 1 checks whether or not the processing of S306 and subsequent steps has been executed for all the shipments whose information is registered in the delivery list table (FIG. 3). If the processing has not yet been completed for all the deliverables, the proxy receipt management server 1 returns the processing to S305 in order to execute the process for the next deliverable.

  On the other hand, if it is determined in S310 that the processing for all the shipments registered in the delivery list table (FIG. 3) has been completed, the proxy receipt management server 1 advances the processing to S311. . Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 advances the processing to S311 as it is.

  In S311, the proxy receipt management server 1 checks whether or not one or more sender information is registered in the SPAM sender table (FIG. 6). If no sender information is registered, the proxy receipt management server 1 advances the process to S318. On the other hand, when the information of one or more senders is registered, the loop processing from S312 to S317 is executed.

  In the first step S312 after entering this loop process, the proxy receipt management server 1 identifies one delivery from the delivery list table (FIG. 3).

  In next step S313, the proxy receipt management server 1 checks whether or not the sender of the delivery registered in the delivery list table (FIG. 3) is registered in the SPAM sender table (FIG. 6). If it is not registered, the proxy receipt management server 1 advances the process to S317 as it is. Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 advances the process to S317 as it is.

  On the other hand, when the sender of the delivery is registered in the SPAM sender table (FIG. 6), the proxy receipt management server 1 is registered in the delivery list table (FIG. 3) in S314. Whether the type of the delivery matches the condition registered in the SPAM condition table (FIG. 7) corresponding to the sender number of the sender of the delivery, or whether the condition is unconditional To check. If the type of the delivery does not match any of the conditions registered in the SPAM condition table (FIG. 7) corresponding to the sender number of the sender of the delivery, the proxy receipt management server 1 Advances the process to S317 as it is.

  On the other hand, in the case where the type of the delivery matches or is unconditional with any of the conditions registered in the SPAM condition table (FIG. 7) corresponding to the sender number of the sender of the delivery. In S315, the proxy receipt management server 1 notifies the person in charge of an instruction to discard the delivery (corresponding to an instruction unit). This notification is performed, for example, by transmitting a message or an electronic mail to a terminal dedicated to the person in charge. Upon receiving the notification, the person in charge searches for the actual delivery using the code printed on the destination label, and discards the delivery. After completion of S315, the proxy receipt management server 1 advances the process to S316.

  In S316, the proxy receipt management server 1 deletes the delivery information of the delivery from the delivery list table (FIG. 3). After completion of S316, the proxy receipt management server 1 advances the process to S317.

  In S317, the proxy receipt management server 1 checks whether or not the processing in S312 and subsequent steps has been executed for all the shipments whose information is registered in the delivery list table (FIG. 3). If the processing has not yet been completed for all the deliverables, the proxy receipt management server 1 returns the processing to S312 in order to execute the process for the next deliverable.

  On the other hand, if it is determined in S317 that the processing for all the shipments registered in the delivery list table (FIG. 3) has been completed, the proxy receipt management server 1 advances the processing to S318. . Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 advances the process to S318 as it is.

  Steps S318 to S323 are loop processes for individually determining transfer or discard of each shipment according to the flag value registered for each shipment on the shipment list table (FIG. 3).

  In S318, the proxy receipt management server 1 identifies one delivery from the delivery list table (FIG. 3).

  In next S319, the proxy receipt management server 1 checks whether or not the value of the “flag” field for the delivery registered in the delivery list table (FIG. 3) is “−1”. If it is “−1”, the proxy receipt management server 1 notifies the person in charge of an instruction to discard the delivery in S324 as in the case of S315 (instruction) Equivalent to means).

  In next step 325, the proxy receipt management server 1 deletes the delivery information of the delivery from the delivery list table (FIG. 3). After completion of S316, the proxy receipt management server 1 advances the process to S323.

  On the other hand, when it is determined in S319 that the value of the “flag” field for the delivery is not “−1”, the proxy receipt management server 1 advances the process to S320. Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 advances the process to S320 as it is.

  In S320, the proxy receipt management server 1 checks whether or not the value of the “flag” field for the delivery registered in the delivery list table (FIG. 3) is “1”. If it is “1”, the proxy receipt management server 1 notifies the person in charge in S321 that the delivery should be discarded as in S308 (instruction means). Equivalent).

  In next step S322, the proxy receipt management server 1 deletes the information of the delivery from the delivery list table (FIG. 3). After completion of S322, the proxy receipt management server 1 advances the process to S323.

  In S323, the proxy receipt management server 1 checks whether or not the processing from S318 onward has been executed for all the items for which information is registered in the item list (FIG. 3). If the processing for all the sent items has not been completed, the proxy receipt management server 1 returns the processing to S318 in order to execute the process for the next sent item.

  On the other hand, if it is determined in S323 that the processing for all the shipments registered in the delivery list table (FIG. 3) has been completed, the proxy receipt management server 1 performs this delivery disposal processing. Exit. Even when the delivery information is not registered in the delivery list table (FIG. 3), the proxy receipt management server 1 ends the delivery disposal process.

(Operation)
The operation of the present embodiment configured as described above will be described with reference to FIG. According to the present embodiment, when a user who has concluded a service supply contract with an ISP operating the proxy receipt management server 1 intends to use the proxy reception service provided by the proxy receipt management server 1 Then, the proxy reception management server 1 is caused to execute the setting process of FIG. 8 by inputting the URL of the setting screen into the browser of its own user terminal 2. Then, the virtual address is set in the user database 17 together with the virtual address flag (S007). Further, when a notification is received by mail every time a new delivery is received by the ISP, a notification mail flag is set in the user database 17 (S011).

  Furthermore, if necessary, users who have a high degree of credibility who do not send unneeded deliverables to the whitelist sender table (FIG. 4) can be transferred to themselves in a batch. The name or name of the sender can be registered (S014). At this time, all the items sent from the sender registered in the white list sender table (Fig. 4) are transferred to the user in principle. It is possible to select and set whether to transfer or determine whether to transfer or discard individually without requesting batch transfer. That is, when the user desires batch transfer of only some types of shipments, the types of shipments that are desired to be batch transferred in association with the name or name of the sender on the white list setting screen (FIG. 19). By designating, the type of the designated delivery item is registered as a condition in the white condition table (FIG. 5).

  In addition, the user, if necessary, sends low-quality senders that send only unnecessary deliverables to the SPAM sender table (FIG. 6) so as to refuse receipt at once and have the ISP discard them. The name or name of the sender can be registered (S017). At this time, in principle, all the items sent from the sender registered in the SPAM sender table (FIG. 6) will be discarded. It is possible to select and set whether to determine transfer or discard individually without asking. In other words, when the user desires to discard all kinds of deliverables at once, the type of deliveries that are desired to be discarded on the SPAM setting screen (FIG. 20) in association with the name or name of the sender. By designating, the type of the designated delivery item is registered in the white condition table (FIG. 7) as a condition.

  After the above, when the user has to tell the destination of the delivery to another person, the user may tell the virtual address generated by the proxy receipt management server 1 instead of his own address.

  If the sender who is informed of the virtual address writes this virtual address on the shipment, the virtual address has an appearance showing the inside of the building of the building where the department that performs proxy receipt service in the ISP is located. The post office worker or the carrier of the carrier can deliver the delivery to the building. The delivery delivered to the building in this way is received by proxy by the person in charge of the ISP managing this building. Then, when the person in charge receives the delivery by proxy, the person in charge inputs the name or name of the sender of the delivery, the temporary address described as the destination, and the type of the delivery to the proxy receipt management server 1 (S102). ). Then, these pieces of information are registered in the delivery list table (FIG. 3) as information on the delivery received as a proxy (S104).

  On the other hand, the proxy receipt management server 1 periodically checks whether there is information on the newly registered delivery in the delivery list table (FIG. 3) (S201). Then, as described above, when the information about the delivery addressed to the user for which the notification mail flag is set is newly registered in the delivery list table (FIG. 3), the proxy receipt management server 1 Then, a delivery notification mail is transmitted to the user (S204).

  Regardless of whether or not the notification mail flag is set, the user inputs the URL of the delivery disposal process (CGI) into the browser of the user terminal 2 of FIG. The proxy receipt management server 1 is made to execute the sent material disposal process.

  Then, first, the information (the name or name of the sender, the type of the delivery) of the delivery registered in the delivery list table (FIG. 3) as addressed to the virtual address of the user is displayed on the delivery list screen ( FIG. 25) is displayed as a list (S302). On the delivery list screen, information on the delivery from the sender registered in the white list sender table (FIG. 4) and the SPAM sender table (FIG. 6) is also displayed. Further, the user can select the person selected by operating the “white” button 53 from the senders whose names or names are listed (or by pressing the “white list setting” button 57. The person who has been selected by not checking the delete check box 68 on the white list batch setting screen (FIG. 34) can be registered in the white list sender table (FIG. 4). At this time, it is also possible to set the type (condition) of the items to be collectively transferred (FIGS. 30 and 34). Similarly, the user is displayed by pressing a “SPAM” button 54 (or a “SPAM setting” button 58) selected from the senders whose names or names are listed. The person selected by not checking the deletion check box 73 on the SPAM collective setting screen (FIG. 36) can be registered in the SPAM sender table (FIG. 6). At this time, it is also possible to set the type (condition) of the items to be collectively discarded (FIGS. 32 and 36). In addition, the user is registered in the white list sender table (FIG. 4) and the sent items from the sender who are not registered in the white list sender table (FIG. 4) and the SPAM sender table (FIG. 6). A type of delivery that does not correspond to the conditions registered in the white list condition table (FIG. 5) sent from the sender, and the SPAM condition table (FIG. 6) sent from the registered sender. For the types of deliveries that do not meet the conditions registered in FIG. 7), they can be individually transferred by operating the “ship” button 52 or by operating the “discard” button 55. Discarding can also be selected. The selection result thus made is set as a flag on the delivery list table (FIG. 3).

  After the above, when the “end” button 59 is operated, the processing after S304 in FIG. 12 for determining the disposal of the sent item is executed. Note that the processing from S304 onward is also executed by a periodic interrupt.

  First, from the sender registered in the white list sender table (FIG. 4) and unconditionally “0” is registered in the white list condition table (FIG. 5), the delivery to the user, and the white From the sender registered in the list sender table (FIG. 4), the types of deliverables that match the conditions registered in the white list condition table (FIG. 5) addressed to the user are collectively displayed. It is transferred to the address (S308). Next, from the sender registered in the SPAM sender table (FIG. 6) and registered unconditionally “0” in the SPAM condition table (FIG. 7), the mail addressed to the user, and the SPAM sender table ( From the sender registered in FIG. 6), the types of deliveries that meet the conditions registered in the SPAM condition table (FIG. 7) addressed to the user are discarded in a lump (S315). Next, among the sent items associated with the virtual address of the user in the sent item list table (FIG. 3), the items for which the flag “1” indicating transfer is set to the real address of the user. Those that have been transferred (S321) and for which the flag "-1" indicating discard has been set are discarded (S324).

  In this way, the user does not disclose his / her real address to the sender of the shipment, and whether the sender uses mail as a means of transporting the shipment or which delivery company to use. Regardless, the person in charge of the ISP can receive the delivery by receiving the delivery by proxy and forwarding it to the real address of the user in accordance with the instructions of the proxy receipt management server 1. In addition, it is possible to select items sent from untrustworthy senders in a lump, and send items from other senders individually, and have the ISP personnel discard them. Therefore, the user does not have to disclose his / her real address, so avoid the risk of misuse by the person whose address was disclosed or the third party who learned his / her own real address leaked from here. Can do.

The block diagram which shows the structural example of the network system containing the proxy receipt management server which is embodiment of this invention Table showing data structure of user database Table showing the data structure of the delivery list table Table showing data structure of white list sender table Table showing data structure of whitelist condition table Table showing data structure of SPAM sender table Table showing data structure of SPAM condition table Flow chart showing the contents of the setting process Flow chart showing the contents of the setting process Flow chart showing the contents of the delivery receipt process Flow chart showing the contents of the email notification process Flow chart showing the contents of the sent material disposal process Flow chart showing the contents of the sent material disposal process Flow chart showing the contents of the sent material disposal process Figure showing the setting screen Figure showing the authentication screen Figure showing the virtual address registration screen Figure showing notification email setting screen Figure showing the whitelist setting screen Figure showing the SPAM setting screen Figure showing the completion screen Figure showing the input screen Figure showing email text Figure showing the authentication screen Figure showing the delivery list screen Figure showing the shipping screen Figure showing the completion screen Figure showing the discard screen Figure showing the completion screen Figure showing the whitelist setting screen Figure showing the completion screen Figure showing the SPAM setting screen Figure showing the completion screen Figure showing the whitelist batch setting screen Figure showing the completion screen The figure which shows the SPAM collective setting screen Figure showing the completion screen Schematic showing the flow of information and information centered on the proxy receipt management server

Explanation of symbols

1 proxy receipt management server 2 user terminal 10 CPU
11 RAM
12 Display 13 Input Device 15 Disk Device 16 Program 17 User Database 18 Other Table 19 Printer 21 Display 22 CPU for Executing Browser
23 Input device

Claims (17)

Since the virtual address including the character string indicating the address of the specific building and the identification information of the user who is the sending partner is described, the sent matter sent to the building and received on behalf of the sending partner A delivery receipt agent management device used for management,
First storage means for storing the identification information and the real address in association with each other for each user;
An input means for inputting the delivery information comprising the identification information of the user as the sending partner and the identification information of the sender included in the virtual address described in the delivery received on behalf by being operated by the operator;
Second storage means for storing the delivery information input by the input means for each delivery;
For each piece of delivery information stored in the second storage means, the real address corresponding to the user identification information included in the delivery information is read from the first storage means and corresponds to the delivery information. A delivery receipt agent management apparatus comprising: instruction means for outputting an instruction to transfer a delivery to the real address. A communication means for communicating with a terminal operated by each user via a network and transferring information to and from the terminal;
In accordance with a request from a terminal operated by any user received by the communication means, the contents of the delivery information including the identification information of the user stored in the second storage means are displayed in a list. 2. The delivery receipt agent management apparatus according to claim 1, further comprising list response means for responding screen data from the communication means to the terminal. 2. The delivery receipt agent managing apparatus according to claim 1, wherein the user identification information is an electronic mail address of the user. A communication means for communicating with a terminal operated by each user via a network and transferring information to and from the terminal;
An e-mail transmitting means for transmitting an e-mail notifying the receipt of the deliverable to the e-mail address in the virtual address included in the sent information when the sent information is input by the input means; 4. The delivery receipt agent management device according to claim 3, further comprising: The e-mail includes link information to screen data for displaying a list of contents of the delivery information including the identification information of the user stored in the second storage means,
When the request transmitted from the terminal operated by the user based on the link information is received by the communication means, the list response means causes the screen data to respond to the terminal from the communication means. 5. A delivery receipt agent managing device according to claim 4, Since the virtual address including the character string indicating the address of the specific building and the identification information of the user who is the sending partner is described, the sent matter sent to the building and received on behalf of the sending partner A delivery receipt agent management device used for management,
First storage means for storing the identification information and the real address in association with each other for each user;
An input means for inputting the delivery information comprising the identification information of the user as the sending partner and the identification information of the sender included in the virtual address described in the delivery received on behalf by being operated by the operator;
For each shipment, a transfer flag that specifies that the shipment information input by the input means should be transferred to the user to whom the shipment is sent or a discard that specifies that the shipment should be discarded Second storage means for storing the flag in a settable format;
A communication means for communicating with a terminal operated by each user via a network and transferring information to and from the terminal;
In accordance with a request from a terminal operated by any user received by the communication means, the transfer information including the identification information of the user stored in the second storage means includes the transfer flag or Flag setting means for setting a discard flag;
For each piece of delivery information stored in the second storage means, for which a transfer flag is set, an actual address corresponding to the user identification information included in the delivery information is stored in the first storage. Read from the means, output an instruction to transfer the delivery corresponding to the delivery information to the real address, and for those for which the discard flag is set, an instruction to discard the delivery corresponding to the delivery information A delivery receipt agent management apparatus, comprising: an instruction means for outputting a message. In accordance with a request from a terminal operated by any user received by the communication means, the contents of the delivery information including the identification information of the user stored in the second storage means are displayed in a list. 7. The delivery receipt agent managing apparatus according to claim 6, further comprising list response means for responding screen data from the communication means to the terminal. 7. The delivery receipt agent managing apparatus according to claim 6, wherein the identification information of the user is an electronic mail address of the user. An e-mail transmitting means for transmitting an e-mail notifying the receipt of the deliverable to the e-mail address in the virtual address included in the sent information when the sent information is input by the input means; 9. The delivery receipt agent management apparatus according to claim 8, further comprising: The e-mail includes link information to screen data for displaying a list of contents of the delivery information including the identification information of the user stored in the second storage means,
When the request for the screen data transmitted from the terminal operated by the user based on the link information is received by the communication means, the list response means sends the screen data from the communication means to the terminal. 10. The delivery receipt agent managing apparatus according to claim 9, wherein a response is made. The screen data includes link information for transmitting a request for setting the transfer flag to the delivery information for the delivery to the flag setting means for each delivery, and the delivery to the flag setting means. 11. The delivery receipt agent management apparatus according to claim 10, further comprising link information for transmitting a request for setting the discard flag to the delivery information. For each user, the apparatus further comprises third storage means for registering in advance the conditions of the sender's identification information for the items to be transferred to the user at one time,
The instruction means includes a destination address registered in the third storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. For items including identification information, the real address corresponding to the identification information of the user included in the delivery information is read from the first storage means regardless of the state of each flag, and the correspondence is made to the delivery information. The delivery receipt agent managing apparatus according to claim 6, wherein an instruction to transfer the delivery to be sent to the real address is output. The delivery information includes type information indicating the type of the delivery,
Each user further comprises a third storage means for pre-registering a combination condition of sender identification information and type information about a delivery to be transferred to the user,
The instruction means includes a destination address registered in the third storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. For those including a combination of identification information and type information, regardless of the state of each flag, the real address corresponding to the identification information of the user included in the delivery information is read from the first storage means, 7. The delivery receipt agent managing apparatus according to claim 6, wherein an instruction for transferring a delivery corresponding to the delivery information to the real address is output. For each user, it further comprises a fourth storage means for registering in advance the identification information of the sender of the items to be collectively discarded,
The instruction means includes a destination address registered in the fourth storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. 7. The delivery receipt agent managing apparatus according to claim 6, wherein for an item including identification information, an instruction to discard the delivery corresponding to the delivery information is output regardless of the state of each flag. The delivery information includes type information indicating the type of the delivery,
For each user, the apparatus further includes a fourth storage unit that pre-registers a combination condition of sender identification information and type information about a delivery to be discarded,
The instruction means includes a destination address registered in the fourth storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. 7. The sent item according to claim 6, wherein for an item including a combination of identification information and type information, an instruction to discard the sent item corresponding to the sent item information is output regardless of the state of each flag. Receiving agency management device. For each user, a third storage means for registering in advance the identification information of the sender of the items to be transferred to the user in a batch, and
For each user, it further comprises a fourth storage means for registering in advance the identification information of the sender of the items to be collectively discarded,
The instruction means includes a destination address registered in the third storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. For items including identification information, the real address corresponding to the identification information of the user included in the delivery information is read from the first storage means regardless of the state of each flag, and the correspondence is made to the delivery information. For instructions that output instructions to forward the delivery to the real address and include the destination identification information registered in the fourth storage means corresponding to the user identification information contained in the delivery information. 7. The delivery receipt agent managing apparatus according to claim 6, wherein an instruction to discard the delivery corresponding to the delivery information is output regardless of the state of each flag. The delivery information includes type information indicating the type of the delivery,
For each user, a third storage means that pre-registers the combination conditions of the sender's identification information and type information for the items to be transferred to the user; and
For each user, the apparatus further includes a fourth storage unit that pre-registers a combination condition of sender identification information and type information about a delivery to be discarded,
The instruction means includes a destination address registered in the third storage means corresponding to the identification information of the user included in the delivery information among the delivery information stored in the second storage means. For those including a combination of identification information and type information, regardless of the state of each flag, the real address corresponding to the identification information of the user included in the delivery information is read from the first storage means, The destination identification information registered in the fourth storage means corresponding to the identification information of the user included in the delivery information is outputted by outputting an instruction to transfer the delivery corresponding to the delivery information to the real address. 7. A delivery receipt agent according to claim 6, wherein an instruction for discarding a delivery corresponding to the delivery information is output regardless of a state of each flag for a combination including a combination of type information. Management apparatus.