throbber
SMARB19.001APC
`
`PATENT
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Applicant
`
`:
`
`Perreault et a1.
`
`App. No
`
`: Unknown
`
`Filed
`
`For
`
`: April 30, 2009
`
`:
`
`PRODUCING ROUTING MESSAGES FOR
`
`VOICE OVER IP COMMUNICATIONS
`
`Examiner
`
`: Unassigned
`
`Art Unit
`
`: Unassigned
`
`Conf No.
`
`: Unassigned
`
`
`PRELIMINARY AMENDMENT
`
`Mail Stop Amendment
`Commissioner for Patents
`
`PO. Box 1450
`
`Alexandria, VA 22313-1450
`
`Dear Sir:
`
`Prior to examination of the above—identified application, Applicant respectfully submits
`
`the following amendment.
`
`Amendments to the Specification begin on page 2 of this paper.
`
`Amendments to the Claims are reflected in the listing of claims which begins on page 3
`
`of this paper.
`
`Remarks begin on page 12 of this paper.
`
`AT&T, EXh. 1002, p. 1
`
`AT&T, Exh. 1002, p. 1
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`AMENDMENTS TO THE SPECIFICATION
`
`Please enter the following paragraph after the title:
`
`This application is a national phase entry of PCT/CA2007/001956, filed November 1,
`
`2007, which claims priority to US. Provisional Application No. 60/856,212, filed November 2,
`
`2006, both of which are incorporated in their entirety.
`
`AT&T, EXh. 1002, p. 2
`
`AT&T, Exh. 1002, p. 2
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`AMENDMENTS TO THE CLAIMS
`
`Please amend Claim 30. Please cancel Claims 60-107.
`
`1.
`
`(Original) 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 comprising:
`
`in response to initiation of a call by a calling subscriber, receiving a caller
`
`identifier and a callee identifier;
`
`using call classification criteria associated with the caller identifier to classify the
`
`call as a public network call or a private network call;
`
`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; and
`
`producing a routing message identifying a gateway to the public network when the
`
`call is classified as a public network call.
`
`2.
`
`(Original) The process of claim 1
`
`further comprising receiving a request to
`
`A establish a call, from a call controller in communication with a caller identified by said callee
`
`identifier.
`
`3.
`
`(Original) The process of claim 1 wherein using said call classification criteria
`
`comprises searching a database to locate a record identifying calling attributes associated with a
`
`caller identified by said caller identifier.
`
`4.
`
`(Original) The process of claim 3 wherein locating a record comprises locating a
`
`caller dialing profile comprising a username associated with said caller, a domain associated with
`
`said caller, and at least one calling attribute.
`
`5.
`
`(Original) The process of claim 4 wherein using said call classification criteria
`
`comprises comparing calling attributes associated with said caller dialing profile with aspects of
`
`said callee identifier.
`
`6.
`
`(Original) The process of claim 4 wherein comparing comprises determining
`
`whether said callee identifier includes a portion that matches an IDD associated with said caller
`
`dialing profile.
`
`AT&T, EXh. 1002, p. 3
`
`AT&T, Exh. 1002, p. 3
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`7.
`
`(Original) The process of claim 4 wherein comparing comprises determining
`
`whether said callee identifier includes a portion that matches an NDD associated with said caller
`
`dialing profile.
`
`8.
`
`(Original) The process of claim 4 wherein comparing comprises determining
`
`whether said callee identifier includes a portion that matches an area code associated with said
`
`caller dialing profile.
`
`9.
`
`(Original) The process of claim 4 wherein comparing comprises determining
`
`whether said callee identifier has a length within a range specified in said caller dialing profile.
`
`10.
`
`(Original) The process of claim 4 further comprising formatting said callee
`
`identifier into a pre-defined digit format to produce a re-formatted callee identifier.
`
`11.
`
`(Original) The process of claim 10 wherein formatting comprises removing an
`
`international dialing digit from said callee identifier, when said callee identifier begins with a
`
`digit matching an international dialing digit specified by said caller dialing profile associated
`
`with said caller.
`
`12.
`
`(Original) The process of claim 10 wherein formatting comprises removing a
`
`national dialing digit from said callee identifier and prepending a caller country code to said
`
`callee identifier when said callee identifier begins with a national dialing digit.
`
`13.
`
`(Original) The process of claim 10 wherein formatting comprises prepending a
`
`caller country code to said callee identifier when said callee identifier begins with digits
`
`identifying an area code specified by said caller dialing profile.
`
`14.
`
`(Original) The process of claim 10 wherein formatting comprises prepending a
`
`caller country code and area code to said callee identifier when said callee identifier has a length
`
`that matches a caller dialing number format specified by said caller dialing profile and only one
`
`area code is specified as being associated with said caller in said caller dialing profile.
`
`15.
`
`(Original) The process of claim 10 further comprising classifying said call as a
`
`private network call when said re-formatted callee identifier identifies a subscriber to the private
`
`network.
`
`16.
`
`(Original) The process of claim 10 further comprising determining whether said
`
`callee identifier complies with a pre—defined username format and if so classifying the call as a
`
`private network call.
`
`AT&T, EXh. 1002, p. 4
`
`AT&T, Exh. 1002, p. 4
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`17.
`
`(Original) The process of claim 10 further comprising causing a database of
`
`records to be searched to locate a direct in dial (DID) bank table record associating a public
`
`telephone number with said reformatted callee identifier and if said 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 network call.
`
`18.
`
`(Original) The process of claim 17 wherein producing said routing message
`
`identifying a node on the private network comprises setting a callee identifier in response to a
`
`username associated with said DID bank table record.
`
`19.
`
`(Original) The process of claim 18 wherein producing said routing message
`
`comprises determining whether a node associated with the reformatted callee identifier is the
`
`same as a node associated the caller identifier.
`
`20.
`
`(Original) The process of claim 19 wherein determining whether a node
`
`associated with the reformatted callee identifier is the same as a node associated the caller
`
`identifier comprises determining whether a prefix of said re-formatted callee identifier matches a
`
`corresponding prefix of a username associated with said caller dialing profile.
`
`21.
`
`(Original) The process of claim 20 wherein when said node associated with said
`
`caller is not the same as the node associated with the callee, producing a routing message
`
`including said caller identifier, said reformatted callee identifier and an identification of a private
`
`network node associated with said callee and communicating said routing message to a call
`
`controller.
`
`22.
`
`(Original) The process of claim 19 wherein when said node associated with said
`
`caller is the same as the node associated with said callee, determining whether to perform at least
`
`one of the following: forward said call to another party, block the call and direct the caller to a
`
`voicemail server associated with the callee.
`
`23.
`
`(Original) The process of claim 22 wherein producing said routing message
`
`comprises 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.
`
`24.
`
`(Original) The process of claim 23 further comprising communicating said routing
`
`message to a call controller.
`
`AT&T, EXh. 1002, p. 5
`
`AT&T, Exh. 1002, p. 5
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`25.
`
`(Original) The process of claim 10 wherein producing a routing message
`
`identifying a gateway to the public network comprises searching a database of route records
`
`associating route identifiers with dialing codes to find a route record having a dialing code
`
`having a number pattern matching at least a portion of said reformatted callee identifier.
`
`26.
`
`(Original) The process of claim 25 further comprising searching a database of
`
`supplier records associating supplier identifiers with said route identifiers to locate at least one
`
`supplier record associated with said route identifier associated with said route record having a
`
`dialing code having a number pattern matching at least a portion of said reformatted callee
`
`identifier.
`
`27.
`
`(Original) The process of claim 26 further comprising 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 said route record and loading said routing
`
`message buffer with a time value and a timeout value.
`
`28.
`
`(Original) The process of claim 27 further comprising communicating a routing
`
`message comprising the contents of said routing message buffer to a call controller.
`
`29.
`
`(Original) The process of claim 4 further comprising causing said dialing profile
`
`to include a maximum concurrent call value and a concurrent call count value and causing said
`
`concurrent call count value to be incremented when the user associated with said dialing profile
`
`initiates a call and causing said concurrent call count value to be decremented when a call with
`
`said user associated with said dialing profile is ended.
`
`30.
`
`(Currently amended) A computer readable medium encoded with codes for
`
`directing a processor to execute the a method of any—ene—etLelaimsHQ operating a call routing
`
`controller to facilitate communication between callers and callees in a system comprising a
`
`pluraligg of nodes with which callers and callees are associated, the method comprising:
`
`in response to initiation of a call by a calling subscriber, receiving a caller
`
`identifier and a callee identifier;
`
`usin call classification criteria associated with the caller identifier to classi
`
`the
`
`call as a public network call or a private network call;
`
`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; and
`
`-6-
`
`AT&T, EXh. 1002, p. 6
`
`AT&T, Exh. 1002, p. 6
`
`

`

`Application No.: Unknown
`
`Filing Date:
`
`April 30, 2009
`
`producing a routing message identifling a gateway to the public network when the
`
`call is classified as a public network call.
`
`31.
`
`(Original) A 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 comprising:
`
`receiving means for receiving a caller identifier and a callee identifier, in response
`
`to initiation of a call by a calling subscriber;
`
`classifying means for classifying the call as a private network cal or a public
`
`network call according to call classification criteria associated with the caller identifier;
`
`means 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;
`
`and
`
`means for producing a routing message identifying a gateway to the public
`
`network if the call is classified as a public network call.
`32.
`(Original) The apparatus of claim 31 wherein said receiving means is operably
`
`configured to receive a request to establish a call, from a call controller in communication with a
`
`caller identified by said callee identifier.
`
`33.
`
`(Original) The apparatus of claim 31 further comprising searching means for
`
`searching a database comprising records associating calling attributes with subscribers to said
`
`private network to locate a record identifying calling attributes associated with a caller identified
`
`by said caller identifier.
`
`34.
`
`(Original) The apparatus of claim 33 wherein said records include dialing profiles
`
`each comprising a username associated with said subscriber, an identification of a domain
`
`associated with said subscriber, and an identification of at least one calling attribute associated
`
`with said subscriber.
`
`35.
`
`(Original) The apparatus of claim 34 wherein said call classification means is
`
`operably configured to compare calling attributes associated with said caller dialing profile with
`
`aspects of said callee identifier.
`
`36.
`
`(Original) The apparatus of claim 35 wherein said calling attributes include an
`
`international dialing digit and wherein said call classification means is operably configured to
`
`-7-
`
`AT&T, EXh. 1002, p. 7
`
`AT&T, Exh. 1002, p. 7
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`determine whether said callee identifier includes a portion that matches an IDD associated with
`
`said caller dialing profile.
`
`37.
`
`(Original) The apparatus of claim 34 wherein said calling attributes include an
`
`national dialing digit and wherein said call classification means is operably configured to
`
`determine whether said callee identifier includes a portion that matches an NDD associated with
`
`said caller dialing profile.
`
`38.
`
`(Original) The apparatus of claim 34 wherein said calling attributes include an
`
`area code and wherein said call classification means is operably configured to determine whether
`
`said callee identifier includes a portion that matches an area code associated with said caller
`
`dialing profile.
`
`39.
`
`(Original) The apparatus of claim 34 wherein said calling attribute include a
`
`number length range and wherein said call classification means is operably configured to
`
`determine whether said callee identifier has a length within a range specified in said caller dialing
`
`profile.
`
`40.
`
`(Original) The apparatus of claim 34 further comprising formatting means for
`
`formatting said callee identifier into a pre-defined digit format to produce a re—formatted callee
`
`identifier.
`
`41.
`
`(Original) The apparatus of claim 40 wherein said formatting means is operably
`
`configured to remove an international dialing digit from said callee identifier, when said callee
`
`identifier begins with a digit matching an international dialing digit specified by said caller
`
`dialing profile associated with said caller.
`
`42.
`
`(Original) The apparatus of claim 40 wherein said formatting means is operably
`
`configured to remove a national dialing digit from said callee identifier and prepend a caller
`
`country code to said callee identifier when said callee identifier begins with a national dialing
`
`digit.
`
`43.
`
`(Original) The apparatus of claim 40 wherein said formatting means is operably
`
`configured to prepend a caller country code to said callee identifier when said callee identifier
`
`begins with digits identifying an area code specified by said caller dialing profile.
`
`44.
`
`(Original) The apparatus of claim 40 wherein said formatting means is operably
`
`configured to prepend a caller country code and area code to said callee identifier when said
`
`-3-
`
`AT&T, EXh. 1002, p. 8
`
`AT&T, Exh. 1002, p. 8
`
`

`

`Application N0.: Unknown
`Filing Date:
`April 30, 2009
`
`callee identifier has a length that matches a caller dialing number format specified by said caller
`
`dialing profile and only one area code is specified as being associated with said caller in said
`
`caller dialing profile.
`
`45.
`
`(Original) The apparatus of claim 40 wherein said classifying means is operably
`
`configured to classifying said call as a private network call when said re-formatted callee
`identifier identifies a subscriber to the private network.
`9
`
`46.
`
`(Original) The apparatus of claim 40 wherein said classifying means is operably
`
`configured to classify the call as a private network call when said callee identifier complies with
`
`a pre—defined username format.
`
`47.
`
`(Original) The apparatus of claim 40 further comprising searching means for
`
`searching a database of records to locate a direct in dial (DID) bank table record associating a
`
`public telephone number with said reformatted callee identifier and wherein said classifying
`
`means is operably configured to classify the call as a private network call when said DID bank
`
`table record is found and to classify the call as a public network call when a DID bank table
`
`record is not found
`
`48.
`
`(Original) The apparatus of claim 47 wherein said private network routing
`
`message producing means is operably configured to produce a routing message having a callee
`
`identifier set according to a usemame associated with said DID bank table record.
`
`49.
`
`(Original) The apparatus of claim 48 wherein said private network routing
`
`message producing means is operably configured to determine whether a node associated with
`
`the reformatted callee identifier is the same as a node associated the caller identifier.
`
`50.
`
`(Original) The apparatus of claim 49 wherein said private network routing means
`
`includes means for determining whether a prefix of said re—formatted callee identifier matches a
`
`corresponding prefix of a username associated with said caller dialing profile.
`
`51.
`
`(Original) The apparatus of claim 50 wherein said private network routing
`
`message producing means is operably configured to produce a routing message including said
`
`caller identifier, said reformatted callee identifier and an identification of a private network node
`
`associated with said callee and communicating said routing message to a call controller.
`
`52.
`
`(Original) The apparatus of claim 49 wherein said private network routing
`
`message producing means is operably configured to perform at least one of the following:
`
`-9-
`
`AT&T, EXh. 1002, p. 9
`
`AT&T, Exh. 1002, p. 9
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`forward said call to another party, block the call and direct the caller to a voicemail server
`
`associated with the callee, when said node associated with said caller is the same as the node
`
`associated with said callee.
`
`53.
`
`(Original) The apparatus of claim 52 wherein said means for producing said
`
`private network routing message is operably configured to produce 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.
`
`54.
`
`(Original) The
`
`apparatus of
`
`claim 53
`
`further
`
`comprising means
`
`for
`
`communicating said routing message to a call controller.
`
`55.
`
`(Original) The apparatus of claim 40 wherein said means for producing a public
`
`network routing message identifying a gateway to the public network comprises means for
`searching a database of route records associating route identifiers with dialing codes to find a
`
`route record having a dialing code having a number pattern matching at least a portion of said
`
`reformatted callee identifier.
`
`56.
`
`(Original) The apparatus of claim 55 further comprising means for searching a
`
`database of supplier records associating supplier identifiers with said route identifiers to locate at
`
`least one supplier record associated with said route identifier associated with said route record
`
`having a dialing code having a number pattern matching at least a portion of said reformatted
`
`callee identifier.
`
`57.
`
`(Original) The apparatus of claim 56 further comprising a routing message buffer
`
`and means for loading said routing message buffer with the reformatted callee identifier and an
`
`identification of specific routes associated respective ones of the supplier records associated with
`
`said route record and loading said routing message buffer with a time value and a timeout value.
`
`58.
`
`(Original) The
`
`apparatus of
`
`claim 57
`
`further
`
`comprising means
`
`for
`
`communicating a routing message comprising the contents of said routing message buffer to a
`
`call controller.
`
`59.
`
`(Original) The apparatus of claim 34 further comprising means for causing said
`
`dialing profile to include a maximum concurrent call value and a concurrent call count value and
`
`for causing said concurrent call count value to be incremented when the user associated with said
`
`-10-
`
`AT&T, EXh. 1002, p. 10
`
`AT&T, Exh. 1002, p. 10
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`dialing profile initiates a call and for causing said concurrent call count value to be decremented
`
`when a call with said user associated with said dialing profile is ended.
`
`60. — 107. (Canceled)
`
`-11-
`
`AT&T, EXh. 1002, p. 11
`
`AT&T, Exh. 1002, p. 11
`
`

`

`Application No.: Unknown
`Filing Date:
`April 30, 2009
`
`REMARKS
`
`
`
`Applicant has amended Claim 30 and canceled Claims 60-107. Applicant
`
`is not
`
`conceding in this application that the previously pending claims are not patentable over the cited
`
`references. Rather, any alterations or characterizations are being made to facilitate expeditious
`
`prosecution of this application. Applicant reserves the right to pursue at a later date the
`
`previously pending claims or other broader or narrower claims that capture any subject matter
`
`supported by the present disclosure. Accordingly, reviewers of this or any parent, child or related
`prosecution history shall not reasonably infer that Applicant has made any disclaimers or
`
`disavowals of any subject matter supported by the present application.
`
`Please charge any additional fees, including any fees for additional extension of time, or
`
`credit overpayment to Deposit Account No. 11-1410.
`
`
`
`KNOBBE *
`
`LSON & BEAR, LLP
`
`Dated: April 30, 2009
`
`By:
`
`705 8627
`042809
`
`John M. Carson
`
`Registration No. 34,303
`Attorney of Record
`Customer No. 20995
`
`(619) 235-8550
`
`-12-
`
`AT&T, EXh. 1002, p. 12
`
`AT&T, Exh. 1002, p. 12
`
`

`

`
`
`
`IN THE PATENT COOPERATION TREATY
`
`IN RE APPLICATION
`Serial No.:
`PCT/CA2007/OO1956
`
`Filing Date:
`Applicant:
`Title:
`
`Inventor:
`
`01 NOVEMBER 2007 (01—11—2007)
`.
`DlGlFONICA (INTERNATIONAL) LIMITED
`PRODUCING ROUTING MESSAGES FOR VOICEOVER IP
`COMMUNICATIONS
`
`PERREAULT, Clay; NICHOLSON, Steve; THOMSON, Rod;
`BJORSELL, Johan Emil Victor; ARAFA, Fuad
`
`Agent’s Ref.:
`
`83636-16
`
`The International Bureau of WIPO
`
`34, chemin des Colombettes
`1211 Geneva 20
`Switzerland
`
`Dear Sirs:
`
`17 April 2008 _
`
`VIA FACSIMILE ONLY
`
`AMENDMENT UNDER ARTICLE 19
`
`Please cancel claim pages 82 — 84 and substitute the enclosed claim pages 82 — 84
`
`thereto r.
`
`A (
`
`John W. Knox
`SMART & BIGGAR
`Box 11560 Vancouver Centre
`
`Suite 2200, 650 West Georgia Street
`Vancouver, British Columbia
`Canada VBB 4N8
`
`JWK:GHC:gsg:m|m
`Encls.:
`Replacement Claim Pages 82 — 84
`
`AT&T, Exh. 1002, p. 13
`
`AT&T, Exh. 1002, p. 13
`
`

`

`IN THE PATENT COOPERATION TREATY
`
`IN RE APPLICATION
`Serial No.2
`PCT/CA2007/001956
`
`Filing Date:
`Applicant:
`Title:
`
`01 NOVEMBER 2007 (01—11—2007)
`DlGlFONlCA (lNTERNATlONAL) LIMITED
`PRODUCING ROUTING MESSAGES FOR VOlCEOVER lP
`COMMUNICATIONS
`
`Inventor:
`
`PERREAULT, Clay; NICHOLSON, Steve; THOMSON, Rod;
`BJORSELL, Johan Emil Victor; ARAFA, Fuad
`
`Agent’s Ref.:
`83636—16
`
`14 April 2008
`
`VIA FACSIMILE ONLY
`
`The International Bureau of WIPO
`
`34, chemin des Colombettes
`1211 Geneva 20
`Switzerland
`
`Dear Sirs:
`
`Letter Ex lainin the Differences Between the Claims as Filed and the Claims as
`
`
`Amended
`
`Claims 60 and 61 have been amended.
`
`The remaining claims 1 — 59 and 62 — 107 are unchanged.
`
`
`
`John W. Knox
`SMART & BlGGAR
`Box 11560 Vancouver Centre
`
`'
`
`Suite 2200, 650 West Georgia Street
`Vancouver, British Columbia
`Canada V6B 4N8
`
`JWK:GHC:gsg:mlm
`
`AT&T, EXh. 1002, p. 14
`
`
`
`
`AT&T, Exh. 1002, p. 14
`
`

`

`_82.
`
`code having a number pattern matching at least 'a portion of said
`
`reformatted callee identifier.
`
`57.
`
`The apparatus of claim 56 further comprising a routing message buffer
`
`and means
`
`for
`
`loading said routing message buffer with
`
`the
`
`reformatted callee identifier and an identification of specific routes
`
`associated respective ones of the supplier records associated with said
`
`route record and loading said routing message buffer with a time value
`
`and a timeout value.
`
`10
`
`58.
`
`The apparatus of claim 57 further comprising means for communicating
`
`a routing message comprising the contents of said routing message
`
`buffer to a call controller.
`
`15
`
`59.
`
`The apparatus of claim 34 further comprising means for causing said
`dialing profile to include a maximum concurrent call value and a
`
`concurrent call count value and for causing said concurrent call count
`
`value to be incremented when the user associated with said dialing
`
`profile initiates a call and for causing said concurrent call count value to
`
`20
`
`be decremented when a call with said user associated with said dialing
`
`profile is ended.
`
`Data Stru ctu re
`
`25
`
`60.
`
`A data structure for access by an apparatus for producing a routing
`
`message for use by a call
`
`routing controller in a communications
`
`system, the data structure comprising:
`
`30
`
`subscriber username with respective subscribers to the system;
`
`dialing profile
`
`records comprising fields
`
`for associating a
`
`AT&T, EXh. 1002, p. 15
`
`
`
`AT&T, Exh. 1002, p. 15
`
`

`

`. -83-
`
`direct—in—dial
`
`records comprising fields for associating a user
`
`domain and a direct-in-dial number with respective subscriber
`
`usernames;
`
`prefix to node records comprising fields for associating a node
`
`address of a node in said system with at least a portion of said
`
`respective subscriber usernames:
`
`whereby said subscriber username can be used to find said user
`
`domain, at least a portion of said subscriber username can be
`
`used to find said node with which a subscriber identified by said
`
`subscriber user name is associated, and said user domain and
`
`said subscriber username can be located in response to said
`
`direct—in—dial number.
`
`61.
`
`A data structure for access by an apparatus for producing a routing
`
`message for use by a call
`
`routing controller in a communications
`
`system, the data structure comprising:
`
`master list records comprising fields for associating a dialing
`
`code with respective master list identifiers; and
`
`supplier list records linked to said master list records by said
`
`master list identifiers, said supplier list records comprising fields
`
`for associating with a communications services supplier:
`
`a supplier id;
`
`a master list id;
`
`a route identifier; and
`
`’10
`
`’15
`
`20
`
`25
`
`30
`
`AT&T, EXh. 1002, p. 16
`
`
`
`AT&T, Exh. 1002, p. 16
`
`

`

`
`
`-84_
`
`a billing rate code,
`
`whereby at
`
`least one communications
`
`service supplier
`
`is
`
`associated with said dialing code, such that said dialing code
`
`can be used to locate suppliers capable of providing a
`
`communications link associated with a given dialing code.
`
`62.
`
`A method of determining a time to permit a communication session to
`
`be conducted, the method comprising:
`
`calculating a cost per unit time;
`
`calculating a first time value as a sum of a free time attributed to
`
`a participant in the communication session and the quotient of a
`
`funds balance held by said participant to said cost per unit time
`
`value; and
`
`producing a second time value in response to said first time
`
`value and a billing pattern associated with said participant, said
`billing pattern including first and second billing intervals and:
`
`said second time value
`
`being
`
`said
`
`time
`
`to
`
`permit
`
`a
`
`communication session to be conducted.
`
`63.
`
`The method of claim 62 wherein calculating said first
`
`time value
`
`comprises retrieving a record associated with said participant and
`obtaining from said record at least one of said free time and said funds
`
`balance.
`
`10
`
`15'
`
`20
`
`25
`
`AT&T, EXh. 1002, p. 17
`
`AT&T, Exh. 1002, p. 17
`
`

`

`PATENT COOPERATION TREATY A
`
`PCT
`
`INTERNATIONAL SEARCH REPORT
`(PCT Article 18 and Rules 43 and 44)
`
`
`
`
`
`FOR FURTHER
`11
`h
`l' bl , 't
`
`ACTION as we as, W,“ app ‘03 f;
`
`. (fifiiéfiflfi’it‘fié? datie‘lcday/monthélear)
`International filing date (day/month/year)
`01 November 2007 (01-11—2007)
`02 November 2006 (02-11-2006)
`
`
`
`
`
`
`
`5 b l
`
`Applicant’s or agent's file reference
`83636-16
`International application No.
`
`PCT/CA2007/001956
`
`
`Applicant
`DIGIFONICA (INTERNATIONAL) LIMITED ET AL
`
`This international search report has been prepared by this International Searchin
`Article 18. A copy is being transmitted to the International Bureau.
`
`
`
`g Authority and is transmitted to the applicant according to
`
`
`
`
`
`:v
`
`
`
`
`This international search report consists of a total of
`
` [X] It is also accompanied by a copy of each prior art document cited in this report.
`
`sheets,
`
`1.
`
`Basis of the report '
`
`a. With regard to the language, the international search was carried out on the basis of:
`
`[X]
`
`the international application in the language in which it was filed
`
`[
`
`]
`
`a translation of the international application into
`ofa translation furnished for the purposes of international search (Rules 12.3(a) and 23.1(b))
`
`, which is the language
`
`b.
`
`[
`
`]This international search report has been established taking into account the rectification of an obvious mistake
`
`authorized by or notified to this Authority under Rule 91 (Rule 43.6biS(a)).
`
`c.
`
`[
`[
`
`] With regard to any nucleotide and/or amino acid sequence disclosed in the international application, see Box No. I
`] Certain claims were found unsearchable (see Box No. II)
`
`[X] Unity of invention is lacking (see Box No. III)
`
`With regard to the title,
`
`[X] the text is approved as submitted by the applicant
`
`[
`
`] the text has been established by this Authority to read as follows :
`
`2.
`
`3.
`
`4.
`
`5.
`
`With regard to the abstract,
`
`[X] the text is approved as submitted by the applicant
`
`[
`
`]the text has been established, according to Rule 38.2, by this Authority as it appears in Box No. IV. The applicant
`
`may, within one month from the date of mailing of this international search report, submit comments to this Authority
`
`6.
`
`With regard to the drawings,
`
`a.
`
`the figure of the drawings to be published with the abstract is Figure No.
`
`l
`
`[X]
`
`as suggested by the applicant
`
`[
`
`[
`
`[
`
`b.
`
`]
`
`]
`
`as selected by this Authority, because the applicant failed to suggest a figure
`
`as selected by this Authority, because this figure better characterizes the invention
`
`/
`
`] none of the figures is to be published with the abstract
`
`Form PCT/ISA/210 (first sheet) (April 2007) (Revised)
`
`1 90¢
`@3913(V.
`
`ll
`
`, 42-3
`Page 1 of 5
`
`'
`
`AT&T, EXh. 1002, p. 18
`
`AT&T, Exh. 1002, p. 18
`
`

`

`
`
`International application No.
`PCT/CA2007/001956
`
`
`
`INTERNATIONAL SEARCH REPORT
`
`
`
`
`This international search report has not been established in respect of certain claims under Article 17(2)(a) for the following
`reasons :
`
`Observations where certain claims were found unsearchable (Continuation of item‘2‘of the first sheet) ‘
`
`
`
`1,
`
`[
`
`] Claim Nos. :
`
`because they relate to subject matter not required to be searched by this Authority, namely :
`
`2.
`
`[
`
`]ClaimNos.:
`
`because they relate to parts of the international application that do not comply with the prescribed requirements to such an extent
`that no meaningful international search can be carried out, specifically :
`
`3.
`
`[
`
`] Claim Nos::
`
`because they are dependant claims and are not drafted in accordance with the second and third sentences of Rule 6.4(a).
`
`Box No. III
`
`Observations where unity of invention is lacking (Continuation of item 3 of first sheet)
`
`This International Searching Authority found multiple inventions in this international application, as follows :
`
`Group I
`Group II
`Group III
`Group IV
`
`Claims 1-59
`Claims 60, 61
`Claims 62-84
`Claims 85-107
`
`1.
`
`[X] As all required additional search fees were timely paid by the applicant, this international search report covers all
`searchable claims.
`
`As all searchable claims could be searched without effort justifying additional fees, this Authority did not invite
`payment of additional fees.
`
`As only some of the required additional search fees were timely paid by the applicant, this international search report
`covers only those claims for which fees were paid, specifically claim Nos. :
`
`No required additional search fees were timely paid by the applicant. Consequently, this international search report is
`
`\Kh/x
`
`restricted to the invention first mentioned in die claims; it is covered by claim Nos. :
`
`Remark on Protest
`
`[
`
`[
`
`] The additional search fees were accompanied by the applicant’s protest and, Where applicable,
`the payment of a protest fee.
`
`] The additional search fees were accompanied by the applicant’s protest but the applicable

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket