JP5691111B2 - How to determine the forwarding destination from the homepage address - Google Patents

Description

  The present invention relates to a technique for determining recipient location information indicating a recipient location as a transfer destination from a home page address.

When delivering a delivery object such as goods or money from the shipping source to the receiving party, and a third party courier delivering the delivered object to the receiving destination, Recipient location information, which is information indicating the location of the recipient, is required.
For example, if delivery is by delivery, the address information of the recipient on the slip is electronic money delivery by bank transfer using the online banking system. Corresponds to location information.
There are various methods for the delivery company to acquire the recipient location information, and the following proposal has been made regarding the acquisition method in the prior art.

Patent Document 1 describes a method of acquiring destination location information from a slip number described in a delivery slip affixed to a delivery object without describing an address serving as destination location information.
Since the slip number itself does not correspond to the recipient location information and cannot be delivered to the recipient as it is, it is necessary to determine the recipient location information as the transfer destination from the slip number by some method.
This is a system in which a slip number notified from a sender and auction information including recipient location information are stored in a database in association with each other, and the recipient location information can be uniquely searched from the slip number. It is realized by using.

JP 2008-015767 A

In the system of Patent Document 1, the auction information including the recipient location information is associated with the slip number and the auction ID items, and stored and managed in a database so that the auction information can be uniquely identified. This is because when the system is introduced on a certain web page and the forwarding destination is determined, some work is required separately for associating the web page using the system with the auction ID or slip number for system design. It means that there is. For example, a work for installing a form for transmitting an auction ID or a slip number from a web page to the system corresponds to this work.
On the other hand, this means that a web page that does not perform this operation cannot use the system and cannot determine the transfer destination.
On the Internet, where there are currently 1 trillion web pages, if you try to build an environment that allows you to determine the forwarding destination from any web page, this system requires work to associate each web page. The efficiency is poor.

  In order to solve the above-described problems, the present invention provides a “method for determining a transfer destination from a home page address” for determining destination position information indicating a position of a transfer destination as a transfer destination from the home page address.

  The homepage address here is a URL (Uniform Resource Locator) whose scheme name is http, https, ftp, etc., and information indicating the position where content data such as a web page, image, video, etc. exists in a hierarchical structure. say. The target content data can be acquired by performing communication via the network according to the position information.

By the way, the homepage address is always associated when the content is published via the network.
This is because if the homepage address is not associated with the content, it will not be understood how the user can use the content, and as a result, it will be synonymous with private. It is.
The present invention solves the above-described problems by determining the transfer destination from the homepage address having this feature so that the transfer destination can be determined without performing a separate operation when publishing the content. .

In the invention according to claim 1,
In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
Creating relationship confirmation destination data that is a homepage address indicating another position below the lowest layer that can be obtained from the homepage address of the destination data;
Outputting the relationship confirmation destination data to the recipient terminal;
A relationship for determining whether or not data exists at the position indicated by the relationship confirmation destination data from the content of communication via the network with the destination server that is the server at the location indicated by the relationship confirmation destination data A judgment stage;
If present in the relationship determination step, the method comprises the step of determining the destination location data as a transfer destination for the destination data.

In the first aspect of the present invention, before the destination location information input by the recipient terminal is determined as the transfer destination, it is below the lowest layer that can be acquired from the homepage address input by the recipient terminal. A homepage address indicating another position is created, and the position is output to the recipient terminal to notify the operator of the recipient terminal, and whether or not the position can be operated is confirmed.
By the way, the lowest layer here refers to the deepest layer among the layers that can be represented in the homepage address. If the scheme name is http or https, it means the one up to the slash that appears to the right of the character string representing the domain name. If it's just a domain name, it's the one with the slash appended. For example, “http://www.a.com/b/c/d.html” becomes “http://www.a.com/b/c/”, and “http: //www.b .Com ”is“ http://www.b.com/ ”.
The purpose of this confirmation is that there is no relationship between the administrator who manages the position of the lowest layer that can be acquired from the homepage address entered by the recipient terminal and the operator of the recipient terminal. In spite of the above, it is to prevent the recipient position information input by the recipient terminal from being trusted and determined as it is as the transfer destination.
By the way, the confirmation method like this is that the administrator at the lowest layer that can be obtained from the homepage address entered by the recipient terminal and the hierarchy above it are not necessarily the same. Because there is no. If it is below the lowest level, at least one administrator must pass through the managed hierarchy, even if another administrator manages the data and child hierarchy below that hierarchy. This means that it is under the control of the manager who is the hierarchy, and it sufficiently satisfies the above-mentioned purpose.

In the invention according to claim 2,
In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
Creating a relationship confirmation password data that is a password and outputting it to the recipient terminal;
Whether or not the relationship confirmation password data exists at a specific position in the data at the position indicated by the receiving destination data is determined via a network with a destination server that is a server at the position indicated by the receiving destination data. A relationship determination stage to determine from the communication content of
If present in the relationship determination step, the method comprises the step of determining the destination location data as a transfer destination for the destination data.

In the invention according to claim 2, before determining the recipient location information input by the recipient terminal as the transfer destination, the password is output to the recipient terminal to notify the operator of the recipient terminal, It is confirmed whether the password can be set at a predetermined position in the data at the position of the homepage address input by the recipient terminal.
Note that this confirmation is performed for the same purpose as the confirmation performed before the recipient location information input by the recipient terminal is determined as the transfer destination.

In invention of Claim 3,
In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
From the shipper's terminal, entering the shipping address data that is the homepage address;
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
The destination determination step of determining whether the shipping destination data is a position below the lowest layer that can be obtained from the homepage address of the receiving destination data;
Creating relationship confirmation destination data that is a homepage address indicating another position below the lowest layer that can be obtained from the homepage address of the destination data;
Outputting the relationship confirmation destination data to the recipient terminal;
A relationship for determining whether or not data exists at the position indicated by the relationship confirmation destination data from the content of communication via the network with the destination server that is the server at the location indicated by the relationship confirmation destination data A judgment stage;
Determining the destination location data as a transfer destination for the destination data if it is a position below the lowest layer in the destination judgment step and exists in the relationship judgment step. provide.

In the invention according to claim 3, in addition to the confirmation method of claim 1, the homepage address input by the sender terminal is below the lowest layer that can be acquired from the homepage address input by the recipient terminal. Checking if it exists at the location.
The purpose of this confirmation is limited to those who manage the home page address that the recipient can receive from the home page address that can be obtained from the home page address entered by the recipient terminal. By doing so, it is possible to prevent the reception to the manager who has no relation at all.

In the invention according to claim 4,
In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
From the shipper's terminal, entering the shipping address data that is the homepage address;
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
The destination determination step of determining whether the shipping destination data is a position below the lowest layer that can be obtained from the homepage address of the receiving destination data;
Creating a relationship confirmation password data that is a password and outputting it to the recipient terminal;
Whether or not the relationship confirmation password data exists at a specific position in the data at the position indicated by the receiving destination data is determined via a network with a destination server that is a server at the position indicated by the receiving destination data. A relationship determination stage to determine from the communication content of
Determining the destination location data as a transfer destination for the destination data if it is a position below the lowest layer in the destination judgment step and exists in the relationship judgment step. provide.

In the invention according to claim 4, in addition to the confirmation method of claim 2, the confirmation added in claim 3 is also performed.
This confirmation is performed for the same purpose as the confirmation added in the third aspect.

With the method of determining the transfer destination from the home page address, the recipient location information can be derived from the home page address, and even if the home page address is specified as the destination of the delivery object, the delivery can be made to the recipient.
In addition, by simply publishing the content, the recipient location information can be derived from the homepage address associated with the content without any additional work, so that the delivery object can be delivered to the content manager. Is possible.
Furthermore, since the homepage address itself does not directly indicate the recipient location information, it is possible to ensure safety by anonymity.
Note that these effects are not obtained only for newly published content, and similar effects can be obtained also for already published content.

It is a figure showing typically the whole system configuration in one embodiment of the present invention. It is the figure which represented typically the structure of the transfer destination determination server in one Embodiment of this invention. It is a figure showing the data structure of the delivery file in one Embodiment of this invention. It is a figure showing the data structure of the receiving file in one Embodiment of this invention. It is a flowchart of the main program in one Embodiment of this invention. It is a layout of the top screen output to the terminal in one Embodiment of this invention. It is a flowchart of the dispatch process subroutine in one Embodiment of this invention. It is a layout of the remittance screen output to the terminal in one Embodiment of this invention. It is the 1st page of the flowchart of the reception process subroutine in one Embodiment of this invention. It is the 2nd page of the flowchart of the reception process subroutine in one Embodiment of this invention. It is a layout of the receiving screen output to the terminal in one Embodiment of this invention. 6 is a layout of a reception condition presentation screen output to a terminal when the relationship confirmation method for receiving funds in one embodiment of the present invention is “upload to a specified URL”. FIG. 6 is a layout of a reception condition presentation screen output to a terminal when the relationship confirmation method for receiving funds in one embodiment of the present invention is “password entry in content of destination URL”. FIG. It is a flowchart of the inquiry process subroutine in one Embodiment of this invention. It is a layout of the inquiry screen output to the terminal in one Embodiment of this invention. It is a layout of the inquiry result screen output to the terminal in one Embodiment of this invention. It is the first page of the flowchart of the administrator inquiry processing subroutine in one embodiment of the present invention. It is the 2nd page of the flowchart of the administrator inquiry process subroutine in one Embodiment of this invention. It is a layout of the administrator inquiry screen output to the terminal in one Embodiment of this invention. It is a layout of the administrator inquiry result screen output to the terminal in one Embodiment of this invention. It is a layout of the administrator inquiry result receipt details screen output to the terminal in one Embodiment of this invention.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that “one embodiment of the present invention” is referred to as “this embodiment”.

<Summary of this embodiment>
In order to clarify the effect of the invention, by using the method of determining the transfer destination from the homepage address of the present invention, even if the homepage address is used as the destination of the fund that is the delivery object, the shipping that is the sender This embodiment is a remittance system that can perform home delivery electronically, that is, remittance, from a recipient's account to a recipient's account that is a recipient. The funds are not transferred directly from the sender's account to the recipient's account, but indirectly through an account that is a temporary storage destination.

<Overall system configuration>
FIG. 1 is an overall configuration diagram schematically showing a system of the present embodiment (hereinafter, “system of the present embodiment” is referred to as “present system”).

  The transfer destination determination server 11 is a server managed by the transfer destination determiner 10 and is used to determine a transfer destination from a homepage address used as a fund destination.

  The shipper terminal 21 is a terminal used by the shipper 20 which is a fund shipper, and is used as a terminal of the transfer destination determination server 11.

  The recipient terminal 31 is a terminal used by the recipient 30 who is the recipient of funds, and is used as a terminal of the transfer destination determination server 11.

The destination server 41 is a server used by the destination manager 40 that manages the position of the lowest layer that can be acquired from the homepage address used as the destination of funds. Used to check if there is a relationship between them.
Here, the reason why the destination manager 40 is not set as the manager of the destination server 41 is that a plurality of managers may use one server.
For example, “http://www.a.com/”, “http://www.b.com/”, “http://www.c.com/˜user1/”, “http: //Www.c.com/˜user2/ ”Even if different managers manage the layers below, there are cases in which all are actually operated by one server.

The temporary storage destination courier server 51 is a server managed by the electronic money settlement person 50, and is used to transfer funds from a shipping source account to a temporary storage destination account.
When the user of this server transmits at least user identification information, information on remittance amount, and credit card information for uniquely identifying the user, in accordance with the communication procedure determined by the electronic money clearer 50, The funds corresponding to the remittance amount information are transferred from the account associated with the credit card information to the account associated with the user identification information.
Since this process is often used in a credit card payment system for Internet shopping, a detailed description thereof will be omitted.

The receiver courier server 61 is a server managed by the financial institution 60, and is used to transfer funds from the temporary storage account to the receiver account.
When the user of this server transmits at least user identification information, remittance amount information, and account information, which is information for uniquely identifying the user, according to the communication procedure determined by the financial institution 60, the user identification The funds corresponding to the remittance amount information are transferred from the account associated with the information to the account indicated by the account information.
Since this process is often used in a farm banking system provided by a financial institution, a detailed description thereof will be omitted.

  The transfer destination determination server 11, the transfer destination determiner terminal 12, the sender terminal 21, the receiver terminal 31, the destination server 41, the temporary storage destination courier server 51, and the destination courier server 61 are public Information can be exchanged via the network 71.

<Configuration of transfer destination determination server 11>
As illustrated in FIG. 2, the transfer destination determination server 11 includes an input / output control unit 110, a control unit 120, and a storage unit 130.

  The input / output control means 110 is constituted by a modem, and performs communication control with each terminal and each server connected via the public line network 71.

  The control unit 120 includes a CPU, a memory, and the like, and reads each program and executes it sequentially, thereby controlling each unit, performing various calculations, temporarily storing data, and the like according to the program.

  The storage means 130 is a hard disk and stores an OS 131, a terminal server 132, a main program 133, a home delivery file 134, and a destination file 135.

  The OS 131 stores an operating system program, which is read by the control unit 120 and executed sequentially, thereby controlling each unit and performing process management, memory management, file management, network management, and the like.

  Incidentally, data necessary for sequentially executing the OS 131 is also stored in the storage unit 120, but for the convenience of explanation, illustration on FIG. 2 is omitted.

  In the following description, the OS 131 that is read and sequentially executed by the control unit 120 is referred to as a “boot OS” in order to distinguish it from the OS 131 stored in the storage unit 130.

The terminal server 132 stores a terminal server program that operates in a pair with a terminal client program.
The terminal OS 132 is sequentially executed as the process of the boot OS, and the boot OS provides the operation data and the screen data communicated with the terminal client program of the terminal connected via the network. It is possible to provide a GUI environment such as a desktop or a window to a connection source terminal.

  Incidentally, data necessary for sequentially executing the terminal server 132 is also stored in the storage means 120. However, for convenience of explanation, illustration on FIG. 2 is omitted.

  In the following description, the process of the terminal server 132 is referred to as a “terminal server process” in order to distinguish it from the terminal server 132 stored in the storage unit 130.

The main program 133 stores a program for performing the operation shown in the flowchart of FIG. 5, and is sequentially executed as a process of the boot OS when necessary.
In this program, there is a place where an API (Application Program Interface) is used in order to use the function of the boot OS and the terminal server process.
As a result, when viewed from the main program 133, the control of each terminal via the network can be handled like a local computer without being conscious of the network. Is not expressed every time, but is simply expressed by input / output.

  In the following description, the process of the main program 133 is referred to as “main program process” in order to distinguish it from the main program 133 stored in the storage unit 130.

The home delivery file 134 stores data related to remittance of funds.
This file has the data structure shown in FIG. 3, and includes a “shipping number” field uniquely assigned to each record in the file, a “destination” field indicating a homepage address as a destination, and a remittance amount of funds. The “remittance amount” field indicating “reception” and the “reception number” field indicating reception destination position information are configured as one record.
In the “reception number” field, if there is no stage for storing the recipient location information, the value of the reception number is a “NULL” value indicating that no value is stored.

The recipient file 135 stores data related to recipient location information.
This file has the data structure shown in FIG. 4, and includes a “reception number” field uniquely assigned to each record in the file, a “bank code” field that is account information corresponding to the recipient location information, The “branch code” field, the “account number” field, the “deposit item” field, and the “account name” field are configured as a single record.

  Incidentally, each record of the delivery file 134 and the recipient file 135 has the same field name called a receipt number, but the same numerical value is stored in the corresponding field of each other and associated with each other so that the receipt in the corresponding record of the delivery file 134 is received. The account information record of the recipient can be uniquely retrieved from the recipient file 135 from the number field.

<Initial processing>
First, the transfer destination determination server 11 receives the connection from each terminal by sequentially executing initial processing.

The transfer destination determination server 11 starts the boot OS.
This is performed by the OS 131 being read into the control means 120 when the server is activated.

Next, the terminal server process is sequentially executed to wait for a connection from any one of the transfer destination determiner terminal 12, the sender terminal 21, and the receiver terminal 31.
This is performed by sequentially executing the terminal server 132 as a process of the boot OS.

<Common processing>
Here, the common process executed sequentially when the transfer destination determination server 11 is connected from each terminal is described.
In order to perform this process, it is necessary to complete the above-described initial process in advance and accept connections from each terminal.

  The transfer destination determination server 11 controls the connection source terminal via the terminal server process when each terminal is connected by sequentially executing the terminal client program.

Next, the transfer destination determination server 11 sequentially executes a main program process that performs the operation of the flowchart shown in FIG.
This is performed by sequentially executing the main program 133 as a process of the boot OS.

  Hereinafter, the operation of the main program 133 will be described by describing each step of the flowchart shown in FIG.

In step S11, an exclusive process is performed in consideration of simultaneous connection of a plurality of terminals.
At this time, only one process that can take ownership can proceed to step S12, but the other processes that could not take hold wait for the execution of step S12 until the ownership is released.

In step S12, the top screen shown in FIG. 6 is output to the connection source terminal of the terminal that is the connection source.
At this time, to the connection source terminal operator who is the operator of the connection source terminal, any one of the top dispatch button 211, the top reception button 212, the top inquiry button 213, or the top manager inquiry button 214 is connected. Prompt to click with the terminal mouse.

  In step S13, when it is detected that any button on the top screen output in step S12 is clicked with the mouse of the connection source terminal, the transfer destination determination server 11 selects the top button indicating the selected button. Save data temporarily.

  In step S14, the corresponding subroutine is sequentially executed according to the top button selection data.

In step S15, the ownership of the exclusive process is released so that the next terminal can execute it sequentially, and then the process is terminated.
Note that the release of exclusive control ownership is also performed by detecting the click of the end button output at the upper right of each screen or by detecting that there is no operation from the terminal for a long time.

<Shipment processing>
In the dispatch process, in the above-described outline of the present embodiment, the process is performed from the account of the shipper 20 that is a shipper's account to the point where money is transferred from the account of the transfer destination determiner 10 that is a temporary storage destination account.

  This processing can be performed by any terminal as long as the above-described common processing can be performed. However, for convenience of explanation, it is assumed that the sender 20 uses the sender terminal 21.

The shipper 20 first connects the shipper terminal 21 to the transfer destination determination server 11 and sequentially executes the common processing described above.
In the middle, in step S12, when the sender 20 clicks the top dispatch button 211 with the mouse of the sender terminal 21, the transfer destination determination server 11 sequentially executes a dispatch processing subroutine for performing the operation shown in the flowchart of FIG. To do.

  Hereinafter, each step of the flowchart shown in FIG. 7 will be described to show the operation of the dispatch processing subroutine.

In step S21, the shipping screen shown in FIG.
At this time, the sender 20 receives the homepage address as the destination to be sent in the destination address text box 311, the money transfer amount in the money transfer amount text box 312, and the credit card information used by the sender 20 for money transfer. It is urged to input the shipping source position information 313 by using the keyboard and mouse of the sender terminal 21 respectively.
When these inputs are completed, the user is also prompted to click the shipping button 314 with the mouse of the sender terminal 21 at the end.

  In step S22, when it is detected that the shipping button 314 has been clicked with the mouse, the data input to the remittance amount text box 312 by using the data input to the shipping destination text box 311 as the shipping destination data by that time. Is temporarily stored as the delivery source position data, and the data input to the delivery source position information 313 as the delivery object data.

In step S23, an electronic money settlement process is performed in which funds are transferred from the account of the shipper 20 to the account of the shipper determiner 10.
In the electronic money settlement process, at least user identification information, remittance amount information, and credit card information are transmitted to the temporary storage destination courier server 51 via the public network 71 in accordance with a communication procedure determined by the electronic money settlement person 50. , Done by sending.
At this time, the user identification information that is set in advance in the main program 133 and is read as temporary storage destination courier server user identification data when sequentially executed as a process is used.
Further, the delivery object data is used for the remittance amount information, and the shipping source position data is used for the account information.

In step S24, whether or not the electronic money settlement process in step S23 is successful is confirmed from the contents of communication with the temporary storage destination server 51. If it fails, an error screen is output to the shipper terminal 21 to Complete the process.
If successful, it is determined that remittance has been completed from the account of the shipper 20 to the account of the shipper determiner 10, and the process proceeds to step S 25.

In step S25, the shipping information is stored by additionally writing a record to the home delivery file 134.
The following data is stored in each field of the record at this time.
In the “delivery number” field, a unique value that does not overlap with the value of the delivery number field in all records written in the delivery file 134 is displayed. In the “destination” field, the shipping destination data is displayed in the “remittance amount” field. The delivery target object data is stored, and the “reception number” stores a NULL value.

  In step S26, the fact that the remittance has been completed is output on the screen of the sender terminal 21, thereby completing the shipping process.

<Receipt processing>
In the receiving process, in the above-described outline of the present embodiment, the process is performed from the account of the transfer destination determiner 10 which is a temporary storage destination account to the point where money is transferred from the account of the receiver 30 which is the account of the receiver.
The funds are transferred from the account of the shipper 20 which is the shipper's account to the account of the transfer destination determiner 10 which is the account of the temporary storage destination, and this receiving process is completed. Thus, the above-described outline of the present embodiment is satisfied.

  This process can be performed by any terminal as long as the terminal common process can be performed. However, for convenience of explanation, it is assumed that the receiver 30 uses the receiver terminal 31.

First, the recipient 30 connects the recipient terminal 31 to the transfer destination determination server 11 to sequentially execute the above-described common processing.
On the way, when the recipient 30 clicks the top receipt button 212 with the mouse of the recipient terminal 31 in step S12, the transfer destination determination server 11 performs the operation shown in the flowcharts of FIG. 9 and FIG. Are executed sequentially.

  Hereinafter, each step of the flowcharts shown in FIGS. 9 and 10 will be described to show the operation of the reception processing subroutine.

In step S31, the receiving screen shown in FIG. At this time, the recipient 30 receives the homepage address of the recipient to receive in the recipient destination text box 411, the account information as recipient location information in the recipient location information 412, and the keyboard and mouse of the recipient terminal 31 respectively. Prompt to enter using.
In the relationship confirmation mode 413, the user is prompted to select a confirmation method for receiving funds for the homepage address input in the recipient address text box 411 using the mouse of the recipient terminal 31.
Further, when these inputs are completed, the user is also prompted to click the receipt condition creation button 414 with the mouse of the recipient terminal 31 at the end.

There are two confirmation methods for receiving funds for the homepage address, and one of them is selected.
In this confirmation, there is no relationship between the recipient 30 and the recipient manager 40 who is the manager at the lowest layer position that can be acquired from the homepage address entered in the recipient address text box 411. Nevertheless, the account information input in the recipient location information 412 is trusted to determine it as a transfer destination as it is and to prevent erroneous remittance.

  One is a method by “Upload to specified URL”, which creates a homepage address indicating another position below the lowest layer that can be obtained from the homepage address input in the recipient address text box 411, and This is a method of notifying the recipient 30 by outputting the position to the recipient terminal 31 and confirming whether or not the position can be operated.

  The other is a method based on “description of the password in the content of the recipient URL”, which is notified to the recipient 30 by outputting the password to the recipient terminal 31 and entered in the recipient text box 411. This is a method for confirming whether or not the password can be set at a predetermined position in the data at the position of the home page address.

  In the following description, this “confirmation method for receiving funds for the homepage address” will be referred to as “relationship confirmation method”.

In step S32, when it is detected that the reception condition creation button 414 has been clicked with the mouse, the data input to the reception destination text box 411 is input to the reception destination position information 412 by that time as reception destination data. The data indicating which method is selected in the relationship confirmation mode 413 is temporarily stored as the relationship confirmation mode data.
Note that the relationship confirmation mode data is set to true if “upload to specified URL” is selected in the relationship confirmation mode 413, and false if “write password to destination URL content” is selected. The

In step S33, the delivery file 134 is read in units of records, and the data in the destination field, which is the shipping destination data input in the above-described shipping process, is a position below the lowest layer that can be acquired from the homepage address indicated by the receiving destination data. In addition, a record having a NULL in the receipt number field is searched, and all the matched records are temporarily stored as delivery target delivery data.
By this processing, what can be received by the recipient 30 is limited to those for the manager who manages the position below the lowest layer that can be expressed in the homepage address input from the recipient terminal. This prevents the delivery object from being received by a manager who has nothing to do with the fund, and prevents double receipt of funds.

In step S34, if the relationship confirmation mode data is true, the process proceeds to step S35, and if it is false, the process proceeds to step S36.
The purpose of this is to create data necessary for confirmation in accordance with the relationship confirmation method selected by the recipient 30 in the next step.

In step S35, the relationship confirmation destination data necessary for performing confirmation in accordance with the relationship confirmation method by “upload to the specified URL” is created.
This data is a home page address indicating another position below the lowest layer that can be acquired from the receiving destination data.
For example, when the scheme name of the homepage address indicated by the reception destination data is http, the character string data randomly generated to the character string code from the reception destination data to the lowest layer corresponds to this.
Next, it is confirmed from the contents of communication with the destination server 41 whether or not the data already exists for the corresponding portion of the destination indicated by the relationship confirmation destination data. If the data exists, new data is recreated.
If data still exists after a new number of data has been recreated a certain number of times, an error screen is displayed on the terminal of the recipient terminal 31 to complete the receiving process.

In step S36, the relationship confirmation password data necessary for performing the confirmation in accordance with the relationship confirmation method by "description of the password in the content of the recipient URL" is created.
This data has different password data depending on what kind of content is expected by the homepage address indicated by the receiving destination data. For example, if it is a web page, it is character string data generated randomly, and if it is a still image or a moving image, it is binary data generated randomly.
In addition, when the content is predicted from the homepage address, for example, if the scheme name of the homepage address is http, https, or ftp, it is performed depending on the form of the end of the homepage address. An image can be predicted if it ends with “.jpg” or “.gif”, and a web page can be predicted if it ends with “.html” or “.html”.

In step S37, the reception condition presentation screen is output on the screen of the recipient terminal 31, but the output contents are partially different depending on the relationship confirmation method.
If the relationship confirmation mode data is true, since the relationship confirmation method is based on “upload to a specified URL”, the screen shown in FIG. 12 is output. At this time, the relationship confirmation destination data display area 421 outputs the content of the relationship confirmation destination data created in step S35.
On the other hand, if the relationship confirmation mode data is false, since the relationship confirmation method is based on “description of password in content of destination URL”, the screen shown in FIG. At this time, the contents of the relationship confirmation password data created in step S36 are output to the relationship confirmation password data display area 422.
When it is ready to confirm the relationship, the user is prompted to click the receipt condition presentation receipt button 423 with the recipient 30 mouse.

  In step S38, when the recipient terminal 31 detects the click of the receipt condition presentation receipt button 422 by the recipient 30, the process proceeds to the next step S39.

In step S39, if the relationship confirmation mode data is true, the process proceeds to step S40, and if false, the process proceeds to step S41.
This is intended to perform confirmation in accordance with the relationship confirmation method selected by the recipient 30 in subsequent steps.

In step S40, confirmation is performed according to the relationship confirmation method by "upload to the specified URL".
Specifically, it is confirmed by communicating with the destination server 41 whether data exists at the position indicated by the relationship confirmation destination data.

In step S41, confirmation is performed in accordance with the relationship confirmation method based on “description of password in content of destination URL”.
Specifically, it is confirmed by communicating with the destination server 41 whether or not the relationship confirmation password data exists at a specific position in the data indicated by the reception destination data.

In step S42, it is determined from the contents of communication with the destination server 41 whether data exists. If no data exists, an error screen is displayed on the terminal of the recipient terminal 31 to complete the receiving process. On the other hand, if it can be determined that data exists, the process proceeds to step S43.
The method for determining whether data exists or not depends on the homepage address.
This is because when the scheme name of the home page address is http, https, and ftp, the communication content and the communication procedure are different due to different protocols for communication. In addition, in the relationship confirmation method by “description of the password in the content of the destination URL”, the confirmation position may be different depending on the content expected from the homepage address.
If the existence of the data can be confirmed at this time, the receiving destination position information of the receiving destination position data is determined as the transfer destination for the homepage address of the receiving destination data.

In step S43, a firm banking process is performed in which funds are transferred from the account of the shipping destination determiner 10 to the account of the receiver 30 because the receiver location information has been acquired in step S42.
In the farm banking process, at least user identification information, remittance amount information, and account information are transmitted to the recipient courier server 61 via the public network 71 in accordance with a communication procedure determined by the financial institution 60. Done.
At this time, as the user identification information, information set in advance in the main program 133 and read as the recipient courier server user identification data when sequentially executed as a process is used.
The remittance amount information uses received total amount data which is the total value of all remittance amount fields included in the delivery target delivery data, and the account information uses recipient data.

In step S44, whether or not the farm banking process in step S43 is successful is confirmed from the contents of communication with the recipient courier server 61. If it fails, an error screen is displayed on the terminal of the recipient terminal 31. Display and complete the receiving process.
If successful, it is determined that remittance has been completed from the account of the shipping destination determiner 10 to the account of the recipient 30, and the process is subsequently transferred to step S45.

In step S45, the recipient location information is stored by additionally writing a record to the recipient file 135.
The following data is stored in each field of the record at this time.
In the “reception number” field, a unique value that does not overlap with the values of all the delivery number fields written in the destination file 135 is set, and in the other fields, the corresponding data in the destination position data is set. Is done.

  In step S46, all records that match the delivery number of the delivery target delivery data are searched and searched from the delivery file 134, and the receipt number field in each record is additionally written in the destination file 135 in step S45. The same receipt number as the data in the receipt number field of the record is written. By doing so, it becomes possible to retrieve the recipient location information from the delivery record that has been received, and at the same time, the receipt number field is not a NULL value, thereby preventing double receipt from the combination with step S33. Is possible.

  In step S <b> 47, the transfer destination determination server 11 outputs the fact that the reception is completed on the screen of the recipient terminal 31, thereby completing the reception process.

<Completion of remittance>
Through the above-mentioned shipping process and receiving process, it was possible to transfer funds destined for the homepage address from the shipping source to the receiving party.
In addition, it was also possible to obtain recipient location information from the homepage address during the process.
There are other query processing and administrator query processing, each of which is shown below.

<Inquiry processing>
The inquiry process is prepared for the purpose of browsing the shipping status and the receiving status.

First, the connection source terminal operator sequentially executes the above-described terminal common processing by connecting the connection source terminal to the transfer destination determination server 11.
On the way, in step S12, when the connection source terminal operator clicks the top inquiry button 213 with the mouse of the connection source terminal, the transfer destination determination server 11 sequentially executes an inquiry processing subroutine for performing the operation shown in the flowchart of FIG. Run.

  Hereinafter, each step of the flowchart shown in FIG. 14 will be described to show the operation of the inquiry processing subroutine.

In step S51, the inquiry screen shown in FIG. 15 is output on the screen of the connection source terminal.
At this time, the connection source terminal operator is prompted to input the homepage address to be inquired into the inquiry destination text box 511 using the keyboard of the connection source terminal.
Finally, the user is also prompted to click the inquiry search button 512 with the mouse of the connection source terminal.

  In step S52, when the click of the inquiry search button 512 is detected, the data input in the inquiry destination text box 511 by that time is temporarily stored as inquiry destination data.

In step S53, data for browsing the shipping status and the receiving status is read from the home delivery file 134.
More specifically, all records having a destination field that matches forward with the inquiry destination data are read from the delivery file 134 and temporarily stored as inquiry result data.
Incidentally, the reason why the search is made with the forward match is that if the search is made with the complete match, it is difficult to find information on the delivery object that the recipient should be able to receive.

In step S54, the inquiry processing is completed by outputting the inquiry result screen shown in FIG. 16 to the screen of the connection source terminal using the inquiry result data.
At this time, if the value in the receipt number field of the corresponding record is a NULL value, “not yet” is displayed, and if not, “completed” is displayed as the reception status.

<Administrator inquiry process>
The administrator inquiry process is prepared for the purpose of browsing the shipping status and the receiving status.
Incidentally, although the purpose is the same as that of the above-described inquiry processing, it is different in that the recipient location information is also displayed.
Further, for the purpose of preventing the recipient location information from being misused, it is necessary to input the administrator password so that only the transfer destination determiner 10 of the administrator can make an inquiry.

  This process can be performed by any terminal as long as the above-described terminal common process can be performed. However, for convenience of explanation, it is assumed that the transfer destination determiner 10 uses the transfer destination determiner terminal 12.

First, the transfer destination determiner 10 sequentially executes the above-described terminal common processing by connecting the transfer destination determiner terminal 12 to the transfer destination determination server 11.
On the way, in step S12, when the transfer destination determiner 10 clicks the top manager inquiry button 214 with the mouse of the transfer destination determiner terminal 12, the transfer destination determination server 11 is shown in the flowcharts of FIGS. The administrator inquiry processing subroutine for performing the operation is sequentially executed.

  Hereinafter, the steps of the inquiry processing subroutine will be described by describing each step of the flowcharts shown in FIGS. 17 and 18.

In step S61, the administrator inquiry screen shown in FIG. 19 is output on the screen of the transfer destination determiner terminal 12.
At this time, the transfer destination determiner 10 sends the home page address to be inquired to the administrator inquiry destination text box 611, the administrator password to the administrator inquiry password text box 612, and the keyboard of the transfer destination determiner terminal 12. Prompt with the mouse.
Finally, the administrator is also prompted to click the administrator inquiry button 613 with the mouse of the transfer destination determiner terminal 12.

  In step S62, when the click of the administrator inquiry button 613 is detected, the data input to the administrator inquiry destination text box 611 by that time is input to the administrator inquiry password text box 612 as administrator inquiry destination data. The stored data is temporarily stored as administrator inquiry password data.

In step S63, it is determined whether or not the administrator inquiry password data temporarily stored in step S62 is accurate.
Specifically, the administrator inquiry password data that is preset in the main program 133 and is read as administrator password data when sequentially executed as a process matches the administrator inquiry password data. Is done.
If the data do not match, an error screen is output to the screen of the transfer destination determiner terminal 12 and the administrator inquiry process is completed. If the data match, the process proceeds to step S64.

In step S 64, data for browsing the shipping status and the receiving status is read from the home delivery file 134 and the receiving destination file 135.
Specifically, all records having a destination field that matches the manager inquiry destination data in the forward direction are read from the delivery file 134, and records that match the value of the receipt number field in each record are read from the destination file 135. This is done by temporarily storing aggregated data of newly created records by reading and linking them as administrator inquiry result data.

In step S65, using the administrator inquiry result data, the administrator inquiry result screen shown in FIG. 20 is created and output to the screen of the transfer destination determiner terminal 12.
At this time, if the value in the receipt number field of the corresponding record is not a NULL value, an administrator inquiry receipt detail button 621 that is a button in which the receipt number is described is output.
The transfer destination determiner 10 can browse the destination position information in the corresponding remittance by clicking the desired button in the manager inquiry receipt details button 621 with the mouse of the transfer destination determiner terminal 12. it can.

  In step S66, when the click of any administrator inquiry receipt details button 621 is detected, the receipt number described for the clicked button is temporarily stored as administrator inquiry receipt details receipt number data.

  In step S67, a value matching the administrator inquiry receipt details receipt number data is retrieved from the receipt number field in each record of the administrator inquiry result data, and all the corresponding records are temporarily stored as administrator inquiry result receipt details data. Save to.

  In step S68, using the administrator inquiry result receipt details data, the administrator inquiry result receipt details screen shown in FIG. 21 is created and output to the screen of the transfer destination determiner terminal 12, thereby performing the administrator inquiry processing. Complete.

<Extensibility>
Hereinafter, expandability in the present embodiment will be described.

Even if the hardware and software configurations of the system are changed, processing equivalent to that of the present embodiment is possible.
For example, in the transfer destination determination server 11, the input / output control unit 110 is changed for each communication partner, communication is performed using another network, or the home delivery file 134 and the destination file 135 written in the storage unit 130. Can be made into a database. Further, a web application can be realized by using a web server program instead of the terminal server 132 and using a browser program instead of the terminal client program for each terminal.

  In each terminal and each server, the roles of a plurality of computers can be integrated into one unit, and one function can be divided into a plurality of units.

  In step S11 in the above-described common process, the exclusive process is performed for convenience of explanation. However, by performing a file lock process or the like, it is possible to perform parallel processes on a plurality of terminals.

  In the above-described shipping process, it is also possible to have a contact address and a shipping address for returning goods even if they do not reach the recipient by allowing the sender 20 to separately input an e-mail address, account information, and the like.

  In the above receiving process, after confirming the destination position for the destinations input from the sender 20 and the recipient 30 in step S33, the relationship between the recipient 30 and the destination manager 40 is confirmed in steps S39 to S42. However, it is also possible to confirm the destination position after confirming the relationship by reversing the procedure.

In step S35 in the above-described receiving process, after the relationship confirmation destination data is created, it is confirmed from the contents of communication with the destination server 41 whether data already exists at the destination position indicated by this data. However, this process can be omitted by taking the following procedure.
First, the relationship confirmation destination data is created from the character string data and the reception destination data. At this time, the character string data generates a sufficiently long random character string with the dot in between. For example, the character string data is “A1B2C3d4e5f6g7h8i9J0.0K9L8M7N6o5p4q3r2s1”.
Then, prepare a file to save the relationship confirmation destination data that was used before, check whether it is saved in this file, and if it is not saved, check that it has not been used before. This means that the relationship check destination data is newly saved in a file and used.
In other words, this is to realize the omission of processing by creating relationship confirmation destination data in which the probability that data already exists is reduced as much as possible.

  Since the contents regarding the delivery object are not used for the determination of the transfer destination, it is possible to determine the transfer destination for any delivery object regardless of tangible or intangible.

  Internet users can remit money and deliver to any web page regardless of the country if they only know the URL, so it is easy to send money to their favorite web page and deliver goods. become able to. Further, since the web page manager can receive the delivery object simply by preparing the web page, the work can be expected to be reduced, and the web page manager can concentrate on the production of the web page. In addition, since it is possible to grasp the delivery status for each homepage address, it can be expected to be used for homepage value evaluation and analysis.

DESCRIPTION OF SYMBOLS 10 Transfer destination determiner 11 Transfer destination determination server 12 Transfer destination determiner terminal 20 Shipper 21 Shipper terminal 30 Receiver 31 Receiver terminal 40 Destination manager 41 Destination server 50 Electronic money settlement party 51 Temporary storage destination courier server 60 Financial institution 61 Recipient courier server 71 Public network 110 Input / output control means 120 Control means 130 Storage means 131 OS
132 Terminal server 133 Main program 134 Delivery file 135 Recipient file

Claims (4)

In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
Creating relationship confirmation destination data that is a homepage address indicating another position below the lowest layer that can be obtained from the homepage address of the destination data;
Outputting the relationship confirmation destination data to the recipient terminal;
A relationship for determining whether or not data exists at the position indicated by the relationship confirmation destination data from the content of communication via the network with the destination server that is the server at the location indicated by the relationship confirmation destination data A judgment stage;
A method comprising: determining the destination location data as a transfer destination for the destination data if present in the relationship determination step. In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
Creating a relationship confirmation password data that is a password and outputting it to the recipient terminal;
Whether or not the relationship confirmation password data exists at a specific position in the data at the position indicated by the receiving destination data is determined via a network with a destination server that is a server at the position indicated by the receiving destination data. A relationship determination stage to determine from the communication content of
A method comprising: determining the destination location data as a transfer destination for the destination data if present in the relationship determination step. In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
From the shipper's terminal, entering the shipping address data that is the homepage address;
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
The destination determination step of determining whether the shipping destination data is a position below the lowest layer that can be obtained from the homepage address of the receiving destination data;
Creating relationship confirmation destination data that is a homepage address indicating another position below the lowest layer that can be obtained from the homepage address of the destination data;
Outputting the relationship confirmation destination data to the recipient terminal;
A relationship for determining whether or not data exists at the position indicated by the relationship confirmation destination data from the content of communication via the network with the destination server that is the server at the location indicated by the relationship confirmation destination data A judgment stage;
The method comprising the step of determining the destination location data as a transfer destination for the destination data if it is a position below the lowest layer in the destination judgment step and exists in the relationship judgment step. In the method of determining the forwarding destination from the homepage address,
The forwarding destination determination server
From the shipper's terminal, entering the shipping address data that is the homepage address;
Receiving recipient address data as a homepage address and recipient location data as recipient location information from a recipient terminal;
The destination determination step of determining whether the shipping destination data is a position below the lowest layer that can be obtained from the homepage address of the receiving destination data;
Creating a relationship confirmation password data that is a password and outputting it to the recipient terminal;
Whether or not the relationship confirmation password data exists at a specific position in the data at the position indicated by the receiving destination data is determined via a network with a destination server that is a server at the position indicated by the receiving destination data. A relationship determination stage to determine from the communication content of
The method comprising the step of determining the destination location data as a transfer destination for the destination data if it is a position below the lowest layer in the destination judgment step and exists in the relationship judgment step.

Images