DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Amendment
This Office Action is in response to applicant’s amendment submitted on June 10, 2026.
Claims, 1-6, 8-29 and 31-32 are now currently pending in the present application.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or non-obviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1-6, 8-29 and 31-32 are rejected under U.S.C. 103 as being unpatentable by 3GPP et al. (TSG RAN WG2 #117-e R2-2202550, hereinafter 3GPP) in view of Watts et al. (US 20250233650 A1, hereinafter Watts).
Consider Claim 1, 3GPP discloses a user equipment (UE) for wireless communication, comprising:
access a serving network via a satellite while in a first state with the serving network, the first state comprising a connected state; (Discussion line 1-2, RAN2 has agreed in R2-115e that “Satellite assistance information will be used by the UE for predicting coverage discontinuity).
transition from the connected state to a second state at or before a start of the coverage gap. (Proposal 1: line 1-4, once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status. One question is which RRC state (Idle or Connected) should the UE inform the network of its impending transition to out-of-coverage state).
3GPP discloses the claimed invention but fail to teach one or more memories; and
However, Watts teaches one or more memories; and (paragraph 0029, the WTRU 102 may include a non-removable memory 130 or removable memory 132).
Watts teaches one or more processors, coupled to the one or more memories, configured to: (Paragraph 0034, the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132).
Watts teaches receive, from the serving network, configuration information; (fig. 5, paragraphs 115, 163, read the WTRU receives assistance information from the serving gNB, where assistance information is read as "configuration information" since Watts clearly shows that this assistance information is satellite assistance information regarding the WTRU calculation of coverage gap characteristics).
Watts teaches transmit to the serving network and based on the configuration information and a determination that a coverage gap associated with the satellite is upcoming, a coverage gap indication that indicates that the coverage gap is upcoming; and (fig. 5, paragraphs 70, 163, read as the WTRU transmits a coverage gap report based on the assistance information (.e. configuration information) and a determination of an upcoming coverage gap, where Watts clearly shows that the coverage gap report includes a start of the coverage gap (e.g., a time in which the WTRU estimates it will enter the coverage gap) and a duration of the coverage gap (e.g., an estimated duration of the coverage gap)).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 1, by incorporating 3GPP’s support of discontinuous coverage to include the systems, methods, and instrumentalities for adapting mobility under discontinuous coverage (e.g., associated with gap(s) in coverage of Watts. The motivation to do so would be determining a start and duration of discontinuous coverage based on received assistance information and transmitting to a coverage gap report based on the determination of the coverage gap. Thereby, developing a wireless communication system using satellite assistance information to enable the UE to predict coverage discontinuity.
Consider Claim 2, 3GPP discloses the UE of claim 1, wherein transmitting the coverage gap indication comprises transmitting the coverage gap indication to a radio access network (RAN) node of the serving network. (Proposal 2: line 1-2, once, the UE is out of coverage, we expect that the UE can power down to conserve energy. When the UE detects that it is back in coverage, then it can establish an RRC connection with the network).
Consider Claim 3, 3GPP discloses the UE of claim 2, wherein the RAN node comprises a satellite-based node. (Discussion line 1-2, RAN2 has agreed in R2-115e that “Satellite assistance information will be used by the UE for predicting coverage discontinuity).
Consider Claim 4, 3GPP discloses the UE of claim 3, wherein transmitting the coverage gap indication comprises transmitting the coverage gap indication to a core network node of the serving network. (Proposal 3: line1-2, the UE may additionally provide the network with some assistance information to enable the network to figure when and where the UE is expected to be back in coverage).
Consider Claim 5, 3GPP discloses the UE of claim 4, wherein the core network node comprises an access and mobility management function (AMF). ( Introduction: line 6- 8, while enhancements to core network procedures and NAS layer are out of scope of RAN2, it is well within RAN2’s scope (and one of the objectives of the WID[2]) to discuss what action the UE’s AS layer may take when it determines that the UE is likely to go out of coverage).
Consider Claim 6, 3GPP discloses the UE of claim 5, wherein transmitting the coverage gap indication comprises transmitting a non-access stratum (NAS) layer message including the coverage gap indication. (Introduction: line 6- 8, while enhancements to core network procedures and NAS layer are out of scope of RAN2, it is well within RAN2’s scope (and one of the objectives of the WID[2]) to discuss what action the UE’s AS layer may take when it determines that the UE is likely to go out of coverage).
Consider Claim 8, 3GPP discloses the UE of claim 1, wherein the configuration information comprises a configuration support indication that indicates that the serving network supports receiving the coverage gap indication. (Proposal 1: line1-3, once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status).
Consider Claim 9, 3GPP discloses the UE of claim 1, wherein the configuration information indicates that a value of a UE timer comprises a value selected by the UE, wherein the value selected by the UE is equal to zero, and wherein the one or more processors are further configured to refrain from starting the UE timer based on the value selected by the UE being equal to zero. (Proposal 4: line 1-6, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state(set to zero). Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle. However, in this case, the UE will not simply transit to RRC idle; Instead, it will stop attempting to camp on any cell and be unreachable for paging purposes as long as the UE is out of coverage).
Consider Claim 10, 3GPP discloses the UE of claim 1, wherein the one or more processors are further configured to start a UE timer while transmitting the coverage gap indication or after transmitting the coverage gap indication. (Proposal 6: line 3-4, the network can configure the UE to trigger the mechanism resulting in RRC Release when the UE is within a certain area (e.g., a circular area defined by latitude-long coordinates) or at certain times, or a combination of these factors).
Consider Claim 11, 3GPP discloses the UE of claim 10, wherein a duration of the UE timer is set to one of a UE timer value provided by the serving network or a UE timer value selected by the UE. (Proposal 3: line 1-3, once the UE is out-of-coverage, it is up to UE implementation to detect when it is back in coverage and establish an RRC connection with the network. The UE may additionally provide the network with some assistance information to enable the network to figure when and where the UE is expected to be back in coverage).
Consider Claim 12, 3GPP discloses the UE of claim 11, wherein the UE timer value provided by the serving network is included in the configuration information and comprises a UE timer value, a UE timer range, or an indication of a selectable UE timer value. (Proposal 6: line 3-4, the network can configure the UE to trigger the mechanism resulting in RRC Release when the UE is within a certain area (e.g., a circular area defined by latitude-longitude coordinates) or at certain times, or a combination of these factors).
Consider Claim 13, 3GPP discloses the UE of claim 12, wherein a duration of the UE timer is set to one of the UE timer value when the configuration information is indicative of the UE timer value, a value within the UE timer range when the configuration information is indicative of the UE timer range, or a value selected by the UE when the configuration information is indicative of the selectable UE timer value or an indication that the UE timer value is zero. (Proposal 4: line 1-6, When RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state(set to zero). Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle. However, in this case, the UE will not simply transit to RRC idle, instead it will stop attempting to camp on any cell and be unreachable for paging purposes as long as the UE is out of coverage).
Consider Claim 14, 3GPP discloses the UE of claim 13, wherein the UE timer value selected by the UE is equal to zero. (Proposal 4: line 1-3, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state(set to zero. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 15, 3GPP discloses the UE of claim 13, wherein the one or more processors are further configured to determine that the duration of the UE timer has expired or is set to zero, and wherein the one or more processors, to transition from the connected state to the second state, are configured to transition from the connected state to the second state based on determining that the duration of the UE timer has expired or is set to zero. (Proposal 1: RAN2 assumes that the UE is able to reliably predict when and where it is likely to be out of coverage. Once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status. One question is which RRC state (Idle or Connected) should the UE inform the network of its impending transition to out-of-coverage state).
Consider Claim 16, 3GPP discloses the UE of claim 10, wherein the one or more processors are further configured to transmit the coverage gap indication based on a difference between a duration of the UE timer and a time remaining until a start of the coverage gap associated with the satellite satisfying a threshold time value. (Discussion 2 line 1-5 RAN2 has agreed in R2-115e that “Satellite assistance information will be used by the UE for predicting coverage discontinuity. The details of the assistance information is FFS. FFS whether any applicable agreements made in NR-NTN can be “reused.” At this point, the details of the assistance information (which would be some kind of ephemeris) is to be specified by 3GPP to enable the UE to predict coverage discontinuity).
Consider Claim 17, 3GPP discloses the UE of claim 10, wherein the one or more processors are further configured to transmit an indication of a duration of the UE timer. Proposal 3: line 1-3, once the UE is out-of-coverage, it is up to UE implementation to detect when it is back in coverage and establish an RRC connection with the network. The UE may additionally provide the network with some assistance information to enable the network to figure when and where the UE is expected to be back in coverage).
Consider Claim 18, 3GPP discloses the UE of claim 10, wherein the one or more processors are further configured to receive a connection release command prior to an expiration of a duration of the UE timer. (Proposal 4: line 1-6, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state(set to zero). Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle. However, in this case, the UE will not simply transit to RRC idle, instead it will stop attempting to camp on any cell and be unreachable for paging purposes as long as the UE is out of coverage).
Consider Claim 19, 3GPP discloses the UE of claim 1, wherein the configuration information indicates the second state. (Proposal 1: RAN2 assumes that the UE is able to reliably predict when and where it is likely to be out of coverage. Once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status. One question is which RRC state (Idle or Connected) should the UE inform the network of its impending transition to out-of-coverage state).
Consider Claim 20, 3GPP discloses the UE of claim 1, wherein the one or more processors, to transmit the coverage gap indication, are configured to transmit a medium access control (MAC) layer communication that includes the coverage gap indication, a radio resource control (RRC) layer message that includes the coverage gap indication, or a non-access stratum (NAS) layer message and the coverage gap indication. ( Introduction: line 6- 8, while enhancements to core network procedures and NAS layer are out of scope of RAN2, it is well within RAN2’s scope (and one of the objectives of the WID[2]) to discuss what action the UE’s AS layer may take when it determines that the UE is likely to go out of coverage).
Consider Claim 21, 3GPP discloses the UE of claim 1, wherein the coverage gap indication comprises a release assistance indication. (Proposal 4: line 1-4, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 22, 3GPP discloses the UE of claim 1, wherein the second state comprises an idle state, a suspended state, or an inactive state. (Proposal 4: line 1-4, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 23, 3GPP discloses the UE of claim 1, wherein the one or more processors are further configured to enter a power saving state based on transitioning from the connected state to the second state. (Proposal 1: line 1-4, once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status. One question is which RRC state (Idle or Connected) should the UE inform the network of its impending transition to out-of-coverage state).
Consider Claim 24, 3GPP discloses the UE of claim 23, wherein the one or more processors, to enter the power saving state, are configured to deactivate at least one of a transceiver function, a network search function, or a paging monitoring function. (Proposal 5: line 1-3, once RAN instructs the UE to transit to release the RRC connection on receipt of out-of-coverage indication as per Proposal 1, RAN should consider the UE unreachable (e.g., for paging purposes) till such time as the UE establishes an RRC connection (as per Proposal 2)).
Consider Claim 25, 3GPP discloses the UE of claim 2, wherein the one or more processors, to transition from the connected state to the second state, are configured to suspend or inactivate a signaling connection between the UE and the RAN node. (Proposal 2: line 1-2, once, the UE is out of coverage, we expect that the UE can power down to conserve energy. When the UE detects that it is back in coverage, then it can establish an RRC connection with the network).
Consider Claim 26, 3GPP discloses the UE of claim 25, wherein the second state comprises a suspended state, and wherein the suspended state comprises an idle state associated with a suspended indication. (Proposal 4: line 1-4, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 27, 3GPP discloses the UE of claim 25, wherein the second state comprises an inactive state, and wherein the inactive state comprises a connected state to the serving network associated with a radio resource control inactive state. (Proposal 4: line 1-4, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 28, 3GPP discloses the UE of claim 25, wherein the one or more processors are further configured to transition, based on a resume procedure, from the second state to the connected state based on a determination of an end of the coverage gap. (Proposal 4: line 1-4, when RAN receives information from the UE that it is likely to be out of coverage, then the RAN can instruct the UE to transition to RRC idle or RRC inactive state. Since the latter is only possible if the RAN is connected to SGC, and the WID only intends to support EPC, for Release 17 at least, the only option is for RAN to send the UE to RRC idle).
Consider Claim 29, 3GPP discloses a network node for wireless communication, comprising:
transition the UE to a second state at or before a start of the coverage gap. (Proposal 1: line 1-4, once the UE has determined that it is going out of coverage, it needs to inform the network to ensure that the UE and the network can gracefully manage the transition of the VE from in-coverage to out-of-coverage status. One question is which RRC state (Idle or Connected) should the UE inform the network of its impending transition to out-of-coverage state).
3GPP discloses the claimed invention but fail to teach one or more memories; and
However, Watts teaches one or more memories; and (paragraph 0029, the WTRU 102 may include a non-removable memory 130 or removable memory 132).
Watts teaches one or more processors, coupled to the one or more memories, configured to: (Paragraph 0034, the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132).
Watts teaches transmit, to a user equipment (UE), configuration information; (fig. 5, paragraphs 0115, 0163, read the WTRU receives assistance information from the serving gNB, where assistance information is read as "configuration information" since Watts clearly shows that this assistance information is satellite assistance information regarding the WTRU calculation of coverage gap characteristics).
Watts teaches receive, from the UE while the UE is in a first state with a serving network and based on the configuration information, a coverage gap indication that indicates that a coverage gap associated with a satellite via which the UE accesses the serving network is upcoming, the first state comprising a connected state; and (fig. 5, paragraphs 0070, 0163, read as the WTRU transmits a coverage gap report based on the assistance information (.e. configuration information) and a determination of an upcoming coverage gap, where Watts clearly shows that the coverage gap report includes a start of the coverage gap (e.g., a time in which the WTRU estimates it will enter the coverage gap) and a duration of the coverage gap (e.g., an estimated duration of the coverage gap)).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 29, by incorporating 3GPP’s support of discontinuous coverage to include the systems, methods, and instrumentalities for adapting mobility under discontinuous coverage (e.g., associated with gap(s) in coverage of Watts. The motivation to do so would be determining a start and duration of discontinuous coverage based on received assistance information and transmitting to a coverage gap report based on the determination of the coverage gap. Thereby, developing a wireless communication system using satellite assistance information to enable the UE to predict coverage discontinuity.
Consider Claim 31, 3GPP discloses the claimed invention the UE of claim 1 but fails to teach wherein the configuration information indicates a coverage gap management procedure.
However, Watts teaches wherein the configuration information indicates a coverage gap management procedure (paragraph 0115, 0121, the WTRU may transit a report that it has detected (e.g., determined) an upcoming coverage gap (e.g., based on received satellite assistance information) while in a coverage gap, the WTRU may suspend various WTRU actions and procedures while in a discontinuous coverage gap (e.g., as described herein). To synchronize the WTRU reachability with the network, the WTRU may indicate a time in which it intends to resume in-coverage operation (e.g., normal procedures).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 31, by incorporating 3GPP’s support of discontinuous coverage to include the systems, methods, and instrumentalities for adapting mobility under discontinuous coverage (e.g., associated with gap(s) in coverage of Watts. The motivation to do so would be determining a start and duration of discontinuous coverage based on received assistance information and transmitting to a coverage gap report based on the determination of the coverage gap. Thereby, developing a wireless communication system using satellite assistance information to enable the UE to predict coverage discontinuity.
Consider Claim 32, 3GPP discloses the claimed invention the UE of claim 31 but fail to teach wherein, as part of the coverage gap management procedure, the one or more processors are configured to determine that the coverage gap is upcoming.
However, Watts teaches wherein, as part of the coverage gap management procedure, the one or more processors are configured to determine that the coverage gap is upcoming (paragraph 0030, 0115, the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102. The WTRU may transit a report that it has detected (e.g., determined) an upcoming coverage gap (e.g., based on received satellite assistance information) while in a coverage gap the WTRU estimates it will enter a coverage gap (e.g., the start of the coverage gap); the duration (e.g., estimated duration) of the coverage gap; the procedure for which the WTRU has calculated the coverage gap start time/duration).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 32 by incorporating 3GPP’s support of discontinuous coverage to include the systems, methods, and instrumentalities for adapting mobility under discontinuous coverage (e.g., associated with gap(s) in coverage of Watts. The motivation to do so would be determining a start and duration of discontinuous coverage based on received assistance information and transmitting to a coverage gap report based on the determination of the coverage gap. Thereby, developing a wireless communication system using satellite assistance information to enable the UE to predict coverage discontinuity.
Response to Arguments
Applicant's arguments/remarks made in an amendment filed June 10, 2026, with respect to independent claims 1 and 29 have been fully considered.
In view of Applicant’s arguments (page 10 and 11) of the amended claims and upon further consideration, a new ground(s) of rejection is made in view of newly cited reference Watts as presented in this Office action. Applicants’ arguments with respect to claims are therefore moot."
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHELE CAMILLE DOUGLAS whose telephone number is (571)270-0458. The examiner can normally be reached Monday - Friday 6:30 am - 5:00 pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jeanette J Parker can be reached at 571-270-3647. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MICHELE C DOUGLAS/Examiner, Art Unit 2646
/JEANETTE J PARKER/Supervisory Patent Examiner, Art Unit 2646
Prosecution Insights