Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/09—Mapping addresses
  • H04L61/10—Mapping addresses of different types
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/09—Mapping addresses
  • H04L61/25—Mapping addresses of the same type
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/45—Network directories; Name-to-address mapping
  • H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

• the present invention relates to network addressing over internets and intranets.
• the invention finds particular application in converting telephone numbers into a multi- level domain name to enable devices on a network to communicate. It is to be appreciated however, that the present invention may find further application in private networks or public networks and using private protocols or internet protocols.
• a domain name typically includes a name, plus a x .” (dot) or separator, and a Top Level Domain (TLD) such as " com” , "net”, and w org” .
• TLD Top Level Domain
• Not IP Addressable This means that an individual "site" does not have the option to have a unique IP address and/or a shared one. The only option is a shared IP address with the primary domain name holder.
• the present invention contemplates an improved method and apparatus for a network addressing system which includes a telephone number as a component of the address.
• a method includes receiving a telephone number portion which identifies a device with which communication is desired.
• the telephone number portion is converted into a multiple level domain name which statically represents the device on the network.
• a component of the multiple level domain name is the received telephone number portion. Communication is then established with the device over the network.
• the converting step includes adding domain separators to the received telephone number portion at determmable locations in the received telephone number portions .
• the received telephone number portion includes a separator
• the converting step includes parsing the received telephone number portion for the separator and inserting a domain separator therefor.
• additional domain levels are appended to the converted telephone number portion to complete the multiple level domain name.
• an apparatus to establish communication between at least two devices over a network includes a processor which receives from a first device a telephone number portion identifying a second device. The processor then converts the telephone number portion into a static multiple level domain name sufficient to identify the second device on the network.
• the apparatus further includes a table which matches the static multiple level domain name to a static IP address.
• One advantage of the present invention resides lr the ability to have internet domain names that are meaningful dn ⁇ simultaneously more economical than traditionally used.
• Another advantage of the present invention resides m the ability to convey both an internet address and a telephone number compactly and economically m a communication .
• the invention may take physical form m certain parts and arrangements of parts, and m certain steps and arrangements of steps.
• the drawings are only for purposes ot illustrating the preferred embodiments and are not to be construed as limiting the invention.
• FIGURE 1 is a generic representation of a typical network addressing system or domain name structure
• FIGURE 2 is an exemplary U.S. telephone number
• FIGURE 3 is the telephone number of Figure 2 following conversion into a multiple level domain name
• FIGURE 4 is a flowchart detailing a logical flow that suitably practices the present invention
• FIGURE 5 is a graphical depiction of device connectivity across a network as provided by the present invention.
• an internet telephone number or numbering system is defined as a domain name or set of domain names that enables network addressing system through the use of telephone numbers or internet/intranet networks.
• a telephone number portion is herein defined as at least a part of a telephone number which can include the exchange, the area code, and/or the country code. While telephone numbers generally have gradually increasing geographic specificity with the most generic portion preceding more definite portions, (i.e. the country code precedes the area code which precedes the exchange, etc.) the particular order m which a telephone number portion is converted or presented as a static multiple level domain name is immaterial according to the present invention. That is, the received telephone number may be rearranged m any sequence without materially affecting the scope of the subject invention so long as all are likewise arranged or determmable . As use herein the terms source, target, and/or device are intended to refer to any variety addressable devices interconnected via any of a variety of networks.
• devices amenable to the present invention include without limitation, computers, storage devices, output devices, telephones, personal information managers, laptop, palmtop, or watch based computers, and the like.
• Interconnecting networks include without limitation, intranets, or the internet, wireless and/or wireline telephone networks, either public or private, hardwired, infrared, optical, or electro-magnetic networks and the like.
• BLD Base Level Domain
• the base level domain 10 sometimes called a top level domain or first level domain, is not associated with an IP address itself but is a logical grouping used to distinguish between countries (e.g.
• the second level sub-domain 12 is normally associated with an IP address when used in conjunction with a BLD 10.
• An example of a second level domain name is IBM as used m IBM.COM, or OSU as used m 0SU.EDU.
• the second level domain 12 usually manages any inquiries to the third level sub-domain 1 .
• the third level sub-domain 14 is also normally associated with an IP address when used m conjunction with both .2LD.BLD 12, 10.
• An example of a third level domain name is SUPPORT as used m SUPPORT.IBM.COM.
• the third level sub-domain 14 usually manages any inquiries to the fourth level sub-domain 16.
• the fourth level sub-domain 16 is usually associated with an IP address when used in conjunction with .3LD.2LD.BLD 14, 12, 10.
• Some examples of a fourth level domain name are PC or AIX as used m PC.SUPP0RT.IBM.COM or AIX.SUPP0RT.IBM.COM.
• the fourth level sub-domain 16 usually manages inquiries to the next domain 18 and so on.
• the Nth level domain 18 represents any and all higher level domains where the N represents integer intervals of higher level domains (i.e. 2, 3, 4, 5, 6,). All domain names can contain words or phrases consisting only of letters, numbers, and the dash, (a...z, 0..9, '-').
• All domain name levels 10-18 are separated by the ' ⁇ ot', the domain separator 30.
• This separator 30 is used to designate managing control of higher domain levels to their next lower domain level.
• Complete domain names consist of two parts: a domain name segment 34 and a base level segment 38.
• a base level segment 38 contains a .BLD 10, and contains any number of upper level sub-domains.
• Some examples of base level segments 38 are single level segments (e.g. .COM, .NET) and multi level segments (e.g. IBM.C0M; ABC.DEF.ORG; one.two.three.four.five.six.NET).
• Domain name segments are any group of one or more discrete 'names' separated by a dot 30 that does not contain a .BLD 10.
• do din name segments are single level segments (e.g. ABC, IBM, telenumber) and multi-level segments (e.g. ABC.DEF,
• a domain name tree 42 is any number of domain name segments 34 appended by a base level segment 38.
• a telephone number portion 50 is entered for translation into a single or multiple level domain name segment 34 enabling that segment to be grafted onto any existing domain name tree 42 at any point m that tree.
• the translation of the telephone number portion 50 consists of reducing the number into discrete pieces 52, 54, 56, 58 based on the natural separators 70, 72, 74 of that number, (e.g. dash, parenthesis, dot, or the like) .
• Figure 3 also illustrates appending of additional domain levels onto a converted or translated telephone number portion 50 ( Figure 2) .
• the additional sub domain, "telenumber” 90 and the top level domain, ".com” 92 are appended.
• domain levels may be appended anywhere m the multiple level domain name without departing from the spirit of the present invention.
• further domains or sub- domains can be used for other country codes, area codes, telephone exchanges, etc.
• Figure 4 an exemplary process is illustrated by which the telephone number portion of Figure 2 for example is converted into that of Figure 3.
• the user enters a query or a domain name which includes a telephone number portion suitable to identify a target or desired device across a network, as seen m step 100.
• An ambiguity may be introduced at this point when the processor determines where to place the domain separators 30.
• the ambiguity may be resolved, as seen by decision block 102, depending on whether the user enters separators m their query. If so, the processor then substitutes domain separators 30 for the user entered (manually or according to some predetermined protocol) organic separators 70, 72, 74 as seen m step 106 and illustrated in Figures 2 and 3.
• domain separators 30 will be inserted at determined locations based on information from, or data stored with the user (e.g. m cookies, or other predetermined protocol), assumptions made based on the particular protocol m use, or between determined numbers of digits or the like, as illustrated by step 108.
• the processor may affix any prefixes or suffixes needed to generate a complete multiple level domain name or as may be required based on known factors, as seen m step 110. For instance, an originating user may omit the country code, for example, of their target or desired device. In this case, the processor will recognize the insufficiency or ambiguity resulting from too few sub-domains m the address and substitute or append the country code of the originating user. Similar additions can be made by suffix if desired (e.g. automatic appending of a base level domain) .
• the target device is then queried across the network at the multiple level domain name generated, as seen in block 112. If the target device is available, it will respond in a like fashion at which point communication can be established between the source and the target devices, as seen in step 114.
• a generic system 120 is shown connected to a network 122 for suitably practicing the invention.
• a device 124 is connected to server 120.
• a processor 120a within the server receives from the device 124 a telephone number portion 50 ( Figure 2) address intended to identify a second device 128.
• the processor 120a converts the telephone number portion into a static multiple level domain name 96 ( Figure 3) identifying the second device 128 through the network 122.
• the device 128 is illustrated as also being connected to the network 122 via its own server, however numerous other interconnections are envisioned and apply with equal facility.
• the processor 120a determines the presence or lack of organic separators and, as discussed above, generates a complete multiple level domain name 96 suitable to identify device 128.
• the completed multiple level domain name 96 is then optionally converted m memory 120b to a standard IP address in this example.
• the target device 128 is then queried at the converted IP address location, and if available, responds to the query.
• the details of packet switching and call setup through the network along with path selection through the network are known to those in the art and proceed here conventionally.
• the invention has been described with reference to the preferred embodiment. Obviously, modifications and alterations will occur to others upon the reading and understanding of the specification. It is our intention to include all such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Theoretical Computer Science (AREA)
• Databases & Information Systems (AREA)
• Physics & Mathematics (AREA)
• Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Health & Medical Sciences (AREA)
• General Engineering & Computer Science (AREA)
• Data Mining & Analysis (AREA)
• Economics (AREA)
• General Health & Medical Sciences (AREA)
• Human Resources & Organizations (AREA)
• Marketing (AREA)
• Primary Health Care (AREA)
• Strategic Management (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Telephonic Communication Services (AREA)

Priority Applications (16)

Applications Claiming Priority (2)

Publications (1)

Family

ID=22503226

Family Applications (1)

Country Status (20)

Cited By (3)

Families Citing this family (1)

Citations (1)

Family Cites Families (4)

• 2000
  • 2000-07-07 ES ES200250002A patent/ES2217953B1/es not_active Expired - Lifetime
  • 2000-07-07 AU AU62075/00A patent/AU773711B2/en not_active Ceased
  • 2000-07-07 IL IL14754500A patent/IL147545A0/xx unknown
  • 2000-07-07 PL PL00354683A patent/PL354683A1/xx not_active Application Discontinuation
  • 2000-07-07 WO PCT/US2000/018698 patent/WO2001004767A1/en not_active Application Discontinuation
  • 2000-07-07 EA EA200200148A patent/EA003765B1/ru not_active IP Right Cessation
  • 2000-07-07 AT AT0911600A patent/AT411300B/de not_active IP Right Cessation
  • 2000-07-07 IL IL14753900A patent/IL147539A0/xx unknown
  • 2000-07-07 TR TR2002/00929T patent/TR200200929T2/xx unknown
  • 2000-07-07 CN CNB008101434A patent/CN1244061C/zh not_active Expired - Fee Related
  • 2000-07-07 JP JP2001510102A patent/JP2003504951A/ja active Pending
  • 2000-07-07 KR KR1020027000624A patent/KR20020042803A/ko not_active Application Discontinuation
  • 2000-07-07 BR BR0012639-0A patent/BR0012639A/pt not_active IP Right Cessation
  • 2000-07-07 CA CA002378697A patent/CA2378697A1/en not_active Abandoned
  • 2000-07-07 EP EP00948600A patent/EP1200900A4/de not_active Withdrawn
  • 2000-07-07 NZ NZ517071A patent/NZ517071A/en active IP Right Revival
  • 2000-07-07 MX MXPA02000287A patent/MXPA02000287A/es active IP Right Grant
• 2002
  • 2002-01-08 FI FI20020027A patent/FI20020027A/fi not_active IP Right Cessation
  • 2002-01-08 NO NO20020085A patent/NO20020085L/no not_active Application Discontinuation
  • 2002-01-09 LU LU90873A patent/LU90873B1/xx active
  • 2002-01-09 SE SE0200039A patent/SE0200039L/xx not_active Application Discontinuation

Patent Citations (1)

Also Published As

Similar Documents

Legal Events