as) United States
`a2) Patent Application Publication co) Pub. No.: US 2002/0122547 Al
`(43) Pub. Date: Sep. 5, 2002
`
`Hincheyetal.
`
`US 20020122547A1
`
`(54) METHOD AND APPARATUS FOR
`TELEPHONY ROUTE SELECTION
`
`(52) US. Ch.ec eeeteeseeeeeeseenes 379/221.01; 379/219
`
`(76)
`
`Inventors: Allan J. Hinchey, Kanata (CA);
`Douglas W. J. Zolmer, Nepean (CA)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`Neil Mothew
`Nortel Networks Limited, IPS Legal Department
`P.O. Box 832130
`Mail Stop 468/05/B10
`Richardson, TX 75083-2130 (US)
`
`(21) Appl. No.:
`
`09/746,103
`
`(22)
`
`Filed:
`
`Dec. 21, 2000
`
`Publication Classification
`
`(SL)
`
`Inte Cd. vecccesssestessissssttsstvatsvatnneessive H04M 7/00
`
`A method and apparatus for providing access device input
`format independenttranslations and route selection for tele-
`phony calls. A call request is received,
`the call request
`comprising input information being for a telephonycall. At
`least one call attributes is then determined from the input
`information and a routing policy request is transmitted to
`query a route database. Responsive to the routing policy
`request a routing policy response is received, the response
`comprising at least one routing parameter. The at least one
`routing parameter is used to influence call set up. Route
`selection is therefore not constrained by the service request
`input format.
`
`a 102
`NAGEMENT
`
`SERVER
`
`MA
`
`
`
`1284
`GATEWAY
`Gow
`
`1167
`
`GATEWAY
`Swe
`
`“120
`
`PSTN
`
`COUNTRY
`CODE=1
`O0C=6713, 819
`
`
`
`128
`
`
`
`
`ROUTE
`SERVER
`
`PSTN
`
`
`
`COUNTRY
`GATEWAY
`CODE=44
`
`Gw3
`NDC=181
`
`
`CALL SERVER
`
`
`cs2
`144
`
`:SIP-T
`MESSAGING
`
`PSTN
`
`COUNTRY
`CODE=69
`
`NDC=88
`i
`6789
`
`CALL SERVER
`csi
`
`104
`
`GATEWAY
`aw4
`
`16135915298
`
`}
`
`4419138008
`
`PETITIONER APPLE INC.
`
`EX. 1009-1
`
`PETITIONER APPLE INC. EX. 1009-1
`
`

`

`uoneoyqnguoneoyddyjuajeg
`
`
`
`
`OLJOL9487007‘Ss“das
`TVLes7cct0/700¢SN
`
`‘ft{tt
`
`tt
`
`MANAGEMENT
`SERVER
`
`
`
`PSTN
`
`
`COUNTRY
`
`
`
`ROUTE
`
`CODE=1
`
`PSTN
`
`SERVER
`NDC=613
`
`
`COUNTRY
`GATEWAY
`
`CODE=44
`GW3
`GW1
`GATEWAY
`
`
`NDC=1814
`
`
`
`
`CALL SERVER
`CALL SERVER
`
`
`
`
`136
`c$1
`
`
`
`: SIP-T
`144
`
`
`MESSAGING
`PSTN
`
`
`
`
`GATEWAY
`COUNTRY
`
`
`GWwW2
`PSTN
`
`
`
`CODE=1
`
`COUNTRY
`
`
`DC=613, 819
`
`CODE=69
`120
`NDC=88
`
`
`
`
`
`16135915298
`
`4419138008
`
`FIGURE 1
`
`PETITIONER APPLE INC. EX. 1009-2
`
`

`

`Patent Application Publication
`
`Sep. 5, 2002 Sheet 2 of 10
`
`US 2002/0122547 Al
`
`204
`
`210
`
`
`
`National (significant) number
`
`
`
`International public telecommunications number for networks
`
`Max(15 - n) digits
`
`Max 15 digits
`
`
`
`FIGURE 2
`
`PETITIONER APPLE INC.
`
`EX. 1009-3
`
`PETITIONER APPLE INC. EX. 1009-3
`
`

`

`Originating Agent Information Collection
`
`TRANSLATIONS SUBSYSTI
`
`Information Analysis
`
`Input
`(Dial Plan)
`Schemas ==
`
` uoneoyqng
`
`uoneoyddyjuajeg
`
`
`OLJO€94S7007‘Ss“das
`TVLes7cct0/700¢SN
`
`Route Database
`
`Route List
`Selection
`
`PETITIONER APPLE INC. EX. 1009-4
`
`

`

`
`
`
`
`SS
`——.
`[3[4|5|
`
`save
` 5{6|7[/8 9]
`|
`...
`..
`|
`wn
`| 7/8]
`9
`
`
`
`
`
`
`
`
`
`
`[0] 1)
`[ojaj2]
`o[1f2]_...
`|
`....Lee [7|8]9)
`2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`uoneoyqnguoneoyddyjuajeg
`
`CS1
`
`ID=1234
`
`
`
`
`
`
`
`
`
`1J2)3/4]..|[|we[7[8[9]|. aE [[7/8/19 a
`
`
`
`
`
`
`
`‘
`\
`=
`
`
`
`cs2
`we
`
`4/2)
`ID=6789
`=
`
`
`
`
`
`
`
`0/1/2
`
`
`| i
`
`in
`\
`=
`\
`g
`\.
`
`L
`cs2
`cst
`cst
`319
`
`
`
`
`
`
`
`ID=2345 ‘ID=5678|LaID=3456 2
`Ld
`
`
`
`ty
`
`oe
`\
`
`Me
`Vo,
`
`_S
`
`Ti
`NY
`
`=
`
`=54 >a
`
`FIGURE 4
`
`ID=4567
`
`PETITIONER APPLE INC. EX. 1009-5
`
`

`

`
`
`
`
`
`lo. | Pro|rE th
`o
`
`
`
`
`
`
`
`
`
` uoneoyqnguoneoyddyjuajeg
`
`
`
`
`
`
`
`
`
`
`
`
`= 5/6. 7|/8|9
`
`
`
`
`
`
`
`
`
`
`[71819
`wee
`
`
`
`
`
`
`
`
`O,1]2] |
`
`
`
`
`[o[1]2
`
`
`
`
`
`
`
`
`
`
`
`
`
`_ [7 [8[9)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`7/8/9)
`..... ae 7/8|9)
`1|2/3|4|_
`|
`ww.
`|)... }7|8|9)
`“
`nn
`\ >
`s
`Ve
`a
`LOLt12]"| Yo
`8
`No
`.
`‘
`e
`
`= 3 9
`.
`Cs
`
`
`
`
`
`ID=2345 ID=5678|LaID=3456
`
`S,
`Ld
`=
`
`
`
`cst
`ID=1234
`
`
`
`_ow17/819)
`
`
`
`csi
`fipzogys|
`
`
`
`Csi
`
`
`
`
`
`
`
`
`cs2
`ID=6789,
`
`
`
`
`
`
`CS2
`
`z=
`
`S54 >a
`
`Cs2
`
`FIGURE 5A
`
`PETITIONER APPLE INC. EX. 1009-6
`
`

`

`r5
`
`2
`
`
`
`
`
`
`
`
`
`0/1/2/3|4 5|/6/7|8/9
`-
`
`” }5/617/ 8/9 vee|7we [314/65]
`
`
`
`
`
`s©=
`
`ego
`
`=
`
`0 1/2]3]4]_ ..... = [7[slo]
`7/8
`|...
`[
`o..
`‘17
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`3ee g
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`jof1]2]....
`
`|
`
`of1f2]_....
`lojra)...
`fee 7
`
`
`
`
`
`
`
`
`
`CSs1
`
`Ip=1234;
`
`cst
`ID=2345
`
`
`
`
`
`
`
`
`
`Loss: 7/89
`
`csi
`
`o}1/2["]
`
`=
`
`cst
`ID=3456
`
`cs2
`ID=5678|
`
`
`
`La
`
`
`
`71819
`
`g w
`
`m
`i)
`=
`
`S zo
`
`—
`
`=S
`
`e
`
`F
`
`s5e
`
`S
`
`cs2
`ID=4567
`
`PETITIONER APPLE INC. EX. 1009-7
`
`

`

`
`
`
`
`uoneoyqnguoneoyddyjuajeg
`
`wn
`
`= w
`
`n
`=
`
`S N e
`
`~2 S
`
`S
`4Se
`8eS
`
`
`
`
`
`
`
`
`
`oO
`
`
`
` 3/4] 5 7(/8/9°
`
`
`
`
`ID=2345
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ee /7/8/9|ee
`
`
`
`
`
`
`
`
`fom
`- |
`
`
`
`7/8/19
`
`
`
`
`
`
`
`
`7|8/9
`
`
`
`
`
`
`
`cs1
`ID=1234
`
`
`tI
`
`CcS1
`
`
`
`
`
`
`17/819
`
`CS1
`
`
`ID=3456
`
`
`
`
`
`
`
`
`
`CS1
`ID=2345
`
`
`
`
`
`
`
`
`g]9) |. |7|8]9
`
`
`
`
`
`
`0
`
`=
`2|°"
`
`CS2
`
`
`
`Cs2
`ID=6789
`
`
`
`
`
`
`
`
`
`Cs2
`ID=4567
`
`
`
`PETITIONER APPLE INC. EX. 1009-8
`
`

`

`Patent Application Publication
`
`Sep. 5, 2002 Sheet 8 of 10
`
`US 2002/0122547 Al
`
`FIGURE6
`
`a! INGRESS CALL SERVER RECIVES CALL SETUP INFORMATION FROM
`ORIGINATING ENDPOINT
`_
`
`
`
`
`
`NO
`
`a DOES SIGNALED INFORMATION oN
`
`CONFORM TO INPUT SCHEMA > NO
`ASSOCIATED WITH THE ENDPOINT?~~
`“
`
`604
`
`608
`
`
`
`YES
`
`_
`<7HAS ENOUGH INFORMATION BEEN~~~
`COLLECTED FOR ANALYSIS?
`:
`~
`616
`
`ol
`612
`
`NO
`
`
`
`YES
`'
`
`SIGNALED INFORMATION IS ANALYZED TO
`DETERMINE THE CALL ATTRIBUTES (FULLY
`QUALIFIED ALIAS, SERVICE PROVIDER, CALL
`y7]
`TYPE,..)
`
`620 a
`_
`
`
`
`APPLY ROUTING POLICIES, QUERY THE ROUTE
`DATABASE WITH THE CALL ATTRIBUTES.
`QUERY RESPONSE CONTAINSA LIST OF CALL
`SERVER HOST AND ROUTEID PAIRS.
`
`7]
`624
`
`
`
`
`
`I
`
`
`
`SIGNAL
`ENDPOINT THAT
`THERE ARE NO /<#NO
`ROUTES
`AVAILABLE
`
`‘
`632
`
`J
`|
`|
`i
`
`ENDOINT
`i
`| THATTHE
`| CALL FAILED |
`SCREENING |
`
`
`
`SELECT NEXT ROUTE FROM LIST
`ROUTE SELECTED?
`
`YES
`
`
`
`
`
`
`PPLY SCREENING POLICIEST!
`CALL ATTRIBUTES. IS THE CALL
`2?
`REQUEST AUTHORIZED?
`
`[—<__
`NO
`
`636
`
`
`
`
`
`
`
`
`|
`
`|
`
`—
`
`VES
`
`
`
`SIGNAL ENDPOINT THAT INPUT DOES NOT
`CONFORM TO INPUT SCHEMA
`
`Y
`
`
`($ ROUTE HOSTED
`
`BY LOCAL CALL
`SERVER?
`
`
`
`644
`
`
`
`USE SIP-T FOR
`INTER CALL
`Now»! SIGNALies +0
`THE REMOTE
`HOST
`
`a
`648
`
`
`
`
`EGRESS CALL
`
`SERVER CHECKSIF
`ROUTE AVAILABLE?
`
`652
`
`
`Y
`
`APPLY SIGNALING POLICIES,
`7] FORMATSIGNALING INFO FOR
`656
`TERMINATING ROUTE
`
`t
`SEND CALL SETUP
`77 INFORMATION TO TERMINATING
`ENDPOINT
`660
`
`OO |
`Y
`
`ESTABLISH MEDIA PATH
`
`664
`
`
`
`
`
`640
`
`PETITIONER APPLE INC.
`
`EX. 1009-9
`
`PETITIONER APPLE INC. EX. 1009-9
`
`

`

`Patent Application Publication
`
`Sep. 5, 2002 Sheet 9 of 10
`
`US 2002/0122547 Al
`
`FIGURE 7
`
`700
`804
`
`FIGURE 8
`
`PETITIONER APPLE INC.
`
`EX. 1009-10
`
`PETITIONER APPLE INC. EX. 1009-10
`
`

`

`Patent Application Publication
`
`Sep. 5, 2002 Sheet 10 of 10
`
`US 2002/0122547 Al
`
`900
`
`(
`
`)
`
`(YY
`
`La
`
`904
`
`PROCESSOR
`
`
`
`<¢—————_—_>
`
`908
`
`912
`
`OPERATING
`MEMORY
`
`
`
`
`
`w”
`
`ac
`
`o
`
`
`
`
`
`<>
`
`“|
`
`916
`
`
`
`REMOVABLE
`
`920
`DEVICE
`DEVICE
`
`eT STORAGE||STORAGE 554
`
`
`
`
`
`
`
`
`
`
`
`||
`
`REMOVABLE
`STORAGE ah
`UNIT
`|
`(
`
`928
`
`
`
`
`
`KY
`
`
`FIGURE 9
`
`PETITIONER APPLE INC.
`
`EX. 1009-11
`
`PETITIONER APPLE INC. EX. 1009-11
`
`

`

`US 2002/0122547 Al
`
`Sep. 5, 2002
`
`METHOD AND APPARATUS FOR TELEPHONY
`ROUTE SELECTION
`
`TECHNICAL FIELD
`
`[0001] The invention relates to translating telephonycalls.
`Moreparticularly, this invention relates to route selection for
`telephony calls according to call attributes derived from a
`service request.
`
`BACKGROUND
`
`In a prior art circuit switched telecommunication
`[0002]
`switching system comprising a plurality of switching nodes,
`each switching node requires predefined knowledge of the
`numbering plan of the telecommunication switching system
`and also of how the switching nodes are interconnected. An
`example of such a system is the public telephone networkof
`the United States. Within the United States, the telephone
`numbers were grouped in terms of area codes; and within
`each area code, the telephone numbers were further grouped
`by the first
`three digits of the telephone number. This
`hierarchy of telephone numbers (also referred to as the
`numbering plan hierarchy) was modeledafter the hierarchy
`of switching nodes, e.g. central and tandem offices. Within
`each central office, the routes to be utilized to reach area
`codes or other groups of telephone numbers waspredefined
`at initialization or during system operation by the actions of
`a system administrator in configuring a translations data-
`base. “Translations” is a term used to refer to the process of
`interpreting call
`request
`information (dialed digits for
`example) received from an end user device or incoming
`trunk, determining the requested call type and associated
`called destination, and resolving this information to an
`internal reference which can be used by call processing to
`terminate calls to the appropriate service, end user device or
`outgoing trunk route.
`
`[0003] Translations databases in circuit-switched tele-
`phony networks typically had been manually configured
`through static associations from originating-endpoints to
`routes based on a service request comprising dialed digits.
`The static associations had generated complex data models
`having a directed graph from each possible originating
`endpoint. This model has beenin the form ofa tree structure
`indexed by dialed telephony digits associated with each
`feasible route.
`
`is manually adminis-
`[0004] This complex data model
`tered. With manual administration, a high cost is associated
`with maintaining and updating the data model. Furthermore,
`due to the human intervention required to reconfigure the
`translations and switching equipment when setting up or
`making any changes to network infrastructure, the update
`process becomes increasingly time consuming and error
`prone as the model size and complexity increases.
`
`[0005] Emerging packet-based telephony communications
`technology, such as Voice over Internet Protocol (“VoIP”)
`does not limit the service request input format to dialed
`digits as found on a telephony keypad. Furthermore, whilst
`the most significant digits of the dialed number had previ-
`ously been associated with a predetermined central office,
`this is no longer necessary since the network architecture is
`not hierarchical as with circuit-switched networks.
`
`coupled to the network. With the redundancy of hierarchic
`and geographic restrictions on the allocation of aliases,
`increased flexibility in allocating aliases allows a more
`distributed usage of aliases. However, the trade-off with this
`increasedflexibility is that the management and provision of
`the translations data to translations databases becomes
`increasingly complex and error-prone.
`
`It would be desirable to provide a method and
`[0007]
`apparatus for translating a call to a called alias by deriving
`call attributes from a service request independent of the
`access device and request input format; and use the call
`attributes derived from the service request to translate the
`call to a destination or service associated with the called
`alias.
`
`SUMMARY
`
`[0008] Provided is a method and apparatus for providing
`access device input format
`independent
`translations and
`route selection for telephony calls. A translations method
`and apparatus consistent with the present invention provides
`route selection of telephony calls unconstrained by access
`device input format.
`
`[0009] An important aspect of translations in the tele-
`phony domainis the interpretation ofan alias, the alias being
`associated with an endpoint on the communications net-
`work,and the selection of a route connecting a calling-party
`to a called-party’s endpoint. As used here, an “alias” may be
`a telephony number, web page URL (Universal Resource
`Locator), e-mail address, common name, or any other
`unique identifier associated with the called party. The “alias”
`can use any combination of alphanumeric characters.
`
`[0010] A call request is received, the call request com-
`prising input information being for a telephonycall. At least
`one call attribute is then determined from the input infor-
`mation and a routing policy request is transmitted to query
`a route database. Responsive to the routing policy request a
`routing policy responseis received, the response comprising
`at least one routing parameter. The at least one routing
`parameter is used to influence call set up.
`
`In some embodiments, a call server maintains a
`[0011]
`route database of the aliases associated with its supported
`endpoints and services. The call attributes determine the
`routing policy used to query the translations database of the
`ingress call server to select appropriate routes satisfying the
`call attributes. In some embodiments,
`the database may
`provide a preferred routing based on the call attributes and
`routing policy being applied.
`
`In some embodiments, if the query to the ingress
`[0012]
`call server’s translations database does not yield a routing
`result, then a second query may be performed to a route
`database to determine the appropriate call server that sup-
`ports the called endpoint, service or trunk endpoint that can
`route towards the called destination. In a network with a
`
`plurality of call servers, each call server has responsibility to
`host pre-defined endpoints (terminals and/or trunks) and
`services. Such call server to endpoint and service associa-
`tions maybestatically or dynamically provisioned. Signal-
`ing between call servers may transfer the call handling from
`an ingress call server to an egress call server.
`
`[0006] As the demand for telephony services grows, so
`does the requirement
`to allocate aliases for endpoints
`
`In some embodiments, a network management
`[0013]
`system (NMS) may be responsible for configuring each call
`
`PETITIONER APPLE INC.
`
`EX. 1009-12
`
`PETITIONER APPLE INC. EX. 1009-12
`
`

`

`US 2002/0122547 Al
`
`Sep. 5, 2002
`
`server in the network with data for each endpoint and service
`hosted by the call server, including associated translations
`data. In some embodiments, a network translations route
`database is provided to supportinter call server translations.
`If a translations request cannot be resolved within the local
`translations database of the ingress call server, a query is
`made to the network translations route database. The net-
`work translations route database is responsible for returning
`a reference to the call server hosting the called endpoint,
`service or trunk endpoint that can route towards the called
`destination.
`
`[0014] An advantage of the invention is that route selec-
`tion is made using call attributes rather than dialed digits,
`thus route selection is unconstrained by the request format of
`the access device. In communications networks, and more
`particularly data networks, terminals are not restricted to a
`twelve button keypad used to dial digits, but other more
`elaborate forms of input may be used to express a service
`request and called party alias/address information,
`for
`example, an alphanumeric address, an email address or a
`URL.
`
`it
`[0015] A further advantage of this invention is that
`provides the ability to analyze any form of user input
`representing the service request and interpret it in terms of
`generic call attributes to select an appropriate route. The call
`attributes and translations route selection policies can there-
`fore be reused in a manner independent of the input alias.
`
`[0016] Further features of the invention, as well as the
`structure and operation of various embodiments of the
`invention, are described in detail below with reference to the
`accompanying drawings. The drawing in which an element
`first appears is indicated by the digit(s) to the left of the two
`rightmost digits in the corresponding reference number.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0017] The invention will best be understood by reference
`to the following detailed description when read in conjunc-
`tion with the accompanied drawings, wherein:
`
`[0018] FIG. 1 is a block diagram of an exemplary IP
`network topology;
`
`[0019] FIG. 2 is a diagram of international public tele-
`communications number structure for geographic areas
`under the ITU-T E. 164 Recommendation;
`
`[0020] FIG. 3 is a diagram of a network translations
`subsystem to resolve called alias information to one or more
`terminating endpoints associated with the alias;
`
`[0021]
`
`FIG.4 is a diagram of a number route database;
`
`[0022] FIGS. 5A, 5B and 5C is a flow chart for mapping
`called numbers according to a numbering plan and number
`range;
`
`[0023] FIG. 6 is a flowchart for a call server handling a
`call;
`
`[0024]
`
`FIG.7 is a front view of a board carrier;
`
`[0025] FIG. 8 is a rear view of a board carrier;
`
`DETAILED DESCRIPTION
`
`In the following description, numerous details are
`[0027]
`set forth to provide an understanding of the present inven-
`tion. However, it will be understood by those skilled in the
`art that the present invention may be practiced without these
`details and that numerous variations or modifications from
`the described embodiments may be possible. For example,
`although the description refers to telephony communications
`over data networks, certain aspects of the methods and
`apparatus described may be advantageously used with other
`types of communications systems, such as those used on
`circuit switched networks.
`
`[0028] FIG. 1 is a block diagram of an Internet Protocol
`(“IP”) network topology. The communications network 102
`is coupled to associated endpoints 116, 120, 124, 128, 148
`and 152. As shown,
`the endpoints can be provided as
`communications gateways 116, 120, 124 and 128, and with
`terminals 148 and 152.
`
`It should be appreciated that many more endpoints
`[0029]
`may be connected to communications network 102; and
`these are shown merely as examples.
`
`[0030] Communications network 102 in this example may
`be a packet-based or message-based network.
`In one
`embodiment, the communications network 102 communi-
`cates according to the Internet Protocol (IP), whichis one of
`the protocols on which the Internet is based, as described in
`Internet Engineering Task Force (IETF) Request for Com-
`ment 791, entitled “Internet Protocol,” dated September
`1981. Communications network 102 provides quality of
`service to voice calls sufficient to provide adequate band-
`width and low latency.
`
`[0031] A suitable communications network 102 has a
`single network or link, which can be coupled through
`gateways, routers, and the like. It should be appreciated by
`those skilled in the art that further complex architectures
`could be implemented with multiple networks or links.
`Further, it should be noted that communications network
`102 could have geographically dispersed linked-data net-
`works in business environments. Examples of such data
`networks are Local Area Networks (LANs).
`
`[0032] As shown in FIG. 1, communications networks
`132, 136, 140 and 144 are coupled to communications
`network 102 via communications gateways 116, 120, 124
`and 128 respectively, to provide the communications inter-
`face between the networks.
`
`[0033] Examples of suitable communications networks
`132, 136, 140 and 144 are a public switch telephone network
`(“PSTN”), a private branch exchange (“PBX”), a local area
`network (“LAN”), a metropolitan area network (“MAN”), a
`wide-area network (“WAN”), a private network such as an
`Intranet, and public network such as the Internet. The
`underlying unifying factor of these networksis the ability to
`share data information under a common communications
`protocol, such as TCP/IP. Additional communications pro-
`tocols can be implemented and data may be communicated
`between communications protocols using adequate conver-
`sion techniques.
`
`[0026] FIG. 9 is a computer system programmed for
`executing a computer program according to various embodi-
`ments of the invention.
`
`[0034] Terminals 148 and 152 are capable of performing
`voice and other multi-media communicationsovera packet-
`based or message-based data network. As used herein, a
`
`PETITIONER APPLE INC.
`
`EX. 1009-13
`
`PETITIONER APPLE INC. EX. 1009-13
`
`

`

`US 2002/0122547 Al
`
`Sep. 5, 2002
`
`terminal may be a computer-based system having speech
`capability, or may be telephony units having interfaces to the
`communications network. Accordingly, terminals 148 and
`152 may be Internet Protocol (IP) telephones, each with an
`associated IP address; the IP address of each terminal having
`an associated phone number according to the E.164 stan-
`dard. The aforesaid IP address may be dynamically or
`statically allocated. Dynamicallocation of the IP address can
`be performed using Dynamic Host Configuration Protocol;
`an existing IETF protocol that allows a server to assign IP
`addresses dynamically to endpoints as they connect to the
`network.
`
`[0035] As shown in FIG. 1, call servers 104 and 108 are
`coupled to the communications network 102. The call serv-
`ers act to manage telephony communications (for example,
`call setup, processing, and termination) between or among
`the endpoints. A suitable call server is available under the
`Succession™ Internet Product Portfolio from Nortel Net-
`works, Ltd., of Brampton, Ontario, Canada. A call server
`builds a composite view of the translations data for all its
`endpoints in a local translations database. A function that the
`call servers provide is in the called alias translation to allow
`the call to progress throughout the networkto its destination
`endpoint(s). As used here, an “alias” may be a telephony
`number, web page URL (Universal Resource Locator),
`e-mail address, common name, or any other unique identifier
`associated with the called party. The “alias” can use any
`combination of alphanumeric characters.
`
`[0036] Aroute database 114, accessible by the call servers
`104 and 108 through the communications network 102,
`provides support to inter-call server translations. Thus, if a
`called address translation request cannot be resolved within
`the ingress call server local translations database, a query
`may be made to route database 114. The network transla-
`tions database in the route database 114 returns a reference
`to the call server hosting the terminating endpoint. The
`ingress call server may then use Session Initiation Protocol
`for Telephony (SIP-T,) messaging or an equivalent to for-
`ward the call signaling to the terminating call server. SIP-T
`is an emerging ITU messaging protocol standard for com-
`municating betweencall servers. The terminating call server
`may then use its local translations database to locate the
`terminating endpoint and complete the call.
`
`[0037] Additionally, management server 112 may be
`coupled to the communications network 102 for the man-
`agement of selected resources coupled to communications
`network 102. Management server 112 may send the con-
`figuration data for each call server’s hosted endpoints to the
`respective call server. From this configuration data,
`the
`respective call server may build run-time configuration data
`and a local translations database for the hosted endpoints.
`Endpoint configuration data may be provisioned through a
`management server and stored in a route database.
`
`[0038] Although only one route database 114, manage-
`ment server 112 is illustrated, it should be appreciated that
`multiple route databases, managementservers and call serv-
`ers can be coupled to the communications network, as well
`as additional network resources, sufficient to handle the call
`traffic. In a multiple server configuration, the multiple call
`servers may be responsible for managingcall requests from
`a group of terminals, and the route database may be respon-
`sible for serving a predetermined set of call servers. A call
`
`server, route database, and management server may be
`implemented on separate platforms or in a platform includ-
`ing someorall of the aforementioned components.
`
`[0039] FIG. 2 is a diagram of international public tele-
`communications number structure for geographic areas
`under the ITU-T E. 164 Recommendation,titled “The inter-
`national public telecommunication numbering plan”, dated
`May 1997, which is hereby incorporated by reference. This
`recommendation details the components of the numbering
`structure and the digit analysis required to successfully route
`calls in international public telecommunication networks.
`
`[0040] The international public telecommunication num-
`ber for geographic areas is composed of a variable number
`of decimal digits arranged in specific code fields. The
`international public telecommunication numbercode fields
`are the Country Code (CC) 204 and the National (Signifi-
`cant) Number, 210. The National (Significant) Number 210
`may be (15-n) characters in length, where n is the number of
`digits in the country code (1 to 3 digits).
`
`[0041] As used in the E.164 description, a public number
`is a string of decimaldigits that uniquely indicates the public
`network termination point. The number contains the infor-
`mation necessary to route the call over a public network to
`this termination point; and this number is herein forth
`referred to as a “fully qualified” number. A public number
`can be in a format determined nationally or in an interna-
`tional format. The international format is known as the
`
`International Public Telecommunication Number, which
`includes the country code and subsequent digits, but not the
`international prefix.
`
`[0042] As used also in the E.164 description, a numbering
`plan specifies the format and structure of the numbers used
`within that plan. It typically comprises decimal digits seg-
`mented into groups in order to identify specific elements
`used for identification (or aliasing), translations and charg-
`ing capabilities, e.g. within E.164 to identify countries,
`national destinations and subscribers. A numbering plan
`does not include prefixes, suffixes, and additional informa-
`tion required to complete a call (these are components of dial
`plans). A national numbering plan is a national implemen-
`tation of the E.164 numbering plan.
`
`[0043] Such an example of a national numbering plan is
`the North American Numbering Plan (NANP). According to
`the NANP,
`the termination point has a number in the
`NXX-NXX-XXXX format, where N represents a digit from
`2-9 and X represents a digit from 0-9. The first group of
`three digits indicates the area code or Number Plan Area
`(NPA)of the subscriber, the second group ofthree digits and
`the last four digits comprise the Station Numberand indicate
`the address of the subscriber within the NPA. Digits 0 and
`1 are of course not available as the first digit (N) allowing
`them to be used as dial plan prefixes for operator and long
`distance services.
`
`In an enterprise telecommunications system,a pri-
`[0044]
`vate numbering plan is used. A private numberis a string of
`decimal digits that uniquely indicates the private network
`termination point. Similar to a public number, the number
`contains the information necessary to route the call over a
`enterprise networkto this termination point; and this number
`is herein forth referred to as a “fully qualified” number. A
`private numbering plan is in a format determined by the
`
`PETITIONER APPLE INC.
`
`EX. 1009-14
`
`PETITIONER APPLE INC. EX. 1009-14
`
`

`

`US 2002/0122547 Al
`
`Sep. 5, 2002
`
`enterprise. Like a public numbering plan, a private number-
`ing plan does not includeprefixes, suffixes, and additional
`information required to complete a call (these are compo-
`nents of private dial plans).
`
`[0045] Dial plans define the method by which number
`plans are used in terms of combinations of decimal digits
`dialed to place a call. Dial plans define the meaningofprefix
`and suffix digits, abbreviated called number formats and any
`other
`information,
`supplemental
`to the number plan,
`required to complete a call.
`
`the national or
`[0046] Public dial plans are defined at
`regional level. Such an example of a dial plan is the one
`typically used in most areas of North America whichdefines
`1 as prefix for long distance calls, 0 as a prefix for operator
`calls and allows for local calls to be dialed with a 7 digit
`abbreviated format of the 10 digit national number.
`
`In an enterprise telecommunications system, pri-
`[0047]
`vate dial plans define the combinationsof digits that may be
`used to provide the subscriber with different enterprise
`telecommunications services. These dial plans may service
`predetermined combinations of dialed digits and translate
`them to the various different telecommunications services.
`For example, a user may dial the digit ‘9’ as a prefix to a
`direct-outward-dialed (DOD) number to make a call from
`the enterprise network to a subscriberin the Public Switched
`Telephone Network (PSTN); and a user maydialthe digit ‘6’
`
`Case Call Type
`NumberDescription
`1
`Intra-site call
`2
`Inter-site call
`
`3
`
`29
`
`is a private communications system
`“enterprise network”
`linking up enterprise communications equipment and end-
`points. Examplesofprivate and public telecommunications
`call types are listed in Table 1 below. Examples of dialing
`plan digit patterns for each of the enterprise call types are
`listed in Table 2 below, whilst examplesof dialing plan digit
`patterns for DOD public call types are listed in Table 3
`below. It should be apparent to a person of ordinary skill in
`the art that further examples may be added to these.
`
`[0048] Call types are represented in Table 1 below.
`
`TABLE1
`
`Call Type Reference
`AA
`DA
`DD
`DOD
`ES
`INTER_SITE
`INTRA_SITE
`OA
`VSC
`
`Call Type
`Attendant Assisted
`Directory Assistance
`Direct Dial
`Direct Outward Dial
`Emergency Service
`Inter-Site
`Intra-Site
`Operator Assisted
`Vertical Service Code
`
`[0049] Enterprise (Private) Dialing Plans are represented
`in TABLE 2 below.
`
`TABLE 2
`
`Dialing Plan Schema
`
`Private Call
`Type
`
`Example of
`Plan
`
`EXTN (extension)
`INTERSITE__PREFTX +
`LOCATION_CODE + EXTN
`ATTENDANT_CODE
`
`INTRA_SITE 54000
`INTER_SITE 6 + 395+
`54000
`0
`
`AA
`
`Enterprise
`Attendant Call
`
`Enterprise
`4
`Emergency
`Call
`Direct-
`outward-dialed
`public call
`Vertical
`Service Code
`call
`
`EMERGENCY_SERVICECODE—ES 911
`
`5
`
`6
`
`DOD_PREFIX +
`PUBLIC_DIALING_PATTERN
`
`DOD
`
`VERTICAL_SERVICE__CODE
`
`VSC
`
`9 + 765-4000
`94+1+ 6134+
`765 + 4000
`*72, *1172
`*831, *11831
`
`to prefix a private enterprise number to make a call to
`another party on the enterprise network. As used here, an
`
`[0050] Direct Outward Dialed access to a Public Dialing
`Plan is represented in TABLE 3 below.
`
`TABLE 3
`
`Public
`Call Type Example (North
`Case Call Type
`Attribute America)
`Dialing Plan Schema
`Number Description
`
`7~~Direct- outward-dialed DOD_PREFIX + SN DD 9 + 745-1576
`
`local call
` Direct-outward-dialed DOD_PREFIX +
`nationalcall
`NATL_LD_PREFIX + NDC + SN
` Direct-outward-dialed DOD_PREFIX +
`international call
`INTL_LD_PREFIX + CC +
`NDC + SN
` Direct-outward-dialed DOD_PREFIX +
`operator assisted
`LOCAL_OA_PREFLX +
`national call
`NDC + SN
`
`DD
`
`DD
`
`OA
`
`9+1+ 613 + 745-
`1576
`9+ 011 + 44 + 207
`+ 225-0603
`
`94+0+4 613 + 745-
`1576
`
`8
`
`9
`
`10
`
`PETITIONER APPLE INC.
`
`EX. 1009-15
`
`PETITIONER APPLE INC. EX. 1009-15
`
`

`

`US 2002/0122547 Al
`
`Sep. 5, 2002
`
`TABLE 3-continued
`
`Public
`Call Type Example (North
`Case Call Type
`Attribute
`America)
`Dialing Plan Schema
`Number Description
`
`11~——Direct-outward-dialed DOD_PREFIX + OA 9+01+ 444207 +
`
`225-0603
`operator assisted
`INTL_OA_PREFTX + CC + NDC +
`internationalcall
`SN
`9+0
`
`12~~‘Direct-outward-dialed _DOD_PREFIX + OA
`
`attendant call
`LOCAL_OA_CODE
`Direct-outward-dialed DOD_PREFIX +
`emergency call
`EMERGENCY_SERVICE_CODE
`Direct-outward-dialed DOD_PREFIX +
`directory assistance
`DIRECTORY_ASSISTANCE_
`call
`CODE
`Direct-outward-dialed DOD_PREFIX +
`national service call
`NATIONAL_SERVICE_CODE
`
`9+911
`
`9+ 411
`
`9+1+4+
`800/888/877/86 6/90
`
`13.
`
`14
`
`15
`
`
`
`ES
`
`DA
`
`DD
`
`[0051] Call attributes may be derived by analysis of the
`dialed digits according to the dial plan in effect. One or more
`call attributes may be set as a result of the analysis. Table 4
`below lists the call attributes and their possible values.
`[0052] Call Attributes are represented in TABLE4 below.
`
`Call Attribute
`
`Value
`
`TABLE 4
`
`PRIVATE CALL TYPE
`PUBLIC CALL TYPE
`EQUAL ACCESS TYPE
`ORIGINATING
`ENVIRONMENT
`PUBLIC CALL REACH
`LOCAL CALL
`INDICATOR
`PUBLIC LATA TYPE
`
`PUBLIC CARRIER ID
`NATIONAL SERVICE
`TYPE CODE
`FULLY QUALIFIED
`ALIAS
`
`NONE, DOD, AA, ES, INTRA_SITE,
`INTER_SITE, VSC
`NONE, DD, OA, DA, ES, VSC
`NONE, PREF, CAC
`PRIVATE, PUBLIC
`
`UNKNOWN,NATL, INTL
`BOOL
`
`NOTAPPLICABLE, INTRA_LATA
`INTER_LATA
`VALUE (range: 0 to 9999)
`NONE, FREEPHONE, PAYPERCALL
`
`STRING
`Example for telephony numbers:
`Numbering Plan ID: E.164 or private ID
`Number: fully qualified E.164 or private
`number
`
`[0053] A high-level block diagram of the network trans-
`lations subsystem to resolve called alias information to one
`or more terminating endpoints associated with the alias is
`provided in FIG. 3. Arrows between the blocksindicate the
`general flow of execution. The functions provided by the
`translations subsystem 300 are organized into subcompo-
`nents. A subcomponent function may be implemented using
`software executing on a computer platform or using