Office Action 2: Notice of Allowance (2025-03-17)

CLAIMS:
Amendments to the Claims

1\. (Currently Amended) A servicer satellite configured to perform rendezvous with a client satellite, the servicer satellite comprising:
a body comprising an X axis with a +X direction and a -X direction, a Y axis with a +Y direction and a -Y direction, and a Z axis with a +Z direction and a -Z direction;
a set of thrusters comprising: i) a first thruster coupled to the body, ii) a second thruster coupled to the body, iii) a third thruster coupled to the body, and iv) a fourth thruster coupled to the body;
a controller configured with commands to fire: i) the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and the client satellite and that removes an angular momentum or a rotational velocity of the body, and ii) the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body, the controller further configured with commands to fire the first thruster and the second thruster to follow a rendezvous traiectory that matches orbital parameters of the servicer satellite and the client satellite;
wherein:
the first thruster is coupled to at least one of a first hinge and a first gimble and the second thruster is coupled to at least one of a second hinge and a second gimble to enable the first thruster and the second thruster to position to produce the first thrust vector; and
the third thruster is coupled to at least one of a third hinge and a third gimble and the fourth thruster is coupled to at least one of a fourth hinge and a fourth gimble to enable the third thruster and the fourth thruster to position to produce the second thrust vector.

2\. (Original) The servicer satellite of claim 1, wherein each of the first thruster, the second thruster, the third thruster, and the fourth thruster are electric propulsion thrusters.
3\. (Currently Amended) The servicer satellite of claim 1, wherein:
the controller is further configured with commands to fire: i) the first thruster and the second thruster to accelerate the servicer satellite toward the client satellite, and ii) to fire the third thruster and the fourth thruster to decelerate the servicer satellite with respect to the client satellite.
4\. (Currently Amended) The servicer satellite of claim 1, wherein:
the first thruster is coupled to the first gimble;
the second thruster is coupled to the second gimble;
the third thruster is coupled to the third gimble; and
the fourth thruster is coupled to the fourth gimble.
5\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster and the second thruster are disposed at an aft panel of the body, the aft panel facing in the -Z direction.
6\. (Original) The servicer satellite of claim 5, wherein:
each of the third thruster and the fourth thruster are disposed on a nadir panel of the body, the nadir panel positioned to face opposite to the aft panel.
7\. (Currently Amended) The servicer satellite of claim 13,-wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are gimbled thrusters.
8\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to fire through a center of mass of the servicer satellite.
9\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to avoid firing through a center of mass of the servicer satellite.

10\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured for orientation independent from one another.

11\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to fire simultaneously.

12\. (Original) The servicer satellite of claim 1, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to throttle.

13\. (Currently Amended) A servicer satellite comprising:
a body comprising an X axis with a +X direction and a -X direction, a Y axis with a +Y direction and a -Y direction, and a Z axis with a +Z direction and a -Z direction;
a set of thrusters comprising: i) a first thruster coupled to the body, ii) a second thruster coupled to the body, iii) a third thruster coupled to the body, and iv) a fourth thruster coupled to the body; and
a controller configured with commands to: i) fire the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and the client satellite and that removes an angular momentum or a rotational velocity of the body, ii) fire the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body; iii) fire the first thruster and the second thruster to follow a rendezvous trajectory that matches orbital parameters of the servicer satellite and the client satellite; and iv) fire the first thruster and the second thruster to accelerate the servicer satellite toward the client satellite.

14\. (Currently Amended) A method of performing rendezvous by a servicer satellite, the method comprising:
providing the\[\[a\]\] servicer satellite comprising:a body comprising an X axis with a +X direction and a -X direction, a Y axis with a +Y direction and a -Y direction, and a Z axis with a +Z direction and a -Z direction;
a set of thrusters comprising: i) a first thruster coupled to the body, ii) a second thruster coupled to the body, iii) a third thruster coupled to the body, and iv) a fourth thruster coupled to the body; and
a controller configured with commands to fire the set of thrusters;
wherein:
the controller fires the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and a client satellite and that removes an angular momentum or a rotational velocity of the body; and
the controller fires the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body; and
the controller fires the first thruster and the second thruster to follow a first rendezvous trajectory that matches orbital parameters of the servicer satellite and the client satellite.

15\. (Currently Amended) The method of claim 14, wherein
the controller is further configured with commands to fire the first thruster and the second thruster to accelerate the servicer satellite toward the client satellite.

16\. (Currently Amended) The method of claim 14, wherein:
the first thruster is coupled to a first gimble and the second thruster is coupled to a second gimble to enable the first thruster and the second thruster to produce the first thrust vector; and
the third thruster is coupled to a third gimble and the fourth thruster is coupled to a fourth gimble to enable the third thruster and the fourth thruster to produce the second thrust vector.

17\. (Currently Amended) The method of claim 14, wherein:
each of the first thruster and the second thruster are disposed at an aft panel of the body, the aft panel facing in the -Zdirection; and
each of the third thruster and the fourth thruster are disposed on a nadir panel of the body, the nadir panel positioned to face opposite to the aft panel.

18\. (Currently Amended) The method of claim 14,wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to fire through a center of mass of the servicer satellite.

19\. (Original) The method of claim 14, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to fire simultaneously and are electric propulsion thrusters.

20\. (Currently Amended) The method of claim 14, wherein:
each of the first thruster, the second thruster, the third thruster, and the fourth thruster are configured to avoid firing through a center of mass of the servicer satellite.

OFFICE ACTION:
Reasons for Allowance
Claims 1-20 are allowed.
The following is an examiner’s statement of reasons for allowance:
Regarding Claims 1-6 and 8-12, the prior art of record does not reasonably teach or suggest the combination of features of a servicer satellite configured to perform rendezvous with a client satellite including a controller configured with commands to fire: i) the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and the client satellite and that removes an angular momentum or a rotational velocity of the body, and ii) the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body, the controller further configured with commands to fire the first thruster and the second thruster to follow a rendezvous trajectory that matches orbital parameters of the servicer satellite and the client satellite; wherein: the first thruster is coupled to at least one of a first hinge and a first gimble and the second thruster is coupled to at least one of a second hinge and a second gimble to enable the first thruster and the second thruster to position to produce the first thrust vector; and the third thruster is coupled to at least one of a third hinge and a third gimble and the fourth thruster is coupled to at least one of a fourth hinge and a fourth gimble to enable the third thruster and the fourth thruster to position to produce the second thrust vector
Regarding Claims 7 and 13, the prior art of record does not reasonably teach or suggest the combination of features of a servicer satellite including a set of thrusters comprising: i) a first thruster coupled to the body, ii) a second thruster coupled to the body, iii) a third thruster coupled to the body, and iv) a fourth thruster coupled to the body; and a controller configured with commands to: i) fire the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and the client satellite and that removes an angular momentum or a rotational velocity of the body, ii) fire the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body; iii) fire the first thruster and the second thruster to follow a rendezvous trajectory that matches orbital parameters of the servicer satellite and the client satellite; and iv) fire the first thruster and the second thruster to accelerate the servicer satellite toward the client satellite.
Regarding Claims 14-20, the prior art of record does not reasonably teach or suggest the combination of steps of performing rendezvous by a servicer satellite including providing the servicer satellite comprising a controller configured with commands to fire the set of thrusters; wherein: the controller fires the first thruster and the second thruster to produce a first thrust vector that reduces a separation distance between the servicer satellite and a client satellite and that removes an angular momentum or a rotational velocity of the body; and the controller fires the third thruster and the fourth thruster to produce a second thrust vector that reduces a rate of closure between the servicer satellite and the client satellite and that removes the angular momentum or the rotational velocity of the body; and the controller fires the first thruster and the second thruster to follow a first rendezvous trajectory that matches orbital parameters of the servicer satellite and the client satellite.
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”
Conclusion

APPLICANT REBUTTAL: Remarks
This paper is submitted with respect to the Office Action mailed on 27 November 2024. Claims 1, 3, 4, 7, 13-18, and 20 are amended. No new matter has been added. There are no new claims. Therefore, claims 1-20 are pending.
Examiner Interview
Examiner Leung, Primary Examiner Zarroli and the undersigned held a brief telephone discussion on 31 January 2025. Among other things, proposed claim amendments to independent claim 1 were presented and discussed. Agreement was reached that the presented claim amendments to claim 1 appear to overcome all pending rejections, i.e. the 35 U.S.C. § 112(a) and 35 U.S.C. § 112(b) rejections, and the objection of the drawings under 37 C.F.R. @ 1.83(a). However, no agreement was reached regarding allowance of any claims because a new prior art search is required. The undersigned thanks Examiner Leung and Primary Examiner Zarroli for their time and guidance.
Objection to the Drawings under 37 C.F.R.
§
(a)
The drawings are objected to under 37 C.F.R. @ 1.83(a) because the drawings are
asserted to not show the recited thrusters feature of "configured to provide 6 DOE thruster firing." Without admission as to the validity of the objection and solely to facilitate prosecution, the feature at issue has been deleted from each of independent claims 1, 13, and 14 and thus the objection is moot. Therefore, the drawing objections being addressed, Applicant requests the drawing objections be withdrawn.
Claim Rejections Under 35 U.S.C.
§
112(a) and 35 U.S.C.
§
112(b)
Claims 1-20 are rejected under 35 U.S.C. § 112(a) and under 35 U.S.C. § 112(b) for failing to comply with the written description requirement and as being indefinite, respectively, with reference to the thruster feature "configured to provide 6 DOE thruster firing."
Without admission as to the validity of the § 112(a) and § 112(b) rejections and solely to facilitate prosecution, the feature at issue has been deleted from each of independent claims 1, 13, and 14 and therefore the rejections are moot.
Therefore, the rejections being addressed, Applicant requests the § 112(a) and § 112(b) rejections be withdrawn.
Independent Claim 1 Amendments with respect to Examiner Interview
Claim 1 is presented with the features presented during the Examiner Interview and therefore overcomes, per agreement, the pending set of 35 U.S.C. § 112(a) and 35 U.S.C. § 112(b) rejections and the objection of the drawings under 37 C.F.R. § 1.83(a). Therefore, independent claim 1 is allowable. Claims 2-6 and 8-12, depending from allowable claim 1, are therefore also allowable.
Further Claim Amendments to Independent Claim 1
Independent claim 1 has been further amended solely to facilitate prosecution and to further distinguish claim 1 from the prior art, to include, e.g., U.S. Pat. Publ. No. 2021/0078732 to Reitman ("Reitman"). Specifically, claim 1 recites, inter alia, the feature:
the controller further configured with commands to fire the first thruster and the second thruster to follow a rendezvous trajectory that matches orbital parameters of the servicer
satellite and the client satellite
This feature, at least, is not disclosed nor suggested by Reitman or any other prior art. Reitman, e.g., describes station keeping operations of a servicer satellite docked with a client satellite, and is silent regarding the rendezvous structure of a servicer satellite as recited in claim 1, to include the above feature.
Thus, this feature provides a further distinction to the prior art and provides further evidence that claim 1, and its dependent claims 2-6 and 8-12, are allowable.
Claim Amendments to Independent Claim 13
In addition to deleting the thruster feature "configured to provide 6 DOF thruster firing" as described above, independent claim 13 has been amended solely to facilitate prosecution and to further distinguish claim 13 from the prior art, to include, e.g., Reitman. Specifically, claim 13 recites, inter alia, the features1:
a controller configured with commands to:
... fire the first thruster and the second thruster to follow a rendezvous trajectory that matches
orbital parameters of the servicer satellite and the client satellite; and
a controller configured with commands to:
... fire the first thruster and the second thruster to accelerate the servicer satellite toward the
client satellite
These features, at least, are not disclosed nor suggested by Reitman or other prior art. Reitman, e.g., describes station keeping operations of a servicer satellite docked with a client satellite, and is silent regarding the servicer satellite structure as recited in claim 13, to include the above features.
Thus, such features provide further distinctions to the prior art and evidence that claim 13 and its dependent claim 7 are allowable.
Claim Amendments to Independent Claim 14
In addition to deleting the thruster feature "configured to provide 6 DOF thruster firing" as described above, independent claim 14 has been amended solely to facilitate prosecution and to further distinguish claim 14 from the prior art, to include, e.g., Reitman. Specifically, claim 14 recites, inter alia, the feature:
the controller fires the first thruster and the second thruster to follow a first rendezvous
trajectory that matches orbital parameters of the servicer satellite and the client satellite
1 The second highlighted feature finds support at least at pg. 25, 11. 14-26 of the application as filed, i.e., "Generally, the RvD phase of operation comprises thrusting along the positive Z axis for steering the LEXI toward the host satellite. An on-board satellite computer using on-board sensors computes the thrust profile (acceleration and deceleration) for the LEXI to execute. ... The two diagonal thrusters (for example Ni and S2) are fired continuously based on a trajectory profile calculated by the LEXI on board computer and guidance and control system. As long as the acceleration is needed, the two diagonal thrusters are operating and close the range between the LEXI and the Host satellite. In case the trajectory calls for deceleration or reaching a complete stop of the acceleration or producing an outer plane corrections in the X or Y directions, the two diagonal thrusters (for example Ni and S2) in the positive Z direction are turned off. Two other diagonal thrusters (for example N2 and Si) are used such that the thruster vector is in the negative Z direction for decelerating the LEXI.
This feature, at least, is not disclosed nor suggested by Reitman or other prior art.
Reitman, e.g., describes station keeping operations of a servicer satellite docked with a client satellite, and is silent regarding the rendezvous operations of a servicer satellite as recited in claim 14, to include the above feature.
Thus, this feature provides a further distinction to the prior art and provides further evidence that claim 14, and its dependent claims 15-20, are allowable.
Conclusion