throbber
I hereby certify that this paper (along with any paper referred to as -'- ing attached or enclosed) is being deposited with the
`U.S.-Postal Service as Express Mail, Airbill No. EV 470 629 139
`'1
`, on the date shown below in an envelope addressed to:
`
`(PATENT)
`
`Docket No.: 562492001600
`
`Application No.: 10/278,342
`
`,
`
`Confirmation No.: 9463
`
`Filed: October 23, 2002
`
`Art Unit: 2616
`
`For: PACKET DATA QUEUING AND
`PROCESSING
`
`Examiner: P. H. Tran
`
`AMENDMENT IN RESPONSE TO NON-FINAL OFFICE ACTION
`
`MS Amendment
`
`Commissioner for Patents
`
`PO, Box 1450
`
`.
`
`Alexandria, VA 22313-1450
`
`Dear Sir:
`
`INTRODUCTORY COMMENTS
`
`This is in response to the non-final Office Action dated February 8, 2007 (Paper No.
`
`20070130), for which a response was due on May 8, 2007. Accordingly, this response is timely
`filed. Reconsideration and allowance of the pending claims, as amended, in light of the remarks
`
`presented herein are respectfully requested.
`
`' Amendments to the Abstract begin on page 3 of this paper.
`
`Amendments to the Claims are reflected in the listing of claims which begins on page 4
`
`of this paper.
`
`I
`
`Amendments to the Drawings begin on page 9 of this paper and include an attached
`
`replacement sheet.
`
`sf-2273153
`
`ERICSSON EXHIBIT 1008
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`2
`
`Docket No.: 562492001600
`
`Remarks/Arguments begin on page 10 of this paper.
`
`sf—2273153
`
`

`
`'
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`3
`
`Docket No.: 562492001600
`.
`
`AMENDMENTS TO THE ABSTRACT
`
`A method of processing queued data packets in a packet data communication system i_s_
`provided. The method includes allocating a tier of service for substantially each of a plurality of
`
`individualpacket data queues and determining a total number of data packets that can use an
`
`available communication resource. A proportion of a total number of data packets is allocated to a
`
`number of the tiers of service to allow individual packet data queues on a number of tiers to share a
`
`communication resource. A communication resource is provided to queued packet data users on a
`
`tier-by-tier basis, such that the communication resource is made available to substantially all tiers.
`
`
`
`sf-2273153
`
`

`
`-
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`4
`
`i
`
`0
`
`Docket No.: 562492001600
`
`AMENDMENTS TO THE CLAIMS
`
`This listing of claims will replace all prior versions, and listings of claims in the application:
`
`Listing of Claims:
`
`Claim 1 (Currently amended) A method of processing queued data packets in a packet data
`
`communication system, the method comprising:
`
`allocating a tier of service for‘ substantially each of a plurality of individual packet data
`
`queues; wherein allocating a tier of service comprises:
`
`determining a total number of data packets that can use an available communication-
`
`resource;
`
`allocating a proportion of said total number of data packets to a number of the tiers of
`
`service to allow individual packet data queues on a number of tiers to share a communication
`
`resource; and
`
`I
`
`providing said communication resource to queued packet data users on a tier-by-tier
`
`basis, such that said communication resource is made available to a substantial number of tiers.
`
`Claim 2 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, wherein said step-of allocating a proportion of a total
`
`number of data packets [[is]] further comprises:
`
`providing a commitment that a proportion of an entire communication system bandwidth
`
`will be allocated to users operating on a" particular tier. ’_
`
`Claim 3 (Currentlyamended) The method of processing queued data packets in a packet data
`
`communication system accordingto Claim 1, the method further comprising: eharaeterised-by-the
`
`allocating different weights to each tier of service to provide a differential level of
`
`service in the allocation of said communication resource between said tiers.
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007 ’
`
`5
`
`Docket No.: 562492001600
`
`Claim 4 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, wherein said step-of allocating a proportion of atotal
`number of data packets is performed by using rate allocating service disciplines.
`
`Claim 5 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, the method further comprising: eharaeterised-by-t-he
`
`step-ef—:
`
`providing a packet data user with an identification code to assist in the tier allocation
`
`step, wherein, the identification code provides an identifier for the user and/or an
`
`indication of a number of data packets that the user wishes to transfer.
`
`Claim 6 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 5, the method further comprising: ehaiaeterised-by-the
`
`steps-of-2
`
`determining, for substantially each respective tier, that a number of data packets are
`
`requested to be processed; and
`
`allocating a proportion of said communication resource to substantially each tier in
`
`response to said determination.
`
`Claim 7 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, the method further comprising: eharaeterised-by-tlae
`
`placing a user at a tail of an allocated queue, depending on the user's tier of service when
`
`said user provides data packets for queuing.
`
`Claim 8 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, the method further compfising:i
`
`allocating data packets to a user at a head of the tier queue;
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`6
`
`Docket No.: 562492001600
`
`moving said user at said head of the tier queue to the tail of the queue when the user's
`
`data packets have been sent; and
`
`moving other users in the queue closer to the head of the queue.
`
`Claim 9 (Currently amended) The method of processing queued data packets in a packet data
`
`communication system according to Claim 8, the method further comprising: eharaeter-ised-by-the
`
`step-of-:
`
`repeating the steps method of Claim 8 until the total number of packets allocated to the
`
`tier is transferred.
`
`Claim 10 (Currently amended)
`
`.
`
`The method of processing queued data packets in a packet data
`
`communication system according to Claim 1, the method further comprising: eharaeter-ised-by-the
`
`determining a tier of service for each user when a packet data session for each user
`
`CO1'l'lI'I1€l'1CCS .
`
`Claim 11 (Original) A packet data scheduler queuing data packets in a packet data communication
`
`system, the packet data scheduler comprising:
`
`means for allocating a tier of service for substantially each of a plurality of individual
`
`packet data queues;
`
`means for determining a total number of data packets that can use an available
`
`‘ communication resource;
`
`means, operably coupled to the aforementioned means, for allocating a proportion of
`
`said total number of data packets to a number of the tiers of service to allow individual packet data
`
`queues on a number of tiers to share a communication resource;
`
`wherein the packet data scheduler is characterised by:
`
`scheduling means to provide said communication resource to queued packet data users
`
`on a tier-by-tier basis, such that said resource is made available to substantially all tiers.
`
`sf-2273153
`
`

`
`1
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`7
`
`.
`
`Docket No.: 562492001600
`
`Claim 12 (Original) The packet data scheduler according to Claim 11, wherein said means for
`
`allocating a proportion of a total number of data packets provides a commitment that a proportion of
`
`an entire communication system bandwidth will be allocated to users operating on a particular tier.
`
`Claim 13 (Original) The packet data scheduler according to Claim _11, wherein said means for
`
`allocating a proportion of a total number of data packets further allocates different weights to each
`
`tier of service to provide a differential level of service in the allocation of said communication
`
`resource between said tiers.
`
`Claim 14 (Original) The packet data‘ scheduler according to Claim 11, wherein said means for
`
`allocating a proportion of a total number of data packets allocates data packets using rate allocating
`
`service disciplines.
`
`Claim 15 (Original) The packet data scheduler according to Claim 11, wherein said means for
`allocating a proportion of a total number of data packets provides a packet data user with an ‘
`identification code to assist in the tier allocation step, wherein, for example, the identification code
`provides an identifier for the user and/or an indication of a number of data packets that the user
`
`wishes to transfer.
`
`Claim 16 (Original) The packet data scheduler according to Claim 15, wherein said.means for
`
`allocating a proportion of a total number of data packets determines, for substantially each
`
`respective tier, that a (number of data packets are requested to be processed; and allocates a
`
`proportion of said communication resource to substantially each tier in response to said
`
`determination.
`
`Claim 17 (Original) The packet data scheduler according to Claim 11, wherein said scheduling
`
`means places a user at a tail of the allocated queue, depending on the user's tier of service when said
`
`user provides data packets for queuing.
`
`Claim 18 (Original) The packet data scheduler according to Claim 11, wherein said scheduling _
`means:
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`8
`
`'
`
`Docket No.: 562492001600
`
`allocates data packets to a user at a head of the tier queue;
`
`moves said user at said head of the tier queue to the tail of the queue when the user's data
`
`packets have been sent; and
`
`moves other user's in the queue closer to the head of the queue.
`
`Claim 19 (Original) The packet data scheduler according to Claim 18, wherein said scheduling
`
`means repeats the operation of moving data packets and allocating data packets to a head of a tier
`
`queue until the total number of packets allocated to the tier has been transferred.
`
`Claim 20 (Original) A communication unit comprising the packet data scheduler of Claim 11.
`
`Claim 21 (Original) The communication unit according to Claim 20, wherein said communication
`
`unit operates as a gateway to and/or from two packet data networks.
`
`Claim 22 (Original) The communication unit of Claim 20, wherein said communication unit is a
`
`radio network controller for operation in a third Generation Partnership Project (3GPP) specification
`
`for wide-band code-division multiple access (WCDMA) communication system.
`
`Claim 23 (Original) A packet data communication system comprising the packet data scheduler of
`
`Claim 11.
`
`Claim 24 (Currently amended)
`
`A packet data communication system adapted to facilitate the
`
`method ef—&n-y-of Claim 1.
`
`Claim 25 (Currently amended)
`
`A computer-readable medium comprising instructions for
`
`performing the method
`
`
`
`apm%%e of claim 1.
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`9
`
`Docket No.: 562492001600
`
`AMENDMENTS TO THE DRAWINGS
`
`The attached sheets of drawings include changes to Figure 1 to label as “Frior Art”, and
`
`changes to Figure 3 to remove reference characters.
`
`Submitted herewith are two sheets of replacement drawing, Figure 1 and Figure 3, for
`
`filing in the above-identified Patent application.
`
`Attachments: Replacement sheet (FIG. 1)
`
`Replacement sheet (FIG. 3)
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`10
`
`'
`
`Docket No.: 562492001600
`
`REMARKS
`
`Claims 1-25 were pending. By virtue of this response, claims 1-10 and 24-25 are
`
`amended. No new matter is added. Accordingly, claims 1-25 are currently under consideration.
`
`Amendment or cancellation of subject matter is not to be construed as an abandonment of any
`
`subject matter.
`
`Drawings
`
`The Examiner indicated FIG. 1 should be designated by a legend such as “Prior Art”
`
`because allegedly only that which is old is illustrated.
`
`_In response, FIG. 1 has been amended to include a “Prior Art” label.
`
`The drawings are objected to under 37 CFR 1.83(a) for allegedly not showing every
`
`feature ofthe invention specified in the claims. The Examiner alleges “packet data scheduler” is a
`
`feature not shown in the drawings. I
`
`In response, Applicant respectfully submits that “packet data scheduler” is shown in the
`
`drawings. Embodiments of “packet data schedulers” are described, for example, in paragraphs
`
`[0075] and [0085], which are shown in FIG. 2, for example.
`
`The drawings are also objected to under 37 CFR 1.84(p) because they allegedly include
`
`reference characters not mentioned in the description.
`
`In response, FIG. 3 is amended to remove reference characters 320, 330, 335, 380, and
`
`385.
`
`Specification
`
`The Examiner indicated that the abstractis generally limited to a single paragraph and
`
`within the range of 50 to 150 words.
`
`sf—2273153
`
`

`
`.
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`, 11
`
`Docket No.:‘ 562492001600
`
`In response, the abstract is appropriately amended.
`
`Claim Rejection Under 35 USC § 101
`
`Claim 25 is rejected under 35 U.S.C. § 101 because the claimed invention is allegedly
`
`directed to non—statutory subject matter.
`
`In response, claim 25 is amended. Applicant.respectfi.1lly submits amended, claim 25 is
`directed to statutory subject matter. Accordingly, Applicant respectfully requests reconsideration
`
`and allowance of claim 25.
`
`Allowable "Subject Matter
`
`Applicant thanks the Examiner for indicating claimsel-24 are allowed. Claims 1-10, and
`
`24 are amended for editorial corrections. No new matter is added. Applicant respectfully submits
`
`claims 1-25 are allowable.
`
`sf-2273153
`
`

`
`Application No.: 10/278,342
`Response to Office Action of February 8, 2007
`
`12
`
`Docket No.: 562492001600
`
`CONCLUSION
`
`In view of the above, each of the presently pending claims in this application is believed
`
`to be in immediate condition for allowance. Accordingly, the Examiner is _respectfully requested to
`withdraw the outstanding rejection of the claims and to pass this application to issue. If it is
`
`determined that a telephone conference would expedite the prosecution of this application, the
`
`Examiner is invited to telephone the undersigned at the number given below.
`
`In the event the U.S. Patent and Trademark office determines that an extension and/or
`
`other relief is required, applicant petitions for any required relief including extensions of time and
`
`authorizes the Commissioner to charge the cost of such petitions and/or other fees due in connection
`
`with the filing of this document to Deposit Account No. 03-1952 referencing docket no.
`
`562492001600. However, the Commissioner is not authorized to charge the cost of the issue fee to
`
`the Deposit Account.
`
`I
`
`Dated: May 8, 2007
`
`Respectfiilly submitted,
`
`By
`
`Denise H. Wong
`Registration No.: 59,622
`MORRISON & FQERSTER LLP
`425 Market Street
`
`San Francisco, California 94105-2482
`(415) 268-6221
`
`sf-2273153
`
`

`
`Appl. No.: 10/278,342
`T Docket No.: 562492001600
`Inventor: Timothy J. SPEIGHT
`Title: PACKET DATA QUEUING AND
`PROCESSING
`
`1/3
`
`REPLACEMENT SHEET
`
`
`
`PRIOR ART
`
`

`
`Appl No.: 10/278,342
`Docket No.: 562492001600
`Inventor: Timothy J. SPEIGHT
`Title: PACKET DATA QUEUING AND
`PROCESSING
`
`3/3
`
`REPLACEMENT SHEET
`
`FIG.3
`
`300
`
`/

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