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 Arguments
Applicant’s arguments with respect to claim(s) 1-11 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
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.
Claim(s) 1-3, 5-8, 10 and 11 is/are rejected under 35 U.S.C. 103 as being unpatentable over Park et al. (Park), U.S. Patent Pub. No. 2022/0345879 in view of Bangolae et al. (Bangolae), U.S. Patent Pub. No. 2017/0013515.
Regarding claim 1, Park discloses a wireless terminal (UE 100; see figure 4), comprising: transmitting circuitry (transceiver 1031a; see figure 17) configured to: transmit a suggested time to release connection to a core network node (AMF node) (the UE may request the suspension (or postponement) of the signaling connection release through the N1 NAS signaling connection keep indication IE, may request that the explicit release is required through information on whether or not an explicit NAS signaling connection release is required, and may transmit the release suspend (or postponement) time value to the AMF through the time information for requesting and requesting the release suspend (or postponement), such that the AMF may perform explicit release of the NAS signaling connection after the time delivered by the terminal.) (0635); and receiving circuitry (transceiver 1031a; see figure 17).
Park, however, fails to disclose wherein the receiving circuitry is configured to receive a proposed connection release time from the core network node, wherein the proposed connection release time is derived by the core network node based on the suggested time.
In a similar field of endeavor, Bangolae discloses a user equipment and methods to indicate power saving mode configuration to RAN nodes. Bangolae further discloses wherein the receiving circuitry of a user equipment is configured to receive a proposed connection release time from the core network node (the negotiation process between the user equipment and the core network described below), wherein the proposed connection release time is derived by the core network node based on the suggested time (The inactivity timer may be used by the eNB to determine when to release the UE RRC connection after the last UE activity has occurred. In one embodiment, the UE may initially store an activation timer and provide the activation timer in the PSM configuration indication when attaching to the RAN network in the Initial UE Context Setup Request. In various embodiments, the MME may accept the activation timer or may negotiate a change of the activation timer with the UE. In some embodiments, the MME may determine that the activation timer should be increased, for example due to excessive traffic on the network in general or on the eNB to which the UE is or is to be attached. The MME in this embodiment may send a NAS message to the UE adjusting the activation timer.) (0057).
Therefore, before the effective filing date, it would have been obvious to a person of ordinary skill in the art to modify Park with the teachings of Bangolae to compensate for increased traffic as taught by Bangolae (0057).
Regarding claim 2, Park as modified discloses the wireless terminal of claim 1, wherein the wireless terminal is in an RRC_CONNECTED state when the suggested time to release connection is transmitted (In summary, when the UE receives a configuration update command message including “registration requested”, the UE operates as a Relay UE, and the Remote UE is in RRC_CONNECTED state, then the UE may transmit configuration update completion message including an N1 NAS signaling connection keep indication IE to the AMF) (0626).
Regarding claim 3, Park as modified discloses the wireless terminal of claim 1, wherein the suggested time to release connection comprises ULInformationTransfer and uplink non-access stratum (UL NAS) transport signaling messages (Additional NAS messages may be exchanged between the UE and the AMF. For example, the NAS may transmit a DOWNLINK NAS TRANSPORT message to the gNB. Then, the gNB may transmit a downlink information transfer message (eg, a DLInformationTransfer message) to the UE. The UE may transmit an uplink information transfer message (eg, a ULInformationTransfer message) to the gNB.) (0487).
Regarding claim 5, Park as modified discloses the wireless terminal of claim 1, wherein the proposed connection release time comprises DLInformationTransfer and downlink non-access stratum (DL NAS) transport signaling messages (Additional NAS messages may be exchanged between the UE and the AMF. For example, the NAS may transmit a DOWNLINK NAS TRANSPORT message to the gNB. Then, the gNB may transmit a downlink information transfer message (eg, a DLInformationTransfer message) to the UE. The UE may transmit an uplink information transfer message (eg, a ULInformationTransfer message) to the gNB.) (0487).
Regarding claim 6, Park discloses a core network node (AMF node), comprising: receiving circuitry (inherent since it receives information from the UE; see figure 4) configured to: receive a suggested time to release connection from a wireless terminal (the UE may request the suspension (or postponement) of the signaling connection release through the N1 NAS signaling connection keep indication IE, may request that the explicit release is required through information on whether or not an explicit NAS signaling connection release is required, and may transmit the release suspend (or postponement) time value to the AMF through the time information for requesting and requesting the release suspend (or postponement), such that the AMF may perform explicit release of the NAS signaling connection after the time delivered by the terminal.) (0635); and transmitting circuitry since it transmits to the wireless terminal (In this case, the AMF may transmit a UE Configuration Update (UCU) Command message including “registration requested” information to the UE) (0006).
Park, however, fails to disclose wherein the transmitting circuitry is configured to transmit a proposed connection release time to the wireless terminal, wherein the proposed connection release time is derived by the core network node based on the suggested time.
In a similar field of endeavor, Bangolae discloses a user equipment and methods to indicate power saving mode configuration to RAN nodes. Bangolae further discloses wherein the transmitting circuitry of core network node is configured to transmit a proposed connection release time to the wireless terminal (the negotiation process between the user equipment and the core network described below), wherein the proposed connection release time is derived by the core network node based on the suggested time (The inactivity timer may be used by the eNB to determine when to release the UE RRC connection after the last UE activity has occurred. In one embodiment, the UE may initially store an activation timer and provide the activation timer in the PSM configuration indication when attaching to the RAN network in the Initial UE Context Setup Request. In various embodiments, the MME may accept the activation timer or may negotiate a change of the activation timer with the UE. In some embodiments, the MME may determine that the activation timer should be increased, for example due to excessive traffic on the network in general or on the eNB to which the UE is or is to be attached. The MME in this embodiment may send a NAS message to the UE adjusting the activation timer.) (0057).
Therefore, before the effective filing date, it would have been obvious to a person of ordinary skill in the art to modify Park with the teachings of Bangolae to compensate for increased traffic as taught by Bangolae (0057).
Regarding claim 7, Park as modified discloses the core network node of claim 6, wherein the wireless terminal is in an RRC_CONNECTED state when the suggested time to release connection is received (In summary, when the UE receives a configuration update command message including “registration requested”, the UE operates as a Relay UE, and the Remote UE is in RRC_CONNECTED state, then the UE may transmit configuration update completion message including an N1 NAS signaling connection keep indication IE to the AMF) (0626).
Regarding claim 8, Park as modified discloses the core network node of claim 6, wherein the suggested time to release connection comprises ULInformationTransfer and uplink non-access stratum (UL NAS) transport signaling messages (Additional NAS messages may be exchanged between the UE and the AMF. For example, the NAS may transmit a DOWNLINK NAS TRANSPORT message to the gNB. Then, the gNB may transmit a downlink information transfer message (eg, a DLInformationTransfer message) to the UE. The UE may transmit an uplink information transfer message (eg, a ULInformationTransfer message) to the gNB.) (0487).
Regarding claim 9, Park discloses the core network node of claim 6, further comprising transmitting circuitry (inherently since the AMF transmits to the UE) configured to transmit a proposed connection release time to the wireless terminal (Alternatively, the specific time may mean an arbitrary time value (eg, a time value set by an operator or AMF). For example, the time value of the specific time may be a time value of about 10 to 15 seconds.) (0634).
Regarding claim 10, Park as modified discloses the core network node of claim 6, wherein the proposed connection release time comprises DLInformationTransfer and downlink non-access stratum (DL NAS) transport signaling messages (Additional NAS messages may be exchanged between the UE and the AMF. For example, the NAS may transmit a DOWNLINK NAS TRANSPORT message to the gNB. Then, the gNB may transmit a downlink information transfer message (eg, a DLInformationTransfer message) to the UE. The UE may transmit an uplink information transfer message (eg, a ULInformationTransfer message) to the gNB.) (0487).
Regarding claim 11, Park discloses a method by a wireless terminal, comprising: entering an RRC_CONNECTED state; and transmitting a suggested time to release connection to a core network node (In summary, when the UE receives a configuration update command message including “registration requested”, the UE operates as a Relay UE, and the Remote UE is in RRC_CONNECTED state, then the UE may transmit configuration update completion message including an N1 NAS signaling connection keep indication IE to the AMF) (0626) and receiving circuitry (transceiver 1031a; see figure 17).
Park, however, fails to disclose wherein the receiving circuitry is configured to receive a proposed connection release time from the core network node, wherein the proposed connection release time is derived by the core network node based on the suggested time.
In a similar field of endeavor, Bangolae discloses a user equipment and methods to indicate power saving mode configuration to RAN nodes. Bangolae further discloses wherein the receiving circuitry of a user equipment is configured to receive a proposed connection release time from the core network node (the negotiation process between the user equipment and the core network described below), wherein the proposed connection release time is derived by the core network node based on the suggested time (The inactivity timer may be used by the eNB to determine when to release the UE RRC connection after the last UE activity has occurred. In one embodiment, the UE may initially store an activation timer and provide the activation timer in the PSM configuration indication when attaching to the RAN network in the Initial UE Context Setup Request. In various embodiments, the MME may accept the activation timer or may negotiate a change of the activation timer with the UE. In some embodiments, the MME may determine that the activation timer should be increased, for example due to excessive traffic on the network in general or on the eNB to which the UE is or is to be attached. The MME in this embodiment may send a NAS message to the UE adjusting the activation timer.) (0057).
Therefore, before the effective filing date, it would have been obvious to a person of ordinary skill in the art to modify Park with the teachings of Bangolae to compensate for increased traffic as taught by Bangolae (0057).
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to TEMICA M. BEAMER whose telephone number is (571)272-7797. The examiner can normally be reached Monday thru Friday; 9:00 AM to 3: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, Matthew D. Anderson can be reached at 571-272-4177. 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.
/TEMICA M BEAMER/Primary Examiner, Art Unit 2646