throbber
. .
`.,..
`
`.
`
`.
`
`'
`
`..
`
`!
`
`. '
`
`r,,
`
`•
`
`,,.
`
`t
`
`to.
`
`•
`
`',, .
`
`•i.
`
`~
`
`- ~··- ... '
`
`Examiner: Dao L. Phan
`
`Serial No.: 09/194,367
`
`Issue Batch No.: 130
`
`Filed: November 24, 1998
`
`Atty. File No.: 1003-PUS
`
`For:
`
`"LOCATION OF A MOBILE
`STATION"
`
`AMENDMENT AFTER NOTICE OF
`ALLOW ABILITY
`
`CERTIFICATE OF MAILING
`
`I HEREBY CERTIFY THAT THIS CORRESPONDENCE IS BEING
`DEPOSITED WITH THE UNITED STATES POSTAL SERVICE AS
`FIRST CLASS MAIL IN AN ENVELOPE ADDRESSED TO
`ASSISTANT COMMISSIONER FOR P TENTS, WASHINGTON,
`DC 20231 ON THIS __l'±:_ DAY OF
`'
`,2001.
`
`Dear sir:
`
`~,/"' •: •• ( ~\. 1
`
`Chasl C. Ross urn
`
`Assistant Commissioner for Patents
`· . .. ;l
`Washington, D.C. 20231
`,..
`. ~/
`Bv:0 .
`,\ . ,, ,,. -~_\,. <
`In the(;)o~identified patent application, formal drawings necessitated that Fig. 9 as
`originally filed has now become Figs. 9A and 9B. Accordingly it is requested that the following
`
`changes to the specification be entered to reflect these changes, and reconsideration of the
`
`application is requested.
`
`Please amend the above-identified patent application as follows:
`
`IN THE SPECIFICATION:
`
`Please amend the paragraph beginning on page 22, line 14 as follows:
`
`Figs. 9A and 98 are high level data structure diagrams describing the fields of a
`location hypothesis object generated by the first order models 1224 of the location
`center.
`
`Please amend the paragraph beginning on page 79, line 26 as follows:
`
`Input:
`
`hypothesis;
`hypothesis: MS locati
`collection of measured location signatures ("Joe
`measured_loc_sig_bag:
`from the MS (the data structure here is an
`sigs" for short) obtaine
`rray or list). Note, it is assumed that there is at
`aggregation such as an
`most one loc sig here pe Base Station in this collection. Additionally,
`note that the input data st cture here may be a location signature
`cluster such as the "loc si cluster" field of a location hypothesis (cf.
`Figs. 9A and 98). Note-that ariations in input data structures may be
`
`,
`
`-
`
`0/o\
`
`Apple, Inc. Exhibit 1021 Page 1
`
`

`
`•
`
`•
`
`•
`
`,4_eplication No. 09/194,367
`~-::::1
`J.j12.cument: "AMENDMENT AFTER ALLOWAN~
`
`accepted here by utilization of flag or tag bits as one skilled in the art will
`appreciate;
`search_criteria: The criteria for arching the verified location signature data
`base for various categories o loc sigs. The only limitation on the types of
`categories that may be provid d here is that, to be useful, each category
`should have meaningful numb of loc sigs in the location signature data
`base. The following categories i eluded here are illustrative, but others
`are contemplated:
`(a) "USE ALL LOG SIGS IN D "(the default),
`(b) "USE ONLY REPEATABL LOC SIGS",
`(c) "USE ONLY LOG SIGS WI
`SIMILAR TIME OF DAY".
`Further categories of loc sigs close to the MS estimate of "hypothesis"
`contemplated are: all loc sigs for the same season and same time of
`day, allloc sigs during a specific weather condition (e.g., snowing) and
`at the same time of day, as well as other limitations for other
`environmental conditions such as traffic patterns. Note, if this parameter
`is NIL, then (a) is assumed.
`
`Please amend the paragraph beginning on page 85, line 5 as follows:
`
`This function creates a new list of I cation hypotheses from the input list,
`"loc_hyp_list", wherein the location hyp theses on the new list are modified versions of
`those on the input list. For each locatio hypothesis on the input list, one or more
`corresponding location hypotheses will b on the output list. Such corresponding output
`location hypotheses will differ from their a ociated input location hypothesis by one or
`more of the following: (a) the "image_area' field (see Figs. 9A and 98) may be
`assigned an area indicative of where the tar et MS is estimated to be, (b) if
`-r---~ "image_area" is assigned, then the "confiden e" field will be the confidence that the
`target MS is located in the area for "image_arJ~"· (c) if there are not sufficient "nearby"
`verified location signature clusters in the locatio signature data base 1320 to entirely
`rely on a computed confidence using such verifi d location signature clusters, then two
`location hypotheses (having reduced confidence will be returned, one having a
`reduced computed confidence (for "image_area") sing the verified clusters in the
`Location Signature data base, and one being subst. ntially the same as the associated
`input location hypothesis except that the confidence for the field "area_est") is reduced
`to reflect the confidence in its paired location hypothe~·s having a computed confidence
`for "image_area". Note also, in some cases, the locat1 n hypotheses on the input list,
`may have no change to its confidence or the area tow 'ch the confidence applies.
`
`-2-
`
`Apple, Inc. Exhibit 1021 Page 2
`
`

`
`•
`
`Application No. 091194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`'
`
`Please amend the paragraph beginning on page 89, line 18 as follows:
`
`(35.5} A location extrapolator module 143 for use in updating previous location estimates
`for a target MS when a more recent I cation hypothesis is provided to the location
`hypothesis analyzer 1332. That is, a ume that the control module 1400 receives a
`new location hypothesis for a target M
`for which there are also one or more previous
`location hypotheses that either have b n recently processed (i.e., they reside in the
`MS status repository 1338, as shown b st in Fig. 6), or are currently being processed
`(i.e., they reside in the run-time location ypothesis storage area 1410). Accordingly, if
`the active_timestamp (see Figs. 9A and B regarding location hypothesis data fields)
`of the newly received location hypothesis
`sufficiently more recent than the
`active_timestamp of one of these previous location hypotheses, then an extrapolation
`may be performed by the location extrapol tor module 1432 on such previous location
`hypotheses so that all target MS location hy otheses being concurrently analyzed are
`presumed to include target MS location esti ates for substantially the same point in
`time. Thus, initial location estimates generate by the FOMs using different wireless
`signal measurements, from different signal tra smission time intervals, may have their
`corresponding dependent location hypotheses
`tilized simultaneously for determining
`a most likely target MS location estimate. Note hat this module may also be daemon
`or expert system rule base.
`
`Please amend the paragraph beginning on page 89, line 18 as follows:
`
`Y. u for a target MS when a more recent location hypothesis is provided to the location
`
`/
`
`(35.5) A location extrapolator module 1432 for use in updating previous location estimates
`
`Jf
`V J1
`hypothesis analyzer 1332. That is, assume that the control module 1400 receives a
`t-o-;f! '-, ~ new location hypothesis for a target MS for which there are also one or more previous
`( 7 V::\S'·
`location hypotheses that either have been recently processed (i.e., they reside in the
`V
`V'
`MS status repository 1338, as shown best in Fig. 6), or are currently being processed
`(i.e., they reside in the run-time location hypothesis storage area 1410). Accordingly, if
`the active_timestamp (see Figs. 9A and 98 regarding location hypothesis data fields)
`of the newly received location hypothesis is sufficiently more recent than the
`active_timestamp of one of these previous location hypotheses, then an extrapolation
`may be performed by the location extrapolator module 1432 on such previous location
`hypotheses so that all target MS location hypotheses being concurrently analyzed are
`presumed to include target MS location estimates for substantially the same point in
`time. Thus, initial location estimates generated by the FOMs using different wireless
`signal measurements, from different signal transmission time intervals, may have their
`corresponding dependent location hypotheses utilized simultaneously for determining
`a most likely target MS location estimate. Note that this module may also be daemon
`
`-3-
`
`Apple, Inc. Exhibit 1021 Page 3
`
`

`
`•
`
`•
`
`Application No. 09/194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`or expert system rule base.
`
`Please amend the paragraph beginning on page 143, line 13 as follows:
`
`hypothesis: MS location hypothesis;
`Input:
`~. k
`-measured_loc_sig_b g: A collection of measured location signatures ("loc
`l:>~ "/,.~ sigs" for short) obtai ed from the MS (the data structure here is an
`')..~
`aggregation such as
`array or list). Note, it is assumed that there is at
`r Base Station in this collection. Additionally,
`most one loc sig here
`note that the input data tructure here may be a location signature
`cluster such as the "loc_s ~cluster" field of a location hypothesis (cf.
`Figs. 9A and 98). Note th variations in input data structures may be
`accepted here by utilization
`f flag or tag bits as one skilled in the art will
`appre\iate;
`search_ criteria: The criteria for searching the verified location signature
`data base for various categories of loc sigs. The only limitation on the
`types of categories that may be provided here is that, to be useful, each
`category should have meaningful number of lac sigs in the location
`signature data base. The following categories included here are
`illustrative, but others are contemplated:
`(a) "USE ALL LOC SIGS IN DB" (the default),
`(b) "USE ONLY REPEATABLE LOC SIGS",
`(c) "USE ONLY LOG SIGS WITH SIMILAR TIME OF DAY".
`Further categories of loc sigs close to the MS estimate of "hypothesis"
`contemplated are: all loc sigs for the same season and same time of
`day, allloc sigs during a specific weather condition (e.g., snowing) and
`at the same time of day, as well as other limitations for other
`environmental conditions such as traffic patterns. Note, if this parameter
`is NIL, then (a) is assumed.
`
`Please amend the paragraph beginning on page 161, line 9 as follows:
`
`This function creates a new list of lo ation hypotheses from the input list,
`"loc_hyp_list", wherein the location hypo eses on the new list are modified versions of
`those on the input list. For each location ypothesis on the input list, one or more
`corresponding location hypotheses will be n the output list. Such corresponding output
`location hypotheses will differ from their ass ciated input location hypothesis by one or
`more of the following: (a) the "image_area" eld (see Figs. 9A and 9B) may be
`assigned an area indicative of where the targ t MS is estimated to be, (b) if
`"image_area" is assigned, then the "confidenc "field will be the confidence that the
`target MS is located in the area for "image_are ", (c) if there are not sufficient "nearby"
`
`-4-
`
`Apple, Inc. Exhibit 1021 Page 4
`
`

`
`,
`
`•
`
`~plication No. 09/194,367
`,,..~J
`L£ocument: "AMENDMENT AFTER ALLOWAN§!j
`
`in the location signature data base to entirely rely on
`verified location signature cluste
`verified location signature clusters, then two
`a computed confidence using su
`location hypotheses (having reduc d confidences) will be returned, one having a
`reduced computed confidence (for 'image_area") using the verified clusters in the
`Location Signature DB, and one bei g substantially the same as the associated input
`location hypothesis except that the c nfidence (for the field "area_est") is reduced to
`reflect the confidence in its paired loc tion hypothesis having a computed confidence for
`"image_area". Note also, in some cas s, the location hypotheses on the input list, may
`have no change to its confidence or the area to which the confidence applies. Note that
`the steps herein are also provided in flo chart form in Figs. 25a and 25b.
`
`Please amend the paragraph beginning on page 162, line 10 as follows:
`
`else I* the location hypothesis n (and will) be modified; in particular, an
`"image_area" may be assi ned, the "confidence" changed to reflect a
`confidence in the target MS eing in the "image_area". Additionally, in
`some cases, more than one 1~cation hypothesis may be generated from
`"loc_hyp[i]". See the com men~ son FIGS. 9A and 98 and the comments for
`for a description of the terms here. *I
`"get_adjusted_loc_hyp_list_fo
`
`-5-
`
`Apple, Inc. Exhibit 1021 Page 5
`
`

`
`•
`
`•
`
`Application No. 09/194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`REMARKS/ARGUMENTS
`
`Attached hereto is a marked up version of the changes made to the specification and
`
`claims by the current amendment. The attached page is captioned "Version With Markin~:s to
`
`Show Chan~:es Made."
`
`It is believed that no fees are due with the present transmittal. However, in the event that
`
`such fees are due, Applicants request a telephone call to the Applicant listed hereinbelow.
`
`Respectfully submitted,
`
`P, y
`o. 46,
`Registratio
`1801 Belvedere Street
`Golden, Colorado 80401
`(303) 863-2975
`
`-6-
`
`Apple, Inc. Exhibit 1021 Page 6
`
`

`
`•
`
`•
`
`Application No. 091194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`VERSION WITH MARKINGS TO SHOW CHANGES MADE
`
`In the Specification:
`
`The paragraph beginning on page 22, line 14 has been amended as follows:
`
`Figs. 9A and 98 [Fig. 9 is a] are high level data structure diagram§ describing the
`fields of a location hypothesis object generated by the first order models 1224 of the
`location center.
`
`The paragraph beginning on page 79, line 266 has been amended as follows:
`
`Input:
`
`hypothesis: MS location hypothesis;
`measured_loc_sig_bag: A collection of measured location signatures ("lac
`sigs" for short) obtained from the MS (the data structure here is an
`aggregation such as an array or list). Note, it is assumed that there is at
`most one lac sig here per Base Station in this collection. Additionally,
`note that the input data structure here may be a location signature
`cluster such as the "loc_sig_cluster'' field of a location hypothesis (cf.
`Fig§. 9A and 9B). Note that variations in input data structures may be
`accepted here by utilization of flag or tag bits as one skilled in the art will
`appreciate;
`search_ criteria: The criteria for searching the verified location signature data
`base for various categories of loc sigs. The only limitation on the types of
`categories that may be provided here is that, to be useful, each category
`should have meaningful number of Joe sigs in the location signature data
`base. The following categories included here are illustrative, but others
`are contemplated:
`(a) "USE ALL LOC SIGS IN DB" (the default),
`(b) "USE ONLY REPEATABLE LOC SIGS",
`(c) "USE ONLY LOC SIGS WITH SIMILAR TIME OF DAY".
`Further categories of loc sigs close to the MS estimate of "hypothesis"
`contemplated are: allloc sigs for the same season and same time of
`day, allloc sigs during a specific weather condition (e.g., snowing) and
`at the same time of day, as well as other limitations for other
`environmental conditions such as traffic patterns. Note, if this parameter
`is NIL, then (a) is assumed.
`
`The paragraph beginning on page 85, line 5 has been amended as follows:
`This function creates a new list of location hypotheses from the input list,
`"loc_hyp_list", wherein the location hypotheses on the new list are modified versions of
`
`-7-
`
`Apple, Inc. Exhibit 1021 Page 7
`
`

`
`•
`
`•
`
`Application No. 091194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`those on the input list. For each location hypothesis on the input list, one or more
`corresponding location hypotheses will be on the output list. Such corresponding output
`location hypotheses will differ from their associated input location hypothesis by one or
`more of the following: (a) the "image_area" field (see Fig§. 9A and 98) may be
`assigned an area indicative of where the target MS is estimated to be, (b) if
`"image_area" is assigned, then the "confidence" field will be the confidence that the
`target MS is located in the area for "image_area", (c) if there are not sufficient "nearby"
`verified location signature clusters in the location signature data base 1320 to entirely
`rely on a computed confidence using such verified location signature clusters, then two
`location hypotheses (having reduced confidences) will be returned, one having a
`reduced computed confidence (for "image_area") using the verified clusters in the
`Location Signature data base, and one being substantially the same as the associated
`input location hypothesis except that the confidence (for the field "area_est") is reduced
`to reflect the confidence in its paired location hypothesis having a computed confidence
`for "image_area". Note also, in some cases, the location hypotheses on the input list,
`may have no change to its confidence or the area to which the confidence applies.
`
`The paragraph beginning on page 89, line 18 has been amended as follows:
`
`(35.5) A location extrapolator module 1432 for use in updating previous location estimates
`for a target MS when a more recent location hypothesis is provided to the location
`hypothesis analyzer 1332. That is, assume that the control module 1400 receives a
`new location hypothesis for a target MS for which there are also one or more previous
`location hypotheses that either have been recently processed (i.e., they reside in the
`MS status repository 1338, as shown best in Fig. 6), or are currently being processed
`(i.e., they reside in the run-time location hypothesis storage area 1410). Accordingly, if
`the active_timestamp (see Fig§. 9A and 98 regarding location hypothesis data fields)
`of the newly received location hypothesis is sufficiently more recent than the
`active_timestamp of one of these previous location hypotheses, then an extrapolation
`may be performed by the location extrapolator module 1432 on such previous location
`hypotheses so that all target MS location hypotheses being concurrently analyzed are
`presumed to include target MS location estimates for substantially the same point in
`time. Thus, initial location estimates generated by the FOMs using different wireless
`signal measurements, from different signal transmission time intervals, may have their
`corresponding dependent location hypotheses utilized simultaneously for determining
`a most likely target MS location estimate. Note that this module may also be daemon
`or expert system rule base.
`
`The paragraph beginning on page 143, line 13 has been amended as follows:
`
`Input:
`
`hypothesis: MS location hypothesis;
`measured_loc_sig_bag: A collection of measured location signatures ("loc
`
`-8-
`
`Apple, Inc. Exhibit 1021 Page 8
`
`

`
`•
`
`Application No. 091194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`•
`
`·./
`
`sigs" for short) obtained from the MS (the data structure here is an
`aggregation such as an array or list). Note, it is assumed that there is at
`most one loc sig here per Base Station in this collection. Additionally,
`note that the input data structure here may be a location signature
`cluster such as the "loc_sig_cluster" field of a location hypothesis (cf.
`Fig§. 9A and 98). Note that variations in input data structures may be
`accepted here by utilization of flag or tag bits as one skilled in the art will
`appreciate;
`search_ criteria: The criteria for searching the verified location signature
`data base for various categories of loc sigs. The only limitation on the
`types of categories that may be provided here is that, to be useful, each
`category should have meaningful number of loc sigs in the location
`signature data base. The following categories included here are
`illustrative, but others are contemplated:
`(a) "USE ALL LOC SIGS IN DB" (the default),
`(b) "USE ONLY REPEATABLE LOC SIGS",
`(c) "USE ONLY LOC SIGS WITH SIMILAR TIME OF DAY".
`Further categories of loc sigs close to the MS estimate of "hypothesis"
`contemplated are: allloc sigs for the same season and same time of
`day, allloc sigs during a specific weather condition (e.g., snowing) and
`at the same time of day, as well as other limitations for other
`environmental conditions such as traffic patterns. Note, if this parameter
`is NIL, then (a) is assumed.
`
`The paragraph beginning on page 161, line 8 has been amended as follows:
`
`This function creates a new list of location hypotheses from the input list,
`"loc_hyp_list", wherein the location hypotheses on the new list are modified versions of
`those on the input list. For each location hypothesis on the input list, one or more
`corresponding location hypotheses will be on the output list. Such corresponding output
`location hypotheses will differ from their associated input location hypothesis by one or
`more of the following: (a) the "image_area" field (see Fig§. 9A and 9B) may be
`assigned an area indicative of where the target MS is estimated to be, (b) if
`"image_area" is assigned, then the "confidence" field will be the confidence that the
`target MS is located in the area for "image_area", (c) if there are not sufficient "nearby"
`verified location signature clusters in the location signature data base to entirely rely on
`a computed confidence using such verified location signature clusters, then two
`location hypotheses (having reduced confidences) will be returned, one having a
`reduced computed confidence (for "image_area") using the verified clusters in the
`Location Signature DB, and one being substantially the same as the associated input
`location hypothesis except that the confidence (for the field "area_est") is reduced to
`
`-9-
`
`Apple, Inc. Exhibit 1021 Page 9
`
`

`
`r
`
`•
`
`. '
`
`Application No. 09/194,367
`Document: "AMENDMENT AFTER ALLOWANCE"
`
`reflect the confidence in its paired location hypothesis having a computed confidence for
`"image_area". Note also, in some cases, the location hypotheses on the input list, may
`have no change to its confidence or the area to which the confidence applies. Note that
`the steps herein are also provided in flowchart form in Figs. 25a and 25b.
`
`The paragraph beginning on page 162, line 10 has been amended as follows:
`
`else I* the location hypothesis can {and will) be modified; in particular, an
`"image_area" may be assigned, the "confidence" changed to reflect a
`confidence in the target MS being in the "image_area". Additionally, in
`some cases, more than one location hypothesis may be generated from
`"loc_hyp[i)". See the comments on FIGS. 9A and 98 and the comments for
`"get_adjusted_loc_hyp_list_for" for a description of the terms here. *I
`
`-10-
`
`Apple, Inc. Exhibit 1021 Page 10

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