Prosecution Insights
Last updated: July 17, 2026
Application No. 18/758,034

METHOD AND APPARATUS FOR TRANSCEIVING INFORMATION, AND COMMUNICATION SYSTEM

Non-Final OA §102§112
Filed
Jun 28, 2024
Priority
Jan 07, 2022 — continuation of PCTCN2022070768
Examiner
ZHU, BO HUI ALVIN
Art Unit
Tech Center
Assignee
1FINITY Inc.
OA Round
1 (Non-Final)
80%
Grant Probability
Favorable
1-2
OA Rounds
1y 1m
Est. Remaining
96%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allowance Rate
631 granted / 785 resolved
+20.4% vs TC avg
Strong +16% interview lift
Without
With
+16.1%
Interview Lift
resolved cases with interview
Typical timeline
3y 1m
Avg Prosecution
23 currently pending
Career history
811
Total Applications
across all art units

Statute-Specific Performance

§101
1.4%
-38.6% vs TC avg
§103
70.4%
+30.4% vs TC avg
§102
18.1%
-21.9% vs TC avg
§112
8.8%
-31.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 785 resolved cases

Office Action

§102 §112
DETAILED ACTION Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Claim Objections Claims 3, 12, 14 and 15 are objected to because of the following informalities: Claim 3: “SRAP” should change to “sidelink relay adaptation protocol (SRAP)”. Claim 12: “Relay Adaptation Protocol (SRAP)” should change to “a Sidelink Relay Adaptation Protocol (SRAP)”. Appropriate correction is required. Claim 14: “SRAP entity” should change to “a sidelink relay adaptation protocol (SRAP) entity”. Claim 15: “processer” should change to “processor”. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 7-9, 13, and 15-18 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. Regarding claim 7, “the signaling radio bearer 0 (SRB0) message” lacks antecedent basis. Regarding claim 8, it is unclear whether “(the remote UE)” in line 6 is an essential claim limitation or merely a citation to a reference. Regarding claim 9, “the SRAP-related configuration” lacks antecedent basis. Regarding claim 13, “the default SRAP related configuration” and “the relevant configuration of SRAP” lack antecedent basis. Regarding claim 15, it is unclear whether “(a relay UE)” in line 2 is an essential claim limitation or merely a citation to a reference. Claims 16-18 are rejected because they depend from claim 15. Claim Rejections - 35 USC § 102 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 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. Claims 1-18 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Pan (US 2022/0210847 A1, hereinafter “Pan”). Regarding claim 1: Pan discloses an apparatus (e.g., 300 in Fig. 3), applicable to a first terminal equipment (e.g., UE1 in Fig. 23), the apparatus comprising: processor circuitry (e.g., 306 in Fig. 3) configured to control to establish PC5 connection with a second terminal equipment (e.g., UE2 in Fig, 23); and a receiver (e.g., 314 in Fig. 3) configured to receive a radio resource control (RRC) message via the second terminal equipment by means of default configuration (e.g., Fig. 18, “RRCSetup”, “SecurityModeCommand”, “RRReconfigurationComplete”, Fig. 23, “UE1’s RRCREsume in sent on specific PC5 RLC channel (for UE1’s Uu SRB1)”). Regarding claim 2: Pan further discloses the apparatus according to claim 1, wherein the RRC message is at least one of a radio resource control setup (RRC setup) message, a radio resource control resume (RRC resume) message, a radio resource control re-establishment (RRC re-establishment) message and a radio resource control reconfiguration (RRC reconfiguration) message (e.g., Fig. 23, UE1’s RRCResume). Regarding claim 3: Pan further discloses the apparatus according to claim 2, wherein, the receiver receives a signaling radio bearer 1 (SRB1) message by using default SRAP configuration of SRB1 and/or SL-RLC1 default configuration at the PC5 interface between the first terminal equipment and the second terminal equipment (e.g., Fig. 23, UE1’s Uu SRB1, see PC5 RLC channel and Uu SRB mapping in Fig. 21). Regarding claim 4: Pan further discloses the apparatus according to claim 1, wherein, the default configuration includes default sidelink radio link control bearer configuration (sidelink RLC bearer configuration) and/or default sidelink relay adaptation protocol (SRAP)-related configuration (e.g., PC5 RLC channel and Uu SRB mapping in Fig. 21). Regarding claim 5: Pan further discloses the apparatus according to claim 4, wherein, the default sidelink radio link control bearer configuration is sidelink radio link control 0 (SL-RLC0) default configuration or sidelink radio link control 1 (SL-RLC1) default configuration (e.g., PC5 RLC channel mapping in Fig. 21). Regarding claim 6: Pan further discloses the apparatus according to claim 4, wherein, the default SRAP-related configuration includes at least one of the following: a local or temporary identifier of the first terminal equipment, an added mapping list or a deleted mapping list, and default SRAP configuration of signaling radio bearer 0 (SRB0) and/or default SRAP configuration of signaling radio bearer 1 (SRB1) (e.g., [0774]-[0775], mapping between Uu SRB, PC5 RLC channel, and Uu RLC channel in Fig. 21). Regarding claim 7: Pan further discloses the SRB1 message carries the RRC resume message and/or the RRC re-establishment message, or the SRB1 message is a first SRB1 message to be received by the first terminal equipment after the signaling radio bearer 0 (SRB0) message of the first terminal equipment is transmitted to the network apparatus (e.g., [0777], remote UE receives RRCResume on the PC5 RLC channel mapped to Uu SRB1). Regarding claim 8: Pan further discloses wherein the processor circuitry is further configured to control to use the SRB1 default SRAP configuration and/or use the SL-RLC1 default configuration for SRB1 when the first terminal equipment (the remote UE) transmits a radio resource control re-establishment request (RRC re-establishment request) message or a radio resource control resume (RRC resume request) message or when the first terminal equipment (the remote UE) initiates a radio resource control re-establishment procedure or a radio resource control resume procedure (e.g., [0777], remote UE receives RRCResume on the PC5 RLC channel mapped to Uu SRB1). Regarding claim 9: Pan further discloses a transmitter configured to transmit a radio resource control resume complete (RRC resume complete) message and/or a radio resource control re-establishment complete (RRC re-establishment complete) message by using the sidelink relay adaptation protocol (SRAP)-related configuration (e.g., [0780], [0791]), wherein the radio resource control resume (RRC resume) message or the radio resource control re-establishment (RRC re-establishment) message includes the SRAP-related configuration (e.g., [0332], radioBearerConfig, [0722], identity information of Remote UE Uu Radio Bearer and identity information of Remote UE). Regarding claim 10: Pan further discloses the apparatus according to claim 1, wherein the RRC message includes sidelink relay adaptation protocol (SRAP)-related configuration (e.g., [0332], [0347], radioBearerConfig in RRCSetup and RRCResume, [0722], identity information of Remote UE Uu Radio Bearer and identity information of Remote UE). Regarding claim 11: Pan further discloses the apparatus according to claim 10, wherein, the RRC message is a RRC setup message (e.g., RRCSetup in Fig. 18), after the receiver receives the SRAP-related configuration in the RRC setup message, the processor circuitry control to perform at least one of the following operations: establishing an SRAP entity; configuring parameters of the SRAP entity according to the SRAP-related configuration; applying the terminal equipment identifier in the RRC setup message as a cell radio network temporary identifier (C-RNTI) of the first terminal equipment; and transmitting a radio resource control setup complete (RRC setup complete) message based on SRAP-related configuration (e.g., RRCSetupComplete in Fig. 18, [0722], [0724], [0725]). Regarding claim 12: Pan further discloses the apparatus according to claim 10, wherein the processor circuitry is further configured to establish Relay Adaptation Protocol (SRAP) entity (e.g., [0718], [0772], bearer and channel mapping on the adaptation layer for sidelink relay in Fig. 17 and Fig. 20) in at least one of the following processes: selecting or reselecting a second terminal equipment; initiating RRC connection establishment process and/or RRC reconstruction process and/or RRC resume process via the second terminal equipment; receiving RRC setup and/or RRC re assembly and/or RRC resume and/or RRC configuration messages via the second terminal equipment; and receiving from the network apparatus an RRC configuration message to perform path switch to the second terminal equipment (e.g., RRCSetup and RRCReconfiguration in Fig. 18, RRCResumeRequest and RRCResume in Fig. 23). Regarding claim 13: Pan further discloses the apparatus according to claim 10, wherein the processor circuitry is further configured to configure, reconfigure, or modify SRAP entity in at least one of the following processes: using the default SRAP related configuration; and receiving the relevant configuration of SRAP in RRC setup message and/or RRC re-establishment message and/or RRC resume message and/or RRC configuration message (e.g., [0332], [0347], radioBearerConfig, [0722], identity information of Remote UE Uu Radio Bearer and identity information of Remote UE, radio bearer configuration and identity information may be considered SRAP related configuration). Regarding claim 14: Pan further discloses 14. The apparatus according to claim 1, wherein the processor circuitry is further configured to release SRAP entity during at least one of the following processes: switching from communicating with the network apparatus via relay to directly communicating with the network apparatus, releasing PC5 connection between the remote UE and the relay UE, and entering radio resource control idle (RRC_Idle) or radio resource control inactive (RRC_Inactive) state (e.g., [0150], network initiated RRC connection release to transmit a UE to RRC_IDLE or RRC_INACTIVE, or release and redirect a UE to another frequency, an RRC connection may be considered a SRAP entity, [0388], release a PC5 unicast connection between a Remote UE and a UE-to-Network Relay, a PC5 connection may be considered a SRAP entity). Regarding claim 15: Pan discloses an apparatus (300 in Fig. 3) for transceiving information, applicable to a second terminal equipment (a relay UE) (e.g., UE2 in Fig. 23), the apparatus comprising: processer circuitry (e.g., 306 in Fig. 3) configured to control to establish PC5 connection with a first terminal equipment; and a transmitter (e.g., 314 in Fig. 3) configured to transmit a radio resource control (RRC) message via the second terminal equipment by means of default configuration (e.g., Fig. 18, “RRCSetup”, “SecurityModeCommand”, or “RRReconfigurationComplete”, Fig. 23, “UE1’s RRCREsume in sent on specific PC5 RLC channel (for UE1’s Uu SRB1)”). Regarding claim 16: Pan further discloses the apparatus according to claim 15, wherein the RRC message is at least one of a radio resource control resume (RRC resume) message, a radio resource control re-establishment (RRC re-establishment) message and a radio resource control reconfiguration (RRC reconfiguration) message (e.g., Fig. 23, UE1’s RRCResume). Regarding claim 17: Pan further discloses the apparatus according to claim 15, wherein, the transmitter transmits a signaling radio bearer 1 (SRB1) message by using the default SRAP configuration of SRB1 and/or the SL-RLC1 default configuration at the PC5 interface between the second terminal equipment and the first terminal equipment (e.g., Fig. 23, UE1’s Uu SRB1, see PC5 RLC channel and Uu SRB mapping in Fig. 21). Regarding claim 18: Pan further discloses the apparatus according to claim 16, wherein, the radio resource control resume (RRC resume) message or the radio resource control re-establishment (RRC re-establishment) message includes sidelink relay adaptation protocol (SRAP)-related configuration (e.g., [0332], radioBearerConfig, [0722], identity information of Remote UE Uu Radio Bearer and identity information of Remote UE). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to Alvin ZHU whose telephone number is (571)270-1086. The examiner can normally be reached Mon-Fri 6am-9am and 2pm-7pm. 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, Gary Mui can be reached at 571-270-1420. 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. /BO HUI A ZHU/ Primary Examiner, Art Unit 2465
Read full office action

Prosecution Timeline

Jun 28, 2024
Application Filed
Jun 12, 2026
Non-Final Rejection mailed — §102, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12676703
UCI REPETITIONS MULTIPLEXING ON PUSCH
3y 2m to grant Granted Jul 07, 2026
Patent 12671535
RECEIVING TIME OVERLAPPING DOWNLINK REFERENCE SIGNALS AND CHANNELS
3y 8m to grant Granted Jun 30, 2026
Patent 12660038
METHOD AND APPARATUS OF HANDLING SIDELINK COMMUNICATION IN CELL SUPPORTING NETWORK ENERGY SAVINGS
2y 4m to grant Granted Jun 16, 2026
Patent 12652601
ROUTE CALCULATION METHOD, DEVICE, AND SYSTEM
3y 8m to grant Granted Jun 09, 2026
Patent 12647984
REPETITION IN A CONFIGURED GRANT
3y 5m to grant Granted Jun 02, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
80%
Grant Probability
96%
With Interview (+16.1%)
3y 1m (~1y 1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 785 resolved cases by this examiner. Grant probability derived from career allowance 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