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 .
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claim 7 is rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. Lines 11-12 of claim 1 recites second message, transmitted after the mobility procedure and include the QoE reports that were buffered or not successfully transmitted. Claim 7 requires that the first message include a configuration to discard those same reports. This limitation is contradictory because a UE cannot discard the report and later transmit the same report. Such ambiguity makes the claim indefinite. Appropriate clarification is needed.
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, 4, 5, 6, 7, 8-11, 16, 17, 19 and 21, is/are rejected under 35 U.S.C. 103 as being unpatentable over SHI et al (U.S. PUB No 2020/0413301 A1) and EKLOF (WO2022/154740A1).
As per claims 1 and 11 SHI disclosed a method performed by a user equipment (UE) (FIG.7) {wireless device 110 with processors 114 and memory 116 having instructions performing the method}, the method comprising: receiving, a first message including a first configuration for handling Quality of Experience (QoE) reports for network services that are buffered by the UE or not successfully transmitted by the UE prior to a radio resource control (RRC) connected state mobility procedure (paragraphs.9 and 62) { in the RRC message (an RRCConnectionReconfiguration encapsulated in a HandoverCommand) from the target radio network node an explicit indication, e.g. “QoE measurement reporting allowed”, “QoE measurement reporting supported”, etc., to allow the wireless device(UE) to report the QoE measurements after the handover.} (Table.2, page.6) and (FIG.3, Elements S102, S110 and S112) {the QoE report whose transmission began in the first cell but was not completed before handover}; and transmitting, after completing the RRC connected state mobility procedure, a second message based on the first configuration (paragraph.80) { Upon receiving the handover command message from the source radio network node 130, the wireless device 110 determines whether to report QoE measurements to the target radio network node 130 (action S112). If the target radio network node 130 does support QoE measurement reporting, then the wireless device 110 may report QoE measurements to the target radio network node 130.} (paragraph.81) {wireless device 110 typically transmits a handover confirmation message (e.g., an RRC Connection Reconfiguration Complete message) to the target radio network node 130 to trigger the completion of the handover procedure (action S114)}.
Although SHI disclosed after the handover, UE usually sends the target node a QoE measurement report when the indication shows reporting is supported. The UE sends the handover confirmation as part of completing the handover as explained above. However, SHI did not explicitly disclose that the first and second messages include the QoE reports that were not successfully transmitted or were buffered by the UE prior to the RRC connected state mobility procedure. In the same field of endeavor, EKLOF disclosed that the first and second messages include the QoE reports that were not successfully transmitted or were buffered by the UE prior to the RRC connected state mobility procedure (Page.9, lines 2-11) { determining that the QoE report was not delivered, the determining being based on one or more of indicating from lower layer to RRC layer that all PDCP protocol data units (PDUs) were not delivered, not receiving indication of delivery from lower layer for one or more PDCP PDUs (associated with the QoE report), the transmission of the PDUs started less than a specified or configured time before the handover occurred/was initiated; and continuing transmitting the QoE report in the second cell from the last unacknowledged PDU}.
It would have been obvious to one in the ordinary skill in the art to have incorporated that the second message includes the QoE reports that were not successfully transmitted or were buffered by the UE prior to the RRC connected state mobility procedure as disclosed by EKLOF in the method disclosed by SHI to make the method more robust and predictable.
As per claims 16 and 21 SHI disclosed a method performed by a network entity (FIG.9) {Network Node 130 with processors 134 and memory 136 having instructions performing the method}, the method comprising: transmitting, to a user equipment (UE), a first message including a first configuration for handling Quality of Experience (QoE) reports for network services not transmitted by the UE prior to a radio resource control (RRC) connected state mobility procedure (FIG.3, Elements S108 thru S110) (FIG.6) (paragraph.69) { the target radio network node builds the handover message which is sent to the wireless device}; and receiving, after completing the RRC connected state mobility procedure, from the UE (paragraph.80) { Upon receiving the handover command message from the source radio network node 130, the wireless device 110 determines whether to report QoE measurements to the target radio network node 130 (action S112). If the target radio network node 130 does support QoE measurement reporting, then the wireless device 110 may report QoE measurements to the target radio network node 130.} (paragraph.81) {wireless device 110 typically transmits a handover confirmation message (e.g., an RRC Connection Reconfiguration Complete message) to the target radio network node 130 to trigger the completion of the handover procedure (action S114)}
Although SHI disclosed after the handover, UE usually sends the target node a QoE measurement report when the indication shows reporting is supported. The UE sends the handover confirmation as part of completing the handover as explained above. However, SHI did not explicitly disclose that the first and second messages being based on the first configuration that includes the QoE reports not transmitted prior to the RRC connected state mobility procedure. In the same field of endeavor, EKLOF disclosed that the first and second messages being based on the first configuration that includes the QoE reports not transmitted prior to the RRC connected state mobility procedure (Page.9, lines 2-11) { determining that the QoE report was not delivered, the determining being based on one or more of indicating from lower layer to RRC layer that all PDCP protocol data units (PDUs) were not delivered, not receiving indication of delivery from lower layer for one or more PDCP PDUs (associated with the QoE report), the transmission of the PDUs started less than a specified or configured time before the handover occurred/was initiated; and continuing transmitting the QoE report in the second cell from the last unacknowledged PDU}.
It would have been obvious to one in the ordinary skill in the art to have incorporated that the first and second messages being based on the first configuration that includes the QoE reports not transmitted prior to the RRC connected state mobility procedure as disclosed by EKLOF in the method disclosed by SHI to make the method more robust and predictable.
As per claims 4 and 14 SHI-EKLOF disclosed the UE of claim 1, wherein the at least one processor is further configured to cause the UE to perform QoE measurement collections based on the first configuration and after completing the RRC connected state mobility procedure (SHI, FIG.11, Operation8) (paragraph.80) { Upon receiving the handover command message from the source radio network node 130, the wireless device 110 determines whether to report QoE measurements to the target radio network node 130 (action S112). If the target radio network node 130 does support QoE measurement reporting, then the wireless device 110 may report QoE measurements to the target radio network node 130.} (paragraph.81) {wireless device 110 typically transmits a handover confirmation message (e.g., an RRC Connection Reconfiguration Complete message) to the target radio network node 130 to trigger the completion of the handover procedure (action S114)}.
As per claims 5, 15 and 19 SHI-EKLOF disclosed the UE of claim 1, wherein the first message is received during an RRC connected state mobility procedure (SHI, FIG.3. S110) (Paragraph.62) {RRC message (an RRCConnectionReconfiguration encapsulated in a HandoverCommand) from the target radio network node an explicit indication, e.g. “QoE measurement reporting allowed”, “QoE measurement reporting supported”}.
As per claim 6 SHI-EKLOF disclosed the UE of claim 1 the first message is received over a new radio (NR) radio access networks and wherein the second message is transmitted over in a Long-Term Evolution (LTE) radio access network (EKLOF, FIG.11) (page.6, lines 19-28) { In 3GPP, the dual connectivity solution has evolved and is now also specified for NR as well as between LTE and NR. Multi -connectivity (MC) is the case when there are more than two nodes involved. With introduction of 5G, the term multi-radio dual connectivity}.
It would have been obvious to one in the ordinary skill in the art to have incorporated the first message is received over a new radio (NR) radio access networks and wherein the second message is transmitted over in a Long-Term Evolution (LTE) radio access network as disclosed by EKLOF in the method disclosed by SHI to make the method more robust and predictable.
As per claim 7 SHI-EKLOF disclosed the UE of claim 1, wherein the first message includes the configuration to discard the QoE reports for network services that are buffered by the UE or not successfully transmitted by the UE prior to the RRC connected state mobility procedure (EKLOF, paragraph.63) {if the target radio network node does not indicate anything with respect to the QoE measurement reporting, the wireless device 110 may infer that QoE measurement reporting is not supported by the target radio network node and may refrain from reporting QoE measurements after handover}.
It would have been obvious to one in the ordinary skill in the art before the effective filing date of the invention to have incorporated wherein the first message includes the configuration to discard the QoE reports for network services that are buffered by the UE or not successfully transmitted by the UE prior to the RRC connected state mobility procedure as disclosed by EKLOF in the method disclosed by SHI to make the method more robust and predictable.
As per claim 8 SHI-EKLOF disclosed the UE of claim 1, wherein the network services include streaming services and multimedia telephony services for IMS (MTSI) services (EKLOF, Page.2, lines 8-13) {The purpose of the study item is to study solutions for QoE measurements in new radio (NR). QoE management in NR will not just collect the experience parameters of streaming services but also consider the typical performance requirements of diverse services (e.g., augmented reality (AR)/virtual reality (VR) and ultra-reliable low-latency communications (URLLC))}.
As per claim 9 SHI-EKLOF disclosed the UE of claim 1, wherein the UE is capable of QoE measurement collection in two or more different radio access technologies (RATs) (EKLOF, FIG.11) (page.6, lines 19-28) { In 3GPP, the dual connectivity solution has evolved and is now also specified for NR as well as between LTE and NR. Multi -connectivity (MC) is the case when there are more than two nodes involved. With introduction of 5G, the term multi-radio dual connectivity}.
As per claim 10 SHI-EKLOF disclosed the UE of claim 1, wherein the RRC connected state mobility procedure includes an intra-5GC inter-RAT (radio access technology) handover procedure (EKLOF,FIG.2, Page.12, lines 25-27).
As per claim 17 SHI-EKLOF disclosed the network entity of claim 16, wherein the QoE reports not transmitted by the UE prior to the RRC connected state mobility procedure include QoE reports stored in a buffer of the UE based on the first configuration (EKLOF, Page.9, lines 2-11).
It would have been obvious to one in the ordinary skill in the art to have incorporated wherein the QoE reports not transmitted by the UE prior to the RRC connected state mobility procedure include QoE reports stored in a buffer of the UE based on the first configuration as disclosed by EKLOF in the method disclosed by SHI to make the method more robust and predictable.
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) 2, 3, 12,13 and 18 is/are rejected under 35 U.S.C. 103 as being unpatentable over SHI et al (U.S. PUB No 2020/0413301 A1) and EKLOF (WO2022/154740A1) and further in view of EKLOF el al (US2023/0284058 A1) (Referred to as “EKOF-4058”).
As per claims 2, 12 and 18 SHI-EKLOF disclosed the UE of claim 1. However, both SHI-EKLOF did not explicitly disclose wherein at least one processor is further configured to cause the UE to: receive, a request to provide radio access capabilities of the UE in a Long-Term Evolution (LTE) network; and transmit capability information identifying the radio access capabilities of the UE in the LTE. In the same field of endeavor wherein at least one processor is further configured to cause the UE to: receive, a request to provide radio access capabilities of the UE in a Long-Term Evolution (LTE) network (EKLOF-4058, paragraph. 177) {UE capability transfer procedure used to transfer UE radio access capability information from the UE to E-UTRAN}; and transmit capability information identifying the radio access capabilities of the UE in the LTE (EKLOF-4058, paragraph. 177) {The UE can respond with a UE Capability Information message that includes a “UE-EUTRA-Capability” IE}.
It would have been obvious to one in the ordinary skill in the art to have incorporated wherein at least one processor is further configured to cause the UE to: receive, a request to provide radio access capabilities of the UE in a Long-Term Evolution (LTE) network; and transmit capability information identifying the radio access capabilities of the UE in the LTE as disclosed by EKLOF-4058 in the method disclosed by SHI-EKLOF to make the method more robust and predictable.
As per claims 3 and 13 SHI-EKLOF disclosed the UE of claim 2. However, both SHI-EKLOF did not explicitly disclose wherein the radio access capabilities include a subset of the network services capable of being performed by the UE in the LTE network. In the same field of endeavor wherein the radio access capabilities include a subset of the network services capable of being performed by the UE in the LTE network (EKLOF-4058, paragraph.178) { UE-EUTRA-Capability-v1530 IE, which can be used to indicate whether the UE supports QoE Measurement Collection for streaming services and/or MTSI services, i.e., a subset of services}.
It would have been obvious to one in the ordinary skill in the art to have incorporated wherein the radio access capabilities include a subset of the network services capable of being performed by the UE in the LTE network. In the same field of endeavor wherein the radio access capabilities include a subset of the network services capable of being performed by the UE in the LTE network as disclosed by EKLOF-4058 in the method disclosed by SHI-EKLOF to make the method more robust and predictable.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure is indicated in PTO form 892.
Applicant's future amendments need to comply with the requirements of MPEP §
714.02, MPEP § 2163.04 and MPEP § 2163.06.
"with respect to newly added or amended claims, applicant should show support in the original disclosure for the new or amended claims." See MPEP § 714.02 and § 2163.06 ("Applicant should * * * specifically point out the support for any amendments made to the disclosure."); and MPEP § 2163.04 ("If applicant amends the claims and points out where and/or how the originally filed disclosure supports the amendment(s), and the examiner finds that the disclosure does not reasonably convey that the inventor had possession of the subject matter of the amendment at the time of the filing of the application, the examiner has the initial burden of presenting evidence or reasoning to explain why persons skilled in the art would not recognize in the disclosure a description of the invention defined by the claims."). See In re Smith, 458 F.2d 1389, 1395, 173 USPQ 679, 683 (CCPA 1972) In re Wertheim, 541 F.2d at 262,191 USPQ at 96 (emphasis added).
"The use of a confusing variety of terms for the same thing should not be permitted.
New claims and amendments to the claims already in the application should be scrutinized not only for new matter but also for new terminology. While an applicant is not limited to the nomenclature used in the application as filed, he or she should make appropriate amendment of the specification whenever this nomenclature is departed from by amendment of the claims so as to have clear support or antecedent basis in the specification for the new terms appearing in the claims. This is necessary in order to insure certainty in construing the claims in the light of the specification." Ex parte Kotler, 1901 C.D. 62, 95 O.G. 2684
(Comm'r Pat. 1901). See 37 CFR 1.75, MPEP § 608.01 (i) and § 1302.01.
Note that examiners should ensure that the terms and phrases used in claims presented late in prosecution of the application (including claims amended via an examiner's amendment) find clear support or antecedent basis in the description so that the meaning of the terms in the claims may be ascertainable by reference to the description, see 37 CFR 1.75(d)(1 ). If the examiner determines that the claims presented late in prosecution do not comply with 37 CFR 1.75(d)(1), applicant will be required to make appropriate amendment to the description to provide clear support or antecedent basis for the terms appearing in the claims provided no new matter is introduced."
"USPTO personnel are to give claims their broadest reasonable interpretation in light of the supporting disclosure." In re Morris, 127 F.3d 1048, 1054-55, 44 USPQ2d 1023,1027-28 (Fed. Cir. 1997). MPEP § 2106. "
The examiner has cited particular columns and line numbers in the references as applied to the claims above for the convenience of the applicant. Although the specified citations are representative of the teachings in the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant, in preparing the responses, to fully consider each of the cited references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage disclosed by the examiner.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ASGHAR H BILGRAMI whose telephone number is (571)272-3907. The examiner can normally be reached M-F 6 AM to 9 PM IFP.
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, Alison Slater can be reached at (571)270-0375. 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.
/ASGHAR H BILGRAMI/Primary Examiner, Art Unit 2647