Prosecution Insights
Last updated: April 19, 2026
Application No. 18/268,542

DATA RETRANSMISSION METHOD AND COMMUNICATION DEVICE

Final Rejection §103
Filed
Jun 20, 2023
Examiner
LIU, SHU
Art Unit
2417
Tech Center
2400 — Computer Networks
Assignee
BEIJING XIAOMI MOBILE SOFTWARE CO., LTD.
OA Round
2 (Final)
100%
Grant Probability
Favorable
3-4
OA Rounds
3y 2m
To Grant
0%
With Interview

Examiner Intelligence

Grants 100% — above average
100%
Career Allow Rate
2 granted / 2 resolved
+42.0% vs TC avg
Minimal -100% lift
Without
With
+-100.0%
Interview Lift
resolved cases with interview
Typical timeline
3y 2m
Avg Prosecution
42 currently pending
Career history
44
Total Applications
across all art units

Statute-Specific Performance

§101
0.9%
-39.1% vs TC avg
§103
74.4%
+34.4% vs TC avg
§102
9.9%
-30.1% vs TC avg
§112
13.5%
-26.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 2 resolved cases

Office Action

§103
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 The amendment filed November 25, 2025 has been accepted and entered. Accordingly, claims 1, 22, 27 and 30 are amended, and claims 6-7 and 26 are cancelled. Claims 1-2, 5, 8-9, 13-22, 27 and 30 are pending in this application. Response to Arguments Applicant’s arguments with respect to claim 1 have been considered but are moot because new ground of rejection relies on the reference not applied in the prior rejection of record for any teaching or matter specifically challenged in the arguments. 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 1-2, 5, 8, 22 and 30 are rejected under 35 U.S.C. 103 as being unpatentable over Baek et al. (US20230299890A1, hereinafter Baek) in view of Baek et al. (US20230397232A1, hereinafter Baek232). For claim 1, Baek teaches a method for data retransmission ([Para. 0038], the method may further include receiving, from the BS, a retransmission resource of the MBS SPS resource), performed by a user equipment ([Para. 0030], a method by which a user equipment (UE) operates), comprising: in response to the failure to receive MBS data (Baek [Para. 0078], when successful transmission of data to be received by the UE using the MBS SPS resource fails, the UE may notify the BS of the transmission failure by transmitting an HARQ NACK message. After receiving the HARQ NACK message, the BS may perform retransmission), monitoring retransmission data scheduling of a multicast broadcast service (MBS) based on a designated retransmission identifier of the MBS (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI). Although teaching monitoring PDCCH based on RNTI for scheduling of retransmission, Baek does not explicitly disclose upon a period starting from a time point of the failure to receive data being equal to a predetermined period. Baek232 is directed to providing method and device for MBS communication in wireless communication system. More specifically, Baek232 teaches upon a period starting from a time point of the failure to receive data being equal to a predetermined period ([Para. 0079], In order for the UE to receive a retransmission, the UE must be able to monitor the PDCCH and receive data at a time when retransmission is possible. To this end, the DRX retransmission timer may be started at a preset time point, and the UE may monitor the PDCCH for retransmission of the base station during this period. The start time of the DRX retransmission timer may be immediately after the HARQ round trip time (RTT) timer expires. [Para. 0085], During the DRX retransmission timer period, the UE may monitor the PDCCH to check whether there are a PDCCH allocated with the G-RNTI and a retransmission resource [Para. 0081], If data to be received in this HARQ process is not successfully received, the UE may have to perform retransmission. To this end, the HARQ RTT timer may be started. [Para. 0090] and [FIG. 1F], Multicast and broadcast services (MBS) assume that a plurality of UEs receive an MBS service. However, the UEs may have different HARQ feedback resources (FB) for MBS data (MBS RX) received through downlink. A constant K1 indicating the time from the received data to the feedback resource may be different for individual UEs. [Para. 0091] and [FIG. 1F], in case of receiving the same MBS service, it is necessary to keep the MBS retransmission scheduling region equal to the length of the DRX retransmission timer by making the start times of the DRX retransmission timers coincide. It is possible to determine the time point when the UE starts the HARQ RTT timer for MBS DRX, as the first symbol after receiving MBS data. The UEs receiving the MBS service can start the HARQ RTT timers in the same way. The base station does not retransmit MBS data during the HARQ RTT timer, and when the HARQ RTT timer expires, it may start the DRX retransmission timer at the next symbol. Even if the feedback resources for MBS data are located at different time points, the UEs start the DRX retransmission timers at the same time, so that the base station can secure an MBS retransmission scheduling region equal to the length of the DRX retransmission timer [Examiner’s Note: The time point of the failure to receive data is the first symbol after receiving MBS data. The period does not depend on the HARQ NACK scheduling, it only depends on HARQ RTT]. [Para. 0071], DRX parameters for an MBS service are: drx-HARQ-RTT-TimerMBS (HARQ RTT timer), drx-RetransmissionTimerMBS (DRX retransmission timer). [Para. 0085], Since the base station knows that retransmission will not be performed during the time in which the HARQ RTT timer of MBS DRX is running. [Examiner’s Note: That base station knows HARQ RTT used by UEs indicates that HARQ RTT itself is also predetermined as a service parameter drx-HARQ-RTT-TimerMBS]). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, so that the wireless device monitors PDCCH immediately HARG RTT time after receiving date transmission, as taught by Baek232. The modification would have utilized resources efficiently by aligning MBS retransmission scheduling regions of one or more terminals receiving MBS (Baek232 [Para. 0017]). For Claim 2, Baek and Baek232 teach the method of claim 1. The references further teach further comprising: determining the designated retransmission identifier of the MBS in response to obtained downlink semi-persistent scheduling (SPS) configuration information (Baek [Para. 0075], the BS may configure an MBS SPS resource by an RRC message transmitted to the UE. Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079], When the data previously transmitted with respect to the resource allocated with the G-CS-RNTI has not been successfully received, the UE may receive a retransmission resource using the G-CS-RNTI. Baek [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI). For claim 5, Baek and Baek232 teach the method of claim 1. The references further teach wherein the designated retransmission identifier of the MBS comprises at least one of following identifiers: a unicast retransmission identifier or a multicast retransmission identifier (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. [Para. 0049], the MBS communication is performed in a multicast method for many specified reception devices Baek [Para. 0126], The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI). For claim 8, Baek and Baek232 teach the method of claim 1. The references further teach wherein monitoring the retransmission data scheduling of the MBS based on the designated retransmission identifier of the MBS comprises (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079], When the data previously transmitted with respect to the resource allocated with the G-CS-RNTI has not been successfully received, the UE may receive a retransmission resource using the G-CS-RNTI. Baek [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI): in response to having been sent a message of failure to receive MBS data to a base station (Baek [Para. 0078], when successful transmission of data to be received by the UE using the MBS SPS resource fails, the UE may notify the BS of the transmission failure by transmitting an HARQ NACK message. After receiving the HARQ NACK message, the BS may perform retransmission), monitoring the retransmission data scheduling of the MBS based on the designated retransmission identifier of the MBS (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. Baek [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI); or in response to a current received data being MBS data, monitoring the retransmission data scheduling of the MBS based on the designated retransmission identifier of the MBS. For claim 22, Baek teaches a method for data retransmission ([Para. 0038], the method may further include receiving, from the BS, a retransmission resource of the MBS SPS resource), performed by a base station (Para. 0038], the method may further include receiving, from the BS, a retransmission resource of the MBS SPS resource), comprising: sending a retransmission identifier for indicating a UE to monitor retransmission data scheduling of an MBS ([Para. 0075], the BS may configure an MBS SPS resource by an RRC message transmitted to the UE. [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI), to the UE via SPS configuration information ([Para. 0075], the BS may configure an MBS SPS resource by an RRC message transmitted to the UE. [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE). Although Beak indicating sending retransmission data based on any retransmission identifier in response of failure (Baek [Para.0078], when successful transmission of data to be received by the UE using the MBS SPS resource fails, the UE may notify the BS of the transmission failure by transmitting an HARQ NACK message. After receiving the HARQ NACK message, the BS may perform retransmission. The retransmission resource may be allocated in a PDCCH using the G-CS-RNTI), Baek232 more specifically discloses and in response to obtaining a message of failure to receive MBS data that is sent by the UE, sending retransmission data of the MBS to the UE based on the retransmission identifier, wherein the retransmission data scheduling is monitored by the UE upon a period starting from a time point of the failure to receive data being equal to a predetermined period. Baek232 is directed to providing method and device for MBS communication in wireless communication system. More specifically, Baek232 teaches and in response to obtaining a message of failure to receive MBS data that is sent by the UE ([Para. 0081], data to be received in the HARQ process indicated by the PDCCH allocation of the G-RNTI may be received. If data to be received in this HARQ process is not successfully received, the UE may have to perform retransmission. [Para. 0082], Starting the HARQ RTT timer at the first symbol after transmitting HARQ feedback [Examiner’s Note: HARQ RTT timer may be started at different point]), sending retransmission data of the MBS to the UE based on the retransmission identifier ([Para. 0090], Multicast and broadcast services (MBS) assume that a plurality of UEs receive an MBS service by using a common group-radio network temporary identifier (G-RNTI). [Para. 0085], During the DRX retransmission timer period, the UE may monitor the PDCCH to check whether there are a PDCCH allocated with the G-RNTI and a retransmission resource [Examiner’s Note: Retransmission is based on G-RNTI]. [Para. 0086], a feedback resource is transmitted on the physical uplink control channel (PDCCH) and a constant K1 indicating the time from the received data to the feedback resource. [Para. 0091], The base station does not retransmit MBS data during the HARQ RTT timer, and when the HARQ RTT timer expires, it may start the DRX retransmission timer at the next symbol. While the DRX retransmission timer is running, the base station may perform MBS data retransmission to the UE), wherein the retransmission data scheduling is monitored by the UE upon a period starting from a time point of the failure to receive data being equal to a predetermined period ([Para. 0079], In order for the UE to receive a retransmission, the UE must be able to monitor the PDCCH and receive data at a time when retransmission is possible. To this end, the DRX retransmission timer may be started at a preset time point, and the UE may monitor the PDCCH for retransmission of the base station during this period. The start time of the DRX retransmission timer may be immediately after the HARQ round trip time (RTT) timer expires. [Para. 0085], During the DRX retransmission timer period, the UE may monitor the PDCCH to check whether there are a PDCCH allocated with the G-RNTI and a retransmission resource. [Para. 0081], If data to be received in this HARQ process is not successfully received, the UE may have to perform retransmission. To this end, the HARQ RTT timer may be started. [Para. 0090] and [FIG. 1F], Multicast and broadcast services (MBS) assume that a plurality of UEs receive an MBS service. However, the UEs may have different HARQ feedback resources (FB) for MBS data (MBS RX) received through downlink. A constant K1 indicating the time from the received data to the feedback resource may be different for individual UEs. [Para. 0091] and [FIG. 1F], in case of receiving the same MBS service, it is necessary to keep the MBS retransmission scheduling region equal to the length of the DRX retransmission timer by making the start times of the DRX retransmission timers coincide. It is possible to determine the time point when the UE starts the HARQ RTT timer for MBS DRX, as the first symbol after receiving MBS data. The UEs receiving the MBS service can start the HARQ RTT timers in the same way. The base station does not retransmit MBS data during the HARQ RTT timer, and when the HARQ RTT timer expires, it may start the DRX retransmission timer at the next symbol. Even if the feedback resources for MBS data are located at different time points, the UEs start the DRX retransmission timers at the same time, so that the base station can secure an MBS retransmission scheduling region equal to the length of the DRX retransmission timer [Examiner’s Note: The time point of the failure to receive data is the first symbol after receiving MBS data. The period does not depend on the HARQ NACK scheduling, it only depends on HARQ RTT]. [Para. 0071], DRX parameters for an MBS service are: drx-HARQ-RTT-TimerMBS (HARQ RTT timer), drx-RetransmissionTimerMBS (DRX retransmission timer). [Para. 0085], Since the base station knows that retransmission will not be performed during the time in which the HARQ RTT timer of MBS DRX is running. [Examiner’s Note: That base station knows HARQ RTT used by UEs indicates that HARQ RTT itself is also predetermined as a service parameter drx-HARQ-RTT-TimerMBS]). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, so that the wireless device monitors PDCCH immediately HARG RTT time after receiving date transmission, as taught by Baek232. The modification would have utilized resources efficiently by aligning MBS retransmission scheduling regions of one or more terminals receiving MBS (Baek232 [Para. 0017]). For claim 30, Baek teaches a communication device ([FIG. 15], UE), comprising: a transceiver ([FIG. 15], Transceiver 1510); a memory ([FIG. 15], Memory 1530); a processor ([FIG. 15], Processor 1520), respectively coupled to the transceiver and the memory ([FIG. 15]), and configured to control wireless signal transmission and reception of the transceiver by executing computer executable instructions on the memory ([Para. 0144], The transceiver 1510 may transmit or receive signals. [0145], the processor 1520 may control signal flows between the respective blocks. [0146], The memory 1530 may store at least one of information received or for transmission by the transceiver 1510 and information generated by the processor 1520), and capable of implementing: in response to the failure to receive MBS data (Baek [Para. 0078], when successful transmission of data to be received by the UE using the MBS SPS resource fails, the UE may notify the BS of the transmission failure by transmitting an HARQ NACK message. After receiving the HARQ NACK message, the BS may perform retransmission), monitoring retransmission data scheduling of a multicast broadcast service (MBS) based on a designated retransmission identifier of the MBS ([Para. 0075], the BS may configure an MBS SPS resource by an RRC message transmitted to the UE. [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI). Although teaching monitoring PDCCH based on RNTI for scheduling of retransmission, Baek does not explicitly disclose upon a period starting from a time point of the failure to receive data being equal to a predetermined period. Baek232 is directed to providing method and device for mbs communication in wireless communication system. More specifically, Baek232 teaches upon a period starting from a time point of the failure to receive data being equal to a predetermined period ([Para. 0079], In order for the UE to receive a retransmission, the UE must be able to monitor the PDCCH and receive data at a time when retransmission is possible. To this end, the DRX retransmission timer may be started at a preset time point, and the UE may monitor the PDCCH for retransmission of the base station during this period. The start time of the DRX retransmission timer may be immediately after the HARQ round trip time (RTT) timer expires. [Para. 0085], During the DRX retransmission timer period, the UE may monitor the PDCCH to check whether there are a PDCCH allocated with the G-RNTI and a retransmission resource [Para. 0081], If data to be received in this HARQ process is not successfully received, the UE may have to perform retransmission. To this end, the HARQ RTT timer may be started. [Para. 0090] and [FIG. 1F], Multicast and broadcast services (MBS) assume that a plurality of UEs receive an MBS service. However, the UEs may have different HARQ feedback resources (FB) for MBS data (MBS RX) received through downlink. A constant K1 indicating the time from the received data to the feedback resource may be different for individual UEs. [Para. 0091] and [FIG. 1F], in case of receiving the same MBS service, it is necessary to keep the MBS retransmission scheduling region equal to the length of the DRX retransmission timer by making the start times of the DRX retransmission timers coincide. It is possible to determine the time point when the UE starts the HARQ RTT timer for MBS DRX, as the first symbol after receiving MBS data. The UEs receiving the MBS service can start the HARQ RTT timers in the same way. The base station does not retransmit MBS data during the HARQ RTT timer, and when the HARQ RTT timer expires, it may start the DRX retransmission timer at the next symbol. Even if the feedback resources for MBS data are located at different time points, the UEs start the DRX retransmission timers at the same time, so that the base station can secure an MBS retransmission scheduling region equal to the length of the DRX retransmission timer [Examiner’s Note: The time point of the failure to receive data is the first symbol after receiving MBS data. The period does not depend on the HARQ NACK scheduling, it only depends on HARQ RTT]. [Para. 0071], DRX parameters for an MBS service are: drx-HARQ-RTT-TimerMBS (HARQ RTT timer), drx-RetransmissionTimerMBS (DRX retransmission timer). [Para. 0085], Since the base station knows that retransmission will not be performed during the time in which the HARQ RTT timer of MBS DRX is running. [Examiner’s Note: That base station knows HARQ RTT used by UEs indicates that HARQ RTT itself is also predetermined as a service parameter drx-HARQ-RTT-TimerMBS]). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, so that the wireless device monitors PDCCH immediately HARG RTT time after receiving date transmission, as taught by Baek232. The modification would have utilized resources efficiently by aligning MBS retransmission scheduling regions of one or more terminals receiving MBS (Baek232 [Para. 0017]). Claims 9, 13 and 27 are rejected under 35 U.S.C. 103 as being unpatentable over Baek et al. (US20230299890A1, hereinafter Baek) in view of Baek et al. (US20230397232A1, hereinafter Baek232), Zhou et al. (US20230063082A1, hereinafter Zhou), and further in view of Huang et al. (Huang et al. (US20250126679A1, hereinafter Huang). For claim 9, Baek and Baek232 teach method of claim 1. The references further teach and monitoring the retransmission data scheduling of the MBS based on the designated retransmission identifier of the MBS comprises at least one of: monitoring the retransmission data scheduling of the MBS based on either the unicast retransmission identifier or the multicast retransmission identifier (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI [Para. 0049], the MBS communication is performed in a multicast method for many specified reception devices. Baek [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI), or determining a target retransmission identifier based on reception time points of retransmission scheduling indications identified by the unicast retransmission identifier and the multicast retransmission identifier respectively, and monitoring the retransmission data scheduling of the MBS based on the target retransmission identifier; or monitoring the retransmission data scheduling of the MBS respectively based on the unicast retransmission identifier and the multicast retransmission identifier, and determining retransmission data identified by any retransmission identifier as a target retransmission data in response to a reception time point of the retransmission data identified by any retransmission identifier being earlier than a reception time point of retransmission data identified by another retransmission identifier; or monitoring first retransmission data scheduling of the MBS based on the unicast retransmission identifier, monitoring second retransmission data scheduling of the MBS based on the multicast retransmission identifier, and performing combined decoding on first retransmission data and second retransmission data. Although teaching monitoring PDCCH based on RNTI for scheduling of retransmission based on a multicast retransmission identifier as noted above, Baek and Baek232 do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Zhou is directed to providing discontinuous reception operation of multicast and broadcast services. More specifically, Zhou teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0292], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the MBS-RNTI. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. [Para. 0297], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the C-RNTI. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. [Para. 0331], the wireless device may not have knowledge, in advance, of whether a retransmission of the MBS TB is via a unicast PDSCH resource or via a multicast PDSCH resource. [Para. 0390] and [FIG. 38], The wireless device may receive the group common DCI (e.g., 2nd DCI with MBS-RNTI at T1 in FIG. 38) scheduling the retransmission of the MBS TB. [Para. 0400], The wireless device may receive the UE specific DCI (e.g., 3rd DCI with C-RNTI at T3 in FIG. 38 ) scheduling the retransmission of the MBS TB. The wireless device may receive the retransmission of the MBS TB (e.g., at T4 in FIG. 38). [Para. 0401], The base station may determine a unicast retransmission (by the 2nd DCI) or a multicast retransmission (by the 3rd DCI) of the MBS TB). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Beak232, so that the retransmission data may be transmitted via either unicast or multicast, as taught by Zhou. The modification would have supported DRX operation to improve UE battery lifetime (Zhou [Para. 0301]). Although teaching monitoring the designated retransmission identifier of the MBS may be a unicast retransmission identifier or a multicast retransmission identifier. Baek, Baek232 and Zhou do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Huang is directed to providing communication method and related product. More specifically, Huang teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0278], The user equipment C may notify, by using feedback information, an access network device of a data packet that needs to be retransmitted. In a process of retransmitting a data packet, the user equipment may receive the multicast service data in both a multicast manner and a unicast manner). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232 and Zhou, so that the retransmission data may be transmitted via both unicast and multicast, as taught by Huang. The modification would have improved the transmission efficiency of the multicast communication (Huang [Para. 0006]). For claim 13, Baek and Baek232 teach the method of claim 1. The references further teach and monitoring the retransmission data scheduling of the MBS based on the designated retransmission identifier of the MBS comprises: in response to successful decoding of retransmission data of the MBS obtained based on any retransmission identifier, stopping monitoring retransmission data scheduling of the MBS associated with another retransmission identifier (Baek [Para. 0079], When data previously transmitted with respect to the resource allocated with the G-CS-RNTI has been successfully received, there is no need to receive the resource allocated with the G-CS-RNTI again). Although teaching monitoring PDCCH based on RNTI for scheduling of retransmission, Baek and Baek232 do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Zhou is directed to providing discontinuous reception operation of multicast and broadcast services. More specifically, Zhou teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0292], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the MBS-RNTI. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. [Para. 0297], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the C-RNTI. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. [Para. 0331], the wireless device may not have knowledge, in advance, of whether a retransmission of the MBS TB is via a unicast PDSCH resource or via a multicast PDSCH resource. [Para. 0390] and [FIG. 38], The wireless device may receive the group common DCI (e.g., 2nd DCI with MBS-RNTI at T1 in FIG. 38) scheduling the retransmission of the MBS TB. [Para. 0400], The wireless device may receive the UE specific DCI (e.g., 3rd DCI with C-RNTI at T3 in FIG. 38) scheduling the retransmission of the MBS TB. The wireless device may receive the retransmission of the MBS TB (e.g., at T4 in FIG. 38). [Para. 0401], The base station may determine a unicast retransmission (by the 2nd DCI) or a multicast retransmission (by the 3rd DCI) of the MBS TB). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the retransmission data may be transmitted via either unicast or multicast, as taught by Zhou. The modification would have supported DRX operation to improve UE battery lifetime (Zhou [Para. 0301]). Although teaching monitoring the designated retransmission identifier of the MBS may be a unicast retransmission identifier or a multicast retransmission identifier. Baek, Baek232 and Zhou do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Huang is directed to providing communication method and related product. More specifically, Huang teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0278], The user equipment C may notify, by using feedback information, an access network device of a data packet that needs to be retransmitted. In a process of retransmitting a data packet, the user equipment may receive the multicast service data in both a multicast manner and a unicast manner). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232 and Zhou, so that the retransmission data may be transmitted via both unicast and multicast, as taught by Huang. The modification would have improved the transmission efficiency of the multicast communication (Huang [Para. 0006]). For claim 27, Baek and Baek232 teach the method of claim 22. The references further teach wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier (Baek [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. Baek [Para. 0126], The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI), and sending the retransmission data of the MBS to the UE based on the retransmission identifier comprises: sending the retransmission data of the MBS to the UE based on any retransmission identifier (Baek [Para. 0077], A group-configured scheduling-transmission radio network temporary identifier (G-CS-RNTI) may be included in the MBS SPS configuration information to be configured for the UE. Baek [Para. 0079], When the data previously transmitted with respect to the resource allocated with the G-CS-RNTI has not been successfully received, the UE may receive a retransmission resource using the G-CS-RNTI. Baek [Para. 0126], the BS may allocate a retransmission resource of an MBS SPS resource to the UE based on the feedback. The UE may be allocated by the BS the retransmission resource for MBS SPS. The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI). Although teaching sending retransmission data based on any retransmission identifier, Baek and Baek232 do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Zhou is directed to providing discontinuous reception operation of multicast and broadcast services. More specifically, Zhou teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0292], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the MBS-RNTI. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. [Para. 0297], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the C-RNTI. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. [Para. 0331], the wireless device may not have knowledge, in advance, of whether a retransmission of the MBS TB is via a unicast PDSCH resource or via a multicast PDSCH resource. [Para. 0390] and [FIG. 38], The wireless device may receive the group common DCI (e.g., 2nd DCI with MBS-RNTI at T1 in FIG. 38) scheduling the retransmission of the MBS TB. [Para. 0400], The wireless device may receive the UE specific DCI (e.g., 3rd DCI with C-RNTI at T3 in FIG. 38) scheduling the retransmission of the MBS TB. The wireless device may receive the retransmission of the MBS TB (e.g., at T4 in FIG. 38). [Para. 0401], The base station may determine a unicast retransmission (by the 2nd DCI) or a multicast retransmission (by the 3rd DCI) of the MBS TB). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the retransmission data may be transmitted via either unicast or multicast, as taught by Zhou. The modification would have supported DRX operation to improve UE battery lifetime (Zhou [Para. 0301]). Although teaching monitoring the designated retransmission identifier of the MBS may be a unicast retransmission identifier or a multicast retransmission identifier. Baek, Baek232 and Zhou do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Huang is directed to providing communication method and related product. More specifically, Huang teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0278], The user equipment C may notify, by using feedback information, an access network device of a data packet that needs to be retransmitted. In a process of retransmitting a data packet, the user equipment may receive the multicast service data in both a multicast manner and a unicast manner). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232 and Zhou, so that the retransmission data may be transmitted via both unicast and multicast, as taught by Huang. The modification would have improved the transmission efficiency of the multicast communication (Huang [Para. 0006]). Claims 14-15 are rejected under 35 U.S.C. 103 as being unpatentable over Baek et al. (US20230299890A1, hereinafter Baek) in view of Baek et al. (US20230397232A1, hereinafter Baek232), and further in view of Chou (US20230403537A1, hereinafter Chou). For claim 14, Baek and Baek232 teach the method of claim 1. Although teaching monitoring PDCCH based on RNTI for scheduling of retransmission, the references do not explicitly disclose further comprising: sending an indication message of reception of retransmission data of the MBS to a base station based on a designated uplink scheduling resource. Chou is directed to providing hybrid automatic repeat request procedures for multimedia broadcast and multicast services. More specifically, Chou teaches further comprising: sending an indication message of reception of retransmission data of the MBS to a base station based on a designated uplink scheduling resource ([Para. 0071] and [FIG. 3C], If the UE 102 fails to successfully receive or decode the second TB, the UE 102 sends 342C a NACK to the second TB on the first PUCCH resource. The base station 104 responds by transmitting 344C a DCI 3 including an updated resource allocation for the second TB and a second PUCCH resource indicator to the UE 102. The DCI 3 may be sent via multicast (i.e., the base station 104 may scramble a CRC of the DCI 3 with the G-RNTI 2), or may be sent via unicast only to the UE 102 (i.e., the base station may scramble a CRC of the DCI 3 with a cell RNTI (C-RNTI) associated with the UE 102). The base station 104 transmits 346C the second TB in accordance with the DCI 3. If the UE 102 soft combines and successfully decodes the second TB, the UE 102 sends 348C the base station 104 an ACK on the second PUCCH resource indicated by the DCI 3). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the UE transmits ACK in PUCCH scheduled in DCI for retransmission, as taught by Chou. The modification would have supported feedback form the UE regarding MBS transmissions to the RAN, especially in scenarios where the UE switches between MBS services or consumes multiple MBS services concurrently (Chou [Para. 0008]). For claim 15, Baek, Baek232 and Chou teach the method of claim 14. The references further teach further comprising: sending an indication message indicating successful reception of retransmission data to the base station in response to successful decoding of at least one piece of retransmitted data (Chou [Para. 0071] and [FIG. 3C], If the UE 102 fails to successfully receive or decode the second TB, the UE 102 sends 342C a NACK to the second TB on the first PUCCH resource. The base station 104 responds by transmitting 344C a DCI 3 including an updated resource allocation for the second TB and a second PUCCH resource indicator to the UE 102. The DCI 3 may be sent via multicast (i.e., the base station 104 may scramble a CRC of the DCI 3 with the G-RNTI 2), or may be sent via unicast only to the UE 102 (i.e., the base station may scramble a CRC of the DCI 3 with a cell RNTI (C-RNTI) associated with the UE 102). The base station 104 transmits 346C the second TB in accordance with the DCI 3. If the UE 102 soft combines and successfully decodes the second TB, the UE 102 sends 348C the base station 104 an ACK on the second PUCCH resource indicated by the DCI 3); or sending an indication message indicating reception failure of the retransmission data to the base station in response to decoding failure of at least one piece of retransmission data; or sending an indication message indicating reception failure of the retransmission data to the base station in response to decoding failure of all retransmission data; or sending an indication message indicating successful reception of any retransmission data to the base station in response to successful decoding of any retransmission data; or sending an indication message indicating reception failure of any retransmission data to the base station in response to decoding failure of any retransmission data. It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the UE transmits ACK in PUCCH scheduled in DCI for retransmission, as taught by Chou. The modification would have supported feedback form the UE regarding MBS transmissions to the RAN, especially in scenarios where the UE switches between MBS services or consumes multiple MBS services concurrently (Chou [Para. 0008]). Claims 16 and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Baek et al. (US20230299890A1, hereinafter Baek) in view of Baek et al. (US20230397232A1, hereinafter Baek232) and Chou (US20230403537A1, hereinafter Chou), Zhou et al. (US20230063082A1, hereinafter Zhou) and further in view of Huang et al. (Huang et al. (US20250126679A1, hereinafter Huang). For claim 16, Baek, Baek232 and Chou teach the method of claim 14. The references further teach wherein the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier (Baek [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. Baek [Para. 0126], The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI), and the designated uplink scheduling resource is an uplink scheduling resource corresponding to any retransmission identifier (Chou [Para. 0071] and [FIG. 3C], If the UE 102 fails to successfully receive or decode the second TB, the UE 102 sends 342C a NACK to the second TB on the first PUCCH resource. The base station 104 responds by transmitting 344C a DCI 3 including an updated resource allocation for the second TB and a second PUCCH resource indicator to the UE 102. The DCI 3 may be sent via multicast (i.e., the base station 104 may scramble a CRC of the DCI 3 with the G-RNTI 2), or may be sent via unicast only to the UE 102 (i.e., the base station may scramble a CRC of the DCI 3 with a cell RNTI (C-RNTI) associated with the UE 102). The base station 104 transmits 346C the second TB in accordance with the DCI 3. If the UE 102 soft combines and successfully decodes the second TB, the UE 102 sends 348C the base station 104 an ACK on the second PUCCH resource indicated by the DCI 3). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the UE transmits ACK in PUCCH scheduled in DCI for retransmission, as taught by Chou. The modification would have supported feedback form the UE regarding MBS transmissions to the RAN, especially in scenarios where the UE switches between MBS services or consumes multiple MBS services concurrently (Chou [Para. 0008]). Although teaching designated uplink scheduling for ACK corresponds to the retransmission identifier, Baek, Baek232 and Chou do not explicitly disclose wherein the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Zhou is directed to providing discontinuous reception operation of multicast and broadcast services. More specifically, Zhou teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0292], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the MBS-RNTI. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. [Para. 0297], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the C-RNTI. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. [Para. 0331], the wireless device may not have knowledge, in advance, of whether a retransmission of the MBS TB is via a unicast PDSCH resource or via a multicast PDSCH resource. [Para. 0390] and [FIG. 38], The wireless device may receive the group common DCI (e.g., 2nd DCI with MBS-RNTI at T1 in FIG. 38) scheduling the retransmission of the MBS TB. [Para. 0400], The wireless device may receive the UE specific DCI (e.g., 3rd DCI with C-RNTI at T3 in FIG. 38 ) scheduling the retransmission of the MBS TB. The wireless device may receive the retransmission of the MBS TB (e.g., at T4 in FIG. 38). [Para. 0401], The base station may determine a unicast retransmission (by the 2nd DCI) or a multicast retransmission (by the 3rd DCI) of the MBS TB). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232 and Chou, so that the retransmission data may be transmitted via either unicast or multicast, as taught by Zhou. The modification would have supported DRX operation to improve UE battery lifetime (Zhou [Para. 0301]). Although teaching monitoring the designated retransmission identifier of the MBS may be a unicast retransmission identifier or a multicast retransmission identifier. Baek, Baek232, Chou and Zhou do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Huang is directed to providing communication method and related product. More specifically, Huang teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0278], The user equipment C may notify, by using feedback information, an access network device of a data packet that needs to be retransmitted. In a process of retransmitting a data packet, the user equipment may receive the multicast service data in both a multicast manner and a unicast manner). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232, Chou and Zhou, so that the retransmission data may be transmitted via both unicast and multicast, as taught by Huang. The modification would have improved the transmission efficiency of the multicast communication (Huang [Para. 0006]). For claim 18, Baek, Baek232 and Chou teach the method of claim 14. The references further teach wherein the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier (Baek [Para. 0079, 0094], Only when an initial transmission resource transmitted with the MBS SPS resource is not successfully received, the UE receives a resource allocated using the G-CS-RNTI. Baek [Para. 0126], The retransmission resource may be transmitted in a DCI format of a PDCCH using the G-CS-RNTI), and the method further comprises: determining an uplink scheduling resource corresponding to a retransmission identifier associated with successfully decoded retransmission data as the designated uplink scheduling resource (Chou [Para. 0071] and [FIG. 3C], If the UE 102 fails to successfully receive or decode the second TB, the UE 102 sends 342C a NACK to the second TB on the first PUCCH resource. The base station 104 responds by transmitting 344C a DCI 3 including an updated resource allocation for the second TB and a second PUCCH resource indicator to the UE 102. The DCI 3 may be sent via multicast (i.e., the base station 104 may scramble a CRC of the DCI 3 with the G-RNTI 2), or may be sent via unicast only to the UE 102 (i.e., the base station may scramble a CRC of the DCI 3 with a cell RNTI (C-RNTI) associated with the UE 102). The base station 104 transmits 346C the second TB in accordance with the DCI 3. If the UE 102 soft combines and successfully decodes the second TB, the UE 102 sends 348C the base station 104 an ACK on the second PUCCH resource indicated by the DCI 3). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek and Baek232, so that the UE transmits ACK in PUCCH scheduled in DCI for retransmission, as taught by Chou. The modification would have supported feedback form the UE regarding MBS transmissions to the RAN, especially in scenarios where the UE switches between MBS services or consumes multiple MBS services concurrently (Chou [Para. 0008]). Although teaching designated uplink scheduling for ACK corresponds to the retransmission identifier, Baek, Baek232 and Chou do not explicitly disclose wherein the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Zhou is directed to providing discontinuous reception operation of multicast and broadcast services. More specifically, Zhou teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0292], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the MBS-RNTI. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. [Para. 0297], The base station may, based on the received HARQ NACK, transmit a second DCI with CRC scrambled by the C-RNTI. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. [Para. 0331], the wireless device may not have knowledge, in advance, of whether a retransmission of the MBS TB is via a unicast PDSCH resource or via a multicast PDSCH resource. [Para. 0390] and [FIG. 38], The wireless device may receive the group common DCI (e.g., 2nd DCI with MBS-RNTI at T1 in FIG. 38) scheduling the retransmission of the MBS TB. [Para. 0400], The wireless device may receive the UE specific DCI (e.g., 3rd DCI with C-RNTI at T3 in FIG. 38) scheduling the retransmission of the MBS TB. The wireless device may receive the retransmission of the MBS TB (e.g., at T4 in FIG. 38). [Para. 0401], The base station may determine a unicast retransmission (by the 2nd DCI) or a multicast retransmission (by the 3rd DCI) of the MBS TB). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232 and Chou, so that the retransmission data may be transmitted via either unicast or multicast, as taught by Zhou. The modification would have supported DRX operation to improve UE battery lifetime (Zhou [Para. 0301]). Although teaching monitoring the designated retransmission identifier of the MBS may be a unicast retransmission identifier or a multicast retransmission identifier. Baek, Baek232 and Zhou do not explicitly disclose wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier. Huang is directed to providing communication method and related product. More specifically, Huang teaches wherein, the designated retransmission identifier of the MBS comprises a unicast retransmission identifier and a multicast retransmission identifier ([Para. 0278], The user equipment C may notify, by using feedback information, an access network device of a data packet that needs to be retransmitted. In a process of retransmitting a data packet, the user equipment may receive the multicast service data in both a multicast manner and a unicast manner). It would have been prima facie obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Baek, Baek232, Chou and Zhou, so that the retransmission data may be transmitted via both unicast and multicast, as taught by Huang. The modification would have improved the transmission efficiency of the multicast communication (Huang [Para. 0006]). Allowable Subject Matter Claims 17 and 19-21 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. 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 SHU LIU whose telephone number is (571)272-5186. The examiner can normally be reached Monday - Friday 9:00 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, REBECCA E SONG can be reached at (571)270-3667. 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. /S.L./Examiner, Art Unit 2417 /REBECCA E SONG/Supervisory Patent Examiner, Art Unit 2417
Read full office action

Prosecution Timeline

Jun 20, 2023
Application Filed
Aug 23, 2025
Non-Final Rejection — §103
Nov 25, 2025
Response Filed
Mar 19, 2026
Final Rejection — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12588064
TECHNIQUES RELATING TO RANDOM ACCESS IN A WIRELESS COMMUNICATIONS NETWORK
2y 5m to grant Granted Mar 24, 2026
Patent 12587990
METHODS AND APPARATUSES FOR ZERO TRUST CELL BROADCASTS
2y 5m to grant Granted Mar 24, 2026
Study what changed to get past this examiner. Based on 2 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
100%
Grant Probability
0%
With Interview (-100.0%)
3y 2m
Median Time to Grant
Moderate
PTA Risk
Based on 2 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

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

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month