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 . Claims 1-28 are currently pending.
Claim Objections
Claims 9 and 23 are objected to because of the following informalities: Claims 9 and 23 appears to be mistakenly misspelled the word “confirmation” with conformation. Appropriate correction is required.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-5, 10-21, and 24-28 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Zhang et al. (US 20240406811 A1).
Regarding claim 1, Zhang et al. disclose a first network entity for wireless communication comprising: a communication interface; and one or more processors coupled to the communication interface, wherein the one or more processors are configured to: send, via the communication interface, configuration information to a second network entity, the configuration information indicating a condition to switch from a current cell to a target cell (paragraph [0075]; transmitting configuration message from source cell to the UE. The configuration message includes triggering conditions for triggering mobility based on the configurations for the candidate (target) cells); exchange, via the communication interface, first information with the second network entity on the current cell via a communication session with the second network entity (paragraph [0008]; UE and source cell exchange command identifying at least one of the candidate cells based on the measurement report); receive, from the second network entity via the communication interface, switch information indicating that the second network entity will switch from the current cell to the target cell based on the condition (paragraph [0014]; receiving, at the CU from the DU, a response message that includes a list of candidate cells and configurations for each of the candidate cells, wherein the candidate cell list is used for identifying at least one of the candidate cells that has been configured. The request message includes at least one of an indication that the procedure is initiated for L1/L2 mobility, or an indication that the procedure is initiated for a type of L1/L2 mobility. The type of L1/L2 mobility comprises a mobility triggered by the DU, or a mobility triggered by a user equipment (“UE”)); send, via the communication interface, confirmation information to the second network entity, the confirmation information confirming that the second network entity will switch from the current cell to the target cell (paragraph [0015]; receiving, through the DU, a confirmation of the configuration message. wherein the configuration message includes at least one of the candidate cell list or the identified at least one of the candidate cells); and exchange, via the communication interface, second information of the communication session with the second network entity on the target cell (paragraph [0183]; the UE activates/accesses the target cell, and sends L1/L2 signaling to the DU to complete the L1/L2 mobility procedure. The target DU may send a Downlink Data Delivery Status frame to inform the CU. Downlink packets may include PDCP PDUs not successfully transmitted in the source DU, are sent from the CU to the target DU).
Regarding claim 2, Zhang et al. further suggest wherein to receive, via the communication interface, the switch information, the one or more processors are configured to receive, via the communication interface, the switch information on the current cell (paragraph [0177]; For UE triggered mobility, the UE directly triggers L1/L2 mobility when at least one of the execution conditions is met. After completion of L1/L2 mobility (e.g. successful completion RA towards the DU, or successful reception of L1/L2 signaling at the DU from the UE), the DU (source DU) may inform the activated/target cell to the CU).
Regarding claim 3, Zhang et al. further suggest wherein to receive, via the communication interface, the switch information, the one or more processors are configured to receive, via the communication interface, the switch information on the target cell (paragraph [0174]; The message includes the candidate cell configuration, and may also include the triggering events/execution conditions associated with the candidate cell(s) (for UE triggered mobility).
Regarding claim 4, Zhang et al. further suggest wherein to receive, via the communication interface, the switch information, the one or more processors are configured to receive, via the communication interface, a communication including the switch information, wherein the communication comprises one of a scheduling request (SR) communication, a sounding reference signal (SRS) communication, a random access channel (RACH) communication, or a physical uplink shared channel (PUSCH) communication (paragraph [0139]; the UE sends Scheduling Request (SR) to the target cell and starts monitoring PDCCH of the target cell to receive the uplink grant and the UE sends L1/L2 signaling to the target cell) (paragraph [0184]; If at least one candidate cell satisfies the corresponding execution condition(s), the UE applies/activates the corresponding candidate cell configuration. In block 1804, the UE activates/accesses the target cell (e.g. via random access procedure) (RACH)).
Regarding claim 5, Zhang et al. further suggest wherein the configuration information includes timing information indicating a time by which to switch to the target cell, and wherein to exchange the second information, the one or more processors are configured to exchange the second information according to the timing information (paragraph [0007]; performing a mobility from the current serving cell to the identified candidate cell and starting a timer for the activating or the mobility) (paragraph [0091]; The L1 measurement report can be further configured with additional parameter values (e.g. additional hysteresis, timeToTrigger, threshold) for L1/L2 mobility) (paragraph [0136]; starting time for L1/L2 mobility).
Regarding claim 10, Zhang et al. further suggest wherein to send, via the communication interface, the confirmation information, the one or more processors are configured to send medium access control (MAC)-layer control element (CE) including the confirmation information (paragraph [0008]; Layer 2 (“L1/L2”) signaling and the received communication at the identified candidate cell is a L1/L2 signaling, wherein the L2 signaling comprises a medium access control element (“MAC-CE”).
Regarding claim 11, Zhang et al. further suggest wherein to send, via the communication interface, the confirmation information, the one or more processors are configured to send, via the communication interface, one or more bits of downlink control information (DCI) (paragraph [0008]; the L1 signaling comprises at least one of a downlink control information (“DCI”)).
Regarding claim 12, Zhang et al. further suggest wherein to receive, from the second network entity via the communication information, the switch information, the one or more processors are configured to send uplink control information (UCI) including the switch information (paragraph [0179]; the UE activates/accesses the target cell, and sends L1/L2 signaling (e.g. via ACK, UCI, MAC CE) to the DU to complete the L1/L2 mobility procedure).
Regarding claim 13, Zhang et al. further suggest wherein to send, via the communication interface, the confirmation information, the one or more processors are configured to send, via the communication interface, downlink control information (DCI) including the confirmation information to the second network entity (paragraph [0008]; the L1 signaling comprises at least one of a downlink control information (“DCI”)).
Regarding claim 14, Zhang et al. further suggest wherein the communication interface comprises a radio unit (RU) associated with one of the current cell or the target cell (paragraph [0061]; In the communication interfaces 212, Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 230 handles transmission and reception of signals for inter-cell mobility).
Regarding claim 15, Zhang et al. further suggest wherein the current cell and the target cell are associated with a common distributed unit (DU) of the first network entity (paragraph [0153]; A single DU may support one or multiple cells).
Regarding claim 16, Zhang et al. further suggest wherein the current cell is associated with a first distributed unit (DU) of the first network entity and the target cell is associated with a second, different DU of the first network entity (paragraph [0153]; The cell mobility between cells may be from different CUs or DUs).
Regarding claim 17, Zhang et al. disclose a first network entity for wireless communication comprising: a communication interface; and one or more processors coupled to the communication interface, wherein the one or more processors are configured to: receive, via the communication interface, configuration information from a second network entity, the configuration information specifying a condition to switch from a current cell to a target cell (paragraph [0075]; transmitting configuration message from source cell to the UE. The configuration message includes triggering conditions for triggering mobility based on the configurations for the candidate (target) cells); exchange, via the communication interface, first information of a communication session with the second network entity on the current cell (paragraph [0008]; UE and source cell exchange command identifying at least one of the candidate cells based on the measurement report); in response to the condition being met: send, to the second network entity via the communication interface, switch information indicating that the first network entity will switch from the current cell to the target cell (paragraph [0014]; receiving, at the CU from the DU, a response message that includes a list of candidate cells and configurations for each of the candidate cells, wherein the candidate cell list is used for identifying at least one of the candidate cells that has been configured. The request message includes at least one of an indication that the procedure is initiated for L1/L2 mobility, or an indication that the procedure is initiated for a type of L1/L2 mobility. The type of L1/L2 mobility comprises a mobility triggered by the DU, or a mobility triggered by a user equipment (“UE”)); receive, from the second network entity via the communication interface, confirmation information confirming the switch (paragraph [0015]; receiving, through the DU, a confirmation of the configuration message. wherein the configuration message includes at least one of the candidate cell list or the identified at least one of the candidate cells); and exchange, via the communication interface, second information of the communication session with the second network entity on the target cell (paragraph [0183]; the UE activates/accesses the target cell, and sends L1/L2 signaling to the DU to complete the L1/L2 mobility procedure. The target DU may send a Downlink Data Delivery Status frame to inform the CU. Downlink packets may include PDCP PDUs not successfully transmitted in the source DU, are sent from the CU to the target DU).
Regarding claim 18, Zhang et al. further suggest wherein to send, to the second network entity via the communication interface, the switch information, the one or more processors are configured to send, to the second network entity via the communication interface the switch information on the current cell (paragraph [0177]; For UE triggered mobility, the UE directly triggers L1/L2 mobility when at least one of the execution conditions is met. After completion of L1/L2 mobility (e.g. successful completion RA towards the DU, or successful reception of L1/L2 signaling at the DU from the UE), the DU (source DU) may inform the activated/target cell to the CU).
Regarding claim 19, Zhang et al. further suggest wherein to send, to the second network entity via the communication interface, the switch information, the one or more processors are configured to send, to the second network entity via the communication interface, the switch information on the target cell (paragraph [0174]; The message includes the candidate cell configuration, and may also include the triggering events/execution conditions associated with the candidate cell(s) (for UE triggered mobility).
Regarding claim 20, Zhang et al. further suggest wherein to send, to the second network entity via the communication interface, the switch information, the one or more processors are configured to send, to the second network entity via the communication interface, a communication including the switch information, the communication comprising one of a scheduling request (SR) communication, a sounding reference signal (SRS) communication, a random access channel (RACH) communication, or a physical uplink shared channel (PUSCH) communication (paragraph [0139]; the UE sends Scheduling Request (SR) to the target cell and starts monitoring PDCCH of the target cell to receive the uplink grant and the UE sends L1/L2 signaling to the target cell) (paragraph [0184]; If at least one candidate cell satisfies the corresponding execution condition(s), the UE applies/activates the corresponding candidate cell configuration. In block 1804, the UE activates/accesses the target cell (e.g. via random access procedure) (RACH)).
Regarding claim 21, Zhang et al. further suggest wherein the configuration information includes timing information indicating a time by which to switch to the target cell, and wherein to exchange the second information via the communication interface, the one or more processors are configured to exchange the second information according to the timing information (paragraph [0007]; performing a mobility from the current serving cell to the identified candidate cell and starting a timer for the activating or the mobility) (paragraph [0091]; The L1 measurement report can be further configured with additional parameter values (e.g. additional hysteresis, timeToTrigger, threshold) for L1/L2 mobility) (paragraph [0136]; starting time for L1/L2 mobility).
Regarding claim 24, Zhang et al. further suggest wherein to receive, from the second network entity via the communication interface, the confirmation information, the one or more processors are configured to receive, from the second network entity via the communication interface, a medium access control (MAC)-layer control element (CE) including the confirmation information (paragraph [0008]; Layer 2 (“L1/L2”) signaling and the received communication at the identified candidate cell is a L1/L2 signaling, wherein the L2 signaling comprises a medium access control element (“MAC-CE”).
Regarding claim 25, Zhang et al. further suggest wherein to receive, from the second network entity via the communication interface, the confirmation information, the one or more processors are configured to receive, from the second network entity via the communication interface, one or more bits of downlink control information (DCI) (paragraph [0008]; the L1 signaling comprises at least one of a downlink control information (“DCI”)).
Regarding claim 26, Zhang et al. further suggest wherein to send, to the second network entity via the communication interface, the switch information, the one or more processors are configured to send, to the second network entity via the communication interface, uplink control information (UCI) including the switch information (paragraph [0179]; the UE activates/accesses the target cell, and sends L1/L2 signaling (e.g. via ACK, UCI, MAC CE) to the DU to complete the L1/L2 mobility procedure).
Regarding claim 27, Zhang et al. further suggest wherein to receive, via the communication interface, the confirmation information, the one or more processors are configured to receive downlink control information (DCI) including the confirmation information (paragraph [0008]; the L1 signaling comprises at least one of a downlink control information (“DCI”)).
Regarding claim 28, Zhang et al. further suggest wherein the one or more processors are further configured to monitor the target cell before receiving the confirmation information (paragraph [0139]; the UE monitors the Physical Downlink Control Channel (PDCCH) of the target cell to receive the uplink grant and the UE sends L1/L2 signaling to the target cell via the received uplink grant. In another embodiment, the UE sends Scheduling Request (SR) to the target cell and starts monitoring PDCCH of the target cell to receive the uplink grant and the UE sends L1/L2 signaling to the target cell via the received uplink grant).
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.
Claim(s) 22 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhang et al. (US 20240406811 A1) in view of Leng et al. (US 20240381195 A1).
Regarding claim 22, Zhang et al. disclose all the subject matter of the claimed invention as recited in claim 21 above without explicitly suggest wherein the one or more processors are configured to send, via the communication interface, arrival confirmation information to the second network entity on the target cell. However, Leng et al. from the same or similar field of endeavor suggest wherein the one or more processors are configured to send, via the communication interface, arrival confirmation information to the second network entity on the target cell (paragraph [0068]; the UE sends an initial UL transmission to notify its arrival in the target cell and NW confirms UE's arrival by sending a confirmation). Therefore it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to incorporate in Zhang et al.’s method/system the step of sending, via the communication interface, arrival confirmation information to the second network entity on the target cell as suggested by Leng et al. to notify its arrival on the target cell. The motivation would have been to declare the switching to target cell is successfully such to enable robust coverage and mobility support (paragraph [0020]).
Allowable Subject Matter
Claims 6-9 and 23 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HOANG-CHUONG Q VU whose telephone number is (571)270-3945. The examiner can normally be reached Monday-Friday (9:30-5:30 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, AYAZ SHEIKH can be reached at 571-272-3795. 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.
HOANG-CHUONG Q. VU
Primary Examiner
Art Unit 2476
/HOANG-CHUONG Q VU/Primary Examiner, Art Unit 2476
Prosecution Insights