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 (IDS) submitted on 9/29/25 and 3/28/25 is being considered by the examiner.
Specification
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
The following title is suggested: SERVICE DATA TRANSMISSION HANDOVER METHOD, TERMINAL, NETWORK NODE AND STORAGE MEDIUM.
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.
Claim(s) 1, 2, 30 are rejected under 35 U.S.C. 103 as being unpatentable over Google (WO 2021/202216), as disclosed in the IDS, and further in view of Huawei (EP 2 983 438), as disclosed in the IDS.
As to claim 1, Google teaches a service data transmission method (Google, Fig 3A & 3B, a data packet transmission method of UE), comprising:
a terminal receiving a handover command (Google, Fig 3A [0071] 316A, a UE receives handover command message);
the terminal transmitting data of a first data radio bearer (DRB) in the target cell according to a configuration of a source cell (Google, [0073], the UE communicates using DRB[0036] with T-CU (target cell) using a portion of the S-BS configuration (configuration of source cell)).
when a data transmission of the first DRB meets a preset condition or a signaling instruction is received from the target cell (Google, Fig 3A [0065], when predetermined thresholds of signal measurements are reached), the terminal performing a process of handover to the target cell (Google, [0065-0067] Fig 3A, UE performing handover to the T-BS/CU/DU (target cell)).
Google does not explicitly teach before performing a handover to a target cell, the terminal transmitting data of a first data radio bearer (DRB) in the target cell according to a configuration of a source cell.
However, Huawei teaches (Huawei, [0098-0099] [0079], before a handover to a target cell is performed, a UE communicating with a target cell eNB(3) using configuration of the first connection (source configuration)).
Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing data of the claimed invention to provide “before handover, communicating in a target cell using source configuration” as taught by Huawei in the system of Google, so that it would prevent interruption of latency and compromise user experience (Huawei, [0079]).
As to claim 2, the combination teaches wherein the first DRB is a bearer on which the terminal has performed a data transmission in the source cell before receiving the handover command (Google, [0036][0066], the DRB is one used for communicating with the source cell)
As to claim 30, Google teaches a terminal (Google, Fig 3A & 3B, a UE), comprising: a memory, a transceiver and a processor, wherein the memory is configured to store a computer program; the transceiver is configured to transmit and receive data under a control of the processor; and the processor is configured to read the computer program in the memory to perform the service data transmission method according to claim 1 (Google, [0039] [0119], UE with processor, memory, transceiver).
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.
Claim(s) 14, 15, 17, 18, 24, 25, 34, 36 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Google (WO 2021/202216), as disclosed in the IDS.
As to claim 14, Google teaches a service data transmission method (Google, Fig 3A & 3B, a data packet transmission method of UE), comprising:
a target network node obtaining a configuration of a source cell corresponding to the terminal (Google, [0073], a T-DU/DU receives a configuration of the S-BS); the target network node transmitting data of a first data radio bearer (DRB) to the terminal according to the configuration of the source cell, wherein the target network node is a network node corresponding to the target cell (Google, [0073], the UE communicates using DRB[0036] with T-CU (target cell) using a portion of the S-BS configuration (configuration of source cell)).
As to claim 15, Google teaches wherein the target network node transmitting data of a first data radio bearer (DRB) to the terminal according to the configuration of the source cell comprises: the target network node transmitting the data of the first DRB to the terminal in part or all of the protocol layer, according to the configuration of the source cell (Google, [0082][0102], the T-(DU/CU) communicates using physical layer protocol configurations).
As to claim 17, Google teaches wherein the target network node transmitting the data of the first DRB to the terminal in all of the protocol layer, according to the configuration of the source cell comprises: the target network node establishing one or more of the following protocol layers for the terminal according to the configuration of the source cell: a MAC entity (Google, [0082][0102], the T-(DU/CU) communication established using MAC layer protocol configurations).; the target network node transmitting data of the first DRB to the terminal based on the MAC entity (Google, [0082][0102], the T-(DU/CU) communicates using MAC layer protocol configurations).
As to claim 18, Google teaches wherein time-frequency resources for the target network node to transmit the data of the first DRB to the terminal according to the configuration of the source cell comprises: a second time-frequency resource used by the terminal in the source cell, the second time-frequency resource is notified by the source network node to the target network node. (Google, [0025], the configuration indicated is the channel (DCCH/UCCH) used by the terminal for the S-BS configuration).
As to claim 24, Google teaches a service data transmission method (Google, Fig 3A & 3B, a data packet transmission method of UE), comprising:
a source network node sending a configuration of a source cell corresponding to a terminal to a target network node(Google, [0073], a T-DU/DU receives a configuration of the S-BS); and
the source network node sending a handover command to the terminal (Google, Fig 3A [0071] 316A, a UE receives handover command message).
As to claim 25, Google teaches further comprising: the source network node indicating, to the target network node, the second time-frequency resource used by the terminal in the source cell (Google, [0025], the configuration indicated is the channel (DCCH/UCCH) used by the terminal for the S-BS configuration).
As to claim 34, Google teaches a network node, wherein the network node is a target network node and comprises: a memory, a transceiver, and a processor, wherein the memory is configured to store a computer program; the transceiver is configured to transmit and receive data under a control of the processor; and the processor is configured to read the computer program in the memory to perform the service data transmission method according to claim 14 (Google, [0037] [0119], UE with processor, memory, transceiver).
As to claim 36, Google teaches a network node, wherein the network node is a source network node comprises: a memory, a transceiver, and a processor, wherein, the memory is configured to store a computer program; the transceiver is configured to transmit and receive data under a control of the processor; and the processor is configured to read the computer program in the memory to perform the service data transmission method according to claim 24 (Google, [0037] [0119], UE with processor, memory, transceiver)..
Allowable Subject Matter
Claims 3, 5, 7, 8, 10, 11, 16, 18, 19, 26 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
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Kim et al (Pub No: 2022/0295354) [0771-800]
Any inquiry concerning this communication or earlier communications from the examiner should be directed to AFSHAWN M TOWFIGHI whose telephone number is (571)270-7296. The examiner can normally be reached M-F 8:00 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, Ian N Moore can be reached at 571-272-3085. 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.
/AFSHAWN M TOWFIGHI/Primary Examiner, Art Unit 2427
Prosecution Insights