PTO/AIA/14 (03-13)
`Approvedfor use through 01/31/2014. OMB 0651-0032
`.
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respondto a collection of information unlessit contains a valid OMB control number.
`
`
`
`
`Attorney Docket Number|SMARB19.001C1
`
`Application Data Sheet 37 CFR 1.76
`
`
`Title of Invention|;PRODUCING ROUTING MESSAGES FOR VOICE OVERIP
`COMMUNICATIONS
`
`
`
`The application data sheet is part of the provisional or nonprovisional application for whichit is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`
`
`document maybe printed and included in a paperfiled application.
`
`
`
`
`
`
`Secrecy Order 37 CFR 5.2
`37 CFR 5.2 (Paperfilers only. Applications that fall under Secrecy Order may notbefiled electronically.)
`O Portionsorall of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`
`Inventor Information:
`
`
`Inventor
`1
`Legal Name
`
`
`Given Name
`
`Middle Name
`
`Family Name
`
`
`
`Residence Information (Select One)
`City
`|PANAMACITY
`
`(@) NonUS Residency
`(©) US Residency
`Country of Residence!
`
`() Active US Military Service
`
`Mailing Address of Inventor:
`
`Address 1
`
`Address 2
`
`340a COROZAL WEST
`
`PANAMACITY
`
`State/Province
`
`
`
`
` Inventor
`2
`Legal Name
`
`Prefix; Given Name
`STEVE
`
`
`
`Middle Name —
`
`Family Name
`NICHOLSON
`
`Suffix’
`
`
`Residence Information (Select One) () US Residency
`(@) NonUS Residency
`() Active US Military Service
`City
`HAMILTON
`Country of Residence i
`NZ
`
`
`
`
`
`
`Mailing Addressof Inventor:
`
`
`Address1
`423 TAUWHARE ROAD, RD 3
`
`
`Address 2
`
`
` HAMILTON
`City
`.
`State/Province
`
`Postal Code
`3283
`.
`Country i
`NZ
`
` Inventor
`
`3
`
`
`Legal Name
`
`
`:
`
`EFS Web2.2.7
`
`AT&T, Exh. 1002, p. 1
`
`AT&T, Exh. 1002, p. 1
`
`

`

`PTO/AIA/14 (03-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respondto a collection of information unlessitcontains a valid OMB control number.
`
`sigs Attorney Docket Number|SMARB19.001C1
`
`Application Data Sheet 37 CFR 1.76
`—
`
`
`
`
`
`
`
`
`Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`
`
`
`
`
`
`
`@) Non US Residency ©) Active US Military Service
`Residence Information (Select One) © US Residency
`NORTH VANCOUVER
`Country of Residence !
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`P| JOHAN ||EMIL VIKTOR BJORSELL
`
`
`
`
`
`Residence Information (Select One) © US Residency
`@) NonUSResidency
`(©) Active US Military Service
`
`
`
`
`
`
`
`
`City|VANCOUVER Country of Residence !
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Inventor 5
`
`
`
`Legal Name
`
`
`
`
`
`
`(©) Active US Military Service
`(@) NonUS Residency
`Residence Information (Select One) © US Residency
`
`
`
`
`
`City|VANCOUVER ° Country of Residence !
`
`
`
`
`
`
`
`
`
`
`
`Mailing Address of Inventor:
`
`—
`
`Address1
`
`3320 GARABALDI DRIVE
`
`4
`Inventor
`Legal Name
`
`
`
`Mailing Addressof Inventor:
`
`Address1
`2681 EAST HASTINGS STREET
`.
`,
`Address 2 |
`
`
`
`
`
`Ea
`ee
`
`Mailing Address of Inventor:
`Address1
`782 WEST 22ND STREET
`
`|
`
`EFS Web2.2.7
`
`AT&T, Exh. 1002, p. 2
`
`AT&T, Exh. 1002, p. 2
`
`

`

`PTO/AIA/14 (03-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unlessit contains a valid OMB control number.
`
`
`Application Data Sheet 37 CFR 1.76
`
`——
`
`
`
`
`Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`
`
`
`
`
`
`
`Inventor Information blocks may be
`Inventors Must Be Listed - Additional
`All
`generated within this form by selecting the Add button.
`
`
`
`
`CorrespondenceInformation:
`Enter either Customer Numberor complete the CorrespondenceInformation section below.
`For further information see 37 CFR 1.33(a).
`
`[_] An Addressis being provided for the correspondenceInformation of this application.
`
`
`
`
`Customer Number
`
`20995
`
`Email Address
`
`efiling@knobbe.com
`
`
`PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`
`
`Application Information:
`
`
`Title of the Invention
`
`
`
`
`
`
`
`
`SMARB19.001C1
`Nonprovisional
`Application Type
`
`Subject Matter
`Utility
`
`| Small Entity Status Claimed
`
`
`
`
`
`Total Number of Drawing Sheets (if any)
`
`32
`
`Suggested Figure for Publication (if any)
`
`Publication Information:
`
`| [] Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`Request Not to Publish. | hereby request that the attached application not be published under
`35 U.S.C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the
`subject of an application filed in another country, or under a multilateral international agreement, that requires
`publication at eighteen monthsafterfiling.
`
`Oo
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a powerof attorney in the application (see 37 CFR 1.32).
`Either enter Customer Number or complete the Representative Name section below.If both sections are completed the customer
`
`Numberwill be used for the Representative Information during processing. ,
`
`
`Please Select One:
`@) Customer Number
`| ©) US PatentPractitioner
`©) Limited Recognition (37 CFR 11.9)
`
`
`20995
`Customer Number
`
`Domestic Benefit/National Stage Information:
`
`This section allowsfor the applicantto either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate ~
`National Stage entry from a PCT application. Providing this information in the application data sheet constitutes the
`
`specific reference required by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78.
`
`Prior Application Status|Pending
`EFS Web2.2.7
`
`AT&T, Exh. 1002, p. 3
`
`AT&T, Exh. 1002, p. 3
`
`

`

`PTO/AIA/14 (03-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`
`Underthe Paperwork Reduction Act of 1995, no personsare required to respond to a collection of information unlessit contains a valid OMB control number.
`
`Attorney Docket Number
`Application Data Sheet 37 CFR 1.76
`
`Application Number |
`
`SMARB19.001C1
`
`
`
`
`Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`
`
`
`
`
`Application Number Prior Application Number|—Filing DateYWYYY-MM-DD)Continuity Type
`
`
`
` 12/513147Continuation of 2010-03-01
`
`
`Prior Application Status|Expired
`
`Application Number Prior Application Number|—Filing Date (YYYY-MM-DD)Continuity Type
`
`
`
`
`a 371 of international PCT/CA2007/001 95612/513147 2007-11-01
`
`
`Prior Application Status|Expired
`
`
`
`Application Number Prior Application Number|—Filing Date YYYY-MM-DD)Continuity Type
`
`
`
`PCT/CA2007/001956
`non provisional of
`60/856212
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`2006-1 1-02
`
`Foreign Priority Information:
`
`This section allows for the applicantto claim priority to a foreign application. Providing this information in the application data sheet
`constitutes the claim for priority as required by 35 U.S.C. 119(b) and 37 CFR 1.55(d). Whenpriority is claimed to a foreign application
`that is eligible for retrieval under the priority document exchange program (PDX)! the information will be used by the Office to
`automatically attempt retrieval pursuant to 37 CFR 1.55(h)(1) and (2). Under the PDX program, applicant bears the ultimate
`responsibility for ensuring that a copy of the foreign application is received by the Office from the participating foreign intellectual
`property office, or a certified copy of the foreign priority application is filed, within the time period specified in 37 CFR 1.55(g)(1).
`
`|
`Application Number
`|
`Country!
`Filing Date (YYYY-MM-DD)
`Access Code(if applicable)
`
`|
`|
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`
`
`Statement under 37 CFR 1.55 or 1.78 for AIA (First Inventor to File) Transition
`Applications
`
`
`
`This application (1) claims priority to or the benefit of an application filed before March 16, 2013 and (2) also
`contains, or contained at any time, a claim to a claimed invention that has an effectivefiling date on or after March
`[] 16, 2013.
`NOTE: By providing this statement under 37 CFR 1.55 or 1.78, this application, with a filing date on or after March
`16, 2013, will be examined underthe first inventor to file provisions of the AIA.
`
`
`
`EFS Web 2.2.7
`
`AT&T, Exh. 1002, p. 4
`
`AT&T, Exh. 1002, p. 4
`
`

`

`PTO/AIA/14 (03-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respondto a collection of information unless it contains a valid OMB control number.
`
`Attorney Docket Number|SMARB19.001C1
`
`Application Number Application Data Sheet 37 CFR 1.76
`
`
`
`Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`+
`
`Authorization to Permit Access:
`
`
`
`Authorization to Permit Accessto the Instant Application by the Participating Offices
`
`If checked, the undersigned hereby grants the USPTO authority to provide the European Patent Office (EPO),
`the Japan Patent Office (JPO), the Korean Intellectual Property Office (KIPO), the World Intellectual Property Office (WIPO),
`and any other intellectual property offices in which a foreign application claiming priority to the instant patent application
`is filed access to the instant patent application. See 37 CFR 1.14(c) and (h). This box should not be checkedif the applicant
`does not wish the EPO, JPO, KIPO, WIPO,or other intellectual property office in which a foreign application claiming priority
`to the instant patent application is filed to have accessto the instant patent application.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` In accordance with 37 CFR 1.14(h)(3), access will be provided to a copy of the instant patent application with respect
`to: 1) the instant patent application-as-filed; 2) any foreign application to which the instant patent application
`
`claims priority under 35 U.S.C. 119(a)-(d) if a copy of the foreign application that satisfies the certified copy requirement of
`37 CFR 1.55 has beenfiled in the instant patent application; and 3) any U.S. application-as-filed from which benefit is
`soughtin the instant patent application.
`:
`
`
`In accordance with 37 CFR 1.14(c), access may be provided to information concerning the dateof filing this Authorization.
`
`
`
`Applicant Information:
`
`
`Providing assignmentinformation in this section does not substitute for compliance with any requirementof part 3 of Title 37 of CFR
`
`to have an assignment recorded by the Office.
`
`
`Applicant
`1
`If the applicant is the inventor (or the remaining joint inventor or inventors under 37 CFR 1.45), this section should not be completed.
`The information to be providedin this section is the name and addressofthe legal representative who is the applicant under 37 CFR
`1.43; or the name and addressof the assignee, person to whom the inventor is under an obligation to assign the invention, or person
`whoothenvise showssufficient proprietary interest in the matter whois the applicant under 37 CFR 1.46.If the applicant is an
`applicant under 37 CFR 1.46 (assignee, person to whom the inventoris obligated to assign, or person who otherwise showssufficient
`proprietary interest) together with one or morejoint inventors, then the joint inventor or inventors who are also the applicant should be
`identified in this section.
`
`
`@) Assignee
`(©) Legal Representative under 35 U.S.C. 117
`©)
`Joint Inventor
`OQ Person to whom theinventoris obligated to assign.
`lO Person who showssufficient proprietary interest
`
`
`
`If applicant is the legal representative, indicate the authority to file the patent application, the inventoris:
`
`
`[
`
`Nameof the Deceased or Legally incapacitated Inventor:
`
`|
`
`
`
`lf the Applicant is an Organization check here.
`XX
`Organization Name|piGiFoNICA (INTERNATIONAL) LIMITED
`
`EFS Web2.2.7
`
`AT&T, Exh. 1002; p. 5
`
`AT&T, Exh. 1002, p. 5
`
`

`

`PTO/AIA/14 (03-13)
`Approvedfor use through 04/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`
`Under the Paperwork Reduction Act of 1995, no persons are required to respondto a collection of information unlessit contains a valid OMB contro! number.
`
`
`Attorney Docket Number|SMARB19.001C1
`Application Data Sheet 37 CFR 1.76
`—
`
`Mailing AddressInformation For Applicant:
`Address 1
`773 HORNBY STREET
`
`
`Address 2
`
`
`BC
`State/Province
`VANCOUVER
`
`Postal Code
`
`V6Z 184
`
`Fax Number
`
`
`| Email Address
`
`
`Additional Applicant Data may be generated within this form by selecting the Add button.
`
`Non-Applicant Assignee Information:
`
`
`
`
`Providing assignmentinformation in this section does not subsitute for compliance with any requirementof part 3 ofTitle 37 of CFR to
`have an assignment recorded by the Office.
`
`
`Assignee
`1
`
`Complete this section onlyif non-applicant assignee information is desired to be included on the patent application publication in
`
`accordance with 37 CFR 1.215(b). Do not include in this section an applicant under 37 CFR 1.46 (assignee, person to whom the
`
`inventor is obligated to assign, or person who otherwise showssufficient proprietary interest), as the patent application publication will
`
`include the nameof the applicant(s).
`
`
`
`
`If the Assignee is an Organization check here.
`
`
`
`
`Middle Name
`Family Name
`| Suffix
`
`UO
`
`Application Number Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
` Phone Number
`Given Name
`| Email Address
`
`Mailing Address Information For Non-Applicant Assignee:
`
`Address 1
`
`
`Address2
`
`
`
`
`City
`State/Province
`
`
`Country i
`| Postal Code
`|
`
`Phone Number
`| Fax Number
`
`
`:
`
`
`
`Additional Assignee Data may be generated within this form by selecting the Add button.
`
`
`
`EFS Web 2.2.7
`
`AT&T, Exh. 1002, p. 6
`
`AT&T, Exh. 1002, p. 6
`
`

`

`PTO/AIA/14 (03-13)
`Approvedfor use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respondto a collection of information unless it contains a valid OMB control number.
`
`
`SMARB19.001C1
`
`Title of Invention|PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`Signature:
`NOTE: This form must be sjg
`certifications.
`
`0
`
`
`
` Attorney Docket Number
`Application Data Sheet 37 CFR 1.76 Application Number
`
`
`
`
`rdance with 37 CFR 1.33. See 37 CFR 1.4 for signature requirements and
`
`
`
`Date (YYYY-MM-DD)| 20 13-e8-(}
`Signature
`
`
`
`
`First Name
`Last Name
`CARSON Registration Number|34303
`
`
`
`
`
`
`Additional Signature may be generated within this form by selecting the Add button.
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTOto process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amountof time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.7
`
`AT&T, Exh. 1002, p. 7
`
`AT&T, Exh. 1002, p. 7
`
`

`

`SMARB19.001C1
`
`PATENT
`
`PRODUCING ROUTING MESSAGES FOR VOICE OVER IP COMMUNICATIONS
`
`BACKGROUNDOF THE INVENTION
`
`Cross Reference to Related Applications
`
`[0001]
`
`This application is a continuation of U.S. Application No. 12/513,147,
`
`filed March 1, 2010, which is a national phase entry of PCT/CA2007/001956,
`
`filed
`
`November 1, 2007, which claims priority to U.S. Provisional Application No. 60/856,212,
`
`filed November 2, 2006, all of which are incorporatedin their entirety.
`
`Field of Invention
`
`[0002]
`
`This invention relates to voice over IP communications and methods and
`
`apparatus for routing andbilling.
`
`Description of Related Art
`
`[0003]
`
`Internet protocol (IP) telephones are typically personal computer (PC)
`
`based telephones connected within an IP network, such as the public Internet or a private
`
`network of a large organization. These IP telephones haveinstalled “voice-over-IP” (VoIP)
`
`software enabling them to make and receive voice calls and send and receive information in
`
`data and video formats.
`
`[0004]
`
`IP telephony switchesinstalled within the IP network enable voice calls to
`
`be made within or between IP networks, and between an IP network and a switched circuit
`
`network (SCN), such as the public switched telephone network (PSTN). If the IP switch
`
`supports the Signaling System 7 (SS7) protocol, the IP telephone can also access PSTN
`
`databases.
`
`[0005]
`
`The PSTN network typically includes complex network nodes that contain
`
`all information about a local calling service area including user authentication and call
`
`routing. The PSTN network typically aggregates all information and traffic into a single
`
`location or node, processes it locally and then passes it on to other network nodes, as
`
`necessary, by maintaining route tables at the node. PSTN nodes are redundant by design and
`
`thus provide reliable service, but if a node should fail due to an earthquake or other natural
`
`AT&T, Exh. 1002, p. 8
`
`AT&T, Exh. 1002, p. 8
`
`

`

`disaster, significant, if not complete service outages can occur, with no other nodes being
`
`able to take up the load.
`
`[0006]
`
`Existing VoIP systems do notallow for high availability and resiliency in
`
`delivering Voice Over IP based Session Initiation Protocol (SIP) Protocol service over a
`
`geographically dispersed area such as a city, region or continent. Most resiliency originates
`
`from the provision of IP based telephone services to one location or a small number of
`
`locations such as a single office or network of branchoffices.
`
`SUMMARYOF THE INVENTION
`
`[0007]
`
`In accordance with one aspect of the invention, there is provided a process
`
`for operating a call routing controller to facilitate communication between callers and callees
`
`in a system comprising a plurality of nodes with which callers and callees are associated. The
`
`process involves, in response to initiation of a call by a calling subscriber, receiving a caller
`
`identifier and a callee identifier. The process also involves using call classification criteria
`
`associated with the caller identifier to classify the call as a public network call or a private
`
`network call. The process further involves producing a routing message identifying an
`
`address, on the private network, associated with the callee when the call is classified as a
`
`private network call. The process also involves producing a routing message identifying a
`
`gateway to the public network whenthecall is classified as a public network call.
`
`[0008]
`
`The process may involve receiving a request to establish a call, from a call
`
`controller in communication with a caller identified by the callee identifier.
`
`[0009]
`
`Using the call classification criteria may involve searching a database to
`
`locate a record identifying calling attributes associated with a caller identified by the caller
`
`identifier.
`
`[0010]
`
`Locating a record may involve locating a caller dialing profile comprising
`
`a username associated with the caller, a domain associated with the caller, and at least one
`
`calling attribute.
`
`[0011]
`
`Using the call classification criteria may involve comparing calling
`
`attributes associated with the caller dialing profile with aspects of the callee identifier.
`
`-2-
`
`AT&T, Exh. 1002, p. 9
`
`AT&T, Exh. 1002, p. 9
`
`

`

`[0012]
`
`Comparing may involve determining whetherthe callee identifier includes
`
`a portion that matches an IDD associated with the caller dialing profile.
`
`[0013]
`
`Comparing may involve determining whetherthe callee identifier includes
`
`a portion that matches an NDDassociated with the caller dialing profile.
`
`[0014]
`
`Comparing may involve determining whetherthe callee identifier includes
`
`a portion that matches an area code associated with the caller dialing profile.
`
`[0015]
`
`Comparing may involve determining whether the callee identifier has a
`
`length within a range specified in the caller dialing profile.
`
`[0016]
`
`The process may involve formatting the callee identifier into a pre-defined
`
`digit format to produce a re-formatted callee identifier.
`
`[0017]
`
`Formatting may involve removing an international dialing digit from the
`
`callee identifier, when the callee identifier begins with a digit matching an international
`
`dialing digit specified by the caller dialing profile associated with the caller.
`
`[0018]
`
`Formatting may involve removing a national dialing digit from the callee
`
`identifier and prepending a caller country code to the callee identifier when the callee
`
`identifier begins with a national dialing digit.
`
`[0019]
`
`Formatting may involve prepending a caller country code to the callee
`
`identifier when the callee identifier begins with digits identifying an area code specified by
`
`the caller dialing profile.
`
`[0020]
`
`Formatting may involve prepending a caller country code and an area code
`
`to the callee identifier when the callee identifier has a length that matches a caller dialing
`
`number format specified by the caller dialing profile and only one area code is specified as
`
`being associated with the caller in the caller dialing profile.
`
`[0021]
`
`The process may involve classifying the call as a private network call
`
`whenthe re-formatted callee identifier identifies a subscriber to the private network.
`
`[0022]
`
`The process may involve determining whether
`
`the callee identifier
`
`complies with a pre-defined username format and if so, classifying the call as a private
`
`networkcall.
`
`[0023]
`
`The process may involve causing a database of records to be searched to
`
`locate a direct in dial (DID) bank table record associating a public telephone numberwith the
`
`AT&T, Exh. 1002, p. 10
`
`AT&T, Exh. 1002, p. 10
`
`

`

`reformatted callee identifier and if the DID bank table record is found, classifying the call as
`
`a private network call and if a DID bank table record is not found, classifying the call as a
`
`public networkcall.
`
`[0024]
`
`Producing the routing message identifying a node on the private network
`
`may involve setting a callee identifier in response to a username associated with the DID
`
`bank table record.
`
`[0025]
`
`Producing the routing message may involve determining whether a node
`
`associated with the reformatted callee identifier is the same as a node associated the caller
`
`identifier.
`
`[0026]
`
`Determining whether a node associated with the reformatted callee
`
`identifier is the same as a node associated the caller identifier may involve determining
`
`whether a prefix of the re-formatted callee identifier matches a corresponding prefix of a
`
`usernameassociated with the caller dialing profile.
`
`[0027]
`
`When the node associated with the caller is not the same as the node
`
`associated with the callee, the process involves producing a routing message including the
`
`caller identifier, the reformatted callee identifier and an identification of a private network
`
`node associated with the callee and communicating the routing messageto a call controller.
`
`[0028]
`
`When the node associated with the caller is the same as the node
`
`associated with the callee, the process involves determining whether to perform at least one
`
`of the following: forward the call to another party, block the call and direct the caller to a
`
`voicemail server associated with the callee.
`
`[0029]
`
`Producing the routing message may involve producing a routing message
`
`having an identification of at least one of the callee identifier, an identification of a party to
`
`whom the call should be forwarded and an identification of a voicemail server associated
`
`with the callee.
`
`[0030]
`
`Producing a routing message identifying a gateway to the public network
`
`may involve searching a database of route records associating route identifiers with dialing
`
`codesto find a route record having a dialing code having a numberpattern matchingatleast a
`
`portion of the reformatted callee identifier.
`
`-4-
`
`AT&T, Exh. 1002, p. 11
`
`AT&T, Exh. 1002, p. 11
`
`

`

`[0031]
`
`The process may involve communicating the routing message to a call
`
`controller.
`
`[0032]
`
`The process may involve searching a database of supplier
`
`records
`
`associating supplier identifiers with the route identifiers to locate at least one supplier record
`
`associated with the route identifier associated with the route record having a dialing code
`
`having a numberpattern matchingat least a portion of the reformatted callee identifier.
`
`[0033]
`
`The process may involve loading a routing message buffer with the
`
`reformatted callee identifier and an identification of specific routes associated respective ones
`
`of the supplier records associated with the route record and loading the routing message
`
`buffer with a time value and a timeout value.
`
`[0034]
`
`The process may involve communicating a routing message involving the
`
`contents of the routing message buffer to a call controller.
`
`[0035]
`
`The process may involve causing the dialing profile to include a maximum
`
`concurrentcall value and a concurrent call count value and causing the concurrent call count
`
`value to be incremented when the user associated with the dialing profile initiates a call and
`
`causing the concurrent call count value to be decremented when a call with the user
`
`associated with the dialing profile is ended.
`
`[0036]
`
`In accordance with another aspect of the invention, there is provideda call
`
`routing apparatus for facilitating communications between callers and callees in a system
`
`comprising a plurality of nodes with which callers and callees are associated. The apparatus
`
`includes receiving provisions for receiving a caller identifier and a callee identifier,
`
`in
`
`response to initiation of a call by a calling subscriber. The apparatus also includesclassifying
`
`provisions for classifying the call as a private network cal or a public network call according
`
`to call classification criteria associated with the caller identifier. The apparatus further
`
`includes provisions for producing a routing message identifying an address, on the private
`
`network, associated with the callee when the call is classified as a private network call. The
`
`apparatus also includes provisions for producing a routing message identifying a gateway to
`
`the public network whenthecall is classified as a public networkcall.
`
`AT&T, Exh. 1002, p. 12
`
`AT&T, Exh. 1002, p. 12
`
`

`

`[0037]
`
`The receiving provisions may be operably configured to receive a request
`
`to establish a call, from a call controller in communication with a caller identified by the
`
`callee identifier.
`
`[0038]
`
`The apparatus may further include searching provisions for searching a
`
`database including records associating calling attributes with subscribers to the private
`
`network to locate a record identifying calling attributes associated with a caller identified by
`
`the caller identifier.
`
`[0039]
`
`The records may include dialing profiles each including a username
`
`associated with the subscriber, an identification of a domain associated with the subscriber,
`
`and an identification of at least one calling attribute associated with the subscriber.
`
`[0040]
`
`The call classification provisions may be operably configured to compare
`
`calling attributes associated with the caller dialing profile with aspects of the callee identifier.
`
`[0041]
`
`The calling attributes may include an international dialing digit and call
`
`classification provisions may be operably configured to determine whether the callee
`
`identifier includes a portion that matches an IDD associated with the caller dialing profile.
`
`[0042]
`
`The calling attributes may include an national dialing digit and the call
`
`classification provisions may be operably configured to determine whether the callee
`
`identifier includes a portion that matches an NDD associated with the caller dialing profile.
`
`[0043]
`
`The calling attributes may include an area code andthecall classification
`
`provisions may be operably configured to determine whether the callee identifier includes a
`
`portion that matches an area code associated with the caller dialing profile.
`
`[0044]
`
`The calling attribute may include a number length range and the call
`
`classification provisions may be operably configured to determine whether the callee
`
`identifier has a length within a numberlength range specified in the caller dialing profile.
`
`[0045]
`
`The apparatus may further include formatting provisions for formatting the
`
`callee identifier into a pre-defined digit format to produce a re-formatted callee identifier.
`
`[0046]
`
`The formatting provisions may be operably configured to remove an
`
`international dialing digit from the callee identifier, when the callee identifier begins with a
`
`digit matching an international dialing digit specified by the caller dialing profile associated
`
`with the caller.
`
`AT&T, Exh. 1002, p. 13
`
`AT&T, Exh. 1002, p. 13
`
`

`

`[0047]
`
`The formatting provisions may be operably configured to remove a
`
`national dialing digit from the callee identifier and prepend a caller country code to the callee
`
`identifier when the callee identifier begins with a national dialing digit.
`
`[0048]
`
`The formatting provisions may be operably configured to prepend a caller
`
`country code to the callee identifier when the callee identifier begins with digits identifying
`
`an area code specified by the caller dialing profile.
`
`[0049]
`
`The formatting provisions may be operably configured to prepend a caller
`
`country code and area codeto the callee identifier when the callee identifier has a length that
`
`matches a caller dialing number format specified by the caller dialing profile and only one
`
`area code is specified as being associated with the caller in the caller dialing profile.
`
`[0050]
`
`The classifying provisions may be operably configured to classify the call
`
`as a private network call when the re-formatted callee identifier identifies a subscriber to the
`
`private network.
`
`[0051]
`
`The classifying provisions may be operably configured to classify the call
`
`as a private network call when the callee identifier complies with a pre-defined username
`
`format.
`
`[0052]
`
`The apparatus may further include searching provisions for searching a
`
`database of records to locate a direct in dial (DID) bank table record associating a public
`
`telephone number with the reformatted callee identifier and the classifying provisions may be
`
`operably configured to classify the call as a private network call when the DID bank table
`
`record is found andto classify the call as a public network call when a DID banktable record
`
`is not found
`
`[0053]
`
`The private network routing message producing provisions may be
`
`operably configured to produce a routing message having a callee identifier set according to a
`
`username associated with the DID banktable record.
`
`[0054]
`
`The private network routing message producing provisions may be
`
`operably configured to determine whether a node associated with the reformatted callee
`
`identifier is the same as a node associated the caller identifier.
`
`-7-
`
`AT&T, Exh. 1002, p. 14
`
`AT&T, Exh. 1002, p. 14
`
`

`

`[0055]
`
`The private network routing provisions may include provisions for
`
`determining whether a prefix of the re-formatted callee identifier matches a corresponding
`
`prefix of a usernameassociated with the caller dialing profile.
`
`[0056]
`
`The private network routing message producing provisions may be
`
`operably configured to produce a routing message including the caller identifier,
`
`the
`
`reformatted callee identifier and an identification of a private network node associated with
`
`the callee and to communicate the routing messageto a call controller.
`
`[0057]
`
`The private network routing mes