FI107215B - A method for minimizing delays associated with name resolution services - Google Patents

Description

1 107215

A method for minimizing delays associated with name resolution services

The invention relates to a method according to the preamble of claim 1 for minimizing delays associated with name resolution services.

5

According to the prior art, the purpose of a name resolution system, such as the DNS rigid system used on the Internet, is to enable reference to an Internet resource without knowing its location. In the case of DNS, the resource is most often the so-called. host, which is a computer connected to the Internet. In the case of 10 DNS, the location is the network location, which is expressed on the Internet by an IP address. Being able to refer to a resource without knowing its location is important because, if the names and locations of the resources were not separated, changing the location of the resource would result in a laborious reconfiguration of all systems that would include references to the transferred resource. Especially if the moving resource were a server, 15 workloads would be considerable. Em. for this reason, the Internet application or user must not, in general, rely directly on a reference, such as an IP address, for sending messages, but must always refer to the object as locally as possible. So, for example, the DNS name eliminates the need for applications to keep kinky about the host IP addresses. For example, the DNS name is used in e-mail addresses as the 20 following the © sign. A host can also be thought of as a location, in this case a physical location where the abstract resource is stored. For example, the name of an abstract resource such as a web page should not (ideally contain parts that refer to the host where the resource is located. Em.

: ·, Eg IETF URN, Uniform Resource Name, which does not contain ....: no locational dependencies have been developed.

25 * · ·. 1 j 1. A dynamic update of URN, DNS, and other name resolution information will be the basis of many locality services. Examples of such services will be ♦: ··: many services based on the work of the IETF MMUSIC.

* Increasing use of localization services results in name resolution systems: '. ·. 30 load increase. To minimize network load, it is preferable that most of the name resolution update traffic is local, as · · ·: ·] ·.

· 107215 2

In the current DNS rigid system, only one stem static IP address usually matches a given host name. As a result, the update load of the DNS system is reasonable. New systems and services are being developed based on a dynamic update of name server information and substantially increasing the deletion of name server operation and system-dependent application delays. One example of such a new system is the Uniform Resource Name (URN), where a web resource, such as a SW object or an HTML document | published on the network, is given a unique host and network location independent name such as an ISBN. 10 Kim This document with a specific URN is copied across networks, leaving the name resolution system to keep track of multiple document physical locations. Another factor that significantly increases the load on name resolution systems is the use of distributed, e.g., object-based computer systems. Object-based interfaces facilitate system decentralization. For example, a web site has been implemented in a poster. 15 services that require dynamic screen updating using an object-based approach. Take, for example, a visiting customer on a company's web site. Kim uses one of the services on the site, a distributed computer system that enables the service can consist of, for example, a client host, as well as a company's web server and database server host. Since the machine-to-machine transmission network causes delays, it makes sense that system support services such as name resolution are physically located as close as possible.

• '·· The name resolution system causes delays not only in updating name queries but also in updating names *****. There are 25 unique location-independent names assigned to each object or resource at birth, and since a distributed system can create countless off-host objects or resources in a short period of time, it doesn't matter how many unique searching for names, registering, and ... taking time. The system can be decentralized to many more mirrors! * between two hosts. There are already dozens of decentralized services

* «· I

4 · * j · '·' 30 for machines. Such are, for example, so-called. jewelery and adventure games online. Jj of objects ”·; · The registration and updating of the location information of the resource interfaces will thus be performed by the 4 *>: ': in the best possible physical location to minimize delays.

I i «107215 3

The most advantageous physical location is, as a rule, the location as close as possible to the users of the resolution services.

An alias definition in the DNS name server system means that if a specific name, for example 5 companycompanyqoaja.fi is replaced with a new name, e.g. companycompany.com, queries to the old name, in this case companycompanyqoaja.fi, can be redirected name, which answers the query according to the definitions given for the new name. This arrangement eliminates the need to update the name server information corresponding to a given name after the alias definition, but it is sufficient to update the name server information corresponding to the new name to avoid duplication of data management. In the prior art, when a customer who publishes a particular network resource based on a particular name wishes to assign a alias to the name of a particular web resource or change an existing alias or other name server information for a particular network resource, this requires contacting the customer via 15 phones, letters, emails or similar new name server information for the DNS server. An arrangement is underway for a customer to update DNS information tied to the name of a published web resource directly into the DNS (Dynamic & Secure DNS) system.

1 ,,,: 20 «I

::: The object of the present invention is to minimize the delays caused by name resolution services and to reduce the number of said resolutions. the network load caused by the systems, and facilitates the transfer of responsibility for '# #' name server information transfer from one operator or system to another.

The invention is based on the fact that the operator management system or the first client ... configures the first client host for the first client host name contained in the name of the first client host. name aliases, that is, assigns all · · · * · requests to the first name server to the name of the first client host · · · to be redirected to the second name server according to the new name in alias definition, eg DNS in CNAME RR! is a change of the DNS name resolution server, or that the operator management system or the first client configures the first client server NAPRT-RR with 107215 4 new NAPTR-RR information, i.e. the information of the second name resolution server, in the case of a URN resolution server change location. The invention transfers the responsibility for updating the name resolution server information of the first client names to the second name resolution server and the information to be updated to the second name resolution server 5 is automatically retrieved to the network client belonging to the operator management system by a control system defining the services. Information to be updated based on a specification stored in the control system from the seeker's network element or network elements with which the control system or management system may communicate. Such information network elements 10 include, for example, the DNS system, other name server systems, the client terminal, the Internet host, as well as the operator management system or the control system itself.

The second name resolution server is better positioned or has better functionality than the first name resolution server. The name resolution server of the toin 15 manages those parts of the namespace that are named. has been allocated to the server and is handling inquiries regarding these. It is also possible that the name services transferred to the first client on the second name server include, for example, the NAPTR RR configuration option, whereupon the URN name resolution server ^ to be retrieved from the second DNS server. NAPTR recursion is possible; NAPTR May refer to another NAPTR. Thus, for example, one can set the first DNS server's NAPTR-RR to indicate the name of the second DNS server where the new NAPTR is found. The last NAPTR of the chain thus formed indicates the name resolution server. Kim || assigning registration and update responsibility to the desired resolution server to minimize the registration and update delays experienced by recipient I <(....: first client; and second, · ·. ·: \ 25 client experienced naming services if another client host is located nearby. ': first-time client-host and name resolution server-host evaluated by network delays.

An arrangement whereby the most common parts of the decentralized systems are to be placed as close as possible to communication delays is practically preferred, if possible, so the advantages of the invention are: v. 30 in these cases the largest.

More particularly, the process according to the invention is characterized in what is set forth in the characterizing part of claim 1.

The invention provides considerable advantages. The method of the invention accelerates the registration, updating and retrieval of name server information in cases where the invention is used to direct inquiries to another name resolution server that is closer to and / or better in communication. The second name resolution server may also be functionally more efficient or more versatile than the previous name resolution server. Again, this speeds up the name resolution server system and / or reduces network load. The invention allows for a flexible transfer of responsibility for performing operations to update name resolution server information from one operator or system to another. The second name resolution server may be used to assist in arranging services that were impossible to provide using the previous name resolution server. The invention allows dynamically updated name resolution server system updates to be managed by those name resolution servers that are inexpensive and / or necessary to provide the desired services dependent on the name resolution server update function. Nameservices received by client hosts are accelerated and ... ... 20 can be deployed with higher name resolution server traffic: services that can be implemented using more complex and: '' more sophisticated distributed computing systems.

• · · · ·

The invention will now be further explored by means of the working examples according to the accompanying figures.

• • I • * · • ♦ *

The first example of Figure 1 illustrates, in block diagram form, how the client-provided name services can be routed from one server to another in accordance with the invention.

• · · • · · · *; The second example illustrated in FIG. 2 illustrates, in block diagram form, how the invention can be used to transfer name resolution services used by a handheld terminal * * and the present invention. to speed up the name resolution services used by the device.

107215 6

The third example of Figure 3 is a block diagram illustrating how the invention could be applied to accelerate name resolution services in object-based systems.

5 illustrates the transfer of name services. In the solution of the pattern in the current TCP / IP environment. The IP terminal 11 establishes a connection with the rigid system 12 of the operator, e.g. via a modem bank. The system 12 of the first operator manages the authentication, authorization and billing data collection and routing to the IP terminal 11 and / or the network client 10 using it, and determines the IP address of the IP-10 terminal 11. The first operator system 12 stores customer user profiles that store information about the services available to the data network client 10 and which services are already available. The services used by the data network client 10 may be determined, for example, by means of web pages on the basis of information received from the data network client. If the control database in the system of the operator 15 is configured to provide a service to the network client 10 that requires the responsibility of updating the name server information from one server to another and the service is not yet operational, the system of the first operator operates as follows. The first operator system 12 checks whether it has update rights 20 to the first name server 14. The first name server 14 is a dynamically updated Dynamic & Secure DNS where the client public name 15 is located. :, 1, If the system 12 of the first operator does not have upgrade rights for the first: '. name server 14, first operator system 12 antfca ·; ··· information for client 10, e.g., in a web page negotiation 25 DNS names 16 and information on how to update name server information when transferring responsibility »: T:. The first operator system 12 may also transmit policy information and the DNS name 16 by providing software to the IP terminal 11 which takes the necessary action. If the system 12 of the first operator '... * has upgrade rights to the first name server 14, the system 12 of the first operator ·' · ': 30 takes the necessary action. Required actions are: '' ·. following. The public name 15 of the client is configured as an alias by binding the client ·. ·. ·; to the public name for the first 15 name servers 14 DNS CNAME Resource Record 107215 7 RR. Ko. The content of the RR becomes the DNS name 16. The first operator system 12 generates the DNS name 16 on the second name server 17, which is Dynamic & Secure DNS controlled by the first operator system 12. The first operator system 12 stores the read RR information corresponding to the client public name 15 15 from the first name server 14, where applicable, to the second name server 17 as RR information corresponding to the DNS name 16. Thereafter, if an end system sends an inquiry with the client's public name 15, it is redirected to another name server 17, which responds to it, thanks to the alias definition. From now on, the system 12 of the first operator will update the name server information corresponding to the public name 15 of the client to the second name server 17.

The following describes a system where the name identifying a particular Internet resource does not contain any resource location information, such as the host name or network address of the resource. An example of this is URN. The first name server 14 is used to search the first name resolution server 18 under the control of the second operator, e.g., by specifying a NAPTR RR (IETF RFC 2168) to refer to the first name resolution server 18.

After aliasing, inquiries to the first name server 14 ... ... 20 direct to the second name server 17, which is the system of the first operator 12:.:: Directs to look for a second name resolution server 19 located better: or has better functionality than the first name resolution server 18.

Thereafter, the system 12 of the first operator takes care of updating the information of the second name resolution server 19. When the client wants to stop using the service • · · * · '* 25, due to which the name server information update was moved to the second name server 17 .., the DNS CNAME Resource Record definition is removed from the first name server. or the software provided by the operator • · «« · · or the system of the first operator 12 if he has the necessary rights.

«· • · · • · ♦ • · '·; · '30 The CNAME RR counterpart found in other name service mechanisms can also be: · used to implement the corresponding service in that application. mechanism.

107215 8

As shown in Figure 2, the name resolution services used by the portable terminal are described. The idea of a URN is to give each resource a name that identifies that resource, which is independent of where in the data network the instances of that resource are located. Location refers here to, for example, a host or an EP-5 address. Resource location information can be retrieved using a waste system (RFC 2108) which first finds out, for example, by DNS, the name resolution server needed, possibly recursively. Only this can tell where in all the locations the resource specified by the URN is located. First, the names of the host (s) where the resource specified by the URN is located and then the host EPs if these were not received with the host information 10 are determined. With this information, the ice system can ask the resource they are looking for in the right place.

The invention can be utilized, for example, in the following case. The client has a portable terminal 21, which is part of a distributed system 15, for example, in an organization's network 22 whose name records, such as the DNS RR field, are stored on the first name resolution server 2j4 in Finland. The terminal 21 is normally used nationally, for example in Finland. The first name resolution server 24 is normally searched, e.g., by DNS and NAPTR (IETF RFC 2168) using the first DNS server 23. The portable terminal 21 of Example 20 is being used overseas, e.g., in the US. There the device slows down because many name searches and data updates: transactions need to exchange messages based in Finland; ' ,, with the first name resolution server 24.

«· 25 According to prior art, the operation is, for example, as follows. Customer

• I

il: Terminal 21 received by DHCP (Dynamic Host Configuration

Protocol) to the nearest DNS server, which is a US name server 28. Subsequently, the so-called "DNS" on the client's terminal 21. stub resolver program, was a · · t program that can send and receive a recursive lookup request: '·': 30 sends all DNS queries to the US name server 28.

The queries are requested recursively, whereby the US DNS server 28 takes care of 'f · 1; for any further DNS queries on behalf of the stub resolver program on terminal 21 <· • · # • * · 107215 9. You want to retrieve a specific document with a specific URN. The location information corresponding to a particular URN is stored on the first name resolution server 24. The location of the first name resolution server 24 can be determined by retrieving a particular NAPTR from the first DNS server 23 in Finland. When the terminal 21 retrieves a particular 5 document, a DNS query is sent to find a particular NAPTR. The submitted DNS query passes to the first DNS server through 23 US nameservers 28. A specific NAPTR is obtained from the first DNS server. From a particular NAPTR, the location of the first name resolution server 24 is determined. The location of Kim's first name resolution server 24 is known, a name resolution request for a particular document 10 may be sent to the first name resolution server 24. Only after receiving the location document information sent by the first name resolution server 24, the document can be requested from these locations. A particular document is stored in multiple locations, and information transmitted by the first name resolution server 24 indicates that a particular document is also found in the United States.

15

It is noted that everything else happened in the US except the name resolution service. It can be traced to the USA by the invention. US operator 27 requests a customer using a handheld terminal 21 to inquire about faster name services or an interest in getting the services used by the customer • 20 to operate faster. The US name server 28 includes a name resolution server

I I

: 24 public name or public name of the server to search for

C I

! name resolution server 24. Defines in US Alain name server 28, 4 '' the public name of the name resolution server 24 or the name of the host server to look up the name resolution server 24 as an alias for dynamically enabled # ·· · · * * 25 In the USA, the name resolution server 29. Now, the US operator subsystem 27 takes care of updating the name resolution server 29 in the US 4 4 4 • * · and ensures that the customer gets the services they want. Customer Experience Naming Services 4 4 4 • ♦ «accelerate when you do not need to apply for name resolution services in Finland.

• 4 4 4 • · · · 4 «· 4« * · · · * 30 US operator subscriber 27 or US operator may also inquire ::: customer interest to temporarily enable services required by US operator dynamic '·' * name server information update , which the customer's Finnish operator 107215 10 does not taq or otherwise did not use the customer in Finland.

Figure 3 illustrates the use of the invention in object-based applications. In this case, web based services are provided. The services are provided in 5 object-oriented programming languages eg Java. The system includes a company server 31, a first operator system 32, and a plurality of clients that may interact with each other. When a client's browser notices an applet tag on a company web page, the client's browser loads code, such as the class in Java that the tag refers to. The code is executed in the client's browser. This object, which is executed by a client browser on the code of a company downloaded from the company's 10 pages, is called apletik $ i. As you run the applet, you can download classes from the company's web pages, install them from their object, and run them as subroutines. Other web site visitors can simultaneously download a similar applet. Each applet and object has its own location-independent ID, which is transformed into a physical address by a particular name resolution server 15 33. The service has a plurality of concurrent users 36-39 that are poorly positioned with respect to the location of a particular name resolution server 33. The service is, for example, a game spinning on a company web site. Players 36-39 are far from a particular name resolution server 33 that runs the game name resolution services, for example, all in the players' city or district 40 and a specific name resolution server 33 ;,, 1 20 in another city or neighborhood 49. In this arrangement, the applets in decentralized: in section 39: 1 via a first DN $ - III ·· '' server 41 managed by a first operator management system 32 to a specific name resolution server 33 managed by a first operator system 32 and a first name server 41;

'♦ * 25 by definition. For example, this definition may be the NAPTR RR definition (IETtF

RFC 2168). According to the invention, a specific public name 48 on a first name server 41 in a player's city or district 47, by means of which the name resolution server 33 can be retrieved, configured as an alias to refer to another name. * · 'Operator system 34 to take care of the second name resolution server 35. After 30, second operator system 34 takes care of the game's need for the game. For example, if nothing happened shortly before the name resolution services were transferred to another server 35, when the first client 37 playing the game exemplified, for example, to shoot a competing player's 38 virtual characters, the game needed name resolution services 5 to another server 35.

The method according to the invention is also useful in the case of a distributed distributed fixed system operating in a certain area, for example a network of a company 10 whose name resolution services are managed far from this system. According to the invention, the name resolution services can be directed to a more appropriate location, closer to the users of the network.

In this application, and in particular in the claims, a symbolic identifier, e.g., a TJRN, which is present in communication systems is intended to have no location dependent element. The name also refers here, for example, to a DNS host name, which is on the one hand a locale name, since the host is a localization for abstract resources, but on the other hand is needed for naming independent of the network level location, e.g.

20 ': In this application, and in particular in the claims, there is intended to be an i:': name resolution server for a system that can share a location-independent name: 1 .. upon determination of the locations of object or resource instances according to such name.

In this application, and in particular in the claim, a name server is provided which, after being able to obtain a name according to a defined name, defines the information associated with that name. Ko. the information may, for example, concern the network location of the named resource.

In this application, and in particular in the claims

Il I

i 30 is responsible for ensuring that the data contained in the database can be updated only by those who have the rights and / or responsibility to ensure that the data received from the appropriate • · 107215 12 is stored in the database and / or the right to update the stored data .

In this application, and in particular in the claims, a control system defining or providing services to a data network client is provided with a system having access to a client or client group specific definition of the services provided to the client through name server updates. In addition, the control system defined by the cybercustomer or the providing services stores information required for the client-specific services provided by name server updates 10, such as the new name 16 to be bound to the customer public name 15 and / or information to be assigned to the new name 16. Such information to be associated with the new name 16 may be, for example, the network location of the client network resource or, possibly by means of recursion, the network location of the name server 15 of the client network resource. The control system, or operator control system, line control system included may also be programmed to retrieve information stored in the name server system from an external element, such as an operator rigid system component or a network terminal connected to a data network.

In this application, and especially in the claim, a location-level location or network location of a resource connected to a data network, or a path to find a network-level location or network location, is intended. Such information may be nirjni, whose name resolution server may be able to recursively retrieve the network-level location of the resource connected to the data network, or ι «· V: 25 location information.

• · <»* ♦ • · ·

A name server, such as a DNS server, can store information other than a specific] tt * name, or information to find location information. The * · method according to the invention can thus be used, for example, in security services, for example; '30 in authentication. By accelerating the search times for the required encryption keys, '·; · * Reduced total authentication time. This can be done by binding the public key of the kahqke • 'cryptographic key system to a specific name for the new 107215 13 server. Subsequently, when it is desired to send encrypted data to a network terminal device of a specific public name, the encryption key is conveniently obtained during DNS querying.

In this application, and in particular in the claims, it is intended to bind data to a logical structure into a specific database such that information bound to a particular information can be retrieved from a given database on the basis of a given information.

The claims of claims 5 and 9 on the DNS name subspace and 10 name subspaces mean that if it is sometimes possible to bind a CNAME-RR type definition to hierarchical names to cover 15 subspaces of a given name, then one definition can direct all name server inquiries 16 and / or its subspace. Thus, the operations to be performed in applying the method according to the invention can be reduced in the case where the update responsibility transfer according to the invention is performed on a sub-space 15 of a given name.

i <I I i <* lii i I <

I 4 I

• • · • · · ·

I I I

• · · • · 4 • ♦ «• · * • · ·

»· I

• · · • »·« · · • {«4 14 •« I 4

• I

• 4 «

I I

• I

4 4 4 4 I 4 «· •« 4 4 14 4 4 4

Claims (10)

107215 A method for minimizing delays associated with name resolution services, the method comprising storing a particular name (15) and its normal location information into 5 data structures on a first server (14) and defining a reference to a new name (16) to be associated with a particular name (15). - storing in the control system defining the services to be provided to the network client (10) a specification of the information to be bound to the new name (16), 10. checking whether the defining system controlling the services provided to the network client (10) exchange, in response to a cyber client (10), a specification in the control system defining the services, automatically retrieving 15 information such as location information to be bound to the new name (16) and storing receiving a request for a new name (16) from the second server (17), the new name (16) being in accordance with a specific reference associated with a particular name (15) for the first server (14), 20 requesting a new name (16) to retrieve a new location information corresponding to the new name (16) and / or other data associated with the new name from another server (17). φ A method according to claim 1, characterized in that the normal location information • · · V: 25 refers to the first name resolution server (18) or to a server with the help of »»:: the first name resolution server (18) is found and the new location information refers to the second name resolution server (19); a server for finding a second * * name resolution server (19) and setting a second name resolution server (19) • * · ♦ · * to perform operations to update the name resolution information managed by the first name resolution server (18). A method according to claim 1 or 2, characterized in that the updating responsibility of the first server (147215) is on the first operator and that of the second server (17) on the second operator. A method according to claims 1-3, characterized in that the updating responsibility of the first name resolution server (18) is on the first operator or the third operator and the updating responsibility of the second name resolution server (19) is on the second operator or the fourth operator. Method according to one of Claims 1 to 4, characterized in that the operations of the method are automatically performed on the basis of the data acquired and maintained by the second operator system and the system. Method according to one of Claims 1 to 5, characterized in that the given name (15) and the second name (16) are public names of the DNS system and the location information is The public names of the DNS system or their respective IP addresses and the first server (14) and / or the second server (17) are the DNS system name servers and the specific reference associated with the name (15) is a CNAME RR field to be associated with a particular name (15). or a corresponding RR field that also covers the DNS name subspace. Method according to one of Claims 1 to 6, characterized in that ... 'the normal location information used to retrieve name resolution servers is found in the DNS NAPTR' << '<RR field before the operations according to the method and that the new location information is found: "DNS NAPTR from the RR field after the procedure according to the method, and that NAPTR gives the yields that get the DNS name from the URL and that changing the yields; [. 25 changes the name resolution server used. A method according to any one of claims 1 to 7, characterized by measuring • · · name server traffic and / or name resolution server traffic and transferring • · · the responsibility of updating name server information and / or name resolution server information to the measured data; '; 30 dynamically to another server according to the method. <'. v Method according to one of Claims 1 to 8, characterized in that, when using 107215 hierarchical names, a specific reference to the new name (16) refers to the namespace of the name 16. Method according to one of Claims 1 to 9, characterized in that the second name resolution server (19) is arranged in such a way that the average delay of the resolution services requested through the first server (14) is reduced. • · • · · · 107215