throbber
PATENT
`Docket No.: 101459
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`In re Patent Application of:
`CustomerNo.:
`23696
`Nitin GUPTA
`
`Application No.: 13/052,516
`
`Art Unit:
`
`2116
`
`
`
`Filed:|March 21, 2011 Conf. No.: 6620
`
`
`
`For: DIRECT SCATTER LOADING OF||Examiner: Abdelmoniem I. ELAMIN
`
`
`
`
`EXECUTABLE SOFTWARE
`IMAGE FROM A PRIMARY
`PROCESSOR TO ONE OR MORE
`SECONDARY PROCESSORIN A
`MULTI-PROCESSOR SYSTEM
`
`
`Mail Stop Amendment
`Commissionerfor Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`DearSir:
`
`REPLY UNDER37 C.F.R. 1.111
`
`In response to the Office Action dated July 19, 2013, reconsideration and further
`
`examination of the above-identified application are respectfully requested based on the
`
`following:
`
`Amendments to the Claimsare reflected in the listing of claims, which begin on page 2
`
`of this paper.
`
`Remarks begin on page8 ofthis paper.
`
`15929473v.1
`
`INTEL 1 005
`
`INTEL 1005
`
`

`

`Docket No. 101459
`
`Amendments to the Claims:
`
`Thislisting of claims will replace all prior versions, andlistings, of claimsin the
`application:
`
`Listing of Claims:
`
`1.
`
`(Currently Amended) A multi-processor system comprising:
`
`a secondary processor comprising:
`
`system memory and a hardware buffer for receiving an image header and at least
`
`one data segment ateteast a-pertien of an executable software image, the image header
`
`and each data segment being received separately, and
`
`the-secondary-precesser-comprising a scatter loader controller ferteading
`
`configured:
`
`to load the image header; and
`
`to scatter load each received data segment executable-seftwareimage,
`
`based at least in part on the loaded image header, directly from the hardware
`
`buffer to the system memory;
`
`a primary processor coupled with a memory, the memory storing the executable software
`
`image for the secondary processor; and
`
`an interface communicatively coupling the primary processor and the secondary
`
`processor via which the executable software image is received by the secondary processor.
`
`2.
`
`(Original) The multi-processor system of claim 1 in whichthe scatter loader
`
`controller is configured to load the executable software image directly from the hardware buffer
`
`to the system memory of the secondary processor without copying data between system memory
`
`locations on the secondary processor.
`
`3.
`
`(Original) The multi-processor system of claim 1 in which raw image data of the
`
`executable software image is received by the secondary processorvia the interface.
`
`4,
`
`(Cancelled)
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`3
`
`(Currently Amended) The multi-processor system of claim [[4]] 1.in which the
`
`secondary processor is configured to-recetvethe+mageheaderand process the image headerto
`
`determineat least one location within the system memory to store the at least one data segment.
`
`6.
`
`(Original) The multi-processor system of claim 5 in which the secondary
`
`processoris configured to determine, based on the received image header, the at least one
`
`location within the system memory to store the at least one data segment before receiving the at
`
`least one data segment.
`
`Vs
`
`(Original) The multi-processor system of claim 1, in which the secondary
`
`processor further comprises a non-volatile memory storing a boot loaderthat initiates transfer of
`
`the executable software image for the secondary processor.
`
`8.
`
`(Original) The multi-processor system of claim 1 in which the primary and
`
`secondary processorsare located on different chips.
`
`9.
`
`(Original) The multi-processor system of claim 1 in whichthe portion of the
`
`executable software image is loaded into the system memory of the secondary processor without
`
`an entire executable software image being stored in the hardware buffer.
`
`10.
`
`(Original) The multi-processor system of claim 1 integrated into at least one of a
`
`mobile phone, a set top box, a music player, a video player, an entertainmentunit, a navigation
`
`device, a computer, a hand-held personal communication systems (PCS) unit, a portable data
`
`unit, and a fixed location data unit.
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`11.
`
`(Currently Amended) A method comprising:
`
`receiving at a secondary processor, from a primary processor via an inter-chip
`
`communication bus, an image header for an executable software image for the secondary
`
`processorthat is stored in memory coupled to the primary processor, the executable software
`
`image comprising the image headerandat least one data segment, the image header and each
`
`data segment being received separately;
`
`processing, by the secondary processor, the image header to determineat least one
`
`location within system memory to which the secondary processoris coupled to store the-atteast
`
`ene cachdata segment;
`
`receiving at the secondary processor, from the primary processorvia the inter-chip
`
`communication bus, the-atteastene cachdata segment; and
`
`scatterloading, by the secondary processor, the-atleasterne eachdata segmentdirectly to
`
`the determinedat least one location within the system memory, and each data segment being
`
`scatter loaded based at least in part on the processed image header.
`
`12.
`
`(Original) The method of claim 11 further comprising booting the secondary
`
`processorusing the executable software image.
`
`13.
`
`(Original) The method of claim 11 further comprising loading the executable
`
`software imagedirectly from a hardware buffer to the system memory of the secondary
`
`processor without copying data between system memory locations.
`
`14.
`
`(Original) The method of claim 11 in which the processing occurs prior to the
`
`loading.
`
`15.|(Original) The method of claim 11 in which the primary and secondary processors
`
`are located on different chips.
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`16.
`
`(Original) The method of claim 11 further comprising performing the receiving,
`
`processing, and loading,in at least one of a mobile phone, a set top box, a music player, a video
`
`player, an entertainment unit, a navigation device, a computer, a hand-held personal
`
`communication systems (PCS) unit, a portable data unit, and a fixed location data unit.
`
`17.
`
`(Currently Amended) An apparatus comprising:
`
`meansfor receiving at a secondary processor, from a primary processor via an inter-chip
`
`communication bus, an image header for an executable software image for the secondary
`
`processorthat is stored in memory coupled to the primary processor, the executable software
`
`image comprising the image headerandat least one data segment, the image header and each
`
`data segment being received separately;
`
`meansfor processing, by the secondary processor, the image header to determineatleast
`
`one location within system memory to which the secondary processor is coupled to store the-at
`
`leastene eachdata segment;
`
`meansfor receiving at the secondary processor, from the primary processorvia the inter-
`
`chip communication bus, the-atteastene eachdata segment; and
`
`meansfor scatter loading, by the secondary processor, the-atteastene eachdata segment
`
`directly to the determinedat least one location within the system memory, and each data segment
`
`being scatter loaded based at least in part on the processed image header.
`
`18.
`
`(Original) The apparatus of claim 17 integrated into at least one of a mobile
`
`phone,a set top box, a music player, a video player, an entertainmentunit, a navigation device, a
`
`computer, a hand-held personal communication systems (PCS) unit, a portable data unit, and a
`
`fixed location data unit.
`
`19.
`
`(Currently Amended) A multi-processor system comprising:
`
`a primary processor coupled with a first non-volatile memory,the first non-volatile
`
`memory coupled to the primary processorandstoring a file system for the primary processor and
`
`executable images for the primary processor and secondary processor;
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`a secondary processor coupled with a second non-volatile memory, the second non-
`
`volatile memory coupled to the secondary processor and storing configuration parameters and
`
`file system for the secondary processor; and
`
`an interface communicatively coupling the primary processor and the secondary
`
`processor via which an executable software image is received by the secondary processor, the
`
`executable software image comprising an image header andat least one data segment, the image
`
`header and each data segment being received separately, and the image header being used to
`
`scatter load each received data segment directly to a system memory of the secondary processor.
`
`20)
`
`(Original) The multi-processor system of claim 19 integrated into at least one of a
`
`mobile phone, a set top box, a music player, a video player, an entertainment unit, a navigation
`
`device, a computer, a hand-held personal communication systems (PCS) unit, a portable data
`
`unit, and a fixed location data unit.
`
`DM
`
`(Currently Amended) A multi-processor system comprising:
`
`a primary processor coupled with a first non-volatile memory,the first non-volatile
`
`memory coupled to the primary processor and storing executable imagesandfile systems for the
`
`primary and secondary processors;
`
`a secondary processornot directly coupled to the first non-volatile memory; and
`
`an interface communicatively coupling the primary processor and the secondary
`
`processor via which an executable software image is received by the secondary processor,the
`
`executable software image comprising an image header andat least one data segment, the image
`
`header and each data segment being received separately, and the image header being used to
`
`scatter load each received data segmentdirectly to a system memory of the secondary processor.
`
`22.
`
`(Original) The multi-processor system of claim 21 integrated into at least one of a
`
`mobile phone, a set top box, a music player, a video player, an entertainment unit, a navigation
`
`device, a computer, a hand-held personal communication systems (PCS) unit, a portable data
`
`unit, and a fixed location data unit.
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`23.
`
`(Currently Amended) A method comprising:
`
`sending, from a memory coupled to a primary processor, an executable software image
`
`for a secondary processor, via an interface communicatively coupling the primary processor and
`
`secondary processor, the executable software image comprising an image header andat least one
`
`data segment;
`
`receiving, at the secondary processor, the image header and each data segmentof the
`
`executable software image, the image header and each data segment being received separately,
`
`and the image header being used to scatter load each received data segmentdirectly to a system
`
`memory of the secondary processor; and
`
`executing, at the secondary processor, the executable software image.
`
`24.
`
`(Original) The method of claim 23 further comprising performing the sending,
`
`receiving, and executing, in at least one of a mobile phone, a set top box, a music player, a video
`
`player, an entertainment unit, a navigation device, a computer, a hand-held personal
`
`communication systems (PCS) unit, a portable data unit, and a fixed location data unit.
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`REMARKS
`
`In response to the Office Action mailed July 19, 2013, the Office Action’s claim
`
`rejections have been considered. Claims 1-24 are pending. Claims 1, 5, 11, 17, 19, 21 and 23 are
`
`currently amended. Claim 4 has been cancelled without prejudice or disclaimer of the subject
`
`matter. No new matter is added. Support for the amendments may be foundat least in, for
`
`example, paragraph 52 of the published application (US 2012/0072710). Applicants respectfully
`
`traverseall rejections ofall pending claims and earnestly solicit allowance of these claims.
`
`Claim Rejections - 35 USC § 102
`
`Claims 1-24 are rejected under 35 U.S.C. § 102(b) as allegedly being unpatentable over
`
`Svensson (International Publication No. 2006/077068). Claim 4 has been cancelled, thus
`
`rendering the rejection of claim 4 moot.
`
`As amended, claim 1 incorporates elements similar to those recited in original claim 4.
`
`Specifically, claim 1 recites system memory and a hardware buffer for receiving an image header
`
`and at least one data segment of an executable software image, the image header and each data
`
`segment being received separately. Claim 1 further recites a scatter loader controller configured
`
`to load the image header andto scatter load each received data segment, based at least in part on
`
`the loaded image header, directly from the hardware buffer to the system memory.
`
`For claim 4, page 3 of the Office Action states that FIG. 3 of Svensson discloses that the
`
`executable software comprises an image headerandat least one data segment. Applicants
`
`provide the following remarks.
`
`FIG. 3 of Svensson arguably discloses that the software includes a header and a data
`
`segment. Asdisclosed in col. 8 lines 10-19 of Svensson, each code and/or data to be transferred
`
`includes a header.
`
`In contrast to Svensson, claim | recites that the image header and each data segmentare
`
`received separately. Applicants submit that separately receiving the image header and each data
`
`segment, as recited in claim 1, is patentably distinguishable from receiving the data and the
`
`associated header, as disclosed in Svensson. Therefore, because Svensson expressly discloses
`-8-
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`that each code and/or data to be transferred includes a headerandfails to disclose that the image
`
`header and each data segmentare received separately, applicants submit that Svensson cannot
`
`teach or suggest “the image header and each data segment are received separately,” as recited in
`
`claim 1.
`
`Moreover,the cited portions of Svensson disclose that several blocks(e.g., data blocks
`
`with headers) are concatenated in the intermediate storage area (ISA). Specifically, the data
`
`blocks are concatenated in the intermediate storage area prior to being transferred to the memory
`
`(see Svensson, step 220). In contrast, claim | recites that each data segmentis scatter loaded
`
`basedat least in part on the loaded image header. Thatis, the individual data segments of claim
`
`1 are not concatenated with the headerfiles. Rather, the image headerfile is loaded into memory
`
`to scatter load each data segment directly from the hardware buffer to the system memory.
`
`Applicants submit that loading each data segmentdirectly from the hardware buffer to
`
`the system memory,as recited in claim 1, is patentably distinguishable from concatenating the
`
`data blocks and headers in the intermediate storage area and then transferring the concatenated
`
`data to the memory,as recited in Svensson. Thus, because Svensson fails to teach or suggest
`
`scatter loading each data segment directly from the hardware buffer to the system memory,
`
`applicants submit that Svensson cannotteach or suggest “a scatter loader controller configured to
`
`load the image headerandto scatter load each received data segment directly from the hardware
`
`buffer to the system memory,” as recited in claim 1.
`
`Applicants have demonstrated above that Svensson fails to teach or suggest various
`
`elements recited in claim 1. Therefore, claim | is believed to be allowable over the cited
`
`reference. Furthermore, the independent claims 11, 17, 19, 21, and 23 also recite separately
`
`receiving the image header and each data segmentand scatter loading each received data
`
`segmentdirectly from the hardware buffer to the system memory. Therefore, the other rejected
`
`independentclaimsare also believed to be allowable. Finally, dependent claims2, 3, 5-10, 12-
`
`16, 18, 20, 22, and 24 are allowable at least by virtue of their dependenceon an allowable base
`
`claim, in addition to reasonsrelated to their ownrecitations.
`
`15929473v.1
`
`

`

`Docket No. 101459
`
`CONCLUSION
`
`The absence ofa reply to a specific rejection, issue, or comment does not signify
`
`agreement with or concession ofthat rejection, issue, or comment. In addition, because the
`
`arguments above may not be exhaustive, there may be other reasons for patentability of any or
`
`all claims that have not been expressed. Finally, nothing in this paper should be construed as
`
`evidencing intent to concede any issue with regard to any claim, except as specifically stated in
`
`this paper, and the amendmentor cancellation of any claim does not necessarily signify
`
`concession of unpatentability of the claim prior to its amendmentor cancellation.
`
`In light of the amendments and remarks, applicants submit that the claimsare in
`
`condition for allowance and respectfully request a notice to this effect. Should the Examiner
`
`have any questions, please call the undersigned at the phone numberlisted below.
`
`To the extent necessary, a petition for an extension of time under 37 C.F.R. § 1.136 is
`
`submitted. Please charge any shortage in fees due in connection withthefiling of this paper,
`
`including extension of time fees, to Deposit Account 17-0026 and please credit any excess fees
`
`to such deposit account.
`
`Dated: October 17, 2013
`
`Respectfully submitted,
`
`By:
`
`/Peter Kamarchik/
`Peter Kamarchik, Reg. No. 63,529
`Attorney for Applicants
`QUALCOMM INCORPORATED
`5775 Morehouse Drive
`San Diego, CA 92121
`(919) 297-3170
`Email: pnk@qualcomm.com
`
`15929473v.1
`
`-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