JP7723418B2 - Program, method, and system - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act Racco Co., Ltd. has made public the "program, method, and system" related to the present invention by publishing its services in various media (42 cases, February 1, 2021 - September 21, 2021), SNS (18 cases, January 6, 2021 - November 1, 2021), and its website (61 cases, December 4, 2020 - November 30, 2021).

The present invention relates to a program, a method, and a system.

2. Description of the Related Art In recent years, it has become common for website administrators to transfer the websites they have been running to others, and to transfer the management authority to the others.
For example, Patent Document 1 discloses a system that invites potential buyers to purchase from a case introduction page and connects potential buyers with potential transferees.

Japanese Patent Application Laid-Open No. 2003-122949

The process of transferring a website to another party typically involves preliminary preparations such as confirming the technical specifications and service characteristics of the source and destination servers, moving the site data from the source server to the destination server, transferring the domain, changing DNS settings, and verifying operation. This type of site migration process is not only complicated, but also carries a certain amount of risk, as any flaws in the process could result in data being lost and becoming unrecoverable, or service being suspended after the transfer. Furthermore, the entire process typically takes anywhere from a few days to around two weeks.

The purpose of this disclosure is to provide a system that simplifies the site migration procedures for website transfers and reduces the risks involved in the site migration procedures.

The program disclosed herein is a program to be executed by a computer having a processor and memory, and causes the processor to execute the following steps: accepting a website sales proposal registration from a seller who wishes to transfer the website; displaying transaction information regarding the website to be sold on a sales proposal page; accepting a website purchase proposal from a buyer who wishes to purchase the website; and switching the name on the website domain contract and the management server contract from the seller to the buyer.

The system of the present invention simplifies the site migration procedures for transferring a website, reducing the risks involved in the site migration process.

1 is a diagram showing the overall configuration of a system according to an embodiment of the present invention; FIG. 2 is a block diagram showing the functional configuration of a terminal device included in the system of the present embodiment. FIG. 2 is a diagram showing the configuration of a transaction management server included in the system of this embodiment. FIG. 2 is a diagram showing the configuration of a domain contract management server included in the system of the present embodiment. FIG. 2 is a diagram illustrating a configuration of a server contract management server included in the system of the present embodiment. FIG. 2 is a diagram showing an example of a data table stored in the transaction management server. 10A and 10B are diagrams illustrating examples of data tables stored in a domain contract management server and a server contract management server. FIG. 10 is a diagram showing the process from the site sale registration to the update of the case information management table, among the processes of the system of this embodiment. FIG. 10 is a diagram showing the process from viewing a sales item page to making a purchase proposal, among the processes of the system of this embodiment. FIG. 10 is a diagram showing the process from inputting transaction terms to transmitting information to an electronic contract service, among the processes of the system of this embodiment. FIG. 10 is a diagram showing the process from receiving a report of contract conclusion to notifying receipt of remittance, among the processes of the system of this embodiment. FIG. 10 is a diagram showing the process from a request for a name change of a server contract to a notification of completion of the procedure, among the processes of the system of this embodiment. FIG. 2 is a diagram showing an example of a screen in the system of the present embodiment. 10 is a diagram illustrating the process of transferring a domain in advance to a domain contract management server and the process of signing a server contract in advance to a server contract management server, among the processes of the system of this embodiment. FIG.

One embodiment of the present invention will now be described in detail with reference to the drawings. In the drawings used to explain the embodiment, identical components will generally be assigned the same reference numerals, and repeated explanations will be omitted.

<1. Overview>
The website transaction and management system 1 (simply referred to as system 1) according to this embodiment is a system for managing websites operated by users. System 1 manages website domains and site data, and also executes the procedures required for transferring (selling) the website to another user in accordance with the agreement between the users. In other words, system 1 has the function of managing website-related transactions between users.

<2. Overall structure>
1 is a diagram showing the overall configuration of a system 1 according to this embodiment. As shown in FIG. 1, the system 1 includes a terminal device 10, a transaction management server 20, a domain contract management server 30, and a server contract management server 40.
The terminal device 10, the transaction management server 20, the domain contract management server 30, and the server contract management server 40 are connected to each other via a network 80 using a wired or wireless communication standard so as to be able to communicate with each other.

The terminal device 10 is, for example, a terminal used by a user who operates a website. The terminal device 10 also includes a terminal used by a user who has purchased a website from another user and plans to operate the website in the future.
In the illustrated example, multiple terminal devices 10 are included in the system 1. The number of terminal devices 10 can be changed as desired depending on the number of users. The content of the websites may include a variety of topics, such as blogs about watching anime or movies, or blogs summarizing game strategies.

The terminal device 10 may be realized, for example, as a desktop personal computer (PC) or a laptop PC. The terminal device 10 may also be a portable computer such as a smartphone, tablet, or head-mounted display.

3. Configuration of terminal device 10
Next, the configuration of the terminal device 10 will be described with reference to Fig. 2. Fig. 2A is a diagram showing the hardware configuration of the terminal device 10. Fig. 2B is a diagram showing the functional configuration of the terminal device 10.
As shown in FIG. 2A , the terminal device 10 includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage unit 16 , and a processor 19 .

The communication IF 12 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with external devices.
The input device 13 is an input device for receiving input operations from a user, and includes, for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, and the like.

The output device 14 is an output device for presenting information to a user, and includes, for example, a display, a speaker, and the like.
The memory 15 is for temporarily storing programs and data to be processed by the programs, and is realized by a volatile memory such as a DRAM (Dynamic Random Access Memory).

The storage unit 16 is a storage device for saving data, and is realized by, for example, a flash memory or a hard disk drive (HDD).
The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

As shown in FIG. 2B, the terminal device 10 includes a communication unit 121, an input/output unit 130, a memory unit 170, and a control unit 180. The terminal device 10 also includes functions and configurations not shown in FIG. 2 (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). The blocks included in the terminal device 10 are electrically connected, for example, by a bus or the like.

The communication unit 121 performs processing to enable the terminal device 10 to communicate with other devices. The communication unit 121 performs transmission processing on signals generated by the control unit 180 and transmits them to the outside (e.g., the transaction management server 20). The communication unit 121 performs reception processing on signals received from the outside and outputs them to the control unit 180.

The input/output unit 130 has a mechanism for accepting input operations from the user of the terminal device 10 and displaying output content. Specifically, the input/output unit 130 includes a keyboard 131 and a display 132. The input/output unit 130 may also include other input devices such as a mouse.

The keyboard 131 outputs typed text data to the control unit 180 as an input operation from the user.
The display 132 displays data such as images, videos, and text under the control of the control unit 180. The display 132 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

The storage unit 170 is configured, for example, with flash memory, and stores data and programs used by the terminal device 10.

The control unit 180 is realized when the processor 19 reads a program stored in the storage unit 170 and executes the instructions included in the program. The control unit 180 controls the operation of the terminal device 10. Specifically, for example, the control unit 180 performs the functions of an operation reception unit 181, a transmission/reception unit 182, an acquisition unit 183, and a presentation unit 184.

The operation acceptance unit 181 performs processing to accept user operations input from the input device 13. For example, the operation acceptance unit 181 accepts operations based on text data input to the keyboard 131.

The transmission/reception unit 182 performs processing to enable the terminal device 10 to send and receive data to and from external devices such as the transaction management server 20 in accordance with a communication protocol.

The acquisition unit 183 acquires information input by a user using the terminal device 10. For example, the acquired information may be information input by the user from the keyboard 131 of the terminal device 10. The information acquired by the acquisition unit 183 is transmitted to the transaction management server 20 via the transmission/reception unit 182.
The presentation unit 184 presents various information to the user.

4. Configuration of transaction management server 20
Next, the configuration of the transaction management server 20 will be described with reference to Fig. 3. Fig. 3A is a diagram showing the hardware configuration of the transaction management server 20. Fig. 3B is a diagram showing the functional configuration of the transaction management server 20.
The transaction management server 20 is a server that manages transactions related to the website. The transaction management server 20 is a computer connected to the network 80.

As shown in FIG. 3A, the transaction management server 20 includes a communication IF 22, an input/output IF 23, memory 25, storage 26, and a processor 29.

The communication IF 22 is an interface for transmitting and receiving signals so that the transaction management server 20 can communicate with external devices.
The input/output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the terminal device 10 .

The memory 25 is for temporarily storing programs and data to be processed by the programs, and is realized by a volatile memory such as a DRAM.
The storage 26 is a storage device for saving data, and is realized by, for example, a flash memory or a HDD.
The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

As shown in Figure 3B, the transaction management server 20 functions as a communication unit 201, a memory unit 202, and a control unit 203.

The communication unit 201 performs processing that enables the transaction management server 20 to communicate with external devices.

The storage unit 202 stores data and programs used by the transaction management server 20. For example, the storage unit 202 stores the following data tables.
Account table 281
Case information management table 282
Transaction information management table 283
Each of these data tables will be described in detail later.

The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes the instructions contained in the program. The control unit 203 controls the operation of the transaction management server 20. Specifically, for example, the control unit 203 performs the functions of a transmission/reception unit 2031, a data acquisition unit 2032, a procedure execution unit 2033, a sales item page creation unit 2034, and a notification unit 2035.

The transmission/reception unit 2031 controls the process by which the transaction management server 20 transmits and receives data to and from external devices such as the terminal device 10 in accordance with a communication protocol.

The data acquisition unit 2032 acquires various information received by the transmission/reception unit 2031 and stores it in the memory unit 202. Depending on the content of the acquired information, the data acquisition unit 2032 records it as a new record in each data table stored in the memory unit 202.

The procedure execution unit 2033 executes the procedure for transferring the website based on the information recorded in the storage unit 202 and the information input from the terminal device 10 .
The procedure execution unit 2033 also requests various operations from the domain contract management server 30 and the server contract management server 40. The various operations that the procedure execution unit 2033 requests from the domain contract management server 30 and the server contract management server 40 will be described later.

The sales item page creation unit 2034 creates a sales item page. The sales item page is a bulletin board where administrator users can post items they wish to sell from the various websites managed by the server contract management server 40. From the sales item page, users can carry out procedures such as purchasing the published websites.

The for-sale offer page displays an overview and detailed information about each website that is up for sale. The specific display format of the for-sale offer page will be described later.
The sales item page creation unit 2034 displays the information for each item stored in the item information management table 282 in accordance with the format of the sales item page in response to viewing operations by a user viewing the sales item page.

The notification unit 2036 sends various notifications to the terminal device 10 .
The notification unit 2036 notifies the terminal device 10 of requests for payment, receipt of payment, completion of a transaction, and contract details in a transaction via the sales item page. The details of each of these processes will be described later.

5. Configuration of domain contract management server 30
Next, the configuration of the domain contract management server 30 will be described with reference to Fig. 4. Fig. 4A is a diagram showing the hardware configuration of the domain contract management server 30. Fig. 4B is a diagram showing the functional configuration of the domain contract management server 30.
As shown in FIG. 4A, the domain contract management server 30 includes a communication IF (Interface) 32 , an input/output IF 33 , a memory 35 , a storage 36 , and a processor 39 .

The communication IF 32 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with external devices.
The input/output IF 33 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the terminal device 10 .

Memory 35 is used to temporarily store programs and data processed by the programs, and is realized by volatile memory such as DRAM (Dynamic Random Access Memory).

The storage 36 is a storage device for saving data, and is realized by, for example, a flash memory or a hard disk drive (HDD).
The processor 39 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

As shown in Figure 4B, the domain contract management server 30 functions as a communication unit 301, a memory unit 302, and a control unit 303.

The communication unit 301 performs processing that enables the domain contract management server 30 to communicate with external devices.

The storage unit 302 stores data and programs used by the domain contract management server 30. For example, the storage unit 302 stores the following data tables.
Domain contract information management table 284
This data table will be described in detail later.

The control unit 303 is realized when the processor 39 reads a program stored in the storage unit 302 and executes the instructions contained in the program. The control unit 303 controls the operation of the domain contract management server 30. Specifically, the control unit 303 performs the functions of, for example, a transmission/reception unit 3031, a data acquisition unit 3032, and a domain management unit 3033.

The transmission/reception unit 3031 controls the process by which the domain contract management server 30 transmits and receives data to and from external devices such as the terminal device 10 in accordance with a communication protocol.

The data acquisition unit 3032 acquires various information received by the transmission/reception unit 3031 and stores it in the memory unit 302. Depending on the content of the acquired information, the data acquisition unit 3032 records it as a new record in each data table stored in the memory unit 302.

The domain management unit 3033 manages the domains of websites managed by the domain contract management server 30. The domain management unit 3033 makes name server applications that link domain names with DNS servers. The domain management unit 3033 manages each domain by associating it with the contract name of the user who is the website administrator.

6. Configuration of the server contract management server 40
Next, the configuration of the server contract management server 40 will be described with reference to Fig. 5. Fig. 5A is a diagram showing the hardware configuration of the server contract management server 40. Fig. 5B is a diagram showing the functional configuration of the server contract management server 40.
As shown in FIG. 5A, the server contract management server 40 includes a communication IF (Interface) 42 , an input/output IF 43 , a memory 45 , a storage 46 , and a processor 49 .

The communication IF 42 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with external devices.
The input/output IF 43 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the terminal device 10 .

Memory 45 is used to temporarily store programs and data processed by the programs, and is realized by volatile memory such as DRAM (Dynamic Random Access Memory).

The storage 46 is a storage device for saving data, and is realized by, for example, a flash memory or a hard disk drive (HDD).
The processor 49 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

As shown in FIG. 5B, the server contract management server 40 functions as a communication unit 401, a memory unit 402, and a control unit 403.

The communication unit 401 performs processing that enables the server contract management server 40 to communicate with external devices.

The storage unit 402 stores data and programs used by the server contract management server 40. For example, the storage unit 202 stores the following data tables.
Server contract information management table 285
This data table will be described in detail later.

The control unit 403 is realized when the processor 49 reads a program stored in the storage unit 402 and executes the instructions contained in the program. The control unit 203 controls the operation of the server contract management server 40. Specifically, for example, the control unit 403 performs the functions of a transmission/reception unit 4031, a data acquisition unit 4032, and a server management unit 4033.

The transmission/reception unit 4031 controls the process by which the server contract management server 40 transmits and receives data to and from external devices such as the terminal device 10 in accordance with a communication protocol.

The data acquisition unit 4032 acquires various information received by the transmission/reception unit 4031 and stores it in the memory unit 402. Depending on the content of the acquired information, the data acquisition unit 4032 records it as a new record in each data table stored in the memory unit 402.

The server management unit 4033 manages server contracts. The server management unit 4033 changes the name on the server contract in accordance with input operations. Details will be described later.

8. Data Structure
Fig. 6 is a diagram showing an example of a data table stored in the transaction management server 20. The structure of each data table shown in Fig. 6 is merely an example, and data items not shown may be included.

<8-1. Account table>
6A is a diagram showing an example of the data structure of the account table 281. The account table 281 is a data table for managing user account information.
Each record in the account table 281 includes the following items: "User ID", "Password", "Attributes", "Organization Name", "Name", "Email Address", "Postal Code", "Location", "Telephone Number", "SMS Authentication Flag", "Personal Identity Verification Flag", "Bank Account Information", etc.

The "User ID" item stores an ID for identifying the user.

The "Password" item stores the password that the user corresponding to the user ID is required to enter when logging in to the system 1.

The "Attributes" item stores information about the attributes of the user corresponding to the user ID. Information about user attributes refers to information distinguishing whether the user is an organization such as a corporation, or an individual.

The "Organization Name" field stores the name of the organization to which the user corresponding to the user ID belongs.

The "Name" item stores the name of the user corresponding to the user ID.

The "Email address" item stores the email address of the user corresponding to the user ID.

The "Postal Code" item stores the postal code of the address or residence of the user corresponding to the user ID.

The "Location" item stores the address or location of the user corresponding to the user ID.

The "Phone Number" item stores the phone number of the user corresponding to the user ID.

The "SMS authentication flag" item stores information on whether SMS authentication using the user's phone number, which is performed during user registration, was performed properly.

The "Personal Identification Flag" item stores information about whether or not the user's driver's license or other identification has been verified during user registration. Identification is verified, for example, by the user providing an image of their driver's license.

The item "Bank Account Information" stores information about the bank account that the user uses to pay various bills.
The account table 281 may also store other information.

<8-2. Case information management table>
6B is a diagram showing an example of the data structure of the case information management table 282. The case information management table 282 is a data table for managing information on a website operated by a user.

Each record in the case information management table 282 includes the following items: "Case ID," "Seller User ID," "Name of Main Item for Sale," "URL of Main Item for Sale," "Case Status," "Real-time Transfer Linkage Flag," "Desired Selling Price," "Category," "Access Data," "Income and Expenditure Information," "Summary," etc.

The "Item ID" field stores an ID for identifying the website that is the item for sale.

The "Seller User ID" item stores the user ID of the seller of the website identified by the project ID.

The "Name of Main Item for Sale" field stores the name of the website identified by the item ID.

The "URL of the main item for sale" field stores the URL of the website identified by the item ID.

The "Project Status" field stores the status of the website identified by the project ID. Website statuses include "Under review," "Listed," "Seller determined," and "Deal completed."

The project status "Under review" indicates that the website's operational status is being checked and its asset value is being reviewed. The status equivalent to "Under review" may also be expressed as "Preparing for listing."
The "listed" project status indicates that the project has been registered for sale and is listed on the sales project page. The status equivalent to "listed" may also be expressed as "open for sale."

The item status "Seller Decided" indicates that the item has accepted a purchase proposal from the user who wishes to sell.
The case status "concluded" indicates that a contract has been concluded between the user wishing to sell and the user wishing to purchase, and all transactions have been completed.

The "Real-time transfer linkage flag" item stores information about whether the website identified by the case ID is linked to real-time transfers executed by the system 1. Specifically, in order to perform a real-time transfer, the website must already be managed by the domain contract management server 30 and the server contract management server 40, and multiple websites must not be managed by the server account ID.

The "Desired Selling Price" item stores the selling price desired by the seller for the website identified by the item ID.

The "Category" item stores the website category identified by the case ID. A website category is a division that indicates the content of the website, such as sports, anime, games, movies, etc.

The "Access Data" item stores data regarding access to the website identified by the case ID.

The "Income and Expenditure Information" item stores income and expenditure information for the operation of the website identified by the project ID.

The item "Summary" stores an explanatory text that shows the summary of the website identified by the case ID.
The case information management table 282 may also store other information.

<8-3. Transaction Information Management Table>
4C is a diagram showing an example of the data structure of the transaction information management table 283. The transaction information management table 283 is a data table for managing information related to transactions on a website between users.

Each record in the transaction information management table 283 includes the following items: "Transaction ID," "Project ID," "Seller User ID," "Buyer User ID," "Transaction Status," "Agreed Amount," "Transaction Terms," "Contractor Information," etc.

The "Transaction ID" item stores an ID for identifying a transaction related to a sales item.

The "Project ID" item stores the project ID of the website that is the subject of the transaction identified by the transaction ID.

The "Seller User ID" item stores the user ID of the user selling the website in the transaction identified by the transaction ID.

The "Buyer User ID" item stores the user ID of the user who purchases the website in the transaction identified by the transaction ID.

The "Transaction Status" item stores the status of the transaction identified by the transaction ID. Transaction statuses include "Negotiation Request," "Negotiation in Progress," "Confirmation of Transaction Terms," "Contract Creation," "Escrow Deposit," "Site Migration/Inspection," and "Transaction Completed." Each of these statuses corresponds to a transaction-related process, described below, and the status is updated as the transaction progresses.

The "Agreed Amount" item stores the amount agreed upon between the users as the selling price for buying and selling the website in the transaction identified by the transaction ID.

The "Transaction Terms" item stores the various conditions for the transaction identified by the transaction ID. Specifically, the various conditions refer to items to be included in the contract, such as the deadline for site migration, training period, operational support period, and non-compete period.

The item "Contractor Information" stores information about the contractors in the transaction identified by the transaction ID, that is, information about the seller user and the buyer user.
The transaction information management table 283 may also store other information.

<8-4. Domain Contract Information Management Table>
FIG. 7 is a diagram showing an example of a data table stored in the domain contract management server 30 and the server contract management server 40. As shown in FIG.
7A is a diagram showing an example of the domain contract information management table 284 stored in the domain contract management server 30. The domain contract information management table 284 is a data table for managing information related to domain contracts.

Each record in the domain contract information management table 284 includes the following items: "Domain ID," "Domain name," "Status," "User ID (owner)," "Expiration date," and "Administrator lock flag."

The "Domain ID" item stores an ID for identifying the domain managed by the domain contract management server 30.

The "Domain Name" item stores the name of the domain identified by the domain ID.

The "Status" item stores the status of the domain identified by the domain ID.

The "User ID (Owner)" field contains the user ID of the domain identified by the domain ID.

The "Expiration Date" item stores the expiration date of the domain identified by the domain ID.

The "Administrator Lock Flag" item stores information indicating whether the domain identified by the domain ID has been locked (operation restricted) by the administrator.

<8-5. Server Contract Information Management Table>
7B is a diagram showing an example of the server contract information management table 285 stored in the server contract management server 40. The server contract information management table 285 is a data table for managing information related to server contracts.

Each record in the server contract information management table 285 includes the following items: "Server account ID," "Login information," "Plan," "Status," "User ID (owner)," "Expiration date," "Add-on domain information," and "Administrator lock flag."

The "Server Account ID" item stores an ID that identifies the server contract managed by the server contract management server 40.

The "Login Information" item stores the login information that you are required to enter when logging in to the server account identified by the server account ID.

The "Plan" item stores information indicating the contract plan for the server account identified by the server account ID.

The "Status" item stores the status of the server account identified by the server account ID.

The "User ID (Owner)" item stores the user ID of the user who owns the server account identified by the server account ID. The user who owns the server contract is the owner of the website that is being sold.

The "Expiration Date" item stores information indicating the expiration date of the server account identified by the server account ID.

The "Add-on Domain Information" item stores a list of domain names linked to the server contract management server 40.

The "Administrator Lock Flag" item stores information indicating whether the server account identified by the server account ID has been locked (operation restrictions imposed) by the administrator.

9. System processing flow
The processing by the system 1 will be described below with reference to FIGS.
FIG. 8 is a diagram showing the process from the site sale registration to the update of the case information management table 282 among the processes of the system of this embodiment.

First, a user wishing to sell a website that they manage operates the terminal device 10 to register a sale offer for the website (step S111). Registering a sale offer is an expression of intent to sell the website.

After step S111, the transaction management server 20 accepts the registration of a sales proposal (step S211). At this time, the data acquisition unit 2032 of the transaction management server 20 changes the proposal status in the proposal information management table 282 to "Under review." At this point, a review is conducted by the operator of system 1. During the review, the website desired for sale is properly managed and is examined to determine whether it can be the subject of a transaction. If the review is passed, the processing of step S212 is executed. If the review is not passed, the sales transaction is not approved and the procedure ends.

After step S211, the transaction management server 20 requests operation restrictions from the domain contract management server 30 and the server contract management server 40 (step S212).
After step S212, the domain contract management server 30 imposes operational restrictions on the domain contract so as to restrict changes to the domain contract (step S311), which causes the data acquisition unit 3032 of the domain contract management server 30 to turn on the administrator lock flag in the domain contract information management table 284.

After step S212, the server contract management server 40 is subjected to operation restriction for the server contract (step S411). As a result, the data acquisition unit 4032 of the server contract management server 40 turns on the administrator lock flag in the server contract information management table 285.
Steps S311 and S411 prevent the seller who operates the website from changing settings related to the display of the website, adding domain settings that are not subject to transfer, canceling the contract, changing the management company, etc. This allows the individual contracts, namely the domain contract and the server contract, to be established as a single unit called the website, and the transferable state is maintained.

After step S212, the transaction management server 20 updates the item information management table 282 so that the website can be published as a sales item (step S213). Specifically, the sales item page creation unit 2034 of the transaction management server 20 updates the sales item page. At this time, the item status of the website in the item information management table 282 becomes "listed."

FIG. 9 is a diagram showing the process from viewing the sales item page to making a purchase proposal, among the processes of the system of this embodiment.
A prospective purchaser who wishes to purchase a website accesses the transaction management server 20 from the terminal device 10 and views the sales item page (step S121).

After step S121, the prospective purchaser makes a negotiation request. Specifically, the terminal device 10 accepts the negotiation request operation (step S122).
After step S122, the transaction management server 20 updates the transaction information management table 283 based on the negotiation request entered by the prospective purchaser (step S221). Specifically, the transaction status in the transaction information management table 283 is updated to "Negotiation Request."

After step S221, the transaction management server 20 notifies the seller of the negotiation offer (step S222).
After step S222, if the seller-desiring user approves the negotiation application, step S131 is executed on the terminal device 10. Specifically, the terminal device 10 of the seller-desiring user accepts an operation to approve the negotiation application from the seller-desiring user (step S131).
On the other hand, if the seller does not approve the negotiation request, the negotiation ends.

After step S131, the transaction management server 20 updates the transaction status in the transaction information management table 283 to "under negotiation" and discloses the website information to the user wishing to purchase (step S223). At this time, the transaction management server 20 also notifies each user that negotiations have begun. This initiates negotiations between the two parties. The transaction management server 20 accepts chat messages exchanged between users.

After step S223, if the prospective buyer wishes to purchase under the purchase conditions agreed upon with the prospective seller, the prospective buyer operates to make a purchase proposal under the purchase conditions. The prospective buyer's terminal device 10 accepts the purchase proposal operation (step S123). If the prospective buyer does not agree to the purchase conditions, the negotiation status can be maintained. During the negotiation status, both the prospective buyer and the prospective seller can end the negotiation at any time.

If negotiations are to continue, after step S123, the transaction management server 20 receives a purchase proposal from the user wishing to purchase (step S224). At this time, the transaction management server 20 notifies the terminal device 10 used by the user wishing to sell of the received purchase proposal.

After step S224, the seller approves the purchase proposals from users who are willing to transfer the items (step S132). Specifically, the terminal device 10 accepts an operation to approve the purchase proposals. The terminal device 10 notifies the transaction management server 20 of the result.
Purchase proposals may be received from multiple users wishing to purchase. In this case, the user wishing to sell selects any one of the multiple purchase proposals. If the user wishing to sell does not approve the purchase proposal, the status of the purchase proposal will remain under negotiation.

After step S132, the transaction management server 20 receives approval of the purchase proposal (step S225). At this time, the transaction management server 20 changes the case status in the case information management table 282 to "Seller determined." The transaction management server 20 also updates the transaction status in the transaction information management table 283 to "Transaction terms confirmed."

FIG. 10 is a diagram showing the processing from input of transaction terms to transmission of information to the electronic contract service, among the processing of the system of this embodiment.
After step S224, the terminal device 10 receives input of transaction conditions from the seller (step S151). Transaction conditions include various conditions to be included in the contract, such as a non-competition period and an inspection period.

After step S151, the transaction management server 20 requests confirmation of the transaction terms from the terminal device 10 of the user wishing to purchase (step S226).

After step S226, the terminal device 10 of the user wishing to purchase accepts approval of the transaction conditions (step S141). Specifically, the user wishing to sell confirms the transaction conditions presented by the transaction management server 20 and approves them. The terminal device 10 returns the entered approval operation to the transaction management server 20.

After step S141, the transaction management server 20 creates a contract (step S227). The contract is created based on the approved transaction terms. At this time, the transaction status in the transaction information management table 283 is changed to "Contract created."

After step S227, the terminal device 10 of the seller accepts a request to check the contract (step S152). Specifically, the seller checks the contract and indicates to the terminal device 10 that there are no problems. The terminal device 10 returns the results to the transaction management server 20.

After step S152, the transaction management server 20 requests the terminal device 10 of the user wishing to purchase to confirm the contract (step S228). Specifically, the contract checked by the user wishing to sell is sent to the user wishing to purchase, and the user is asked to enter a response as to whether there are any problems.

After step S228, the terminal device 10 of the prospective purchaser accepts approval of the contract (step S142). Specifically, the prospective purchaser checks the contract and indicates to the terminal device 10 that there are no problems. The terminal device 10 returns the result to the transaction management server 20.

If either the seller or the buyer wishes to amend the contents of the contract, one of the following procedures is carried out.
・If you want to change only the values defined within the transaction conditions, the seller must start over by entering the transaction conditions.
- Download the automatically generated contract, modify it, and upload it as a PDF.
- Create all original contracts and upload them as PDF data.
After performing one of the above, the contract will be confirmed again with the user who wishes to purchase.

After step S142, the transaction management server 20 sends information to the electronic contract service (step S229). Specifically, the transaction management server 20 provides the electronic contract service with information about the user wishing to sell and the user wishing to purchase, as well as information about the contents of the contract, and causes the service to conclude an electronic contract. The transaction management server 20 and the electronic contract service are API-linked.

FIG. 11 is a diagram showing the process from receiving a report of the conclusion of the contract to notifying receipt of remittance, among the processes of the system of this embodiment.
After step S229, the transaction management server 20 receives a report of the conclusion of the contract from the electronic contract service (step S231).

After step S231, the transaction management server 20 requests an escrow transfer from the terminal device 10 of the prospective buyer (step S232). An escrow transfer is a method of remittance in which the purchase price is temporarily held by the prospective buyer, and after confirming that the item to be transferred has been properly transferred, the sale price is paid to the prospective seller. At this time, the transaction management server 20 designates a bank account to which the prospective buyer will transfer the money. The prospective buyer transfers the money to the designated bank account. At this time, the transaction status in the transaction information management table 283 is also changed to "Escrow Deposit."

After step S232, the transaction management server 20 receives notification that the escrow transfer has been properly completed (step S233). Accordingly, the transaction management server 20 updates the transaction status in the transaction information management table 283 to "Site migration/inspection."

After step S233, the transaction management server 20 notifies the terminal devices 10 of the purchasing user and the selling user that the remittance from the purchasing user has been received (step S234).

Figure 12 shows the processing of the system in this embodiment, from requesting a name change for a server contract to notifying the completion of the procedure.

After step S234, the transaction management server 20 requests the server contract management server 40 to change the name of the server contract (step S241). The request to change the name of the server contract is triggered by the receipt of the escrow remittance (step S233).

After step S241, the server contract management server 40 changes the name on the server contract (step S421). This changes the contract holder of the server account from the user wishing to sell to the user wishing to purchase.

After step S421, the server contract management server 40 assigns new login information and notifies the purchasing user (step S422). At this time, the server management unit 4033 of the server contract management server 40 takes over the server account related to the server contract as is, and issues a random password corresponding to the server account and changes it. The data acquisition unit 4032 uses the assigned login information to update the login information and user ID in the server contract information management table 285. At this time, operation restrictions on the server contract are also lifted.

After step S422, the terminal device 10 of the purchasing user receives new login information (step S161).

After step S234, the transaction management server 20 requests the domain contract management server 30 to change the domain name (step S242). The request to change the domain name is triggered by the receipt of the escrow remittance (step S233).

After step S242, the domain contract management server 30 changes the name of the domain (step S321). The domain management unit 3033 of the domain contract management server 30 updates the user ID in the domain contract information management table 284. At this time, operational restrictions on the domain contract are also lifted.

After step S321, the transaction management server 20 notifies both the prospective buyer and seller of the domain and server name change by email (step S243). The notification informs them that the name change is complete, instructs them to transfer any other assets that need to be transferred, and instructs the prospective buyer to perform an inspection once the transfer is complete. This allows the prospective buyer to begin inspection work, including checking the operation of the purchased website. In other words, in a real-time transfer performed by this system, the website transfer between users is completed through steps S421 and S321.

After step S243, the terminal device 10 accepts an operation to indicate that the inspection has been completed (step S162). Specifically, the prospective buyer inputs to the terminal device 10 that the inspection has been carried out and there are no problems. If a problem arises during the inspection, this is communicated and a request to cancel the transaction is sent to the prospective seller. If the prospective seller approves this, the contract is terminated. If the contract is terminated, the item to be transferred that has already been transferred to the prospective buyer is returned to the prospective seller.

After step S162, the transaction management server 20 transfers the selling price from the seller (step S244). In other words, provided that inspection is complete, the seller can receive the payment (sale price) due for the sale of the website. The sales price received by the seller is equivalent to the purchase price paid by the buyer minus a specified fee.

After step S244, the transaction management server 20 notifies the seller and buyer users that the procedures have been completed (step S245). This completes all procedures related to the transfer of the website. At this time, the transaction status in the transaction information management table 283 is changed to "Transaction Completed." In addition, the case status in the case information management table 282 is changed to "Deal Completed."

<10. Screen example>
Next, with reference to Fig. 13, an example of a screen of the system 1 will be described. Fig. 13 is a diagram showing an example of a first screen of the system 1. The example of the first screen is a diagram showing a sales proposal page that publishes websites that are the subject of buying and selling in the system 1.

As shown in Figure 13, the sales proposal page displays an overview of the websites managed by the server contract management server 40 in a list format (L1, L2, L3, ...). On the left side of the screen, there is a search field A for searching for websites.

In search field A, you can narrow down your website search by criteria such as "tag," "type," "status," "keywords," "category," "revenue model," "desired selling price," "sales," "page views," "number of articles," "number of users," and "total number of social media followers."

The tag refers to the label displayed in the bottom right of each listing. Among these, the listings marked "Real-time Transfer" allow for the immediate transfer of the website by changing the name on the domain and server contracts mentioned above.
Furthermore, the tag "PICK UP" is attached to recommended cases with favorable transaction conditions among the cases managed by the transaction management server 20.
In addition, the tag "Site migration available" is used for cases where real-time sales are not possible, but the site migration procedures can be handled by the service provider of this system.

Each listing includes evaluation indicators for each project, such as "site name,""askingprice,""operatingprofit,""sales,""PV,""number of views,""number of negotiation applications," and "release date." Additionally, the main evaluation indicators are visualized using radar charts.
Clicking on the site name will display detailed information about the website.

11. Modifications
Next, a modified example of the system 1 will be described. In the above embodiment, it is assumed that the website to be bought and sold is already managed by the domain contract management server 30 and the server contract management server 40. In contrast, in this modified example, the process of having the website managed by the domain contract management server 30 and the server contract management server 40 will be described. That is, the process performed as pre-processing for the sales proposal registration (step S111) shown in FIG. 8 will be described. Specifically, it is assumed that a user starts using a server (rental server) managed by the server contract management server 40.
At this time, the user makes a request from the terminal device 10 to have the domain of the website that the user operates managed by the domain contract management server 30. Specifically, the terminal device 10 receives a request for domain management (step S101).

After step S101, the domain contract management server 30 manages the domain (step S301). As a result, the management authority of the domain is transferred to the domain contract management server 30.
Specifically, the domain transfer will be carried out according to the following procedure.
・Prepare for the transfer at the original registrar (cancel WHOIS information proxy publication, unlock domain, obtain AUTHCODE, etc.)
- Submit a transfer application (transfer-in) to the domain contract management server 30 to which the domain will be transferred.
- The transfer will be approved (transferred out) by the original registrar.
・Transfer completed

After step S301, the terminal device 10 exports the site data (step S102). Specifically, in order to extract the site data from the source server, the terminal device 10 downloads the site configuration file from the server and exports and downloads SQL data from the database.

After step S102, the terminal device 10 accepts a contract request for the destination server (step S103). Specifically, the user operates the terminal device 10 to apply for a server contract with the server contract management server 40.

After step S103, the server contract management server 40 concludes a server contract (step S401). As a result, a new record is recorded in the server contract information management table 285, and a new server account ID is issued. The new server account created in step S401 is issued when the server contract is applied for (step S103), and is immediately available for use.

After step S401, the terminal device 10 installs the site data on the destination server (step S104).

After step S104, the terminal device 10 receives a request to change the DNS (step S105).
After step S105, the domain contract management server 30 changes the DNS (step S302), thereby associating the IP address of the new server with the domain.

This completes the process of transferring the managed website from another server to a server under the management of the server contract management server 40.
After this process, the process of registering a sale item (step S111) shown in FIG. 8 may be performed.

<12. Summary>
As described above, in the system 1 according to this embodiment, after accepting a proposal to purchase a website from a user wishing to purchase, the transaction management server 20 instructs the domain contract management server 30 to change the name of the domain contract for the website. The transaction management server 20 also instructs the server contract management server 40 to change the name of the server contract. This allows the ownership of a website to be transferred from the user wishing to sell to the user wishing to purchase by simply changing the contract names for the domain and server, without transferring website data between servers or involving domain transfer procedures. This simplifies the website migration procedure for transferring a website and reduces the risks involved in the site migration procedure.

Furthermore, after accepting the registration of a sales proposal, the transaction management server 20 imposes certain operational restrictions on the domain contract and server contract that make up the website to be transferred. In other words, by restricting changes to the domain contract and settings, it is possible to prevent the seller from transferring the domain to another person or making unintended changes. Furthermore, by restricting changes to the server contract and settings, it is possible to prevent other sites from being added to the server account or making unintended changes. This allows the individual contracts, the domain contract and server contract, to be established as a single unit called a website, and to maintain a transferable state.

Furthermore, after detecting payment of the purchase price from the prospective purchaser, the transaction management server 20 switches the domain name and the contract with the server contract management server 40 upon detecting payment of the purchase price. This prevents the procedure from proceeding while the purchase price remains unpaid.

The transaction management server 20 also executes a step of changing the password of the server account related to the management server contract to a randomly issued password used by the prospective buyer, thereby allowing the prospective seller to appropriately change the password of the server account related to the management server contract for the prospective buyer.
If the website is managed by a CMS or the like, the login information for the CMS may also be changed, or the login information for the CMS may be left unchanged and carried over as is.

The transaction management server 20 also notifies the prospective purchaser of the login information, including the changed password. This allows the prospective purchaser to properly understand the changed login information. If the CMS login information has been changed, the transaction management server 20 notifies the prospective purchaser of the changed login information.

By using this system 1, users wishing to sell can shorten the lead time, which is the most time-consuming part of transferring a website. Conventional procedures would normally take anywhere from a few days to two weeks, but this can be completed by simply changing the name on the domain and server contracts, allowing for real-time (instant) site transfers.

Furthermore, by simplifying and reducing the risk of transferring websites, removing barriers to transferring websites, and shortening the lead time for transactions, it is expected that the liquidity of the website market will be improved.
As a result, sellers can quickly and safely sell their websites and quickly convert them into cash. Buyers can quickly and safely purchase websites and quickly earn profits from them. Intermediaries operating this system 1 can expect an improved success rate in website transfer contracts, higher website purchase prices, improved asset values, and increased commission income.

While the above describes preferred embodiments of the present disclosure, the present disclosure is not limited to such specific embodiments, and includes the inventions set forth in the claims and their equivalents. Furthermore, the device configurations described in the above embodiments and variations can be combined as appropriate, provided no technical contradictions arise.

<Additional Notes>
The matters described in the above embodiments will be supplemented below.

(Appendix 1)
A program to be executed by a computer having a processor and a memory, the program causing the processor to:
A step of accepting a website sales proposal registration from a user who wishes to transfer the website (step S211);
Displaying transaction information about the website to be sold on a sales item page (step S213);
A step of accepting a proposal to purchase the website from a prospective purchaser who wishes to purchase the website (step S224);
and a program for executing steps (steps S241 and S242) of switching the name of the website domain contract and the name of the management server contract from the user wishing to sell to the user wishing to purchase.

(Appendix 2)
After the step of accepting the sales proposal registration (step S211),
The program described in Appendix 1 executes a step (step S212) of imposing certain operational restrictions on the domain contract and server contract that constitute the website to be transferred.

(Appendix 3)
After receiving a purchase offer from the website (step S211), a step of detecting payment of the purchase price from the prospective purchaser (step S233) is executed;
The program described in Appendix 1 or 2, which switches the name of the domain contract and the name of the server contract when the detection of the payment is triggered.

(Appendix 4)
In the step of switching the name of the website domain contract and the name of the management server contract from the user who wishes to sell to the user who wishes to purchase (steps S241 and S242),
4. The program according to any one of appendices 1 to 3, which executes a step (step S422) of changing the password of the server account related to the contract of the management server to the password used by the prospective purchaser.

(Appendix 5)
The program according to appendix 4, which executes a step (step S422) of notifying the prospective purchaser of login information including the changed password.

(Appendix 6)
Before the step of accepting sales proposal registration on the website,
A step of requesting management of a website domain from a system that manages domain contracts (step S101);
The program according to any one of appendices 1 to 5, which executes the steps of: installing site data constituting the website in a management server (step S104).

(Appendix 7)
A method for execution by a computer having a processor and a memory, the method comprising the processor:
A step of accepting a website sales proposal registration from a user who wishes to transfer the website (step S211);
Displaying transaction information about the website to be sold on a sales item page (step S213);
A step of accepting a proposal to purchase the website from a prospective purchaser who wishes to purchase the website (step S224);
and a step of switching the name of the website domain contract and the name of the management server contract from the user wishing to sell to the user wishing to purchase (steps S241, S242).

(Appendix 8)
A system comprising a computer having a processor and a memory, wherein the processor in the system
a module (2032) for accepting registration of a website sale proposal from a user who wishes to transfer the website;
a module (2034) for displaying transaction information about the website to be sold on a sales item page;
a module (2032) for receiving a proposal to purchase the website from a prospective purchaser who wishes to purchase the website;
and a module (2033) for switching the name of the website domain contract and the name of the management server contract from the user wishing to sell to the user wishing to purchase.

1... System 10... Terminal device 13... Input device 14... Output device 15... Memory 16... Storage unit 19... Processor 20... Server 201... Communication unit 202... Storage unit 203... Control unit 25... Memory 26... Storage 29... Processor

Claims (7)

A program to be executed by a transaction management server that is a server that manages transactions related to a website, the program comprising a processor and a memory, the program causing the processor to:
A step of accepting registration of a sale proposal for the website from a user who wishes to transfer the website;
a step of requesting a domain contract management server that manages a domain contract constituting the website to restrict operations related to changes to the domain contract;
a step of requesting a server contract management server that manages a contract for a management server that constitutes the website to restrict operations related to changes to the contract for the management server that constitutes the website ;
displaying transaction information about the website on a sales listing page;
receiving a proposal to purchase the website from a prospective purchaser who wishes to purchase the website;
a step of requesting the server contract management server to release operational restrictions related to changes in the contract of the management server constituting the website and to change the name of the contract in order to switch the name of the contract of the management server constituting the website from the user wishing to sell to the user wishing to purchase;
A program that executes a step of requesting the domain contract management server to lift operational restrictions regarding changes to the domain contract and change the name of the domain contract for the website, in order to switch the name of the domain contract from the user wishing to sell to the user wishing to purchase. after the step of accepting a purchase offer from the website, a step of detecting payment of the price for the purchase from the prospective purchaser is executed;
2. The program according to claim 1, wherein detection of the payment is used as a trigger to switch the name of the domain contract holder and the name of the contract holder for the management server that constitutes the website. In a step of switching the name of the domain contract for the website and the name of the contract for the management server constituting the website from the user wishing to sell to the user wishing to purchase,
3. The program according to claim 1, further comprising a step of changing a password of a server account related to a contract for said management server constituting said website to a password used by said prospective purchaser. The program described in claim 3 executes a step of notifying the prospective purchaser of login information including the changed password. Before the step of accepting registration of a sale proposal on the website,
requesting management of the domain of the website from a system for managing domain contracts;
5. The program according to claim 1, further comprising: a step of installing site data constituting the website in the management server constituting the website . A method for causing a transaction management server, which is a server that manages transactions related to a website, to execute the method, the method comprising:
A step of accepting registration of a sale proposal for the website from a user who wishes to transfer the website;
a step of requesting a domain contract management server that manages a domain contract constituting the website to restrict operations related to changes to the domain contract;
a step of requesting a server contract management server that manages a contract for a management server that constitutes the website to restrict operations related to changes to the contract for the management server that constitutes the website ;
displaying transaction information about the website on a sales listing page;
receiving a proposal to purchase the website from a prospective purchaser who wishes to purchase the website;
a step of requesting the server contract management server to release operational restrictions related to changes in the contract of the management server constituting the website and to change the name of the contract in order to switch the name of the contract of the management server constituting the website from the user wishing to sell to the user wishing to purchase;
A method for executing a step of requesting the domain contract management server to lift operational restrictions on changes to the domain contract and to change the name of the domain contract for the website, in order to switch the name of the domain contract from the user wishing to sell to the user wishing to purchase. A system including a transaction management server that is a server that manages transactions related to a website, the transaction management server including a processor and a memory, the processor in the system
a module for accepting registration of a sale proposal for the website from a user who wishes to transfer the website;
a module for requesting a domain contract management server that manages a domain contract constituting the website to restrict operations related to changes to the domain contract;
a module for requesting a server contract management server that manages a contract for a management server that constitutes the website to restrict operations related to changes to the contract for the management server that constitutes the website ;
a module for displaying transaction information about the website on a sales listing page;
a module for receiving a proposal to purchase the website from a prospective purchaser who wishes to purchase the website;
a module for requesting the server contract management server to release operational restrictions related to changes in the contract of the management server constituting the website and to change the name of the contract in order to switch the name of the contract of the management server constituting the website from the user wishing to sell to the user wishing to purchase;
A system comprising: a module that requests the domain contract management server to lift operational restrictions regarding changes to the domain contract and change the name of the domain contract for the website, in order to switch the name of the domain contract from the user wishing to sell to the user wishing to purchase.