Prosecution Insights
Last updated: August 17, 2026
Application No. 18/256,120

CONNECTION ESTABLISHMENT METHOD AND APPARATUS

Non-Final OA §103§112
Filed
Jun 06, 2023
Priority
Dec 07, 2020 — nonprovisional of PCTCN2020134352
Examiner
WALSH, JOHN B
Art Unit
2451
Tech Center
2400 — Computer Networks
Assignee
Beijing Xiaomi Mobile Software Co., Ltd.
OA Round
3 (Non-Final)
82%
Grant Probability
Favorable
3-4
OA Rounds
0m
Est. Remaining
91%
With Interview

Examiner Intelligence

Grants 82% — above average
82%
Career Allowance Rate
674 granted / 819 resolved
+24.3% vs TC avg
Moderate +9% lift
Without
With
+8.6%
Interview Lift
resolved cases with interview
Typical timeline
2y 11m
Avg Prosecution
27 currently pending
Career history
842
Total Applications
across all art units

Statute-Specific Performance

§101
11.9%
-28.1% vs TC avg
§103
34.3%
-5.7% vs TC avg
§102
29.8%
-10.2% vs TC avg
§112
13.9%
-26.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 819 resolved cases

Office Action

§103 §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 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 1-6, 8-13, 15 and 18-22 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. Claims 1, 13 and 18 recite “receiving connection-related information…and the relay device is in a non-connected state”. It is unclear how the relay device can receive connection related information if it is not connected? Claim Rejections - 35 USC § 103 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. Claims 1-6, 8, 10-15 and 18-22 are rejected under 35 U.S.C. 103 as being unpatentable over U.S. Patent Application Publication 2022/0394807 to Xu et al. in view of U.S. Patent Application Publication 2021/0160951 to Lee et al. Xu et al. ‘807 disclose: As concerns claim 1, a method for connection establishment, performed by a relay device (Fig. 5, 106), the method comprising: receiving connection-related information (Fig. 5, 502) from a remote device (Fig. 5, 107), wherein the connection-related information is configured to indicate a connection request (Fig. 5, 502 radio resource control procedure; Fig. 9-RRC connection request) from the remote device and the connection-related information comprises a first cause of the connection request, and the relay device is in a non-connected state (0120-relay link failure…for a relay); and determining a second cause for performing a connection establishment or a connection resumption with a base station (Fig. 5, 102 Base station) by the relay device (Fig. 5, 106; Fig. 9) according to the first cause. As concerns claim 13, a method for connection establishment, performed by a remote device, the method comprising: communicating with a base station (Fig. 5, 102 Base station) through a relay device (Fig. 5, 106; Fig. 9), wherein the relay device is in a non-connected state (0120-relay link failure…for a relay); and sending connection-related information (Fig. 5, 502 radio resource control procedure; Fig. 9-RRC connection request) to the relay device, wherein the connection-related information is configured to indicated a connection request (Fig. 5, 502 radio resource control procedure; Fig. 9-RRC connection request) from the remote device (Fig. 5, 107), and the connection-related information comprises a first cause of the connection request. As concerns claim 14, the method of claim 13, wherein sending the connection-related information to the relay device comprises: sending the connection related information to the relay device through a sidelink (0120). As concerns claim 18, a relay device (Fig. 5, 106; Fig. 9), comprising: a processor (Fig. 3, 302); and a memory (Fig. 3, 306) for storing instructions executable by the processor; wherein the processor is configured to: receiving connection-related information (Fig. 5, 502 radio resource control procedure; Fig. 9-RRC connection request) from a remote device (Fig. 5, 107), wherein the connection-related information is configured to indicate a connection request (Fig. 5, 502 radio resource control procedure; Fig. 9-RRC connection request) from the remote device and the connection-related information comprises a first cause of the connection request, and the relay device is in a non-connected state (0120-relay link failure…for a relay); and determining a second cause for performing a connection establishment or a connection resumption with a base station (Fig. 5, 102 Base station) by the relay device (Fig. 5, 106; Fig. 9) according to the first cause. As concerns claim 19, a non-transitory computer readable storage medium having stored therein a computer program that, when executed by a processor (Fig. 3, 302) of a relay device (Fig. 5, 106; Fig. 9), caused the relay device to perform the method of claim 1 (see rejection of claim 1 above). As concerns claim 20, a remote device (Fig. 5, 107) comprising: a processor (Fig. 3, 302); and a memory (306) for storing instructions executable by the processor; wherein the processor is configured to perform the method of claim 13 (see rejection of claim 13 above). As concerns claim 21, a non-transitory computer readable storage medium having stored therein a computer program that, when executed by a processor (Fig. 3, 302) of a remote device (Fig. 5, 107), causes the remote device to perform the method of claim 13 (see rejection of claim 13 above). Xu et al. ‘807 do not disclose: a first cause of the connection request and a second cause for performing a connection establishment or connection resumption. Lee et al. ‘951 teach: a first cause (0007-indicator indicating a purpose associated with the RRC connection request; 0100-purpose associated with RRC connection request; 0087-cause values; 0091-cause values, field value RRC, emergency, highpriorityaccess, mt-access, mo-signalling, mo-data) of the connection request and a second cause (0087-different cause values) for performing a connection establishment or connection resumption (0087-connection resumption). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to provide the system of Xu et al. ‘807 with a cause value, as taught by Lee et al. ‘951, in order to distinguish between messages and limit number of messages (0087). Lee et al. 951 further teach: As concerns claim 2, the method of claim 1, wherein determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: in response to the connection establishment being triggered by the connection- related information from the remote device, the connection-related information indicating a connection resumption request of the remote device, and the first cause in the connection resumption request being a radio access network (RAN) area update (0087-RAN notification area update procedure), determining that the second cause for performing the connection establishment with the base station by the relay device is a third cause (second cause being a “third” cause, is merely relabeling), wherein the third cause is related to the RAN area update (0087-RAN notification area update procedure). As concerns claim 3, the method of claim 2, wherein the third cause is a user-initiated signaling (0006-0007-UE intends to connect, thus “user-initiated”). As concerns claim 4, determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: in response to the connection-related information indicating a connection re-establishment request of the remote device, determining that the second cause for performing the connection establishment or the connection resumption with the base station by the relay device is a fourth cause (second cause being a “fourth” cause, is merely relabeling), wherein the fourth cause is related to a connection re-establishment (0087-RRC connection reestablishment request message). As concerns claim 5, the method of claim 4, wherein the fourth cause is a user-initiated signaling (0006-0007-UE intends to connect, thus “user-initiated”). As concerns claim 6, the method of claim 4, wherein the fourth cause is re-establishment (0087-RRC connection reestablishment request message). As concerns claim 8, the method of claim 1, determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: determining the first cause as the second cause for performing by the relay device the connection establishment or the connection resumption (first cause being a “second” cause, is merely relabeling; 0087-connection resumption). As concerns claim 10, the method of claim 1, wherein determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: determining that the second cause for performing by the relay device the connection establishment or the connection resumption is relay (Fig. 5, “via relay”). As concerns claim 11, the method of claim 10, wherein determining that the second cause for performing by the relay device the connection establishment or the connection resumption is the relay comprises: determining that the second cause for performing by the relay device the connection establishment or the connection resumption is relay (Fig. 5, “via relay”) for the remote device. As concerns claim 12, the method of claim 1, further comprising: sending the second cause to the base station while sending a connection establishment request or a connection resumption request (0087-RRC connection resumption request) to the base station. As concerns claim 15, the method of claim 13, wherein the connection request comprises at least one of: a connection establishment request, a connection re-establishment request or a connection resumption request (0087). As concerns claim 22, the relay device of claim 18, wherein the processor is further configured to: in response to the connection establishment being triggered by the connection- related information from the remote device, the connection-related information indicating a connection resumption request of the remote device, and the first cause in the connection resumption request being a radio access network (RAN) area update (0087-RAN notification area update procedure), determine that the reason second cause for performing the connection establishment with the base station by the relay device is a third cause (second cause being a “third” cause, is merely relabeling), wherein the third cause is related to the RAN area update (0087-RAN notification area update procedure). Claim 9 is rejected under 35 U.S.C. 103 as being unpatentable over U.S. Patent Application Publication 2022/0394807 to Xu et al. and U.S. Patent Application Publication 2021/0160951 to Lee et al. in view of U.S. Patent Application Publication 2020/0100123 to Liang. Xu et al. ‘807 as modified do not disclose: As concerns claim 9, the method of claim 1, wherein determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: determining a service type corresponding to the connection request of the remote device indicated by the connection-related information; and determining the second cause for performing the connection establishment or the connection resumption according to the service type. Liang ‘123 teach: As concerns claim 9, the method of claim 1, wherein determining the second cause for performing the connection establishment or the connection resumption with the base station by the relay device according to the first cause comprises: determining a service type (0011-access category) corresponding to the connection request of the remote device indicated by the connection-related information; and determining the second cause for performing the connection establishment or the connection resumption according to the service type (0011-mapping between access category and connection establishment reason). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to provide the system of Xu et al. ‘807 with a service type, as taught by Liang ‘123, in order to provide service specific control (0003). Response to Arguments Applicant's arguments filed May 11, 2026 have been fully considered but they are not persuasive. The applicant’s arguments are directed to newly amended limitations. The limitation of “the relay device is in a non-connected state” has been identified as rendering the claims indefinite (see rejection above). It is unclear how the relay device is receiving connection-related information if it is in a non-connected state. The claims are given the broadest reasonable interpretation and limitations from the specification are not read into the claims. The claims do not provide any context to define the “non-connected state” or any other limitations to set forth how such functionality is accomplished. In response to applicant's arguments against the references individually, one cannot show non-obviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986). The base prior art of Xu disclose the features of connection establishment with a remote device, base station and a relay device as set forth in the claims. The prior art of Lee, which is relevant prior art, teach cause values for connections. Therefore the combination of the prior art references disclose and teach the claimed limitations and renders the claimed invention obvious to one of ordinary skill in the art. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See PTO-892. U.S. Patent Application Publication 2016/0212708 disclose sleep mode for communication devices; U.S. Patent Application Publication 2022/0337990 disclose a cause or reason; U.S. Patent Application Publication 2019/0239273 to Berggren et al. disclose relay device in idle mode no bearer established with a base station, relay request from remote terminal will trigger a message from relay device to base station (0070). Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN B WALSH whose telephone number is (571)272-7063. The examiner can normally be reached 7:30-3:30 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, Christopher L Parry can be reached at 571-272-8328. 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. /JOHN B WALSH/Primary Examiner, Art Unit 2451
Read full office action

Prosecution Timeline

Jun 06, 2023
Application Filed
Jul 23, 2025
Non-Final Rejection mailed — §103, §112
Oct 23, 2025
Response Filed
Feb 11, 2026
Final Rejection mailed — §103, §112
Apr 11, 2026
Response after Non-Final Action
May 11, 2026
Request for Continued Examination
May 21, 2026
Response after Non-Final Action
Jun 10, 2026
Non-Final Rejection mailed — §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12701044
METHOD AND SYSTEM FOR CONFIGURING A USER EQUIPMENT
2y 0m to grant Granted Aug 04, 2026
Patent 12696267
Uplink Transmission Parameter Determination
2y 9m to grant Granted Jul 28, 2026
Patent 12695685
REMOTE MANAGEMENT DEVICE ADAPTOR
2y 6m to grant Granted Jul 28, 2026
Patent 12694199
DEPLOYABLE TAG MANAGEMENT IN COMPUTER DATA NETWORKS
1y 9m to grant Granted Jul 28, 2026
Patent 12676793
METHOD AND APPARATUS FOR EDGE ENABLER SERVER LIFECYCLE MANAGEMENT
1y 11m to grant Granted Jul 07, 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

3-4
Expected OA Rounds
82%
Grant Probability
91%
With Interview (+8.6%)
2y 11m (~0m remaining)
Median Time to Grant
High
PTA Risk
Based on 819 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