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 .
Information Disclosure Statement
The information disclosure statement submitted on 10/26/2023, have been considered by the examiner and made of record in the application file.
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-12, 15 and 17-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, 3GPP 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; and (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).
performing the system message update based on an information field corresponding to a type of the terminal. and (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 2, 3GPP discloses the system message update method according to claim 1, 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).
a capability of the first type terminal is different from a capability of the second type terminal. (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 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 4, 3GPP discloses the system message update method according to claim 3, wherein 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 a system message for the first sub-type terminal and a system message for the second sub-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).
Consider Claim 5, 3GPP discloses the system message update method according to claim 1, 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).
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 8, 3GPP discloses the system message update method according to claim 6, 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; and (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).
a capability of the first type terminal is different from a capability of the second type terminal. (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 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 10, 3GPP discloses the system message update method according to claim 9, wherein 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, and 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. (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) ora configured set of SIBs).
Consider Claim 17, 3GPP discloses the system message update apparatus according to claim 15, 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; and (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).
a capability of the first type terminal is different from a capability of the second type terminal. 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 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 19, 3GPP discloses the system message update apparatus according to claim 18, wherein 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 a system message for the first sub- type terminal and a system message for the second sub-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).
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.
Claim 15 is rejected under U.S.C. 103 as being unpatentable over 3GPP (3GPP TSG-RAN WG2 R2-2103058, hereinafter 3GPP) in view of LI et al. (US 2023/0300642 Al, hereinafter LI).
Consider Claim 15, 3GPP discloses a system message update apparatus, comprising: a processor; and
a memory configured to store processor executable instructions;
wherein the processor is configured to execute the following steps when the processor executable instructions are executed by the processor:
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: and (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).
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 in the limitations noted above but fails to teach a processor; and a memory configured to store processor executable instructions;
wherein the processor is configured to execute the following steps when the processor executable instructions are executed by the processor.
However, LI teaches (paragraph 0131, Referring to FIG. 16, the apparatus 1600 may include one or more of the following components: a pro-cessing component 1602, a memory 1604, a power supply component 1606, a multimedia component 1608, an audio component 1610, an input/output (I/O) interface 1612, a sensor component 1614 and a communication component 1616).
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, (Clam 15) to modify by incorporating the system message update method of 3GPP to combine with the method and apparatus for receiving indication of LI. The motivation to do so would be to develop a method/apparatus in the configuration aspects of TRS/CSI-RS for paging reception and enhancement to short message. Thereby, creating a system message updating method comprises receiving system message update indication comprising information domains configured for indicating different types of terminals to update system message, and updating system message based on information domain.
Conclusion
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, Matthew Anderson can be reached at 571-272-4177. 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
/MATTHEW D. ANDERSON/ Supervisory Patent Examiner, Art Unit 2646
Prosecution Insights