KR20020042834A - Methods and appratus for establishing and maintaning internet domain name registration - Google Patents

Abstract

A method and apparatus for performing a transaction related to the management of an Internet domain name includes establishing a connection between an Internet domain name register and another user's application on the Internet, and authenticating the user's rights to perform the transaction. Establishing an ESLE on the connection, and processing the post-authentication command.

Description

METHODS AND APPRATUS FOR ESTABLISHING AND MAINTANING INTERNET DOMAIN NAME REGISTRATION}

With the rapid growth of the Internet, there has been a demand for management of procedures for establishing domain name registrations (Web addresses), and administrative measures that involve changing ownership, renewal, and so on.

Until recently, Virginia Herndon's Network Solution, Inc., had domain name registrations ("DNRs") with domain names ending in .com, .net, .org, and .edu. It was exclusive to what was registered and acquired.

In that role, Network Solutions Incorporated is known as a registrar.

To date, approximately 5 million web addresses have been registered by network solutions.

Current implementation systems for registration of web addresses rely heavily on the use of e-mail between the user and the registrar for each step of the procedure.

For example, FIG. 4 shows the sequential steps for registration, beginning with preparation 100 for a new web address registration by a customer (registrant).

The registrant fills in the service agreement (102). The service agreement is submitted by registrant to e-mail, for example hastmaster@internic.net (step 104).

The request is automatically assigned 106 with a tracking number.

Errors for service agreement are automatically checked 108.

If there is no error, the service agreement continues and the registrant is notified via e-mail at completion 112. Web address registration ends with a message.

For example, the content of the message is "Your Web address is complete" (step 114).

The customer is informed of the invoice for registering the web address (step 116) and pays for the registration (step 118).

Finally, the registrar sends a re-registration notice to the registrant 60 days before two years from the date of initial registration establishment (step 120).

If there is an error in the service agreement, the registration process is not completed, and the customer is notified of the problem by e-mail.

While this procedure works effectively, there may be some drawbacks. In particular, the use of the Internet for e-mail notification is not "real-time" based.

Especially in parts of the world where Internet support is not fully established, it can sometimes take days to receive email.

In addition, the e-mail may be broken, and a more delayed time may occur, requiring the recipient to resend the message.

Moreover, the occurrence of resends has led to the development of the concept "Wholesaling" by organizations such as Internet Services Providers ("ISPs"), Internet hosting providers, and Internet portals and e-commerce providers have been To protect the DNRs.

In fact, these organizations serve themselves as registrants by suggesting to their customers an interface that allows a complex or uncomplicated user with an interface with registration procedures and ancillary management.

Ultimately, however, DNRs are allocated and distributed by Network Solutions Incorporated, which is still a registrant.

The expansion of outlet numbers to protect DNRs has led to the development of systems and methods that facilitate wholesaling.

Network Solutions Incorporated is an NSI Full Service Protocol ("WSP") that establishes support for a real-time programmable interface for the purchase and management of services for Network Solutions Incorporated products and systems. WholesaleService Protocol).

Such a system allows a user looking for registration to complete the procedure, regardless of the level of expertise of the Internet and computer technology.

The WSP uses an ASCII text-based protocol that is simple, connection-based, concurrency, and allows communication with NSI Failsale systems over the Internet, whereby the qualifiers can use customer accounts and Internet domain names. It will be possible to create, modify, and delete a variety of products, including registration and management.

The WSP includes a command line used to create a product associated with a customer account or domain-name.

Each command translates into a column of "properties" and a majority or few error codes.

In most cases, the result of one command is used as input to the next command. The sale command is either synchronous or asynchronous.

In general, customer creation and management commands are synchronous, while domain creation and management commands are asynchronous.

An "as-fast-possible" execution system for asynchronous commands maintains a queue to guarantee that the commands are not lost in case of external system problems.

Typical synchronous response time is less than a few seconds, while asynchronous time to complete registration is less than a few minutes.

There are two main safety mechanisms in the NSI funsale system.

Every full sailor must supply an IP address by connecting and establishing an ESSE ("SSL") secure socket layer connected to the NSI full sale system.

In addition, the hull sailor must use the number of accounts and passwords when performing a session command. NSI gives hullsails time ahead.

The system offers various advantages over existing technologies, but there is a need to make the system universally effective.

Thus, it is possible to provide an application program interface that can allow other users' computer applications, access a full sale system, and drive processing related to the registration and management of Internet domain names in the same way as the WSP. There is a need for a method and apparatus to be able to do so.

The present invention relates to the field of domain name registration.

More specifically, the present invention relates to a method and apparatus for providing an application program interface that enables registration and maintenance of Internet domain names.

The accompanying drawings, which form a part of this specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention.

1 is a diagram of a preferred embodiment of the present invention wherein an application program interface, WSP Java API, performs the functions of a WSP in a column of Java object classes.

2 illustrates an exemplary flowchart of a method for interfacing a user application to a system that performs a transaction related to the management of an Internet domain name.

3 illustrates an exemplary flowchart of an apparatus for interfacing a user application to a system that performs a transaction related to the management of an Internet domain name.

In order to achieve the advantages associated with the object according to the invention, its embodiments are described in detail.

The present invention can interface a user application to a system for performing transactions related to managing internet domain names by establishing a connection between the user and the system on the Internet; Verify the authenticity of the user's rights to perform transactions related to the management of Internet domain names; Establish a Secure Socket Layer (SSL) in the application program interface and in the system; After proof of the authentication, a request in an application program interface by the application program can be received to start a transaction; A method and apparatus are provided to enable sending a command by the application program interface to a system capable of making the transaction.

Preferred embodiments of the present invention will be described in detail with reference to the embodiments shown in the accompanying drawings. In the drawings, the same reference numerals are used for the same components.

The method and apparatus of the present invention provide an application program interface accessed by a user application to establish a connection to a system for performing transactions related to the management of an Internet domain name.

With reference to FIG. 1, computer application 12 typically provides an interface to a user to collect customer data.

The computer application 12 makes a session request to the application program interface, WSP Java ASI, in order to establish a session on the Internet 10 having the sale system 16 and execute various commands.

The WSP Java API 14 is substantially a Java 'wrapper' of the WSP.

It consists of two main classes: the NSI Wholesale API and the WSP Response.

The NSI Full Sale API includes all the ways to create customers, products and services.

The WSP response is mostly a single class returned by the method, containing the result of the command request, and optionally containing some additional data generated by the request.

The advantage of the WSP Java API 14 is that, when an NSI holiday sale API object is created, the object creates a 'pool' connection of SSL to the holiday sale system 16.

The class eliminates the need for issuing a 'session' command and removes responsibility from the hulsailers who configure and manage SSL connections. Multi-threaded applications use the connection pool.

2 shows a preferred floor chart of the present invention.

User 20 sends a request to application 12 to perform a transaction related to the management of an Internet domain name.

The application program 12 provides an interface to the user to collect customer data.

The application 12 issues a session request to the application program interface 14 to establish a session on the Internet 10 with the discount system 16.

The application program interface 14 will authenticate the user's right to conduct a transaction by attempting to connect with the sale system 16 using the user account information received from the application.

If the authentication fails, the application program interface 14 will attempt two additional authentications.

The application program interface 14 will send the result of authentication to the application program 12.

If the authentication is successful, the application program interface 14 will establish a Secure Socket Layer (SSL) with the sale system 16.

The application program 12 will send a request to the application program interface 14 to make the command line valid through demonstration of an object of the NSI Full Sale API.

The application 12 will send a request directly to any of the object methods to request the procedure of the command.

The application program interface 14 receives a command request with some data.

The application program interface 14 formats data and commands into a string, as described in US Patent Application Serial No. 09 / 544,305.

Next, the application 14 sends a request across the Internet to the sale system 16 for a transaction to occur.

The sale system 16 will proceed with the request and return the result of the transaction to the application program interface 14 across the Internet 10.

The application program interface 14 will send a response to the application program 12.

3 is a diagram illustrating a preferred computer environment in which the method associated with the present invention may be implemented.

Each component is provided such that it can send a request to the application 12 to perform a transaction related to the management of the Internet domain name.

The application program interface 14 issues a session request to the application program interface 14 to establish a session on the Internet 10 having the sale system 16.

Each component is provided such that it can authenticate the user's 20 rights to conduct a transaction.

The application program interface 14, using the user account information received from the application program 12, attempts to connect to the discount system 16, thereby authenticating the user's right to conduct a transaction.

If authentication fails, the application program interface 14 will attempt two additional authentications.

The application program interface 14 will send the result of the authentication to the application program 12.

If the authentication is successful, each component is provided to establish a Secure Socket Layer (SSL).

The application program interface 14 will establish a Secure Socket Layer (SSL) associated with the discount system 16.

After successful authentication, a component is provided to initiate a transaction.

The application program 12 will send a request to the application program interface 14 to make the command line valid through demonstration of an object of the NSI Full Sale API.

The application 12 will send a request directly to any of the object methods to request the procedure of the command.

The application program interface 14 receives a command request with some data.

A component is provided for transmitting commands over Secure Socket Layer (SSL).

The application program interface 14 formats data and commands into a string, as described in US Patent Application Serial No. 09 / 544,305.

Next, the application 14 sends a request across the Internet to the sale system 16 for a transaction to occur.

The sale system 16 will proceed with the request and return the result of the transaction to the application program interface 14 across the Internet 10.

The application program interface 14 will send a response to the application program 12.

The name of the WSP Java API array file is typically WSPjavaAPI.conf.

The file contains specific information about each holiday user.

The value for the parameter is a file provided when the sale agreement is terminated by a registrar such as NSI.

The file contains the following parameters.

The value indicated by "X" will change according to the user. The rules for each parameter are as follows:

The NSI holiday sale API class is called to allow computer application 12 to create and manage Internet domain names and perform holiday-related operations, such as connecting the holiday sale system 16 to the Internet via SSL. Constructs an example of a new NSI Full Sale API object that contains a method.

Class definitions for the NSI Full Sale API include:

The WSP response class represents the components of the various WSP responses.

The WSP response will be returned for the command request issued through the application program interface 14.

The response will be described in more detail as a result of the request made, and optionally includes additional information generated by the request.

The result consists of a "result code" followed by a "result message".

The result code is followed by a minor result code and consists of a major result code followed by a period.

Three digital major result codes provide a universal indication of the success or failure of a raised request.

The three digital minor result codes may provide additional information about the major result code.

Each command request may have a unique sequence of minor result codes or may have a value 100.

The WSP response and result code are described in detail in US patent application Ser. No. 09 / 544,305.

The resulting property consists of the property key followed by a colon (:), followed by the property value.

As a result, the clear text is returned (eg information returned from the help command).

The resulting properties are described in detail in US Pat. No. 09 / 544,305.

The class specification for the WSP response includes the following.

The NSI Full Sale Exception class is a user-defined exception class that indicates a particular error that is generated by the method in the Class NSI Full Sale API.

In particular, exceptions to the class NSI discount exception include: (a) class startup failure; (b) the method in the NSI fitness API is called without successful initialization of the class; (c) the instruction cannot be completed. (D) due to communication problems; (d) occurs when the NSI exception is reconfigured at a low level to impart additional contextual information.

The class WSP exception is the source for a exception protocol exception that handles the response sent by the sale server 16 to the computer application 12. This provides a basic way to store error information in all exception classes.

The class invalid discussion exception and invalid response format exception are detailed class children of the WSP exception. Both methods have the same internal function as WSP exceptions.

In addition, both classes are independent, and thus the generated and received method knows the type of error detected, even when the error context information is the same.

In particular, the WSP response class generates an invalid discussion exception when data returned by the sale server 16 becomes invalid.

The WSP response class generates a class invalid response format exception if the data returned by the sale server 16 is not properly formatted.

Class rules for NSI holiday sale exceptions include:

Classes for WSP exceptions include:

The class rules for exceptions are as follows.

Class definitions for invalid response format exceptions include:

As a preferred embodiment of the present invention, the present invention will become clearer by showing an example of a computer program file for creating a session with a pleasure system to initiate a sale operation.

The WSP Java API 14 is the execution of the WSP. In each case, the WSP Java API 14 is used. The first step is to start a session and then create an instance of the class to reference the method. Each call to the method is an instance of a single protocol change. Each call contains all the necessary information (eg customer authentication, contact information). Except for the session information, no information is transmitted from method to method.

The invocation of the first routine in the WSP Java API 14 is the class method NSIWholesaleAPI.init which causes the fungal system 16 to start the interface.

The second invocation creates an instance of the class NSIWholesaleAPI that makes the method 12 valid for the application 12 to send a command to the sale system.

The application program 12 sends a command request to the application program interface 14.

The final call is a shutdown method that ends the session with the pleasure system 16.

With reference to the above description with reference to network solutions and NSIs, classes, methods, constructors, drawings, and the like are not limited to those included in a given embodiment, and are not limited to specific implementations as just one embodiment.

In addition to the description based on the client-server architecture, those skilled in the art will appreciate that other types of architectures may be used in connection with the present invention. In addition to the descriptions based on software implementation, other implementations may be used in connection with the present invention. Moreover, it will be apparent to those skilled in the art that the description is based on the Java language and that other forms of language may be used in connection with the present invention.

Accordingly, the invention is not limited to the specific implementation and methods, and the invention includes all implementations without departing from the spirit of the claims. It is not intended to be exhaustive or to limit the invention to the precise form, and various modifications are possible in light of the above teachings and may be obtained from embodiments of the invention.

The principles of the present invention and its application can enable those skilled in the art to use the invention in various embodiments, and various modifications can be made as intended.

The class definition for NSI Full Sale API is as follows.

The present invention relates to a method and apparatus for providing an application program interface that enables registration and maintenance of Internet domain names.

Claims (9)

Methods for interfacing user applications to systems for performing transactions related to the management of Internet domain names include: Receiving a request at an application program interface by the application program to establish a session between the user and the system on the Internet; Authenticating a user's rights to perform a transaction relating to management of an internet domain name; Establishing a Secure Socket Layer (SSL) in the application and the system; After the authentication, it is possible to receive a request in an application program interface by the application program to start a transaction; A method for establishing and maintaining an Internet domain name registration for enabling sending a command from the application program interface to a system capable of making the transaction. 2. The method of claim 1, further comprising the step of notifying an application about the operational status of the command procedure. 3. The method of claim 2, wherein the notifying step further comprises returning a response to the application program containing a statement indicating whether the transaction has completed execution. 4. The method of claim 3 wherein the description includes a message having an ASII text portion followed by a delimiter portion. 5. The method of claim 4, wherein said ASCII text portion is selected from a predefined dictionary for descriptive text. 2. The establishment and maintenance of internet domain name registration according to claim 1, wherein the user's authentication is determined from an Internet protocol address, Secure Socket Layer (SSL) encryption, a username and password provided by an application. Way for. 2. The method of claim 1, wherein the step of authenticating further comprises one additional attempt to authenticate the user after the first failed attempt. 8. The establishment and maintenance of internet domain name registration as claimed in claim 7, wherein after said one additional attempt to authenticate said user is denied, another attempt to authenticate fails as said one further attempt. Way for. The device for interfacing a user application to a system for performing transactions related to the management of an Internet domain name is: A component for receiving a request by an application program to establish a connection between a user and a system on the Internet; A component for authenticating a user's rights to perform a transaction relating to management of an internet domain name; A component for establishing ESSEL in the device; A component for starting a transaction after receiving a request by the application and after the authentication; And a component for sending a command to the system to enable a transaction by the ESSEL.