Office Action Predictor
Last updated: April 15, 2026
Application No. 18/029,998

MBS DATA PROCESSING METHOD AND DEVICE

Final Rejection §103
Filed
Apr 03, 2023
Examiner
SIDDIQUEE, INTEKHAAB AALAM
Art Unit
2462
Tech Center
2400 — Computer Networks
Assignee
Kt Corporation
OA Round
2 (Final)
80%
Grant Probability
Favorable
3-4
OA Rounds
2y 5m
To Grant
83%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allow Rate
234 granted / 291 resolved
+22.4% vs TC avg
Minimal +2% lift
Without
With
+2.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 5m
Avg Prosecution
35 currently pending
Career history
326
Total Applications
across all art units

Statute-Specific Performance

§101
1.9%
-38.1% vs TC avg
§103
73.5%
+33.5% vs TC avg
§102
8.1%
-31.9% vs TC avg
§112
6.1%
-33.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 291 resolved cases

Office Action

§103
DETAILED ACTION Response filed on 9/18/2025 has been entered and made of record. 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 status Claims 18, 22, and 26 are amended. Claims 1-17, 20, 24, and 28 are canceled. Claims 18-19, 21- 23, 25-27, and 29 are pending for examination. Response to arguments Re: 35 U.S.C. § 103 rejection. Applicant’s response has been fully considered but is moot in view of claim amendments are new grounds of rejection. 35 U.S.C. § 103 rejection is not withdrawn. 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 nonobviousness. Claims 18, 22, and 26 are rejected under 35 U.S.C. 103 as being unpatentable over R2-2007033, “ Overview of NR MBS”, 3GPP TSG-RAN WG2 Meeting #111-e Electronic meeting, 17th – 28th August 2020, hereinafter “vivo” in view of Ronneke Has Bertil et al. (WO-2021229346-A1), hereinafter “Hans”. Claims 18, 22, and 26: Regarding claim 18, Vivo teaches, a method for processing multicast and broadcast services (MBS) data by a user equipment (UE) (see [Introduction]), the method comprising: switching a radio resource control (RRC) state to an RRC inactive state (implied by the disclosure by vivo: § 2.2, “To support the IDLE/INACTIVE UE reception of the MBS service, we could have the following options: Option 1: The MBS configuration is sent via the RRC release message.”; a release message would switch a radio resource control state to an RRC inactive state); receiving a paging message transmitted from a base station according to MBS session activation or MBS data reception of the base station (vivo: § 2.2 if the network wants to update the MBS configuration, the network would also need to page the UE in order to provide the updated MBS configuration to the UE.”). Regarding claim element, initiating an RRC connection resume procedure for an RRC state change based on the paging message, though vivo does not expressly teach it, it would have been obvious to a person of ordinary skill before the effective filing date of the claimed invention to come up with this claim element based on vivo disclosure, “The drawbacks of Option 1 is that it requires the UE to enter the CONNECTED” (vivo: §2.2). RRC connection establishment is necessary so that MBS service configuration could be sent to the UE via dedicated message. Vivo discloses, “the dedicated signalling would be faster than the broadcast signalling for the CONNECTED UE” (§ 2.2). Vivo does not expressly teach, ‘wherein initiating the RRC connection resume procedure is triggering the RRC connection resume procedure when the UE joins an MBS session included in the paging message’, but in the same field of endeavor Hans teaches the claim, implied by the following: Fig.5, steps 7-9 “ UEs respond to the Group paging e.g. by sending UL NAS MB Session Join Request (TMGI) to AMF (see clause 6.2.2.1 step 6 to 8); Fig.5, steps 11 “If there are UEs in CM-Connected with RRC_INACTIVE state with the TMGI in their UE Contexts, NG-RAN performs the Network triggered transition from RRC_INACTIVE to RRC_CONNECTED procedure for those UEs (see TS 38.300 [x])”; [0086] (in reference to Fig.7) “This is probably the most common sequence for mission critical group calls. FIG. 8 shows the sequence for the first UE in a cell, i.e. when the MB Session resources has to be established in the cell before reception can commence.”; and [0087] (in reference to Fig.7 step 1) “The new UE indicates its interest to join the MB Session by sending an UL NAS MB Session Join Request (TMGI) message.”. The disclosures above by Hans shows that joining the MBS session happens after triggering from network and that the transition to RRC_CONNECTED state, implying connection resume procedure. It would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to combine disclosure by Hans with that of Huawei to come up with the claimed invention motivated by joining an MBS session when triggered by network. Claims 22 is for method by a base station, the method being complimentary to the method by user equipment of claim 18. Claim is rejected based on rejection of claim 18. Claim 26 is for user equipment performing method of claim 18. The claim is change in category with respect to claim 18. Claim is rejected based on rejection of claim 18. Claims 19, 23, and 27 are rejected under 35 U.S.C. 103 as being unpatentable over combination of vivo and Hans as applied to claim 18 above, and further in view of R2-2007029, “IDLE/INACTIVE UE support for NR MBS”, 3GPP TSG-RAN WG2 Meeting #111-e, Electronic meeting, 17th – 28th August 2020, hereinafter “Huawei”. Claims 19, 23, and 27: Regarding claim 19, vivo teaches the method of claim 18 (discussed above). Vivo however fails to expressly teach but in the same field of endeavor Huawei teaches, wherein the paging message includes one or more pieces of MBS session identification information, and wherein the MBS session identification information includes at least one of temporary mobile group identity (TMGI), MBS session identifier (ID), and internet protocol (IP) multicast address information (Huawei: 2.3.2 “to avoid bringing the UEs that are not interested in this service to RRC_CONNECTED state, assistant information, i.e. the service ID or TMGI of this service, might be included to the paging message.”). It would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to combine disclosure by Huawei with that of combination of vivo and Hans and come up with the claimed invention to avoid bringing the UEs that are not interested in this service to RRC_CONNECTED state, as disclosed by Huawei. As per discussion above in claim 18, claims 23 and 27 are also rejected based on rejection of claim 19. Claims 21, 25, and 29 are rejected under 35 U.S.C. 103 as being unpatentable over vivo as applied to claim 18 above, and further in view of Fujishiro et al. (US 20190182632 A1), hereinafter “Fujishiro”. Claims 21, 25, and 29: Regarding claim 21, vivo teaches the method of claim 18 (discussed above). Vivo however fails to expressly teach but in the same field of endeavor Fujishiro teaches, wherein the switching further includes suspending an MBS radio bearer for the MBS session (Fujishiro: [0089] The UE 100 may receive the MBMS service in the RRC connected mode. The UE 100 may receive the MBMS service in the RRC idle mode. In the following, the case where the UE 100 receives the MBMS service in the RRC idle mode is mainly assumed. It is noted that the RRC idle mode includes a suspend state. In the suspend state, since the context information of the UE 100 is maintained in the eNB 200, the RRC connection can be promptly restored.”. It would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to combine disclosure by Fujishiro with that of vivo so as to maintain the context information in the suspend state and promptly restore RRC connection as described above. As per discussion above in claim 18, claims 25 and 29 are also rejected based on rejection of claim 20. 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 INTEKHAAB AALAM SIDDIQUEE whose telephone number is (571)272-0895. The examiner can normally be reached Monday to Friday 9AM-5PM EST. 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, Yemane Mesfin can be reached at 571-272-3927. 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. /INTEKHAAB A SIDDIQUEE/Primary Examiner, Art Unit 2462
Read full office action

Prosecution Timeline

Apr 03, 2023
Application Filed
Apr 03, 2023
Response after Non-Final Action
Jun 14, 2025
Non-Final Rejection — §103
Sep 18, 2025
Response Filed
Dec 26, 2025
Final Rejection — §103
Mar 30, 2026
Request for Continued Examination
Apr 07, 2026
Response after Non-Final Action

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12593330
COMMUNICATIONS METHOD AND APPARATUS
2y 5m to grant Granted Mar 31, 2026
Patent 12593250
SIDELINK TRANSMISSION CONTROL METHOD, TRANSMIT TERMINAL, AND RECEIVE TERMINAL
2y 5m to grant Granted Mar 31, 2026
Patent 12581482
DATA TRANSMISSION MANAGEMENT IN RADIO RESOURCE CONTROL (RRC) INACTIVE STATE
2y 5m to grant Granted Mar 17, 2026
Patent 12574848
METHOD FOR CONTROLLING COMMUNICATION IN DRX
2y 5m to grant Granted Mar 10, 2026
Patent 12574751
METHOD FOR SETTING COMMUNICATION SCHEME, AND ELECTRONIC DEVICE USING SAME
2y 5m to grant Granted Mar 10, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

3-4
Expected OA Rounds
80%
Grant Probability
83%
With Interview (+2.4%)
2y 5m
Median Time to Grant
Moderate
PTA Risk
Based on 291 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in for Full Analysis

Enter your email to receive a magic link. No password needed.

Free tier: 3 strategy analyses per month