Patent Application 18107646 - Handover for Synchronization of Data Flows

Title: Handover for Synchronization of Data Flows

Application Information

Invention Title: Handover for Synchronization of Data Flows
Application Number: 18107646
Submission Date: 2025-05-14T00:00:00.000Z
Effective Filing Date: 2023-02-09T00:00:00.000Z
Filing Date: 2023-02-09T00:00:00.000Z
National Class: 370
National Sub-Class: 350000
Examiner Employee Number: 94765
Art Unit: 2473
Tech Center: 2400

Rejection Summary

102 Rejections: 1
103 Rejections: 0

Cited Patents

No patents were cited in this rejection.

Office Action Text

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 .

Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.

The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.

Claims 7-8 and 15-16 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 7 recites the limitation "the user plane function" in line 2. There is insufficient antecedent basis for this limitation in the claim.
Claim 8 recites the limitation "the second packets“ and “the first wireless device" in line 1-2. There is insufficient antecedent basis for this limitation in the claim.
Claim 15 recites the limitation "the user plane function" in line 2. There is insufficient antecedent basis for this limitation in the claim.
Claim 16 recites the limitation "the second packets“ and “the first wireless device" in line 1-2. There is insufficient antecedent basis for this limitation in the claim.

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 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.

Claims 1-20 are rejected under 35 U.S.C. 102(a2) as being anticipated by Zeng et al (US20230067851A1, PCT Priority Date: Apr 30, 2020).

Regarding claim 1, Zeng’851 discloses a method (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139) comprising:
receiving, by a second base station (see, Fig. 7, target network device, par 0277) from a first base station (see, Fig. 7, source network device, par 0277), an indication (see, indication information indicating M QoS flows in session belong to synchronization QoS flow set, par 0177) of synchronization of data flows of one or more wireless devices (see, Fig. 7 Step 703, target network device receives from source network device the handover request message including indication information indicating M QoS flows belong to synchronization QoS flow set of terminal device, par 0177, 0276-0277); and
synchronizing forwarding, by the second base station (see, Fig. 7, target network device, par 0284) and based on the indication of synchronization (see, indication information indicating M QoS flows in session belong to synchronization QoS flow set, par 0177), of packets of the data flows (see, Fig. 7 Step 707-708, target network device processes the data packets in M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set, par 0284, 0287).

Regarding claim 2, Zeng’851 discloses the method of claim 1 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the synchronizing forwarding is between the one or more wireless devices and a user plane function (see, Fig. 3a and Fig. 7 707-708, target network device processes the data packets in M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session between terminal and UPF, par 0139, 0177, 0284, 0287. Noted, synchronization flows in session between terminal and UPF (receiver) in both uplink and downlink, par 0226).

Regarding claim 3, Zeng’851 discloses the method of claim 2 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the second base station (see, Fig. 7, target network device, par 0226, 0284) from the user plane function (see, Fig. 3A, UPF, par 0226), downlink packets of the packets of the data flows (see, Fig. 7 707-708, target network device receives downlink data packet in the M QoS flows from UPF, par 0224, 0226, 0284).

Regarding claim 4, Zeng’851 discloses the method of claim 3 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the synchronizing forwarding comprises synchronizing transmitting, by the second base station (see, Fig. 7, target network device, par 0284) to the one or more wireless devices (see, Fig. 7, terminal, par 0286), of the downlink packets (see, Fig. 7 step 707, target network device forwards to terminal the downlink data packets in the M QoS flows according to indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0284).

Regarding claim 5, Zeng’851 discloses the method of claim 3 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the second base station (see, Fig. 7, target network device, par 0284) from a first wireless device (see, Fig. 7, terminal, par 0286), first packets of a first data flow of the data flows (see, Fig. 7 step 708, target network device receives from terminal the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0286).

Regarding claim 6, Zeng’851 discloses the method of claim 5 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the second base station (see, Fig. 7, target network device, par 0284), second packets of a second data flow of the data flows (see, Fig. 7 step 708, target network device receives from terminal the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0286. Noted, uplink data packets in QoS flows, and thus second data flow and second packet, par 0286).

Regarding claim 7, Zeng’851 discloses the method of claim 6 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the synchronizing forwarding comprises synchronizing transmitting, by the second base station (see, network device, par 0224-0226) to the user plane function (see, UPF, par 0226), of the first packets and the second packets (see, Fig. 7 step 708, target network device receives from terminal and forwarding to UPF the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0224-0226, 0286. Noted, network device forwarding packet according to indication information between terminal and UPF in both uplink and downlink based on PDB and FSD (frame spread delay), par 0224-0226).

Regarding claim 8, Zeng’851 discloses the method of claim 1 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the second packets are received from the first wireless device (see, Fig. 7 step 708, target network device receives from terminal the data packets in the M QoS flows based on the indication information, par 0287).

Regarding claim 9, Zeng’851 discloses a method (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139) comprising:
receiving, by a first base station (see, Fig. 7, source network device, par 0272) from a network function (see, Fig. 7, SMF, par 0272), an indication of synchronization (see, indication information indicating M QoS flows in session belong to synchronization QoS flow set, par 0177) of data flows of one or more wireless devices (see, Fig. 7 step 701, source network device receives from SMF the indication information indicating M QoS flows of terminal belong to a synchronization QoS flow set, par 0177, 0269, 0272);
synchronizing forwarding, by the first base station (see, Fig. 7, source network device, par 0274) and based on the indication of synchronization, of packets of the data flows (see, Fig. 7 step 702, source network device processes the M QoS flows based on the indication information indicating M QoS flows of terminal belong to a synchronization QoS flow set, par 0177, 0274); and
sending, by the first base station (see, Fig. 7, source network device, par 0277) to a second base station (see, Fig. 7, target network device, par 0277), the indication of the synchronization (see, indication information indicating M QoS flows in session belong to synchronization QoS flow set, par 0177) of the data flows of the one or more wireless devices (see, Fig. 7 Step 703, source network device sends target network device the handover request message including indication information indicating M QoS flows belong to synchronization QoS flow set of terminal device, par 0177, 0276-0277).

Regarding claim 10, Claim 10 recites a method performing the steps recited in claim 2 and thereby, is rejected for the reasons discussed above with respect to claim 2.

Regarding claim 11, Zeng’851 discloses the method of claim 10 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the first base station (see, Fig. 7, source network device, par 0226, 0274) from the user plane function (see, Fig. 3A, UPF, par 0226), downlink packets of the packets of the data flows (see, Fig. 3a and Fig. 7 702, source network device processes the data packets in M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session between terminal and UPF, par 0139, 0177, 0274. Noted, synchronization flows in session between terminal and UPF (receiver) in both uplink and downlink, par 0226).

Regarding claim 12, Zeng’851 discloses the method of claim 11 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the synchronizing forwarding comprises synchronizing transmitting, by the first base station (see, Fig. 7, source network device, par 0274) to the one or more wireless devices (see, Fig. 7, terminal, par 0269), of the downlink packets (see, Fig. 7 step 702, source network device forwards to terminal the downlink data packets in the M QoS flows according to indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0274).

Regarding claim 13, Zeng’851 discloses the method of claim 9 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the first base station (see, Fig. 7, source network device, par 0274) from a first wireless device (see, Fig. 7, terminal, par 0269), first packets of a first data flow of the data flows (see, Fig. 7 step 702, source network device receives from terminal the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0274. Noted, synchronization flows in session between terminal and UPF (receiver) in both uplink and downlink, par 0226).

Regarding claim 14, Zeng’851 discloses the method of claim 13 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), further comprising receiving, by the first base station (see, Fig. 7, source network device, par 0274), second packets of a second data flow of the data flows (see, Fig. 7 step 702, source network device receives from terminal the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0274. Noted, uplink (and downlink) data packets in QoS flows, and thus second data flow and second packet from terminal or UPF, par 0226).

Regarding claim 15, Zeng’851 discloses the method of claim 14 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the synchronizing forwarding comprises synchronizing transmitting, by the first base station (see, Fig. 7, source network device, par 0224-0226, 0274) to the user plane function (see, UPF, par 0226), of the first packets and the second packets (see, Fig. 7 step 702, source network device receives from terminal and forwarding to UPF the uplink data packets in the M QoS flows based on the indication information indicating M QoS flows belong to synchronization QoS flow set in session, par 0177, 0224-0226, 0274. Noted, network device forwarding packet according to indication information between terminal and UPF in both uplink and downlink based on PDB and FSD (frame spread delay), par 0224-0226).

Regarding claim 16, Zeng’851 discloses the method of claim 9 (see, Fig. 3a, QoS flows in session between terminal and UPF through network device in both uplink and downlink direction, par 0139), wherein the second packets are received from the first wireless device (see, Fig. 7 step 702, source network device receives from terminal the data packets in the M QoS flows based on the indication information, par 0274-0275. Noted, packets in flows and thus multiple packets in different flow).

Regarding claim 17, Claim 17 encompass limitations that are similar to limitations of claim 1, except one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the second base station to perform operations.
Zeng’851 discloses
one or more processors (see, Fig. 11, processors, par 0378); and
memory (see, Fig. 11, memory, par 0378) storing instructions (see, computer program instructions, par 0400) that, when executed by the one or more processors, cause the second base station to perform operations (see, computer program instructions stored in a computer-readable memory that can instruct the processor to perform the specific function, par 0400).
Thus, it is rejected with the same rationale applied against claim 1 above.

Regarding claim 18, Claim 18 recites a second base station performing the steps recited in claim 2 and thereby, is rejected for the reasons discussed above with respect to claim 2.

Regarding claim 19, Claim 19 recites a second base station performing the steps recited in claim 3 and thereby, is rejected for the reasons discussed above with respect to claim 3.

Regarding claim 20, Claim 20 recites a second base station performing the steps recited in claim 4 and thereby, is rejected for the reasons discussed above with respect to claim 4.

Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Fan et al (US20220361129A1, PCT Priority Date: Jan 23 , 2020) discloses: The foregoing QoS flows may implicitly reflect that the UE needs to perform high-precision time synchronization or the UE is used in an uplink time synchronization scenario (par 0115), When handing over a terminal that needs to perform high-precision synchronization, the source access network device sends a handover request message only to a target access network device that supports high-precision time synchronization (par 0157).

Any inquiry concerning this communication or earlier communications from the examiner should be directed to XUAN LU whose telephone number is (571)272-2844. The examiner can normally be reached on Monday - Friday 7:30am-5:30pm.
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, KWANG Yao can be reached on (571)272-3182. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see https://ppair-my.uspto.gov/pair/PrivatePair. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.

/XUAN LU/ Primary Examiner, Art Unit 2473