Prosecution Insights
Last updated: April 19, 2026
Application No. 18/281,227

TRANSMISSION CONFIGURATION INDICATION STATE CONFIGURATION METHOD AND APPARATUS, AND STORAGE MEDIUM

Final Rejection §102§103
Filed
Sep 08, 2023
Examiner
LINDENBAUM, ALAN LOUIS
Art Unit
2413
Tech Center
2400 — Computer Networks
Assignee
BEIJING XIAOMI MOBILE SOFTWARE CO., LTD.
OA Round
2 (Final)
48%
Grant Probability
Moderate
3-4
OA Rounds
3y 7m
To Grant
64%
With Interview

Examiner Intelligence

Grants 48% of resolved cases
48%
Career Allow Rate
204 granted / 421 resolved
-9.5% vs TC avg
Strong +16% interview lift
Without
With
+15.8%
Interview Lift
resolved cases with interview
Typical timeline
3y 7m
Avg Prosecution
69 currently pending
Career history
490
Total Applications
across all art units

Statute-Specific Performance

§101
2.2%
-37.8% vs TC avg
§103
56.7%
+16.7% vs TC avg
§102
20.4%
-19.6% vs TC avg
§112
17.5%
-22.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 421 resolved cases

Office Action

§102 §103
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 § 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. 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, 3-5, 7-14, 16-17, 19-20, 24 and 26-28 is/are rejected under 35 U.S.C. 102((a)(2)) as anticipated by or, in the alternative, under 35 U.S.C. 103 as obvious over Koskela et al. (US 2023/0096338). Regarding claim 1, Koskela discloses a method for configuring a transmission configuration indication (TCI) state (Koskela, paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell), comprising: obtaining TCI state configuration information, wherein the TCI state configuration information comprises cell type indication information and a serving cell index, the cell type indication information indicates a cell type corresponding to the TCI state configured by the TCI state configuration information, and the cell type comprises a serving cell or a neighboring cell, wherein the cell type indication information is represented by a flag bit, there is a correspondence between a part of value in a plurality of values of the flag bit and the serving cell, and/or there is a correspondence between a part of values in the plurality of values and different neighboring cell physical cell identifiers (PCIs) (Koskela, Fig. 11A-11C, TCI state, serving cell index #0, serving cell index #1 (PCI1); Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0128], TCI state in Fig. 11B; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell); determining a component carrier in which a serving cell corresponding to the serving cell index is located (Koskela, Fig. 11A-11C, BWP ID 1;paragraph [0019], UE configured to operate with a carrier BWP, only one BWP active on a given component carrier; paragraph [0126], carrier bandwidth of a currently serving cell “serving cell index #0”; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell); and determining a cell corresponding to the TCI state configured by the TCI state configuration information based on a value of the flag bit and/or a neighboring cell PCI corresponding to the component carrier (Koskela, Fig. 11A-11C, BWP ID 1, TCI state, serving cell index #0, serving cell index #1 (PCI1); Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0128], TCI state in Fig. 11B; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 3, Koskela discloses the method of claim 1, wherein the TCI state configuration information further comprises at least one of a TCI state identification (ID) or a reference signal ID (Koskela, Fig. 11A, CSI-RS#; Fig. 13, TCI state ID, serving cell ID; paragraph [0126], CSI-RS#). Regarding claim 4, Koskela discloses the method of claim 3, wherein determining the cell corresponding to the TCI state configured by the TCI state configuration information based on the TCI state configuration information, comprises: determining the cell corresponding to the TCI state configured by the TCI state configuration information based on the flag bit (Koskela, paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 5, Koskela discloses the method of claim 4, wherein determining the cell corresponding to the TCI state configured by the TCI state configuration information based on the value of the flag bit, comprises: determining the cell corresponding to the TCI state configured by the TCI state configuration information as a serving cell, wherein no flag bit exists in the TCI state configuration information; or determining the cell corresponding to the TCI state configured by the TCI state configuration information as a neighboring cell, wherein the flag bit is configured for identifying the neighboring cell (Koskela, paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field may be added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 7, Koskela discloses the method of claim 5, further comprising: determining the neighboring cell corresponding to the TCI state configured by the TCI state configuration information from a plurality of neighboring cells identified by the flag bit, wherein the flag bit identifies the plurality of neighboring cells with a plurality of flag bit values (Koskela, paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 8, Koskela discloses the method of claim 7, wherein determining the neighboring cell corresponding to the TCI state configured by the TCI state configuration information from the plurality of neighboring cells identified by the flag bit, comprises: determining a neighboring cell physical cell identifier (PCI) based on the serving cell index included in the TCI state configuration information; and determining a cell identified by the neighboring cell PCI as the neighboring cell corresponding to the TCI state configured by the TCI state configuration information (Koskela, Fig. 11A, CSI-RS#; Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 9, Koskela discloses the method of claim 8, wherein determining the neighboring cell PCI based on the serving cell index included in the TCI state configuration information, comprises: determining the neighboring cell PCI corresponding to the serving cell index included in the TCI state configuration information based on a correspondence between the serving cell index and the neighboring cell PCI (Koskela, Fig. 8; Fig. 11A, CSI-RS#; Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 10, Koskela discloses the method of claim 8, wherein determining the neighboring cell PCI based on the serving cell index included in the TCI state configuration information, comprises: determining the neighboring cell PCI corresponding to the component carrier (Koskela, paragraph [0019], only one BWP active on a given component carrier; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 11, Koskela discloses the method of claim 10, wherein up to one neighboring cell is configured on the component carrier, the neighboring cell PCI and at least one of the serving cell index or the component carrier are in a one-to-one correspondence (Koskela, Fig. 13, TCI state ID, serving cell ID; paragraph [0019], BWP active on a given component carrier). Regarding claim 12, Koskela discloses the method of claim 10, wherein a plurality of neighboring cells are configured on the component carrier, the neighboring cell PCI and at least one of the serving cell index or the component carrier are in a one-to-many correspondence (Koskela, Fig. 13, TCI state ID, serving cell ID; paragraph [0019], BWP active on a given component carrier; paragraph [0158], cells configured as potential target cells). Regarding claim 13, Koskela discloses the method of claim 12, wherein the neighboring cell corresponding to the TCI state configured by the TCI state configuration information is a neighboring cell identified by the flag bit Koskela, paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Claims 14, 16-17 and 19-20 are rejected under substantially the same rationale as claims 1, 3, 7 and 11-12, respectively. Claims 24 and 26 are rejected under substantially the same rationale as claim 1. Koskela additionally discloses a processor; a memory for storing instructions executable by the processor (Koskela, Figs. 1, 2, memory, processor, program). Regarding claim 27, Koskela discloses the method of claim 4, further comprising: in response to the value of the flag bit being a flag bit value for identifying a serving cell, determining the cell corresponding to the TCI state configured by the TCI state configuration information as the serving cell (Koskela, Fig. 11A-11C, BWP ID 1, TCI state, serving cell index #0, serving cell index #1 (PCI1); Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0128], TCI state in Fig. 11B; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell). Regarding claim 28, Koskela discloses the method of claim 4, further comprising: in response to the flag bit value for identifying the neighboring cell comprising a plurality of flag bit values, determining the neighboring cell corresponding to the TCI state as the neighboring cell (Koskela, Fig. 11A-11C, BWP ID 1, TCI state, serving cell index #0, serving cell index #1 (PCI1); Fig. 13, TCI state ID, serving cell ID; paragraph [0015], non-serving cell is operated by a neighboring base station; paragraph [0020], TCI state; paragraph [0056], TCI state list included in configuration; paragraph [0128], TCI state in Fig. 11B; paragraph [0141], information to identify a non-serving cell may be a PCI; paragraph [0143], additional bit field added to configuration to indicate that a neighbor/non-serving cell is configured; paragraph [0148], UE may be configured with a TCI state list information element including a field for PCI or other indication that the TCI state list is for a non-serving cell, determine the non-serving cell configuration). Response to Arguments Applicant's arguments filed January 23, 2026 have been fully considered but they are not persuasive. Applicant reproduces paragraphs [0143] and [0148] of Koskela and then asserts that the claims are patentable because paragraph [0143] of Koskela does not disclose that the “additional field” has any correspondence with the PCI, while ignoring the disclosure in paragraph [0148], of a field for PCI or other indication that the TCI state list is for a non-serving cell. Additionally, Figs. 11B and 11C further disclose that the configuration includes a serving cell index field, which may further indicate a PCI using a plurality of [flag] bit values. Applicant further asserts that the claims are patentable because Koskela allegedly does not disclose a correspondence between a serving cell index and component carrier, or between a neighboring cell PCI and a component carrier. However, this is incorrect. However, a person of ordinary skill in the art, at the time of the invention, would have understood that the word “cell” in the phrase “Serving cell” is typically interpreted to mean a carrier. This is further indicated by paragraph [0126] of Koskela, which discloses the “carrier bandwidth of a currently serving cell ‘serving cell index #0’.” This is also indicated by the disclosures in Figs. 11A, 11B, 11C and paragraph [0126] that the label “a1,” which illustrates a range of frequencies making up a carrier band in the figures, symbolizes the “carrier bandwidth of a currently serving cell ‘serving cell index #0’.” Conclusion THIS ACTION IS MADE FINAL. 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 ALAN LOUIS LINDENBAUM whose telephone number is (571)270-3858. The examiner can normally be reached Monday through Friday 9:00 AM to 5:00 PM EST. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Nishant Divecha can be reached at (571) 270-3125. 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. /ALAN L LINDENBAUM/Examiner, Art Unit 2466 /Nishant Divecha/Supervisory Patent Examiner, Art Unit 2419
Read full office action

Prosecution Timeline

Sep 08, 2023
Application Filed
Oct 17, 2025
Non-Final Rejection — §102, §103
Jan 23, 2026
Response Filed
Mar 03, 2026
Final Rejection — §102, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12603845
Device-Assisted Services for Protecting Network Capacity
2y 5m to grant Granted Apr 14, 2026
Patent 12557092
Data Scheduling in High Frequency
2y 5m to grant Granted Feb 17, 2026
Patent 12526661
Radio Link Monitoring for Sidelink Communications
2y 5m to grant Granted Jan 13, 2026
Patent 12483974
METHOD AND APPARATUS FOR REDUCED CAPABILITY TERMINAL TO ACCESS A CELL IN MOBILE WIRELESS COMMUNICATION SYSTEM
2y 5m to grant Granted Nov 25, 2025
Patent 12396051
METHOD AND APPARATUS FOR FAILURE RECOVERY IN WIRELESS COMMUNICATION SYSTEM
2y 5m to grant Granted Aug 19, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

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

Prosecution Projections

3-4
Expected OA Rounds
48%
Grant Probability
64%
With Interview (+15.8%)
3y 7m
Median Time to Grant
Moderate
PTA Risk
Based on 421 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