DETAILED ACTION
1. It is hereby acknowledged that 18/621528 the following papers have been received and placed of record in the file: Amendment dated 05/22/26
2. Claims 1, 4-6, 9-11, and 14-16, 19-20 are presented for examination. Claims 1, 4, 6, 9, 11, 14, 16 and 19 have been amended. Claims 2, 3, 7, 8, 12, 13 , 17 and 18 are being cancelled.
Response to Argument
3. Applicant’s arguments, see remarks, filed 05/22/26 with respect to the rejection(s) of claim(s) 1, 4-6, 9-11, and 14-16, 19-20 upon further consideration, a new ground(s) of rejection is made.
Claim Rejections - 35 USC § 112
4. The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
5.Claims 1, 4-6, 9-11, 14-16, 19-20 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claims 1, 6, 11, and 16 discloses…. a third RRC message including report information, wherein the report information indicates whether transmission of a measurement report associated with the application layer measurement performed in an RRC inactive or an RRC idle is allowed…..
It is unclear where the support for this limitation is in the description, especially a third RRC message which includes the limitations.
Claim Rejections - 35 USC § 102
5. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
6. Claim(s) 1, 6, 11 and 16 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Kim (US 2024/0414799A1)
Regarding claim 1, Kim teaches a method performed by a base station in a wireless communication system, the method comprising: transmitting, to a terminal, a first radio resource control (RRC) message including configuration information associated with an application layer measurement of the terminal;(see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) receiving. from the terminal a second RRC message including an indicator associated with the application layer measurement; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..)
transmitting, to the terminal, a third RRC message including report information, wherein the report information indicates whether transmission of a measurement report associated with the application layer measurement performed in an RRC inactive or an RRC idle is allowed; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..paragraph [0172] explains …..In the first other configuration, one segmentation-permission (rrc-Allowed) field, one measurement configuration application layer addition list field, and one measurement configuration application layer release list field are selectively present.)
and receiving, from the terminal, the measurement report associated with the application layer measurement performed in the RRC inactive or the RRC idle, wherein the configuration information is applied to the RRC idle or the RRC inactive.(see paragraph [0051],[0104], [0105], [0174] explains….The measurement configuration application layer addition list includes one or more measurement configuration application layer; The measurement configuration application layer release list includes one or more measurement configuration application layer identifier.)
Regarding claim 6, Kim teaches a method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a first radio resource control (RRC) message including configuration information associated with an application layer measurement of the terminal; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) performing the application layer measurement in an RRC inactive or an RRC idle based on the first RRC message; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..)
transmitting, to the base station, a second RRC message including an indicator associated with the application layer measurement; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) receiving, from the base station, a third RRC message including report information, wherein the report information indicates whether transmission of a measurement report associated with the application layer measurement performed in an RRC inactive or an RRC idle is allowed; (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..paragraph [0172] explains …..In the first other configuration, one segmentation-permission (rrc-Allowed) field, one measurement configuration application layer addition list field, and one measurement configuration application layer release list field are selectively present.) and transmitting, to the base station, the measurement report associated with the application layer measurement, wherein the configuration information is applied to the RRC idle or the RRC inactive. .(see Kim paragraph [0051],[0104], [0105], [0174] explains….The measurement configuration application layer addition list includes one or more measurement configuration application layer; The measurement configuration application layer release list includes one or more measurement configuration application layer identifier.)
7-8. (Cancelled)
Regarding claim 11, Kim teaches a base station in a wireless communication system, the base station comprising: a transceiver; and a controller configured to: transmit, to a terminal, a first radio resource control (RRC) message including configuration information associated with an application layer measurement of the terminal, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) receive, from the terminal, a second RRC message including an indicator associated with the application layer measurement, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) transmit, to the terminal, a third RRC message including report information, wherein the report information indicates whether transmission of a measurement report associated with the application layer measurement performed in an RRC inactive or an RRC idle is allowed, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..paragraph [0172] explains …..In the first other configuration, one segmentation-permission (rrc-Allowed) field, one measurement configuration application layer addition list field, and one measurement configuration application layer release list field are selectively present.) and receive, from the terminal, the measurement report associated with the application layer measurement performed in the RRC inactive or the RRC idle, and wherein the configuration information is applied to the RRC idle or the RRC inactive. .(see paragraph [0051],[0104], [0105], [0174] explains….The measurement configuration application layer addition list includes one or more measurement configuration application layer; The measurement configuration application layer release list includes one or more measurement configuration application layer identifier.)
12-13. (Cancelled)
Regarding claim 16, Kim teaches a terminal in a wireless communication system, the terminal comprising: a transceiver; and a controller configured to: receive, from a base station, a first radio resource control (RRC) message including configuration information associated with an application layer measurement of the terminal, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) perform the application layer measurement in an RRC inactive or an RRC idle based on the first RRC message, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) transmit, to the base station, a second RRC message including an indicator associated with the application layer measurement, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..) receive, from the base station, a third RRC message including report information, wherein the report information indicates whether transmission of a measurement reportassociated with the application layer measurement performed in an RRC inactive or an RRC idle is allowed, (see Kim paragraph [0056] explains… The application layer measurement configuration and measurement reporting are supported in RRC_CONNECTED state only. Application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to a UE in RRCReconfiguration message 1E-11 and 1E-13. It is further forwarded to UE's higher layer which is application layer for streaming services or for MTSI services.…..paragraph [0172] explains …..In the first other configuration, one segmentation-permission (rrc-Allowed) field, one measurement configuration application layer addition list field, and one measurement configuration application layer release list field are selectively present.) and transmit, to the base station, the measurement report associated with the application layer measurement, wherein the configuration information is applied to the RRC idle or the RRC inactive. .(see paragraph [0051],[0104], [0105], [0174] explains….The measurement configuration application layer addition list includes one or more measurement configuration application layer; The measurement configuration application layer release list includes one or more measurement configuration application layer identifier.)
17-18. (Cancelled)
Claim Rejections - 35 USC § 103
7. 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) A patent may not be obtained through the invention is not identically disclosed or described as set forth in section 102 of this title, if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains. Patentability shall not be negatived by the manner in which the invention was made.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied 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 nonobviousness.
8. Claims 4, 5, 9, 10, 14, 15, 19, 20 are rejected under 35 U.S.C. §103 as being unpatentable over Kim (US 2024/0414799A1) in view of NPL-3GPP TSG RAN WG2 Meeting #121 R2-2300602,
Regarding claim 4, Kim taught the method of claim 1, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the first RRC message is an RRC reconfiguration message or an RRC resume message transmitted to the terminal before the terminal transitions to the RRC idle or the RRC inactive, and wherein the second-third RRC message is an RRC reconfiguration message transmitted to the terminal after the terminal transitions from the RRC idle or the RRC inactive to an RRC connected see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration….also see 2.2)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 5, Kim taught the method of claim 1, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches further comprising:
receiving information associated with a multicast broadcast service (MBS) service type from a core network (CN) entity, wherein the information indicates that configuration information for quality of experience (QoE) applies to a broadcast or a multicast. see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration….also see 2.2)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Cheng with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving QOE measurement in RRC (See Introduction)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with GU. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 9, Kim taught the method of claim 6, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the first RRC message is an RRC reconfiguration message or an RRC resume message received before the terminal transitions to the RRC idle or the RRC inactive, and wherein the RRC message is an RRC reconfiguration message the RRC inactive to an RRC connected. (see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 10, Kim taught the method of claim 6, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the base station receives information associated with a multicast broadcast service (MBS) service type from a core network (CN) entity, and wherein the information indicates that configuration information for quality of experience (QoE) applies to a broadcast or a multicast. (see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 14, Kim taught the base station of claim 11, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the first RRC message is an RRC reconfiguration message or an RRC resume message transmitted to the terminal before the terminal transitions to the RRC idle or the RRC inactive, and wherein the third RRC message is an RRC reconfiguration message transmitted to the terminal after the terminal transitions from the RRC idle or the RRC inactive to an RRC connected. (see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 15, Kim taught the base station of claim 11, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the controller is configured to receive information associated with a multicast broadcast service (MBS) service type from a core network (CN) entity, and wherein the information indicates that configuration information for quality of experience (QoE) applies to a broadcast or a multicast. (see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 19, Kim taught the terminal of claim 16, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches wherein the first RRC message is an RRC reconfiguration message or an RRC resume message received before the terminal transitions to the RRC idle or the RRC inactive, and wherein the third RRC message is an RRC reconfiguration message the RRC inactive to an RRC connected. (see 3GPP 2.1 , conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration….also see 2.2)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
Regarding claim 20, Kim taught the terminal of claim 16, as described above. Kim alone does not explicitly disclose these limitation however further combined with 3GPP teaches The terminal of wherein the base station receives information associated with a multicast broadcast service (MBS) service type from a core network (CN) entity, and wherein the information indicates that configuration information for quality of experience (QoE) applies to a broadcast or a multicast. (see 3GPP 2.1, conclusion explains… QoE measurement for MBS broadcast are configured to UE via the RCC reconfiguration,…. also see 2.2)
It would have been obvious to one of ordinary skill in the art before the effective filling data of the claimed invention to combine Kim with 3GPP. One of ordinary skill in the art would have been motivated to make this modification before the effective filling data of the claimed invention to improving communication with the use of many mobility management operations (See Background)
9. 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 extension fee 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 date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to GERALD A SMARTH whose telephone number is (571)270-1923. The examiner can normally be reached on Monday-Thursday 6am-4:30pm ET.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Joseph Avellino can be reached on 571-272-7784. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/GERALD A SMARTH/Primary Examiner, Art Unit 2478
Prosecution Insights