KR20040015775A - Telephone Number Mapping system and method for employing as the same - Google Patents

Abstract

PURPOSE: An ENUM(tEelephone NUmber Mapping) service system and a method for operating the same are provided to present ENUM DNS(Domain Name System) layer structures, the communication method between an ENUM client and a DNS, and ENUM service registration for a phone page, a homepage in a mobile Internet, in order to extend the efficiency and common use of searching. CONSTITUTION: ENUM, an advanced integrated number identification system, is a protocol to convert phone numbers into a plurality of URIs(Uniform Resource Identifiers) on the basis of a DNS. An ENUM service system comprises ENUM DNS layers 0, 1, and 2 that form an authorized system in the structure of a tree. ENUM DNS layer 1, forming an authorized layer with layer 0, creates a country code zone file and stores layer-2 location information for phone numbers in the file. Layer 2 stores NAPTR(Naming Authority Pointer)-type ENUM service information to execute a service information return for an ENUM number query.

Description

ENNMW service system and its operation {Telephone Number Mapping system and method for employing as the same}

The present invention relates to an ENUM service system and an operation method thereof, and more particularly, to an ENUM service system and an operation method thereof, such as an ENUM DNS hierarchy, an ENUM client-DNS communication method, and an ENUM service registration for a phone page.

ENUM (tElephone NUmber Mapping) is an international Internet standardization technology that links general public telephone number system (E.164) with various address systems such as telephone, e-mail, fax, and internet telephone to ensure commonness and uniqueness of Internet application services. It has been adopted by the Organization as a Standard (RFC2916) and is rushing to be adopted by countries around the world.

In other words, ENUM improves access and use of various information resources by converting telephone numbers, which are identification systems of public telephone exchange networks, into Internet address systems. ENUM was first discussed at the Internet Engineering Task Force (IETF), an Internet-based technical standardization group, and is currently working on ENUM in the ENUM Working Group (WG). ENUM WG released RFC2916 in 2000, which defined a protocol for converting E.164 phone numbers into Uniform Resource Identifiers (URIs) based on DNS. The most basic in ENUM is the combination of the existing Public Switched Telephone Network (PSTN) and Internet Protocol (IP) network. Because phone numbers and Internet addresses work on a single system, entering a phone number on your computer allows you to connect to a variety of communication services, including the Internet homepage, email, fax, and Internet phone.

However, in the past, in the query and response between the ENUM client and the ENUM DNS, the form of querying and returning the queried telephone number 082-02-2186-4551 between the local DNS and the DNS server of each hierarchy is 82.2.2186. It has a hierarchical structure of 4551 and has a limitation of the management system and the search speed because the search is performed according to the buffer and cache when searching the queried telephone number.

In addition, there is no situation in which a separator is defined to distinguish a homepage on a wired homepage and a wireless homepage associated with a phone number.

Accordingly, an object of the present invention is to provide an ENUM DNS layer 1 and 2 structure, a communication method between an ENUM client and DNS, an ENUM service system for registering an ENUM service for a phone page, which is a homepage on a wireless Internet, in order to expand search efficiency and commonality. It is to provide a method of operation.

Specifically, an object of the present invention is to separate the ENUM DNS by 1 and 2 layers, the ENUM DNS layer 1 stores information on the ENUM number, the layer 2 stores service information on the ENUM number, and forms a mutual delegation scheme. The purpose of this study is to establish a stable and common ENUM service system by defining the roles of DNS layers 1 and 2, information contents, and optimal zone file composition method.

In addition, another object of the present invention, when using the ENUM service, after the client program performs a query for the ENUM number to the ENUM DNS, in order to receive service information such as an email address, telephone number, homepage address, The purpose is to improve the commonality of the ENUM service by defining the library elements that should have.

Another object of the present invention is to define an ENUM service registration format using various content types such as WML and HDML for the phone page to define the distinction between the homepage and the phone page on the wired line. Can be extracted and to improve the applicability of the service.

1 is a conceptual diagram of an ENUM service.

2 is a diagram illustrating the configuration of an ENUM DNS layer 1 zone file.

3 is a diagram illustrating a configuration of an ENUM DNS layer 2 zone file.

Figure 4 is a graph of the ENUM DNS layer 1 zone single test results.

5 is a graph of ENUM DNS layer 2 zone single test results.

FIG. 6 is a graph showing ENUM DNS layer 1 and 2 zone interworking test results. FIG.

7 is a schematic diagram showing an ENUM client flow chart and standard configuration range.

8A and 8B are flowcharts illustrating a communication method between an ENUM client and an ENUM DNS according to an embodiment of the present invention.

9 is a conceptual diagram after applying the 'E2U + mob' ENUM service registration format.

The present invention for achieving the above object of the present invention is applied to the ENUM service system consisting of ENUM client, local DNS, layer 0, layer 1 and layer 2 to perform the query and response between the ENUM client and the ENUM DNS, ENUM service system of the present invention is a layer 0 which is the highest layer for storing DNS location information of each country code; A layer 1 which forms a delegate layer with the layer 0 and stores layer 2 location information for each telephone number; And a layer 2 which forms the delegate layer with the layer 1 and stores the ENUM service information in the NAPTR format in order to perform the service information response to the ENUM number query.

At this time, the layer 1 separates the zone file by the destination number including the station number and the carrier number, and the layer 2 separates the zone file by the destination number including the station number and the carrier number. In the layer 2, the ENUM service information for the subscriber number is stored by using the NAPTR record in each destination zone file.

In addition, the ENUM DNS layer 1 checks whether the ENUM number of the registration applicant is correct at the time of ENUM registration and performs the role of the registration management authority to determine the end-use authority and to prevent duplicate registration, the ENUM DNS layer 1 ENUM DNS Layer 2 name server that stores service information including fully qualified domain name (FQDN) of ENUM number and its email, telephone number, and homepage address to perform authentication and duplicate registration prevention. It stores information, and preferably two or more ENUM DNS layer 2 name server information.

The ENUM DNS layer 2 stores the service information and returns a corresponding service information value when the ENUM number FQDN is queried. The ENUM DNS layer 2 may be operated by a plurality of layer 2 management entities such as a communication service provider.

On the other hand, the phone page address for each mobile carrier may be defined as E2U + mob, which is a service type distinguished from the contents on the wire, and stored in the NAPTR format in the ENUM DNS layer 2.

On the other hand, the present invention for achieving the above object of the present invention ENUM client; Local DNS; Layer 0, which is a top layer storing DNS location information of each country code; A layer 1 which forms a delegate layer with the layer 0 and stores layer 2 location information on a telephone number; And a layer 2 which forms a delegation layer with the layer 1 and stores ENUM service information using a NAPTR format, which is a DNS standard resource record type, to perform service information response to an ENUM number query. The present invention relates to a method of operating an ENUM service system that performs a query and a response between an ENUM DNS and an ENUM client composed of layer 0, layer 1, and layer 2, wherein the method of operating an ENUM service system of the present invention is input through a client program. A first step of converting the converted ENUM number into a domain name system; Querying the local DNS with a DNS message format; A third step of receiving NAPTR records by querying and returning between the local DNS and layer 0, layer 1, and layer 2; And a fourth step of outputting the ENUM service information list in the client program.

In this case, the first step may include removing special characters including + and-from the inputted telephone number including country code, destination number (area code or mobile carrier number) and subscriber number; Converting the phone number from which the special characters have been removed in reverse order; Inserting a dot (.) Between each digit of the reverse phone number; And adding a top layer name to the telephone number in which the dot (.) Is inserted. For example, + 82-2-2186-4551 is converted to 1.5.5.4.6.8.1.2.2.2.8.e164.arpa.

Further, in the second step, setting of the DNS message main field is

ENUM Fully Qualified Domain Name (FQDN) form converted in step QNAME = 1;

QTYPE = NAPTR 35;

RD = 1; And

QDCOUNT = 1 (where QNAME is the value to query, QTYPE is the type of record information to be answered, RD is repeated query, and QDCOUNT is the number of queries).

The third step may include receiving query data sent from the ENUM client in a local DNS and querying layer 0; Retrieving information corresponding to a country code from the transmitted DNS message and returning DNS location information for storing the country code to a local DNS; Querying layer 1 where the telephone number zone for the country code is stored in the local DNS; Performing a search on the zone file according to the destination number classification in layer 1 to extract the corresponding destination number, and then returning DNS location information according to the subscriber number to the local DNS; The local DNS querying layer 2 in which the service information is stored in the form of NAPTR for the telephone number; And returning the service information stored in the NAPTR form for the telephone number to the local DNS in Layer 2.

Meanwhile, in the fourth step, the ANCOUNT value is checked and the NAPTR record value of the response section is extracted by the corresponding value. At this time, the field value identifying the response of the header section of the information receiving message may be checked, and the step of confirming whether the response is confirmed may be further performed.

Hereinafter, with reference to the accompanying drawings will be described a preferred embodiment of the present invention.

1 is a conceptual diagram of an ENUM service. As shown in FIG. 1, tNUM Phone Mapping (ENUM) is an integrated number identification system that integrates various DNS-based application service addresses hierarchically separated into one phone number. Converged application service is possible. In addition, as well as a general PC, it can be implemented in various environments such as a mobile phone, PDA, telephone.

ENUM service can be used by entering a phone number in the address bar of ENUM-only program and web browser on PC.

In other words, by performing the process of changing the telephone number input from the client, which is an ENUM-only program, to the domain name ①, according to the promise established by RFC 2916 'E.164 Number and DNS' in the above IETF, + 82-2-2186- Convert 4551 to 1.5.5.4.6.8.1.2.2.2.8.e164.arpa. In the conventional case, in preparation for converting the inputted telephone number into 4551.2186.2.82, the conversion as in the present embodiment is not only different from the existing one, but also based on the above-mentioned international standard RFC 2916.

On the other hand, ENUM DNS stores service information (e-mail, homepage, Internet phone) in DNS, which is stored in the above 1.5.5.4.6.8.1.2.2.2.8.e164.arpa.

Email is IN NAPTR 'E2U + email: mailto' 'mailto: sjlee@nic.or.kr',

The homepage is IN NAPTR 'E2U + web: http' 'http://www.nic.or.kr',

Internet phone using SIP is IN NAPTR 'E2U + sip' 'sip: sjlee@nic.or.kr'

Stored as.

The ENUM DNS is hierarchically separated for efficiency of searching, in particular, layer 1 stores layer 2 location information on an ENUM number, and layer 2 stores service information on an ENUM number.

The present invention defines the role of ENUM DNS Layers 1 and 2, information content, and optimal zone file construction. The conventional case has a hierarchy of 82 · 2 · 2186 · 4551, but has a hierarchy of Root · 82 · NAPTR DNS.

ENUM client program prepares standard about the value that should be set in order to query ① ENUM DNS and receive service information (e-mail, homepage, phone number, etc.). Regulate. This will be described later in detail.

In addition, the mobile phone service provider stipulates the ENUM service registration format for the phone page. This makes it possible to clarify the classification of phone page types by mobile carriers with various content formats, thereby improving the accuracy of using ENUM service on mobile phones.

Hereinafter, the present invention will be described in detail, in order of 1. ENUM DNS hierarchy structure , 2. ENUM client and DNS communication method , 3. ENUM service registration for the phone page .

1. ENUM DNS Layer 1 and 2 Structure

As described above, ENUM (Telephone Number Mapping) is a next-generation integrated number identification system, which is discussed in the IETF, ITU, etc., and a phone number is converted into a uniform resource identifier (URI) based on the Domain Name System (DNS). It is a protocol to convert.

ENUM DNS is divided into layers, and ENUM DNS layer 1 has different characteristics from existing domain names, such as layer 2 location information on ENUM numbers, and layer 2 stores a plurality of pieces of service information on ENUM numbers.

The present invention proposes the contents of the zone file configuration of the ENUM DNS layer 1 and 2, which is new content not defined in the existing IETF RFC, ITU-T Recommendation.

ENUM is defined in IETF RFC 2916 and is a protocol that converts telephone numbers into a uniform resource identifier (URI) based on DNS. ENUM DNS consists of layers 0, 1, and 2 and forms a delegation structure of a tree structure.

Layer 1 forms a delegation layer with layer 0. It creates a country code zone file (e.g. 2.8.e164.arpa in Korea) to store layer 2 location information for the phone numbers in the zone file. have.

Layer 2 stores ENUM service information in the form of Naming Authority Pointer (NAPTR) to perform a service information return for an ENUM number query. Here, NAPTR is a DNS resource record (RR) used for resolving a plurality of naming systems.

In this embodiment, a stable and common ENUM service can be provided by defining roles, information contents, and an optimal zone file construction method, which are details of ENUM DNS layers 1 and 2.

First, the role and information content of ENUM DNS layer 1 will be described.

In the role of ENUM DNS layer 1, name server information of ENUM DNS layer 1 is registered in e164.arpa name server, which is ENUM layer 0, to form a delegation layer. In Korea, the name server information of 2.8.e164.arpa, the ENUM DNS layer 1 zone file of Korea, is registered in ENUM DNS layer 0. ENUM DNS Layer 1 acts as a Registry. The Registration Agency checks the ENUM number (telephone number) of the applicant for registration at the time of ENUM registration and performs the authentication and duplicate registration prevention process to determine the final use authority.

For information in ENUM DNS Layer 1, ENUM DNS Layer 1 is the Fully Qualified Domain Name (FQDN) of the ENUM number and its service information (email, phone number, ENUM DNS Layer 2 name server information is stored. For example, the number for registering to ENUM is + 82-2-2186-4551, the ENUM DNS tier 1 name server address is ns.enum.or.kr, and the tier 2 name server address is ns1.enum2.or.kr , ns2.enum2.or.kr, ENUM DNS Layer 1 is the nameserver address for 1.5.5.4.6.8.1.2.2 in the 2.8.e164.arpa zone file, ns1.enum2.or.kr, ns2. Enum2.or.kr must have all the information. Schematic of this is as follows. Table 1 shows ENUM DNS layer 1 information.

TABLE 1

Next, the role and information content of ENUM DNS Layer 2 will be described.

In the role of ENUM DNS Layer 2, ENUM DNS Layer 1 stores Layer 2's name server information to form a Delegation Layer with Layer 2. ENUM DNS Layer 2 stores service information (email, phone number, homepage address, etc.) for the ENUM number FQDN and returns the corresponding service information value when querying the ENUM number FQDN. Layer 2 may be operated by a plurality of carriers, such as backbone communications / star communications for number management and authentication.

In the information of ENUM DNS layer 2, ENUM DNS layer 2 stores ENUM service information using a Naming Authority Pointer (NAPTR) Resource Record (RR). For example, ENUM number 82-2-2186-4551 is registered in ENUM DNS layer 1, and the service information is sjlee@enum.nic.or.kr, 82-2-2186-4551, and email. When registering and using the address sjlee@nic.or.kr and the homepage address www.enum.or.kr, the information of ENUM DNS Layer 2 is as follows. Table 2 shows ENUM DNS layer 2 information.

TABLE 2

Next, a method of constructing a zone file of ENUM DNS layers 1 and 2 will be described.

Principles for the construction of ENUM DNS layer 1 and 2 zone files are as follows:

First, when registering ENUM, phone number FQDN should be stored in ENUM DNS layer 1 to prevent duplication, dispute resolution, and verification of ENUM number.

Second, the response speed of DNS queries should be fast for ENUM service quality management.

Third, when telephone number station number is created, integrated, changed and deleted, it must be easy to manage to reflect it quickly and accurately in ENUM DNS.

Fourth, when ENUM service information is created, integrated, changed, or deleted, it should be quickly reflected in ENUM DNS.

In order to satisfy these conditions, the zone file of ENUM DNS Layer 1 consists of zone file by 2.8.e164.arpa zone file and domestic destination number (telephone number FQDN configuration: country code + domestic destination number + subscriber number). Form a delegation system.

2 is a diagram illustrating the configuration of an ENUM DNS layer 1 zone file.

In other words, domestic destination number 011, 064 is present, the phone number + 82-11-123-4567, + 82-11-123-4568, + 82-64-555-7777, + 82-64-555 If -7778 exists, the name server information of 1.1.2.8.e164.arpa and 4.6.2.8.e164.arpa is stored in the 2.8.e164.arpa file. In 1.1.2.8.e164.arpa file, the name server information of ENUM DNS Layer 2, which has service information of + 82-11-123-4567 and + 82-11-123-4568, should be stored. In the .e164.arpa file, the name server information of ENUM DNS Layer 2, which contains service information of + 82-64-555-7777 and + 82-64-555-7778, must be stored.

If ENUM DNS is configured in the same way as above, phone number FQDN can be stored, registered, duplicated, dispute resolution and authentication can be performed. This can improve the quality of service management. In addition, even when domestic destination number is changed, such as generation, consolidation, deletion, modification, change of operator of the same number by the number portability can be reflected immediately, it is easy to manage the phone number.

3 is a diagram illustrating a configuration of an ENUM DNS layer 2 zone file.

The file of ENUM DNS layer 2 is divided and organized by the domestic destination number configured in layer 1. That is, the contents of the ENUM service information are stored in a file for each destination number.

For example, domestic destination number is 011, 064, phone number is + 82-11-123-4567, + 82-11-123-4568, + 82-64-555-7777, + 82-64-555- Assuming 7778 exists, two zone files, 1.1.2.8.e164.arpa and 4.6.2.8.e164.arpa, are separated and configured in ENUM DNS layer 2. Layer 2 also stores service information of + 82-11-123-4567 and + 82-11-123-4568 using NAPTR RR in 1.1.2.8.e164.arpa. In the 4.6.2.8.e164.arpa zone file, the service information of + 82-64-555-7777 and + 82-64-555-7778 is stored using NAPTR RR.

As shown in FIG. 3, grouping by destination number in Korea and separating and configuring the zone file is superior in terms of search speed and telephone number management than configuring zone files for each phone number FQDN.

In addition, if a zone file is configured for each destination number in Korea, the dynamic update method can be used to reflect changes in the generation, modification, and deletion of ENUM service information in the DNS in real time, which facilitates information management. Done.

The speed test results for the optimal zone file construction method for the layer 1 and layer 2 will be described.

The test targets are ENUM DNS Layer 1 (SUN 280R) and ENUM DNS Layer 2 (SUN 280R), and the test conditions consist of ENUM DNS Layer 1 and 2 Zone Files (four in total) to eliminate TTL (Cache). Time To Live) is set to zero. In the case of 10,000 data / 50,000 data, a total of eight tests were performed to evaluate the same situation by increasing the number of queries from 1,000 to 15,000 by 1,000 three times.

In the layer 1 described below, the term 'integration' means that all of the layer 2 location information of the telephone number is stored in a country code zone file. This means that the layer 2 location information of the telephone number is grouped by the destination number and stored in the zone file. In addition, the name 'individual' in layer 2 means creating a zone file for each telephone number and storing the service information file.In the layer 2, the name 'group' groups service information for a telephone number by destination number. It means to save in the zone file.

Table 3 is a test schematic.

TABLE 3

Table 4 shows examples of using Queryperf.

TABLE 4

Table 5 is a test situation table.

TABLE 5

The zone file configuration of each test condition is as follows.

① Tier 1 integration

② Tier 1 Group

③ Tier 2 Individual

④ Tier 2 Group

⑤ Tier 1 Integration / Tier 2 Individual

⑥ Tier 1 Integration / Tier 2 Group

⑦ Tier 1 Group / Tier 2 Individual

⑧ Tier 1 Group / Tier 2 Integration

For other details during testing, the zone data content is 2 (Seoul), 51 (Busan), 53 (Daegu), 62 (Gwangju), 42 (Daejeon), 32 (Incheon), 52 (Ulsan), 31 (Gyeonggi-do), 33 (Gangwon-do), 43 (Chungcheongbuk-do), 41 (Chungcheongnam-do), 54 (Gyeongsangbuk-do), 55 (Gyeongsangnam-do), 63 (Jeollabuk-do), 61 (Jeollanam-do), 11 (SKT), 16 (KTF), 19 (LGT), 17 (SKT), 18 (KTF), and the FQDN phone number is an eight-digit number excluding DDDS and carrier-specific phone numbers, for example, 82-2-1234-5678, 82-11-1234-45678 The total number of NAPTR data is five, namely, a homepage, an e-mail, an Internet telephone, a general telephone, and a mobile telephone.

In other words, the NAPTR format is

8.7.6.5.4.3.2.1.2.2.8.e164.arpa NAPTR 100 50 "u" "E2U + sip" "! ^. Sip: 031-123-4567@100.100.10.10!"

NAPTR 100 50 "u" "E2U + http" "! ^ .Http: //www.enum.or.kr!" .

NAPTR 100 50 "u" "E2U + mailto" "! ^. Mailto: jenum-info@nic.or.kr!" .

NAPTR 200 50 "u" "E2U + sip" "! ^. Sip: 00017@100.100.10.10!" .

NAPTR 300 50 "u" "E2U + sip" "! ^. Sip: 011-123-4567@100.100.10.10!"

to be.

[Table 6] is a table showing the result of layer 1 integration / layer 1 group for 10,000 data.

TABLE 6

[Table 7] is a table showing the result of layer 1 integration / layer 1 group for 50,000 data.

TABLE 7

4 is a graph showing the results of the ENUM DNS layer 1 zone alone test.

Table 8 shows the results of layer 2 individual / layer 2 group for 10,000 data.

TABLE 8

Table 9 shows the results of layer 2 individual / layer 2 group for 50,000 data.

TABLE 9

5 is a graph of ENUM DNS layer 2 zone single test results.

In the graph, Series 1 is Consolidated / Individual, and Series 2 is Consolidated / Group.

[Table 10] is a table showing ENUM DNS layer 1/2 interworking test results for 10,000 data.

TABLE 10

[Table 11] is a table showing ENUM DNS layer 1/2 interworking test results for 50,000 data.

TABLE 11

Figure 6 is a graph of the ENUM DNS layer 1/2 zone interworking test results.

In the graph, Series 1 is Consolidated / Individual, Series 2 is Consolidated / Group, Series 3 is Group / Individual, and Series 4 is Group / Group.

2. Communication method between ENUM client and DNS

To use ENUM (Telephone Number Mapping) service, client program should query ENUM DNS (Local Name System) or local DNS for ENUM number and receive service information (e-mail address, phone number, homepage address, etc.). do.

In this embodiment, the library elements that the ENUM client program should have in the above process are defined.

The field defined in the present embodiment newly defines a DNS message format for ENUM by utilizing existing DNS message format standards and NAPTR (Naming Authority Pointer) standards.

The ENUM client program converts an ENUM number (E.164 phone number) into a domain name system to query the hierarchically separated ENUM DNS or local DNS. ENUM DNS returns service information (email address, phone number, homepage address, etc.) for the ENUM number, and the ENUM client program receives the information and connects the service you want.

In other words, in order to use ENUM service, client program should convert to domain name system of ENUM number, query information list by ENUM DNS or local DNS and output information list according to receiving service information.

In this embodiment, as described above, the communication method between the ENUM client and the DNS that the ENUM client program should comply with is defined.

7 is a schematic diagram showing an ENUM client flow chart and standard configuration range. As shown in FIG. 7, the overall flow of an ENUM service performed by an ENUM client is as follows.

1. Enter the ENUM number. Enter a telephone number, for example + 82-2-2186-4551, through the client program.

2. Convert the ENUM number. Conforms to RFC 2916 to convert ENUM numbers to the domain name scheme, 1.5.5.4.6.8.1.2.2.2.8.e164.arpa.

3. Send and query the ENUM number. Query ENUM DNS server by converting ENUM number to DNS message format.

4. Receive ENUM service information. Receive NAPTR records returned by ENUM DNS.

5. Create and print a list of information. Output the ENUM service information list from the client program.

This will be described in detail with reference to FIG. 8.

8A and 8B illustrate a communication method between an ENUM client and an ENUM DNS according to an embodiment of the present invention.

In this description, a communication method between an ENUM client and an ENUM DNS will be described based on the above-described configuration of layers 1 and 2, and it will be described on the assumption that ENUM service registration for a phone page is made.

First, in order for the present invention to be carried out, the overall system is roughly composed of an ENUM client, a local DNS, layer 0, layer 1, and layer 2.

Run ENUM client program and input ENUM number through this program. At this time, the input ENUM phone number is entered in the form of + 82-2-2186-4551 (S1). This input ENUM telephone number is converted into 82221864551 by which the + and-symbols have disappeared by the ENUM client program (S2). Then, the converted 82221864551 is converted in reverse order. That is, it is converted into 15546812228 (S3). Next, a dot (.) Is inserted into 15546812228, which is converted in the reverse order, and converted into a 1.5.5.4.6.8.1.2.2.2.8 form (S4). Finally, the ENUM client program adds 1.5.5.4.6.8.1.2 by adding e164.arpa, the domain name of layer 0, the top layer, to 1.5.5.4.6.8.1.2.2.2.8 with a dot (.) Inserted. Outputs .2.2.8.e164.arpa (S5).

Query the local DNS outputted 1.5.5.4.6.8.1.2.2.2.8.e164.arpa.

At this time, the query is converted to the DNS message format and then the query is made. The DNS message setting method for the ENUM number query is as follows.

In ENUM number query, DNS message consists of five fields: Header, Question, Answer, Authority, and Additional. In order to query ENUM DNS to ENUM DNS, it should be set to the appropriate value for each field of Header and Question Section of DNS message format.

First, in the Header Section, the RD (Recursion Desired) value is set to 1. The ENUM client obtains the name server information of the layer 2 through the ENUM DNS layer 1, and finally the ENUM service information using the NAPTR RR from the layer 2. (Email address, phone number, homepage address, etc.). To do this, you must enable the Recursion feature so that referrals from ENUM DNS layer 1 to layer 2 can operate normally.

If the RD value is set to 0, since the ENUM client retrieves only the name server location information of the layer 2 from the layer 1, a new algorithm is needed to receive the ENUM service information value using the NAPTR RR through an iterative query. That is, if the RD value is set to 1, the ENUM service information can be normally received without additional work.

Also, set QDCOUNT to "1" to query one ENUM number to ENUM DNS.

Other values are set to "0".

[Table 12] shows how to set the query message header section.

TABLE 12

In the Question Section, the phone number FQDN (Fully Qualified Domain Name) converted to the domain name system is stored in the QNAME. That is, + 82-2-2186-4551 is stored as 1.5.5.4.6.8.1.2.2.2.8.e164.arpa.

QTYPE is set to 35 which is NAPTR RR QTYPE to receive NAPTR RR value. The 16-bit value is 23.

QCLASS is set to 1, the internet class.

[Table 13] is a table showing how to set a query message Question Section.

TABLE 13

to summarize,

QNAME = 1.5.5.4.6.8.1.2.2.2.8.e164.arpa

QTYPE = 35 (NAPTR)

RD = 1

QDCOUNT = 1

The query is made to the local DNS from the ENUM client (S6).

As described above, in the present embodiment, the ENUM client program defines the DNS message format, setting values and confirmation items for querying the ENUM number with the ENUM DNS and receiving service information. In particular, 3. ENUM number transmission and inquiry and 4. ENUM related information are included in the scope of this standard.

On the other hand, the local DNS receives the query data transmitted from the ENUM client and performs a query to the highest layer 0 (S8). The layer 0 searches for information corresponding to the country information (2.8) in the transmitted file (S9) and returns DNS location information storing the country information to the local DNS (S10 to S11).

In response to this, the local DNS queries the telephone number to the layer 1 in which the country information is stored (S12). In layer 1, the zone file is searched according to the destination number (2, 1.1) classification. The destination number is extracted (S13), and then the DNS location information according to the subscriber number (1.5.5.4.6.8.1.2) is extracted in the form of NAPTR (S14). DNS location information extracted in the form of NAPTR is returned to the local DNS (S15).

Accordingly, the local DNS queries the layer 2 in which the DNS location information extracted in the form of NAPTR is stored (S16). In step 2, the service information, which is NAPTR records, is returned to the local DNS (S17).

Subsequently, the local DNS performs a response to the ENUM client (S18). At this time, in receiving the ENUM service information, after checking the field value of the header section of the ENUM service information reception message, the local section receives and outputs the service information in the Answer Section. .

First, in the Header Section, check whether the message is set to 1 indicating a response in the QR (Question or Response) field. Verify that the AA (Authoritative Answer) field is 1 for the confirmation response. In addition, the ANCOUNT value is checked, and the corresponding NAPTR record value of the answer section is parsed by the corresponding value (S19).

In the Answer Section, check the integer values of the Order and Pref in the NAPTR record and the "u" Type in the Flags field. The related information is a string between "and", where! Is a separator and ^. * $ Represents a regular expression.

Table 14 shows an example of the response message.

TABLE 14

3. Register ENUM service for phone page

ENUM service registration is stored in ENUM DNS Layer 2 and follows the guidelines set forth in RFC 2916bis. Currently, the service registration format for SIP, H.323, IFAX, HTTP, FTP, etc. is proposed as a standard.

The web protocols on the wired Internet and phone pages are the same in that they use HTTP, but the content types are different. In other words, the wired Internet uses HTML as the basic content format, while the phone page uses WML and HDML as the content format. As a result, the content addresses of wired Internet and phone pages should be different, and the ENUM service registration format should be different.

Therefore, the present invention is configured to include the content address information of the phone page for the ENUM number, and provides the ease of access to the phone page using the ENUM number in the wireless Internet environment using the same.

Therefore, the present embodiment shows an example of applying the ENUM service registration format for the phone page. Through this, it is possible to extract more accurate address from the mobile phone and improve the applicability of the service.

The domestic phone page content format uses A WAP (Wireless Application Protocol), B company (ME), and C company uses WAP (Wireless Application Protocol). Differences exist between A and C using the same WAP method. As a result, three companies A, B, and C all adopt different content formats.

Therefore, ENUM service registration for A, B, C company should be defined.

First, in ENUM service registration, the ENUM service registration template for each of three domestic mobile communication companies is as follows.

Company A (e.g., SKT)

Company B (eg KTF)

Company C (eg LGT)

In the 'E2U + mob' ENUM service, the phone page is different from the content based on HTML on the wire, and the address value of the phone page content is different from the wired content, so a service type for the phone page is required.

That is, since a new definition for a service type for a phone page other than "web", which is a wired ENUM service type, is required, this standard applies "mob" as a service type for a phone page. The phone page address is stored as "E2U + mob" on the ENUM NAPTR RR, and can be distinguished from the ENUM service registration format on the wire.

In addition, even if the same phone page, domestic SKT, KTF, LGT adopts the phone page format in different ways, it is necessary to distinguish each company. Thus, this standard defines skt, ktf, and lgt subtypes to distinguish phone page types by company.

In conclusion, the ENUM service registration format for skt is classified as "E2U + mob: skt", the ENUM service registration format for ktf is "E2U + mob: ktf", and the ENUM service registration format for lgt is "E2U + mob: lgt".

If the ENUM service registration format defined in this standard is applied as above, it can be applied in a mobile phone as follows. 9 is a conceptual diagram after applying the 'E2U + mob' ENUM service registration format.

In the 'E2U + mob' ENUM service example, [Table 15] shows an example of using ENUM service registered in NAPTR.

TABLE 15

The present invention is not limited to the above-described embodiments, and it will be apparent that many modifications are possible by those skilled in the art within the technical spirit of the present invention.

As described above, the ENUM service system and its operation method according to the present invention has the following advantages.

If ENUM DNS is configured according to the hierarchical configuration, it is possible to store, register, and prevent duplicate duplication, dispute resolution, and verification of the phone number. This can improve the quality of service management. In addition, even when domestic destination number is changed, such as generation, consolidation, deletion, modification, change of operator of the same number by the number portability can be reflected immediately, it is easy to manage the phone number. In addition, it is better in terms of retrieval speed and phone number management than grouping each destination address number into a zone file rather than a zone file for each phone number FQDN. On the other hand, if a zone file is configured for each country's destination number, the dynamic update method can be used to reflect changes in generation, modification and deletion of ENUM service information in DNS in real time for easy information management. Done.

The mobile communication ENUM service registration in the format stored in the ENUM DNS layer 2 can define a service type that is distinguished from the contents on the wire, and extract more accurate addresses on the mobile phone, and improve the applicability of the service.

Claims (14)

In the ENUM service system composed of ENUM client, local DNS, layer 0, layer 1 and layer 2 to perform queries and responses between the ENUM client and ENUM DNS, Layer 0, which is a root server that stores DNS location information of each country code of a telephone number; A layer 1 which forms a delegate layer with the layer 0 and stores location information of the layer 2 for each country code; And A layer 2 that forms a delegation layer with the layer 1 and stores ENUM service information in a NAPTR format to perform a service information response to an ENUM number query. ENUM service system, characterized in that consisting of. The ENUM service system according to claim 1, wherein the layer 1 separates zone files by destination number including a station number and a division number for each mobile communication company. The method of claim 1, wherein the layer 2 separates the zone file for each destination number including the station number and the identification number for each mobile carrier, and uses the NAPTR record for the zone file for each destination in the layer 2 for the ENUM for the subscriber number. An ENUM service system, characterized by storing service information. The ENUM service system according to claim 1, wherein the ENUM DNS layer 1 is an ENUM service system which checks whether the ENUM number of a registration applicant is correct when registering ENUM and performs an authentication and duplicate registration prevention process for determining final use authority. . 5. The ENUM DNS layer 1 of claim 4, wherein the ENUM DNS layer 1 stores an ENUM number FQDN of the ENUM number and service information including e-mail, telephone number, and homepage address thereof to perform authentication and duplicate registration prevention. ENUM service system for storing DNS layer 2 name server information, wherein at least two ENUM DNS layer 2 name server information is stored. 2. The ENUM DNS layer 2 of claim 1, wherein the ENUM DNS layer 2 is operated by a plurality of management entities of a layer 2 including a service provider that stores the service information and returns a corresponding service information value when querying an ENUM number FQDN. ENUM service system. The ENUM service system according to any one of claims 1 to 3, wherein the mobile communication ENUM service registration in a format stored in the ENUM DNS layer 2 defines a service type that is distinguished from the content on the wire. 8. The method of claim 7, wherein the subtype is defined as E2U + mob in consideration of the case where the content format is different for each mobile carrier when registering the mobile communication ENUM service, and the phone page format for each mobile carrier is divided to NAPTR in the ENUM DNS layer 2. ENUM service system, characterized in that the format is stored. With ENUM clients: Local DNS; Layer 0, which is a top layer storing DNS location information of each country code of a telephone number; A layer 1 which forms a delegate layer with the layer 0 and stores location information of the layer 2 with respect to a telephone number; And an ENUM DNS: configured to form a delegation layer with the layer 1 and to store the ENUM service information using the NAPTR format, which is a DNS standard resource record type, to perform service information response to the ENUM number query. In the operation method of the ENUM service system that performs the response, A first step of converting the ENUM number input through the client program into a domain name system; Converting the ENUM number converted into the domain name system into a DNS message format and querying the local DNS; A third step of receiving NAPTR records through query and return between the local DNS and layer 0, layer 1, and layer 2; And The fourth step of outputting the ENUM service information list in the client program Operation method of the ENUM service system, characterized in that made. The method of claim 9, wherein the first step, Removing special characters including + and-from an inputted phone number including country code, area code or mobile carrier number, and phone number; Converting the phone number from which the special characters have been removed in reverse order; Inserting a dot (.) Between each digit of the reverse phone number; And Adding a root server name to the telephone number into which the dot (.) Is inserted Operation method of the ENUM service system, characterized in that made. 11. The method of claim 9 or 10, wherein the setting of the DNS message field in the second step, QNAME = ENUM Fully Qualified Domain Name (FQDN) converted in the first step; QTYPE = NAPTR; RD = 1; And Operation method of the ENUM service system characterized by consisting of QDCOUNT = 1 (where QNAME is the value to query, QTYPE is the type to be answered, RD is a recursive query, QDCOUNT is the number of queries) The method of claim 9, wherein the third step, Receiving query data sent from the ENUM client in a local DNS and querying layer 0 which is a root server; Retrieving information corresponding to a country code from the transmitted DNS message and returning DNS location information for storing the country code to a local DNS; Querying layer 1 where the telephone number zone for the country code is stored in the local DNS; In Layer 1, we search the zone file according to the destination number classification classified by station number and mobile carrier to extract the corresponding destination number, and then extract the DNS location information according to the subscriber number consisting of the phone number in the form of NAPTR. Returning the extracted DNS location information to a local DNS; The local DNS querying layer 2 in which the service information is stored in the form of NAPTR for the telephone number; And Returning the service information stored in the form of NAPTR for the telephone number to the local DNS at layer 2 Operation method of the ENUM service system, characterized in that made. 10. The method of claim 9, wherein the fourth step checks the ANCOUNT value and extracts the NAPTR record value of the response section by the corresponding value. The method as claimed in claim 13, further comprising: checking a field value for identifying a response of a header section of the information reception message, and confirming whether a response is confirmed.