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
This Office Action is in response to applicant’s amendment submitted on March 10, 2026.
Claims 1-12, 15 and 17-20, are now currently pending in the present application.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(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, 3, 5-7, 9, 11-12, 18 and 20, are rejected under U.S.C. 102(a)(1) as being anticipated by 3GPP (3GPP TSG-RAN WG2 R2-2103058, hereinafter 3GPP).
Consider Claim 1, discloses a system message update method, performed by a terminal, comprising:
receiving a system message update indication, wherein the system message update indication comprises a plurality of information fields, and the plurality of information fields are used to instruct different types of terminals to perform system message update, (section 2.1 line 3-6, the intention of sharing TRS/CSI-RS with UEs in RRC Idle/Inactive is to improve efficiency in the use of network resources. Therefore, TRS/CSI-RS configuration should be shared with as many UEs as possible. We do not see any clear use case where a TRS/CSI-RS resource is configured but can’t be shared among multiple UEs; Examiner’s note: The phrase “used to instruct” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to instruct” does not have patentable weight).
wherein the plurality of information fields at least comprise a first information field and a second information field, the first information field is used to instruct a first type terminal to perform the system message update, and the second information field is used to instruct a second type terminal to perform the system message update, (section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs. Examiner’s note: The phrase “used to instruct” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to instruct” does not have patentable weight).
the first information field comprises a first number of bits in a short message information field, and the first number of bits are used to indicate different system messages for the first type terminal, respectively, and (section 2.2 Observation 2, to maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication. Examiner’s note: The phrase “used to indicate” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to indicate” does not have patentable weight).
the second information field comprises a second number of bits in the short message information field, wherein the second number of bits are different from the first number of bits, and the second number of bits are used to indicate system messages for different sub-type terminals in the second type terminal, respectively; and (section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs). To maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication. Examiner’s note: The phrase “used to indicate” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to indicate” does not have patentable weight).
performing the system message update based on an information field corresponding to a type of the terminal. (Section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs).
Consider Claim 3, 3GPP discloses the system message update method according to claim 2, wherein the capability of the first type terminal has a higher level than the capability of the second type terminal; wherein the second type terminal comprises a first sub-type terminal and a second sub-type terminal; and (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs).
the second information field at least comprises a first information sub-field and a second information sub-field, the first information sub-field is used to instruct the first sub-type terminal to perform the system message update, and the second information sub-field is used to instruct the second sub-type terminal to perform the system message update. (Section 2.1 proposal 1, according to the latest RAN1 agreement, TRS/CSI-RS configuration can contain information such as BWP, SCS, slot periodicity and offset, band info of a reference signal, and where to find their occasions, etc. And in typical scenarios, we expect multiple TRS/CSI-RS may be available for UEs to use. Therefore, we expect the total size of those information will be more than just a few bits. Hence at least from the size perspective, it qualifies to occupy a new SIB. Secondly, we do not expect the TRS/CSI-RS configuration changes often. Hence even if it is available by on demand only, having it in a separate SIB may not cause much overhead (e.g. if Msg1 based ODSI is used)).
Consider Claim 5, 3GPP discloses the system message update method according to. (Original) The system message update method according to wherein system messages for the different types of terminals are different. (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
Consider Claim 6, 3GPP discloses a system message update method, performed by a network-side device, comprising:
transmitting a system message update indication, wherein the system message update indication comprises a plurality of information fields, and the plurality of information fields are used to instruct different types of terminals to perform system message update, (section 2.1 line 3-6, the intention of sharing TRS/CSI-RS with UEs in RRC Idle/Inactive is to improve efficiency in the use of network resources. Therefore, TRS/CSI-RS configuration should be shared with as many UEs as possible. We do not see any clear use case where a TRS/CSI-RS resource is configured but can’t be shared among multiple UEs; Examiner’s note: The phrase “used to instruct” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to instruct” does not have patentable weight).
wherein the plurality of information fields at least comprise a first information field and a second information field, the first information field is used to instruct a first type terminal to perform the system message update, and the second information field is used to instruct a second type terminal to perform the system message update, (section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs; Examiner’s note: The phrase “used to instruct” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to instruct” does not have patentable weight).
the first information field comprises a first number of bits in a short message information field, and the first number of bits are used to indicate different system messages for the first type terminal, respectively, and (section 2.2 Observation 2, to maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication. Examiner’s note: The phrase “used to indicate” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to indicate” does not have patentable weight).
the second information field comprises a second number of bits in the short message information field, wherein the second number of bits are different from the first number of bits, and the second number of bits are used to indicate system messages for different sub-type terminals in the second type terminal, respectively. (section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support(e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs). To maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication. Examiner’s note: The phrase “used to indicate” is mere intended use that is not a required step in the method. As such, the limitations following the phrase “used to indicate” does not have patentable weight).
Consider Claim 7, 3GPP discloses the system message update method according to claim 6, wherein transmitting the system message update indication comprises:
determining a type of a terminal; and (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
transmitting the system message update indication indicating an information field corresponding to the type of the terminal. (Section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs).
Consider Claim 9, 3GPP discloses the system message update method according to claim 8, wherein the capability of the first type terminal has a higher level than the capability of the second type terminal; wherein, the second type terminal comprises a first sub-type terminal and a second sub-type terminal; and (section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
the second information field at least comprises a first information sub-field and a second information sub-field, the first information sub-field is used to instruct the first sub- type terminal to perform the system message update, and the second information sub- field is used to instruct the second sub-type terminal to perform the system message update. (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs). To maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication).
Consider Claim 11, 3GPP discloses the system message update method according to claim 6, wherein system messages for the different types of terminals are different. (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
Consider Claim 12, 3GPP discloses the system message update method according to claim 6, wherein the method further comprises: in response to a change in a system message for one type of terminal among the different types of terminals, determining to trigger an information field corresponding to the type of the terminal to indicate system message update. (Section 3 proposal 4, introduce a new indication in short message to indicate whether a system information update is relevant only to a configured UE group (e.g. RedCap) or a configured set of SIBs).
Consider Claim 18, 3GPP discloses the system message update apparatus according to claim 17, wherein the capability of the first type terminal has a higher level than the capability of the second type terminal; wherein the second type terminal comprises a first sub-type terminal and a second sub-type terminal; and (section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
the second information field at least comprises a first information sub-field and a second information sub-field, the first information sub-field is used to instruct the first sub- type terminal to perform the system message update, and the second information sub-field is used to instruct the second sub-type terminal to perform the system message update. (Section 2.1 proposal 1, according to the latest RAN1 agreement, TRS/CSI-RS configuration can contain information such as BWP, SCS, slot periodicity and offset, band info of a reference signal, and where to find their occasions, etc. And in typical scenarios, we expect multiple TRS/CSI-RS may be available for UEs to use. Therefore, we expect the total size of those information will be more than just a few bits. Hence at least from the size perspective, it qualifies to occupy a new SIB. Secondly, we do not expect the TRS/CSI-RS configuration changes often. Hence even if it is available by on demand only, having it in a separate SIB may not cause much overhead (e.g. if Msg1 based ODSI is used)).
Consider Claim 20, 3GPP discloses the system message update apparatus according to claim 15, wherein system messages for the different types of terminals are different. (Section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support(e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs)).
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 non-obviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 2, 4, 8, 10, 15 and 17 and 19 are rejected under U.S.C. 103 as being unpatentable by 3GPP (3GPP TSG-RAN WG2 R2-2103058, hereinafter 3GPP) in view of Xin et al. (US 20220417811 A1, hereinafter Xin).
Examiner’s Note: Claim 15 recites “apparatus, comprising: a processor; and a memory configured to store processor executable instruction. Examiner notes that the memory does not actually store the instructions, but rather, merely configured to store the instructions. As such, the effective claim limitation of claim 15 appears to be “a processor; and a memory configured to store processor executable instructions”. As such, the limitation following “processor is configured to execute the following steps…” do not appear to have patentable weight as the instruction are not part of the apparatus.
Consider Claim 15, 3GPP discloses a system message update apparatus, comprising:
receiving a system message update indication, wherein the system message update indication comprises a plurality of information fields, and the plurality of information fields are used to instruct different types of terminals to perform system message update, (section 2.1 line 3-6, the intention of sharing TRS/CSI-RS with UEs in RRC Idle/Inactive is to improve efficiency in the use of network resources. Therefore, TRS/CSI-RS configuration should be shared with as many UEs as possible. We do not see any clear use case where a TRS/CSI-RS resource is configured but can’t be shared among multiple UEs).
wherein the plurality of information fields at least comprise a first information field and a second information field, the first information field is used to instruct a first type terminal to perform the system message update, and the second information field is used to instruct a second type terminal to perform the system message update, (section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs).
the first information field comprises a first number of bits in a short message information field, and the first number of bits are used to indicate different system messages for the first type terminal, respectively, and (section 2.2 Observation 2, to maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication).
the second information field comprises a second number of bits in the short message information field, wherein the second number of bits are different from the first number of bits, and the second number of bits are used to indicate system messages for different sub-type terminals in the second type terminal ,respectively; and (section 2.2 observation 2, one enhancement to avoid this overhead is to introduce a new indication which provides more information about a system information update to UEs. For example, this indication may indicate that this update is for RedCap UEs only, or it is for Rel-17 UEs only, or it involves only a subset of SIBs that not all UEs support (e.g. SIB12/13/14, which are for sidelink/V2X, may not be relevant to most RedCap UEs). To maximize its use and benefits, the exact scope of this new indication (e.g. set of UE groups, set of SIBs) up to network configuration. We notice that currently bit 4~8 in short message is reserved and hence some of those bits can be used for this new indication).
performing the system message update based on an information field corresponding to a type of the terminal. (Section 2.2, a network sends a short message notification to UE whenever there is a change in its system information. This short message is signaled by one bit in paging DCI. No matter the size of the update, all UEs are notified. However, an update in system information may not be relevant to all UEs).
3GPP discloses the claimed invention as noted above but fails to teach a processor; and.
However, Xin teaches a processor (paragraph 104, at least one processor to run the computer program to perform the communication method).
3GPP discloses the claimed invention as noted above but fails to teach a memory configured to store processor executable instructions;
However, Xin teaches a memory configured to store processor executable instructions (paragraph 0105, one memory is configured to store a computer program, and the at least one processor is configured to invoke the computer program from the at least one memory).
3GPP discloses the claimed invention as noted above but fails to teach wherein the processor is configured to execute the following steps when the processor executable instructions are executed by the processor:
However, Xin teaches wherein the processor is configured to execute the following steps when the processor executable instructions are executed by the processor (paragraph 0107, The at least one processor is configured to run a computer program or instructions).
Consider Claims 2, 8 and 17, 3GPP discloses the claimed invention as noted above The system message update method according to claim 1, as noted above but fails to teach wherein a capability of the first type terminal is different from a capability of the second type terminal.
However, Xin teaches wherein a capability of the first type terminal is different from a capability of the second type terminal (paragraph 0009, This application relates to a plurality of types of terminal devices, and the first type is one of the plurality of types. In an example, the plurality of types of the terminal devices may be classified based on capabilities of the terminal devices. Optionally, the plurality of types of the terminal devices may include the first type and a second type. A capability of a terminal device of the first type is weaker than a capability of a terminal device of the second type. For example, the terminal device of the first type may be reduced capability UE, and the terminal device of the second type is a terminal device whose capability is stronger than that of the reduced capability UE).
Consider Claims 4, 10 and 19, 3GPP discloses the claimed invention The system method according to claim 3 as noted above but fails to teach wherein the second number of bits are used to indicate a system message for the first sub-type terminal and a system message for the second sub-type terminal, respectively.
However, Xin teaches teach wherein the second number of bits are used to indicate a system message for the first sub-type terminal and a system message for the second sub-type terminal, respectively (paragraph 0219, The IE or field is used to list a type or types of one or more terminal devices allowed by the network device to camp on. It is assumed that a name of the IE or field is UE Type-Supported, and a value of the IE or field may be {0, 1, 2}. 0 corresponds to the first type, 1 corresponds to the second type, and 2 corresponds to a third type. The IE or field indicates that terminal devices of the first type, the second type. Paragraph 0222, the first terminal device obtains the IE or field from the system message (in other words, the system message has/includes the IE or field), and the bit corresponding to the first type in the IE or field is 0, the first terminal device determines that the first terminal device is not allowed to camp on the cell of the network device.
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify by incorporating the discussion and decision “ TRS/CSI-RS configuration and enhancement to short message” of 3GPP to include the method involves determining a type of terminal device where switching request message is sent to another network device of Xin. The motivation to so would be to develop a method for exploring the configuration and signaling for TRS/CSI-RS enhancements to short message. Thereby creating a method that enables avoiding terminal system message updating so as to reduce power waste.
Response to Arguments
Applicant' s arguments/remarks made in an amendment filed March 10,2026 with respect to independent claims 1, 6 and 15 have been fully considered.
With regards to Applicant’s argument (page 10) that 3GPP addresses the issue of "indiscriminate notifications causing power waste in RedCap and other UEs" by proposing a new indication. This indication informs the UE of the applicability scope of system message updates (e.g., only RedCap UEs, only Rel-17 UEs, or only specific SIB subsets) and the specific scope of the indication (UE group set, SIB set) determined by network configuration. It also notes that bits 4~8 in the short message are reserved and can carry this new indication. Examiner respectfully disagrees, applicant’s is argument/fact that present in regards to 3GPP are not limitations presented within the claims therefore, does not have patentable weight.
With regards to Applicant’s argument (page 10) that 3GPP only mentions that "some reserved bits may be used for the new indication" without explicitly stating or implying that "bits indicate system messages. Examiner respectfully disagrees, the cited reference 3GPP does disclose a system message update method (see sections discussion 2-3). A network sends a short message to a UE whenever there is a change in a system message. This short message is signaled by one bit in paging DCI. No matter the size of an update, all UEs are notified. However, an update in the system message may not be relevant to all the UEs, and a system message update that is irrelevant to those UEs may become a non-negligible overhead and a waste of power consumption. The current short- message design may be a significant overhead for Rel-17 UEs. One enhancement to avoid this overhead is to introduce a new indication which provides more information regarding a system message update to UEs. For example, the indication may indicate that the update is for RedCap UEs only, or the update is for the Rel-17 UEs only, or the update involves only a subset of SIBs that not all UEs support (e.g., SIBs 12/13/14, which are used for sidelink/V2X, may not be relevant to most RedCap UEs). The exact scope of the new indication (e.g., a set of UE groups, and a set of SIBs) is left up to a network configuration. Bits 4-8 in the short message are currently reserved, and therefore some of those bits may be used for the new indication.
With regards to Applicant’s argument (page 10 & 11) that 3GPP fails to discloses using different numbers of bits for system messages of different sub-types terminals. merely mentions in general terms "using reserved bits carry merely mentions in general terms "using reserved bits to carry new indications", without disclosing technical features such as "dividing short message bits into different information fields". Examiner respectfully disagrees.
3GPP discloses that “the exact scope of the new indication (e.g., a set of UE groups, and a set of SIBs) is left up to a network configuration. Bits 4-8 in the short message are currently reserved, and therefore some of those bits may be used for the new indication. In addition, cited reference 3GPP combined with cited reference Xin does disclose wherein the second number of bits are used to indicate a system message for the first sub-type terminal and a system message for the second sub-type terminal, respectively (paragraph 0219, The IE or field is used to list a type or types of one or more terminal devices allowed by the network device to camp on. It is assumed that a name of the IE or field is UE Type-Supported, and a value of the IE or field may be {0, 1, 2}. 0 corresponds to the first type, 1 corresponds to the second type, and 2 corresponds to a third type. The IE or field indicates that terminal devices of the first type, the second type. As a result, a bitmap may be alternatively added to the system message, and the bitmap is used to indicate a type of a terminal device that is allowed”.
As a result, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify (Claim 1) by incorporating cited 3GPP into cited reference Xin.
As a result, the claims are written such that they read upon the cited references.
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 MICHELE CAMILLE DOUGLAS whose telephone number is (571)270-0458. The examiner can normally be reached Monday - Friday 6:30 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, Jeanette J Parker can be reached at 571-270-3647. 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.
/MICHELE C DOUGLAS/Examiner, Art Unit 2646
/JEANETTE J PARKER/Supervisory Patent Examiner, Art Unit 2646
Prosecution Insights