Program, method, and system

Abstract

To reduce the risk of procedures for a site migration related to a transfer of a website by simplifying the procedures for the site migration.SOLUTION: A program causing a computer including a processor and a memory to execute processing including the steps of: receiving registration of a website selling case from a user who wishes to transfer the website; displaying information related to a transaction of the website to be traded on a selling case page; receiving a purchase proposal for the website from a user who wishes to purchase the website; and changing the name of a domain contract of the website and the name of a contract of a management server from the user who wishes to sell the website to the user who wishes to purchase the website.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a program, a method, and a system. [Background technology]

[0002] 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. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-122949 Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, the process of transferring a website to another party 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 cumbersome, but also carries a certain amount of risk, as any flaws in the process could result in data being lost and becoming unrecoverable, or the website being suspended after the transfer. Furthermore, the entire process typically takes anywhere from a few days to two weeks.

[0005] The present disclosure aims to provide a system that simplifies the site migration procedure for transferring a website and reduces the risks involved in the site migration procedure. [Means for solving the problem]

[0006] The program of the present disclosure is a program to be executed by a computer having a processor and memory, and causes the processor to execute the steps of accepting registration of a website sales proposal from a seller who wishes to transfer the website; displaying information regarding the transaction for 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 name on the management server contract from the seller to the buyer. [Effects of the Invention]

[0007] According to the system of the present invention, the site transfer procedure for transferring a website can be simplified and the risks involved in the site transfer procedure can be reduced. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram showing the overall configuration of a system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing the functional configuration of a terminal device included in the system of the present embodiment. [Figure 3] FIG. 2 is a diagram showing the configuration of a transaction management server included in the system of this embodiment. [Figure 4] FIG. 2 is a diagram showing the configuration of a domain contract management server included in the system of the present embodiment. [Figure 5] FIG. 2 is a diagram illustrating a configuration of a server contract management server included in the system of the present embodiment. [Figure 6] FIG. 2 is a diagram showing an example of a data table stored in the transaction management server. [Figure 7] 10A and 10B are diagrams illustrating examples of data tables stored in a domain contract management server and a server contract management server. [Figure 8] 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. [Figure 9] 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. [Figure 10] 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. [Figure 11] 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. [Figure 12] 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. [Figure 13] FIG. 2 is a diagram showing an example of a screen in the system of the present embodiment. [Figure 14] 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. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and repeated description thereof will be omitted.

[0010] <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.

[0011] <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.

[0012] 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 website may include a variety of topics, such as blogs about watching anime or movies, or blogs summarizing game strategies.

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

[0014] 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.

[0015] The communication IF 12 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with an external device. 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.

[0016] 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).

[0017] The storage unit 16 is a storage device for saving data, and is realized by, for example, a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

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

[0019] The communication unit 121 performs processing for 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 (for example, 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.

[0020] The input / output unit 130 has a mechanism for accepting input operations from the user who owns the terminal device 10 and displaying output contents. 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.

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

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

[0023] The control unit 180 is realized by the processor 19 reading a program stored in the storage unit 170 and executing instructions included in the program. The control unit 180 controls the operation of the terminal device 10. Specifically, for example, the control unit 180 fulfills the functions of an operation reception unit 181, a transmission / reception unit 182, an acquisition unit 183, and a presentation unit 184.

[0024] The operation accepting unit 181 performs processing for accepting user operations input from the input device 13. For example, the operation accepting unit 181 accepts operations based on text data input to the keyboard 131.

[0025] The transmitting / receiving unit 182 performs processing for the terminal device 10 to transmit and receive data to and from external devices such as the transaction management server 20 in accordance with a communication protocol.

[0026] The acquisition unit 183 acquires information entered by a user using the terminal device 10. For example, the acquired information may be information entered 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.

[0027] <4. Configuration of the 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 a network 80.

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

[0029] 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.

[0030] 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.

[0031] As shown in FIG. 3B, the transaction management server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0032] The communication unit 201 performs processing for the transaction management server 20 to communicate with external devices.

[0033] 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 ·Project information management table 282 Transaction information management table 283 Each of these data tables will be described in detail later.

[0034] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. The control unit 203 controls the operation of the transaction management server 20. Specifically, for example, the control unit 203 functions as 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.

[0035] The transmitting / receiving unit 2031 controls the process in 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.

[0036] The data acquisition unit 2032 acquires various pieces of information received by the transmission / reception unit 2031 and stores them in the storage unit 202. The data acquisition unit 2032 records the acquired information as a new record in each data table stored in the storage unit 202, depending on the content of the information.

[0037] 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.

[0038] The sales item page creation unit 2034 creates a sales item page. The sales item page is a bulletin board where administrator users publish items they wish to sell from 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.

[0039] 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 sale 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 sale item page in response to a viewing operation by a user viewing the sale item page.

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

[0041] <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.

[0042] The communication IF 32 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with an external device. 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.

[0043] The memory 35 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).

[0044] The storage 36 is a storage device for saving data, and is realized by, for example, a flash memory or an HDD (Hard Disc Drive). 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.

[0045] As shown in FIG. 4B, the domain contract management server 30 functions as a communication unit 301, a storage unit 302, and a control unit 303.

[0046] The communication unit 301 performs processing for the domain contract management server 30 to communicate with external devices.

[0047] 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.

[0048] The control unit 303 is realized by the processor 39 reading a program stored in the storage unit 302 and executing instructions included in the program. The control unit 303 controls the operation of the domain contract management server 30. Specifically, for example, the control unit 303 fulfills the functions of a transmission / reception unit 3031, a data acquisition unit 3032, and a domain management unit 3033.

[0049] The transmitting / receiving unit 3031 controls the process in 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.

[0050] The data acquisition unit 3032 acquires various pieces of information received by the transmission / reception unit 3031 and stores them in the storage unit 302. The data acquisition unit 3032 records the acquired information as a new record in each data table stored in the storage unit 302, depending on the content of the information.

[0051] The domain management unit 3033 manages the domains of websites managed by the domain contract management server 30. The domain management unit 3033 makes a name server application that links 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 administrator of the website.

[0052] <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.

[0053] The communication IF 42 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with an external device. 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.

[0054] The memory 45 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).

[0055] The storage 46 is a storage device for saving data, and is realized by, for example, a flash memory or an HDD (Hard Disc Drive). 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.

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

[0057] The communication unit 401 performs processing for the server contract management server 40 to communicate with external devices.

[0058] 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.

[0059] The control unit 403 is realized by the processor 49 reading a program stored in the storage unit 402 and executing instructions included in the program. The control unit 203 controls the operation of the server contract management server 40. Specifically, for example, the control unit 403 fulfills the functions of a transmission / reception unit 4031, a data acquisition unit 4032, and a server management unit 4033.

[0060] The transmitting / receiving unit 4031 controls the process in 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.

[0061] The data acquisition unit 4032 acquires various pieces of information received by the transmission / reception unit 4031 and stores them in the storage unit 402. The data acquisition unit 4032 records the acquired information as a new record in each data table stored in the storage unit 402, depending on the content of the information.

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

[0063] <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.

[0064] <8-1. Account Table> 6A is a diagram showing an example of the data structure of account table 281. 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.

[0065] The item "user ID" stores an ID for identifying a user.

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

[0067] The "Attribute" item stores information about the attributes of the user corresponding to the user ID. Information about user attributes indicates whether the user is an organization such as a corporation or an individual.

[0068] The item "organization name" stores the name of the organization to which the user corresponding to the user ID belongs.

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

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

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

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

[0073] The item "telephone number" stores the telephone number of the user corresponding to the user ID.

[0074] The item "SMS authentication flag" stores information on whether or not SMS authentication using the user's phone number, which is performed during user registration, has been properly performed.

[0075] The item "identity verification flag" stores information on whether or not the user's identification, such as a driver's license, has been verified during user registration. The user's identification is verified, for example, by providing an image of their driver's license.

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

[0077] <8-2. Project 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.

[0078] 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.

[0079] The item "deal ID" stores an ID for identifying the website that is the sale deal.

[0080] The item "Seller User ID" stores the user ID of the seller of the website identified by the case ID.

[0081] The item "Name of main item for sale" stores the name of the website identified by the case ID.

[0082] The item "URL of main item for sale" stores the URL of the website identified by the item ID.

[0083] The item "Project Status" stores the status of the website identified by the project ID. Examples of website status include "Under review," "Listed," "Sold to," and "Deal completed."

[0084] 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."

[0085] 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.

[0086] The item "Real-time transfer linkage flag" stores information on whether the website identified by the case ID is linked to the real-time transfer 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.

[0087] The item "desired selling price" stores the selling price desired by the seller for the website identified by the matter ID.

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

[0089] The item "access data" stores data relating to access to a website identified by a case ID.

[0090] The item "Income and expenditure information" stores income and expenditure information for the operation of the website identified by the case ID.

[0091] The item "Summary" stores a description that shows the summary of the website identified by the case ID. The case information management table 282 may also store other information.

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

[0093] 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.

[0094] The item "transaction ID" stores an ID for identifying a transaction related to a sale item.

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

[0096] The item "seller user ID" stores the user ID of the user who sells the website in the transaction identified by the transaction ID.

[0097] The item "buyer user ID" stores the user ID of the user who purchases the website in the transaction identified by the transaction ID.

[0098] 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, which will be described later, and the status is updated as the transaction progresses.

[0099] The item "agreed amount" stores the amount agreed upon between users as the selling price for buying and selling the website in the transaction specified by the transaction ID.

[0100] The "Transaction Terms" field stores various conditions for the transaction identified by the transaction ID. These conditions specifically 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.

[0101] 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.

[0102] <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.

[0103] Each record in the domain contract information management table 284 includes an item "Domain ID", an item "Domain name", an item "Status", an item "User ID (owner)", an item "Expiration date", an item "Administrator lock flag", and the like.

[0104] The item "domain ID" stores an ID for identifying a domain managed by the domain contract management server 30.

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

[0106] The item "status" stores the status of the domain identified by the domain ID.

[0107] The item "User ID (Owner)" contains the name of the owner of the domain identified by the domain ID.

[0108] The "Expiry Date" field stores the expiration date of the domain identified by the domain ID.

[0109] The item "Administrator Lock Flag" stores information indicating whether the domain specified by the domain ID is locked (operation restricted) by the administrator.

[0110] <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.

[0111] 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", "Administrator Lock Flag", etc.

[0112] The item "server account ID" stores an ID for identifying a server contract managed by the server contract management server 40.

[0113] The item "login information" stores login information that is required to be input when logging in to the server account identified by the server account ID.

[0114] The item "Plan" stores information indicating the contract plan of the server account identified by the server account ID.

[0115] The item "status" stores the status of the server account identified by the server account ID.

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

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

[0118] The item "addon domain information" stores a list of domain names linked to the server contract management server 40.

[0119] The item "Administrator lock flag" stores information indicating whether the server account specified by the server account ID has been locked (operation restricted) by the administrator.

[0120] <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.

[0121] First, a seller who wishes to sell a website that he or she manages 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.

[0122] 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 the system 1. The review examines whether the website desired for sale is properly managed and 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.

[0123] 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 an operation restriction on the domain contract so as to restrict changes to the domain contract (step S311). As a result, the data acquisition unit 3032 of the domain contract management server 30 turns on the administrator lock flag in the domain contract information management table 284.

[0124] After step S212, the server contract operation restriction is executed on the server contract management server 40 (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.

[0125] 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."

[0126] 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).

[0127] 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 purchasing user (step S221). Specifically, the transaction status in the transaction information management table 283 is updated to "negotiation request."

[0128] 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.

[0129] 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 who wishes to purchase (step S223). At this time, the transaction management server 20 also notifies each user that negotiation has begun. This initiates negotiation between the two parties. The transaction management server 20 accepts chat messages exchanged between users.

[0130] After step S223, if the purchasing user wishes to purchase under the purchase conditions agreed upon with the selling user, the purchasing user performs an operation to propose a purchase under the purchase conditions. The terminal device 10 of the purchasing user accepts the operation to propose a purchase (step S123). If the purchasing user does not agree to the purchase conditions, the negotiation state can be maintained. In the negotiation state, both the purchasing user and the selling user can end the negotiation at any timing.

[0131] If the negotiation is 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.

[0132] After step S224, the seller approves the purchase proposals from users who are willing to transfer the property (step S132). Specifically, the terminal device 10 accepts an operation to approve the purchase proposal. 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.

[0133] 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 conditions confirmed."

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

[0135] After step S151, the transaction management server 20 requests the terminal device 10 of the user who wishes to purchase to confirm the transaction conditions (step S226).

[0136] 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 the contents. The terminal device 10 returns the input approval operation to the transaction management server 20.

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

[0138] After step S227, the terminal device 10 of the seller accepts the check of 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 result to the transaction management server 20.

[0139] After step S152, the transaction management server 20 requests the terminal device 10 of the buyer to confirm the contract (step S228). Specifically, the contract checked by the seller is sent to the buyer, and the buyer is prompted to enter a response as to whether there are any problems.

[0140] 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.

[0141] 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 in 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.

[0142] After step S142, the transaction management server 20 transmits information to the electronic contract service (step S229). Specifically, the transaction management server 20 provides the electronic contract service with information about the seller and buyer, 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.

[0143] FIG. 11 is a diagram showing the process from receiving a report of the conclusion of a 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).

[0144] After step S231, the transaction management server 20 requests an escrow transfer from the terminal device 10 of the user wishing to purchase (step S232). An escrow transfer is a method of remittance in which the purchase price is temporarily held by the user wishing to purchase, and after confirming that the item to be transferred has been properly transferred, the sale price is paid to the user wishing to sell. At this time, the transaction management server 20 designates a bank account to which the user wishing to purchase should transfer the money. The user wishing to purchase 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."

[0145] After step S232, the transaction management server 20 receives notification that the escrow remittance 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 and inspection."

[0146] After step S233, the transaction management server 20 notifies the terminal devices 10 of the buyer-desiring user and the seller-desiring user that the remittance from the buyer-desiring user has been received (step S234).

[0147] FIG. 12 is a diagram showing the process from the request for the name change of the server contract to the notification of the completion of the procedure, among the processes of the system of this embodiment.

[0148] 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).

[0149] After step S241, the server contract management server 40 changes the name of the server contract (step S421), thereby changing the contract holder of the server account from the user wishing to sell to the user wishing to purchase.

[0150] 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, the operation restrictions on the server contract are also lifted.

[0151] After step S422, the terminal device 10 of the purchase-desiring user receives new login information (step S161).

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

[0153] 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, the operational restrictions on the domain contract are also lifted.

[0154] 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 of the completion of the name change, instructs them to transfer any other assets that need to be transferred, and instructs the prospective buyer to perform an acceptance inspection after the transfer is complete. This allows the prospective buyer to begin an acceptance inspection, 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.

[0155] After step S243, the terminal device 10 accepts an operation to complete the inspection (step S162). Specifically, the user wishing to purchase inputs to the terminal device 10 that the inspection was conducted and there were no problems. If a problem occurs during the inspection, the user is notified of this and a request to cancel the transaction is sent to the user wishing to sell. At this time, if the user wishing to sell approves, the contract is terminated. When the contract is terminated, the transfer object that has already been transferred to the user wishing to purchase is returned to the user wishing to sell.

[0156] After step S162, the transaction management server 20 transfers the selling price from the seller (step S244). That is, provided that the inspection is completed, 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 predetermined fee.

[0157] After step S244, the transaction management server 20 notifies the seller and buyer users that the procedure has 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."

[0158] <10. Screen example> Next, examples of screens of the system 1 will be described with reference to Fig. 13. 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 item page that publishes websites that are the subject of buying and selling in the system 1.

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

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

[0161] 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, among the tags, the "PICK UP" tag is attached to recommended items with favorable transaction conditions among the items 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.

[0162] Each listing includes evaluation indicators for each project, such as "site name," "asking price," "operating profit," "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.

[0163] <11. Variations> 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. On the other hand, 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).

[0164] 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 (remove WHOIS information from the proxy publication, unlock the domain, obtain AUTHCODE, etc.) · A transfer application (transfer-in) is made to the domain contract management server 30 to which the domain is to be transferred. -Approve the transfer (transfer-out) with the original registrar. ·Transfer completed

[0165] 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 a site configuration file from the server and exports and downloads SQL data from the database.

[0166] After step S102, the terminal device 10 accepts a request for a contract for the transfer 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.

[0167] 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 in step S401 is issued when applying for the server contract (step S103), and can be used immediately.

[0168] After step S401, the terminal device 10 installs the site data in the destination server (step S104).

[0169] After step S104, the terminal device 10 accepts 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.

[0170] 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.

[0171] <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 the 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 process for transferring a website and reduces the risks involved.

[0172] Furthermore, after accepting the registration of the sale proposal, the transaction management server 20 imposes certain operational restrictions on the domain contract and server contract that constitute 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, the website, and to maintain a transferable state.

[0173] Furthermore, after detecting the payment of the purchase price from the prospective purchaser, the transaction management server 20 switches the contract with the domain name and the server contract management server 40 upon detecting the payment of the purchase price, which prevents the procedure from proceeding with the purchase price remaining unpaid.

[0174] 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.

[0175] In addition, the transaction management server 20 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 login information for the CMS has been changed, the transaction management server 20 notifies the prospective purchaser of the changed login information.

[0176] In this way, 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. With conventional procedures, work that would normally take several days to two weeks can be completed by simply changing the name on the domain contract and server contract, making it possible to achieve real-time (instant) site transfer.

[0177] 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 increase in the success rate of website transfer agreements, higher website purchase prices, improved asset values, and increased commission income.

[0178] While the preferred embodiments of the present disclosure have been described above, 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 modifications can be combined as appropriate as long as no technical contradiction occurs.

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

[0180] (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 who wishes to sell to the user who wishes to purchase.

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

[0182] (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.

[0183] (Appendix 4) In the steps 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 buy (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 a server account related to the contract for the management server to a password used by the prospective purchaser.

[0184] (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.

[0185] (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); 6. The program according to any one of appendices 1 to 5, which executes the step of installing site data constituting the website in the management server (step S104).

[0186] (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 who wishes to sell to the user who wishes to purchase (steps S241, S242).

[0187] (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 being sold on the sales offer page; a module (2032) for receiving a proposal for purchasing 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. [Explanation of symbols]

[0188] 1. System 10...Terminal device 13...Input device 14...Output device 15...Memory 16...Storage section 19...Processor 20...Server 201…Communications Department 202...Storage section 203...Control unit 25…Memory 26…Storage 29...Processor

Claims

1. 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.

2. 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.

3. 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.

4. 4. The program according to claim 3, further comprising a step of notifying the prospective purchaser of login information including the changed password.

5. 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.

6. 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.

7. 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.

Images