Prosecution Insights
Last updated: May 29, 2026
Application No. 18/430,539

WIRELESS COMMUNICATION METHOD, AND DEVICES

Final Rejection §103
Filed
Feb 01, 2024
Priority
Aug 03, 2021 — continuation of PCTCN2021110388
Examiner
NGUYEN, HAO HONG
Art Unit
2447
Tech Center
2400 — Computer Networks
Assignee
Guangdong OPPO Mobile Telecommunications Corp., Ltd.
OA Round
2 (Final)
68%
Grant Probability
Favorable
3-4
OA Rounds
7m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 68% — above average
68%
Career Allowance Rate
207 granted / 306 resolved
+9.6% vs TC avg
Strong +38% interview lift
Without
With
+37.9%
Interview Lift
resolved cases with interview
Typical timeline
2y 11m
Avg Prosecution
18 currently pending
Career history
337
Total Applications
across all art units

Statute-Specific Performance

§101
1.2%
-38.8% vs TC avg
§103
92.0%
+52.0% vs TC avg
§102
4.6%
-35.4% vs TC avg
§112
0.4%
-39.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 306 resolved cases

Office Action

§103
DETAILED ACTION Applicant’s Amendment filed on December 17, 2025 has been reviewed. Claims 5-7 and 13-14 are cancelled in the amendment. Claims 21-25 are newly added in the amendment. Claims 1, 8, 9 and 19 are amended in the amendment. Claims 1-4, 8-12 and 15-25 have been examined. Claim Objections Claim 1, 9 and 19 are objected to because of the following informalities: In claim 1, at line 9, “a deviation of the arrival time of the first unit” should be changed to “a deviation of an arrival time of the first unit”. In claims 9 and 19, at line 10, “a deviation of the arrival time of the first unit” should be changed to “a deviation of an arrival time of the first unit”. 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 of this title, 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 set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied 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. Claims 1-4, 8-12, 15 and 17-22 are rejected under 35 U.S.C. 103 as being unpatentable over Xu (WO 2023/011100 A1) in view of Minokuchi et al. (US 2022/0338142 A), hereinafter referred to as Minokuchi. With respect to claim 1, Xu teaches A method for wireless communication (wireless communication systems, page 12, lines 35-36), comprising: acquiring, by an access network device, relevant information of a first unit through a first core network device, the first core network device being a session management function (SMF) entity (the access network device receives the configuration information of the quality of service QOS flow; the QOS flow carries at least the data unit of the first data type and the data unit of the second data type, and the configuration information includes the data unit of the first data type in one cycle and the maximum data volume of the data unit of the second data type in one cycle; wherein, the configuration information of the QOS flow is sent by the SMF; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); wherein the first unit comprises at least one of: a first type of frame, a P-frame, a first type of application data unit (ADU) or a first type of encoding slice (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); and wherein the relevant information of the first unit is time sensitive communication assistance information (TSCAI) information (the configuration information includes a first Time Sensitive Communication Assistance Information (Time Sensitive Communication Assistance Information, TSCAI) information element, a second TSCAI information element, page 16, lines 23-36); and the TSCAI information comprises: a transmission direction of the first unit (the first TSCAI information element in the configuration information includes direction of the data unit of the first data type; the second TSCAI information element includes direction of the data unit of the second data type; wherein, the direction includes the uplink direction or the downlink direction, page 16, lines 23-36), the arrival time of the first unit (the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type, page 16, lines 23-36), and a cycle of the first unit (the first TSCAI information element includes the maximum data amount of the data unit of the first data type in one cycle, and the second TSCAI information element includes the maximum data amount of the data unit of the second data type in one cycle, page 16, lines 23-36), Xu does explicitly teach the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type (page 16, lines 23-36). Xu does not explicitly teach the TSCAI information comprises: a deviation of the arrival time of first unit, However, Minokuchi teaches the TSCAI information comprises: a deviation of the arrival time of first unit (the SMF 40 notifies the RAN 30 of a TSCAI parameter modified based on the offset; the TSCAI parameter here is Burst Arrival Time, and also, “offset” is the difference (corrected ΔT) between TSN time and 5G time, the “offset” is the amount of deviation from the ΔT, para. 0092) in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088), Therefore, based on Xu in view of Minokuchi, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Minokuchi to the method of Xu in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088). With respect to claim 2, Xu teaches The method of claim 1, wherein the relevant information of the first unit is information corresponding to target information, and the target information comprises at least one data stream, or the target information comprises at least one service, or the target information comprises at least one application, or the target information comprises at least one quality of service (QoS) flow (the configuration information of the QOS flow is sent by the SMF that carry the QOS configuration information; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice; the QOS flow can be divided into an upstream QOS flow and a downstream QOS flow, and services can also be divided into an upstream service and a downstream service, wherein the upstream QOS flow corresponds to the upstream service, and the downstream QOS flow corresponds to the downstream service; regardless of whether it is an uplink QOS flow or a downlink QOS flow, the flow direction of their corresponding configuration information is AF→SMF→RAN, page 15, lines 46-60). With respect to claim 3, Xu teaches The method of claim 2, wherein the relevant information of the first unit corresponds to at least one piece of the target information (the configuration information of the QOS flow is sent by the SMF that carry the QOS configuration information; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice; the QOS flow can be divided into an upstream QOS flow and a downstream QOS flow, and services can also be divided into an upstream service and a downstream service, wherein the upstream QOS flow corresponds to the upstream service, and the downstream QOS flow corresponds to the downstream service; regardless of whether it is an uplink QOS flow or a downlink QOS flow, the flow direction of their corresponding configuration information is AF→SMF→RAN, page 15, lines 46-60), or the relevant information of the first unit is shared by all the target information, or the relevant information of the first unit is dedicated to one piece of the target information. With respect to claim 4, Xu teaches The method of claim 1, wherein in a case that the first unit comprises the first type of frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), the first type of frame comprises at least one of: an I-frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), a P-frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), a B-frame, a conventional frame, a default frame, a user plane frame, a control plane frame or a special frame. With respect to claim 8, Xu teaches The method of claim [[5]]1, wherein the relevant information of the first unit is second indication information (based on the configuration information of the QOS flow, the access network device can schedule and transmit the QOS flow, page 21, lines 19-20), the second indication information is used to indicate the access network device to determine the first unit corresponding to target information (the access network device schedule and transmit the data units in the period including the data units of the first data type in the QOS flow according to the maximum data volume of the data units of the first data type in a period with only I frames and no P frames, the access network device schedules and transmits the I frames of the QOS flow according to the P(MDBV) of the I frames, page 21, lines 30-33), and the target information comprises at least one data stream, or the target information comprises at least one service, or the target information comprises at least one application, or the target information comprises at least one quality of service (QoS) flow (the access network device schedule and transmit the data units in the period including the data units of the first data type in the QOS flow according to the maximum data volume of the data units of the first data type in a period with only I frames and no P frames, the access network device schedules and transmits the I frames of the QOS flow according to the P(MDBV) of the I frames, page 21, lines 30-33). With respect to claim 9, Xu teaches A core network device (the configuration information of the QOS flow is sent by the SMF, page 15, lines 41-52), comprising a processor and a memory for storing a computer program (one or more memories, on which instructions stored, and the instructions may be executed on the processor, page 38, lines 50-53), wherein the processor is configured to call and execute the computer program stored in the memory to implement following operation: transmitting relevant information of a first unit to an access network device (the access network device receives the configuration information of the quality of service QOS flow; the QOS flow carries at least the data unit of the first data type and the data unit of the second data type, and the configuration information includes the data unit of the first data type in one cycle and the maximum data volume of the data unit of the second data type in one cycle; wherein, the configuration information of the QOS flow is sent by the SMF; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); the core network device being a session management function (SMF) entity (the configuration information of the QOS flow is sent by the SMF, page 15, lines 41-52); wherein the first unit comprises at least one of: a first type of frame, a P-frame, a first type of application data unit (ADU) or a first type of encoding slice (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); and wherein the relevant information of the first unit is time sensitive communication assistance information (TSCAI) information (the configuration information includes a first Time Sensitive Communication Assistance Information (Time Sensitive Communication Assistance Information, TSCAI) information element, a second TSCAI information element, page 16, lines 23-36); and the TSCAI information comprises: a transmission direction of the first unit (the first TSCAI information element in the configuration information includes direction of the data unit of the first data type; the second TSCAI information element includes direction of the data unit of the second data type; wherein, the direction includes the uplink direction or the downlink direction, page 16, lines 23-36), the arrival time of the first unit (the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type, page 16, lines 23-36), and a cycle of the first unit (the first TSCAI information element includes the maximum data amount of the data unit of the first data type in one cycle, and the second TSCAI information element includes the maximum data amount of the data unit of the second data type in one cycle, page 16, lines 23-36), Xu does explicitly teach the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type (page 16, lines 23-36). Xu does not explicitly teach the TSCAI information comprises: a deviation of the arrival time of first unit, However, Minokuchi teaches the TSCAI information comprises: a deviation of the arrival time of first unit (the SMF 40 notifies the RAN 30 of a TSCAI parameter modified based on the offset; the TSCAI parameter here is Burst Arrival Time, and also, “offset” is the difference (corrected ΔT) between TSN time and 5G time, the “offset” is the amount of deviation from the ΔT, para. 0092) in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088), Therefore, based on Xu in view of Minokuchi, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Minokuchi to the device of Xu in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088). With respect to claim 10, Xu teaches The core network device of claim 9, wherein the relevant information of the first unit is information corresponding to target information, and the target information comprises at least one data stream, or the target information comprises at least one service, or the target information comprises at least one application, or the target information comprises at least one quality of service (QoS) flow (the configuration information of the QOS flow is sent by the SMF that carry the QOS configuration information; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice; the QOS flow can be divided into an upstream QOS flow and a downstream QOS flow, and services can also be divided into an upstream service and a downstream service, wherein the upstream QOS flow corresponds to the upstream service, and the downstream QOS flow corresponds to the downstream service; regardless of whether it is an uplink QOS flow or a downlink QOS flow, the flow direction of their corresponding configuration information is AF→SMF→RAN, page 15, lines 46-60). With respect to claim 11, Xu teaches The core network device of claim 10, wherein the relevant information of the first unit corresponds to at least one piece of the target information (the configuration information of the QOS flow is sent by the SMF that carry the QOS configuration information; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice; the QOS flow can be divided into an upstream QOS flow and a downstream QOS flow, and services can also be divided into an upstream service and a downstream service, wherein the upstream QOS flow corresponds to the upstream service, and the downstream QOS flow corresponds to the downstream service; regardless of whether it is an uplink QOS flow or a downlink QOS flow, the flow direction of their corresponding configuration information is AF→SMF→RAN, page 15, lines 46-60), or the relevant information of the first unit is shared by all the target information, or the relevant information of the first unit is dedicated to one piece of the target information. With respect to claim 12, Xu teaches The core network device of claim 9, wherein in a case that the first unit comprises the first type of frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), the first type of frame comprises at least one of: an I-frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), a P-frame (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52), a B-frame, a conventional frame, a default frame, a user plane frame, a control plane frame or a special frame. With respect to claim 15, Xu teaches The core network device of claim 9, wherein the relevant information of the first unit is second indication information (based on the configuration information of the QOS flow, the access network device can schedule and transmit the QOS flow, page 21, lines 19-20), the second indication information is used to indicate the access network device to determine the first unit corresponding to target information (the access network device schedule and transmit the data units in the period including the data units of the first data type in the QOS flow according to the maximum data volume of the data units of the first data type in a period with only I frames and no P frames, the access network device schedules and transmits the I frames of the QOS flow according to the P(MDBV) of the I frames, page 21, lines 30-33), and the target information comprises at least one data stream, or the target information comprises at least one service, or the target information comprises at least one application, or the target information comprises at least one quality of service (QoS) flow (the access network device schedule and transmit the data units in the period including the data units of the first data type in the QOS flow according to the maximum data volume of the data units of the first data type in a period with only I frames and no P frames, the access network device schedules and transmits the I frames of the QOS flow according to the P(MDBV) of the I frames, page 21, lines 30-33). With respect to claim 17, Xu teaches The core network device of claim 9, wherein the processor is further configured to call and execute the computer program stored in the memory to implement following operation: receiving the relevant information of the first unit sent by a second core network device (the SMF receives service description PFD information from the application function AF; the AF send the PFD information of the service to the NEF, and then the NEF sends it to the PCF [a second core network device], and then the PCF sends it to the SMF [the core network device], page 14, lines 2-15). With respect to claim 18, Xu teaches The core network device of claim 17, wherein the core network device is a session management function (SMF) entity and the second core network device is a policy control function (PCF) entity (the SMF [the core network device] receives service description PFD information from the application function AF; the AF send the PFD information of the service to the NEF, and then the NEF sends it to the PCF [a second core network device], and then the PCF sends it to the SMF, page 14, lines 2-15). With respect to claim 19, Xu teaches An access network device (the access network device receives the configuration information of the quality of service QOS flow, page 15, lines 41-52), comprising a processor and a memory for storing a computer program one or more memories, on which instructions stored, and the instructions may be executed on the processor, page 38, lines 50-53, wherein the processor is configured to call and execute the computer program stored in the memory to implement following operation: acquiring relevant information of a first unit through a first core network device, the first core network device being a session management function (SMF) entity (the access network device receives the configuration information of the quality of service QOS flow; the QOS flow carries at least the data unit of the first data type and the data unit of the second data type, and the configuration information includes the data unit of the first data type in one cycle and the maximum data volume of the data unit of the second data type in one cycle; wherein, the configuration information of the QOS flow is sent by the SMF; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); wherein the first unit comprises at least one of: a first type of frame, a P-frame, a first type of application data unit (ADU) or a first type of encoding slice (the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice, page 15, lines 41-52); and wherein the relevant information of the first unit is time sensitive communication assistance information (TSCAI) information (the configuration information includes a first Time Sensitive Communication Assistance Information (Time Sensitive Communication Assistance Information, TSCAI) information element, a second TSCAI information element, page 16, lines 23-36); and the TSCAI information comprises: a transmission direction of the first unit (the first TSCAI information element in the configuration information includes direction of the data unit of the first data type; the second TSCAI information element includes direction of the data unit of the second data type; wherein, the direction includes the uplink direction or the downlink direction, page 16, lines 23-36), the arrival time of the first unit (the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type, page 16, lines 23-36), and a cycle of the first unit (the first TSCAI information element includes the maximum data amount of the data unit of the first data type in one cycle, and the second TSCAI information element includes the maximum data amount of the data unit of the second data type in one cycle, page 16, lines 23-36), Xu does explicitly teach the first TSCAI information element in the configuration information also includes arrival time of the data unit of the first data type; the second TSCAI information element also includes arrival time of the data unit of the second data type (page 16, lines 23-36). Xu does not explicitly teach the TSCAI information comprises: a deviation of the arrival time of first unit, However, Minokuchi teaches the TSCAI information comprises: a deviation of the arrival time of first unit (the SMF 40 notifies the RAN 30 of a TSCAI parameter modified based on the offset; the TSCAI parameter here is Burst Arrival Time, and also, “offset” is the difference (corrected ΔT) between TSN time and 5G time, the “offset” is the amount of deviation from the ΔT, para. 0092) in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088), Therefore, based on Xu in view of Minokuchi, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Minokuchi to the device of Xu in order to perform efficient scheduling by TSCAI as taught by Minokuchi (para. 0088). With respect to claim 20, Xu teaches The access network device of claim 19, wherein the relevant information of the first unit is information corresponding to target information, and the target information comprises at least one data stream, or the target information comprises at least one service, or the target information comprises at least one application, or the target information comprises at least one quality of service (QoS) flow (the configuration information of the QOS flow is sent by the SMF that carry the QOS configuration information; the QOS flow carries at least data units of the first data type and data units of the second data type; a data unit of the first data type is an I frame or an I slice, and a data unit of the second data type is a P frame or a P slice; the QOS flow can be divided into an upstream QOS flow and a downstream QOS flow, and services can also be divided into an upstream service and a downstream service, wherein the upstream QOS flow corresponds to the upstream service, and the downstream QOS flow corresponds to the downstream service; regardless of whether it is an uplink QOS flow or a downlink QOS flow, the flow direction of their corresponding configuration information is AF→SMF→RAN, page 15, lines 46-60). With respect to claim 21, Wu teaches The method of claim 1, wherein the relevant information of the first unit is sent by a second core network device to the first core network device (the SMF receives service description PFD information from the application function AF; the AF send the PFD information of the service to the NEF, and then the NEF sends it to the PCF [a second core network device], and then the PCF sends it to the SMF [the first core network device], page 14, lines 2-15). With respect to claim 22, Wu teaches The method of claim 21, wherein the second core network device is a policy control function (PCF) entity (the SMF receives service description PFD information from the application function AF; the AF send the PFD information of the service to the NEF, and then the NEF sends it to the PCF [a second core network device], and then the PCF sends it to the SMF [the first core network device], page 14, lines 2-15). Claims 16 and 23 are rejected under 35 U.S.C. 103 as being unpatentable over Xu (WO 2023/011100 A1) in view of Minokuchi et al. (US 2022/0338142 A), hereinafter referred to as Minokuchi, and further in view of Lu et al. (WO 2021068260 A1), hereinafter referred to as Lu. With respect to claim 16, Xu in view of Minokuchi teaches The core network device of claim 15 as described above, Xu in view of Minokuchi does not explicitly teach wherein the processor is further configured to call and execute the computer program stored in the memory to implement following operation: transmitting first information to a third core network device, the first information being used by the third core network device to identify different types of the first unit. However, Lu teaches wherein the processor is further configured to call and execute the computer program stored in the memory to implement following operation: transmitting first information to a third core network device (the SMF [the core network device] sends indication information to the UPF [the third core network device], page 14, lines 47-59), the first information being used by the third core network device to identify different types of the first unit (the SMF [the core network device] sends indication information to the UPF [the third core network device] to indicate the restoration of the QoS of the data stream, page 14, lines 47-59) in order to improve the efficiency of service quality adjustment as taught by Lu (page 1, lines 37-38). Therefore, based on Xu in view of Minokuchi, and further in view of Lu, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Lu to the device of Xu in view of Minokuchi in order to improve the efficiency of service quality adjustment as taught by Lu (page 1, lines 37-38). With respect to claim 23, Xu in view of Minokuchi teaches The method of claim 8 as described above, Xu in view of Minokuchi does not explicitly teach wherein first information is transmitted by the first core network device to a third core network device, and the first information is used by the third core network device to identify different types of the first unit. However, Lu teaches wherein first information is transmitted by the first core network device to a third core network device (the SMF [the core network device] sends indication information to the UPF [the third core network device], page 14, lines 47-59), and the first information is used by the third core network device to identify different types of the first unit (the SMF [the core network device] sends indication information to the UPF [the third core network device] to indicate the restoration of the QoS of the data stream, page 14, lines 47-59) in order to improve the efficiency of service quality adjustment as taught by Lu (page 1, lines 37-38). Therefore, based on Xu in view of Minokuchi, and further in view of Lu, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Lu to the method of Xu in view of Minokuchi in order to improve the efficiency of service quality adjustment as taught by Lu (page 1, lines 37-38). Claims 24 and 25 are rejected under 35 U.S.C. 103 as being unpatentable over Xu (WO 2023/011100 A1) in view of Minokuchi et al. (US 2022/0338142 A), hereinafter referred to as Minokuchi, further in view of Lu et al. (WO 2021068260 A1), hereinafter referred to as Lu, and furthermore in view of Zong et al. (US 2024/0214864 A1), hereinafter referred to as Zong. With respect to claim 24, Xu in view of Minokuchi, and further in view of Lu teaches The method of claim 23 as described above, Xu in view of Minokuchi, and further in view of Lu does not explicitly teach wherein the third core network device is a UPF entity, a value of a first domain in a unit in the target information is set by the third core network device, a unit with a first domain being a first value is the first unit, and a unit with a first domain being a second value is not the first unit; and the target information is transmitted by the third core network device to the access network device after the third core network device sets the value of the first domain in the unit in the target information. However, Zong teaches wherein the third core network device is a UPF entity (the user plane network element sends the data packet of the application through a second tunnel; a tunnel header of the second tunnel includes the QFI, para. 0047; the data packet of the application sent to an access network device through the second tunnel, so that the access network device schedule data based on the frame type of the data packet, para. 0048), a value of a first domain in a unit in the target information is set by the third core network device, a unit with a first domain being a first value is the first unit, and a unit with a first domain being a second value is not the first unit (because different frame types correspond to different burst sizes, burst sizes of the I frame and the P frame are different, the user plane network element determine, based on the burst sizes of the frames, the frame type corresponding to the data packet, if the characteristic information includes the identifier or the type of the application, the user plane network element may pre-obtain that the application or the application of the type includes the I frame and the P frame, and the I frame has a higher burst than the P frame, and the user plane network element determine, based on the burst sizes of the frames, the frame type corresponding to the data packet; further, if the characteristic information includes the interval between the frames and the sending rule of the frames, after determining a frame type of the first frame, the user plane network element determine a frame type of a next frame; therefore, after receiving a subsequent data packet, the user plane network element determine, based on the interval between the frames and the sending rule of the frames, the frame type corresponding to the data packet, the user plane network element determines, based on the frame type, a QoS flow corresponding to the frame type, para. 0225-0226); and the target information is transmitted by the third core network device to the access network device after the third core network device sets the value of the first domain in the unit in the target information (the indication information #2 indicates the user plane network element to send the data packet of the application through a second tunnel, and a tunnel header of the second tunnel includes the QFI; the indication information #2 indicates the user plane network element to encapsulate the data packet of the application in a second tunnel, and include the QFI in a tunnel header of the second tunnel; the second tunnel is a tunnel configured to send data to a downstream node; the indication information #2 indicates the user plane network element to send, by using the QoS flow identified by the QFI, the data packet of the application to the downstream node to a radio access network device, para. 0193) in order to improve user experience by performing distinguishing processing on different types of data packets as taught by Zong (para. 0004). Therefore, based on Xu in view of Minokuchi, further in view of Lu, and furthermore in view of Zong, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Zong to the method of Xu in view of Minokuchi, and further in view of Lu in order to improve user experience by performing distinguishing processing on different types of data packets as taught by Zong (para. 0004). With respect to claim 25, Xu in view of Minokuchi, further in view of Lu, and furthermore in view of Zong teaches The method of claim 24 as described above, Further, Zong teaches wherein a unit is a frame (if the characteristic information includes the burst size of the frames, because different frame types correspond to different burst sizes, for example, burst sizes of the I frame and the P frame are different, the user plane network element may determine, based on the burst sizes of the frames, the frame type corresponding to the data pack, para. 0225), a special identification is marked at a frame header of the frame by the third core network device, and the frame whose frame header is marked with the special identification is transmitted by the third core network device to the access network device (the indication information #2 indicates the user plane network element to send the data packet of the application through a second tunnel, and a tunnel header of the second tunnel includes the QFI; the indication information #2 indicates the user plane network element to encapsulate the data packet of the application in a second tunnel, and include the QFI in a tunnel header of the second tunnel; the second tunnel is a tunnel configured to send data to a downstream node; the indication information #2 indicates the user plane network element to send, by using the QoS flow identified by the QFI, the data packet of the application to the downstream node to a radio access network device, para. 0193); and the special identification is used by the access network device to determine whether the frame is a special frame according to the special identification (the indication information #2 indicates the user plane network element to send the data packet of the application through a second tunnel, and a tunnel header of the second tunnel includes the QFI; the indication information #2 indicates the user plane network element to encapsulate the data packet of the application in a second tunnel, and include the QFI in a tunnel header of the second tunnel; the second tunnel is a tunnel configured to send data to a downstream node; the indication information #2 indicates the user plane network element to send, by using the QoS flow identified by the QFI, the data packet of the application to the downstream node to a radio access network device, para. 0193) in order to improve user experience by performing distinguishing processing on different types of data packets as taught by Zong (para. 0004). Therefore, based on Xu in view of Minokuchi, further in view of Lu, and furthermore in view of Zong, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to utilize the teaching of Zong to the method of Xu in view of Minokuchi, and further in view of Lu in order to improve user experience by performing distinguishing processing on different types of data packets as taught by Zong (para. 0004). Response to Arguments Applicant’s arguments with respect to claims 1-4, 8-12 and 15-25 have been considered but are moot because the arguments do not apply to any of the references being used in the current rejection. 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 extension fee 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 date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to HAO HONG NGUYEN whose telephone number is (571)272-2666. The examiner can normally be reached on Monday-Friday 8AM-4:30PM EST. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, JOON H. HWANG can be reached on 571-272-4036. 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 http://pair-direct.uspto.gov. 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. /H.H.N/Examiner, Art Unit 2447 April 2, 2026 /JOON H HWANG/Supervisory Patent Examiner, Art Unit 2447
Read full office action

Prosecution Timeline

Feb 01, 2024
Application Filed
Sep 30, 2025
Non-Final Rejection mailed — §103
Dec 17, 2025
Response Filed
Apr 07, 2026
Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12634254
RETENTION MODEL MANAGEMENT FOR CHAT CONVERSATIONS
2y 0m to grant Granted May 19, 2026
Patent 12627560
SOFTWARE-DEFINED TRAFFIC ROUTING MESH NETWORK MODIFICATIONS
2y 9m to grant Granted May 12, 2026
Patent 12615213
Method and Device for Controlling Power Internet of Things Flow, and Computer Program Product
1y 8m to grant Granted Apr 28, 2026
Patent 12609867
DESIGN SUPPORT SYSTEM AND DESIGN SUPPORT METHOD
2y 2m to grant Granted Apr 21, 2026
Patent 12592901
SYSTEMS AND METHOD FOR EFFICIENT ROUTING BASED UPON IDENTIFIED SUBJECT MATTER
2y 2m to grant Granted Mar 31, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
68%
Grant Probability
99%
With Interview (+37.9%)
2y 11m (~7m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 306 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month