Prosecution Insights
Last updated: May 29, 2026
Application No. 18/180,842

INTELLIGENT CARRIER AGGREGATION FOR TWO-WAY TRAFFIC

Non-Final OA §103
Filed
Mar 08, 2023
Examiner
KWAK, JAEYOUNG
Art Unit
2472
Tech Center
2400 — Computer Networks
Assignee
T-Mobile Usa Inc.
OA Round
3 (Non-Final)
85%
Grant Probability
Favorable
3-4
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 85% — above average
85%
Career Allowance Rate
11 granted / 13 resolved
+26.6% vs TC avg
Strong +29% interview lift
Without
With
+28.6%
Interview Lift
resolved cases with interview
Typical timeline
3y 2m
Avg Prosecution
19 currently pending
Career history
50
Total Applications
across all art units

Statute-Specific Performance

§101
0.9%
-39.1% vs TC avg
§103
93.6%
+53.6% vs TC avg
§102
5.5%
-34.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 13 resolved cases

Office Action

§103
DETAILED ACTION The office action is in response to RCE filed received on January 30, 2026. Claims 1-20 are pending in this application and claims 1-3, 6, 8-10, 13, 15-17, and 20 are amended. 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 . Response to Arguments Applicant’s Amendments and Arguments filed 1/30/2026 have been noted and entered for consideration. Claims 1-20 are pending in the instant application. With regard to the 102/103 rejections, Applicant’s arguments filed 1/30/2026 (see pages 8-10 of Remarks) in view of the amendments have been fully considered and persuasive. Due to the amended claims, upon further consideration, a new ground(s) of rejection is made in the below Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 1/30/2026 has been entered. 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. Claims 1, 3, 5, 7, 8, 10, 12, 14, 15, 17, and 19 are rejected under U.S.C. 103 as being unpatentable over Daniel Vivanco and et. al (USPub No: US 20220408411 A1, hereinafter “Vivanco”) in a view of Geoffrey Mchardy et. al (USPub No: US 20230370894 A1, hereinafter “Mchardy”). Regarding claim 1, Vivanco teaches a method comprising: determining, by the node of the wireless network, that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session that is independent from the two-way data traffic session, wherein the one-way data traffic session carries a different data stream that the two-way data traffic session; (Vivanco, in Fig. 2D and 2E and in Paragraphs [0061], [0066], [0069]-[0070], [0072]-[0073], [0076], and [0099], teaches that in Fig. 2D and in Paragraphs [0069]-[0070] and [0072]-[0073], at step 261, normal data exchange occurs between the UE device 236 and the eNodeB 234. Data exchange is two-way, on the downlink and the uplink. In the example, a downlink shared channel (DL-SCH) is used to communicate downlink data. Similarly, on the uplink, an uplink shared channel (UL-SCH) is used to communicate uplink data. Data is exchanged using the primary cell or PCell, carrier C1. As data is exchanged, the data may be stored in a buffer and the amount of buffered data may be compared with a threshold. At step 270, carrier aggregation begins. In the example, the secondary cell (SCell) that was configured at step 257 is activated. In an example, if the amount of buffered data exceeds a threshold, the SCell is activated and a second carrier C2 associated with the second cell may begin communicating data. For example, if the UE device 236 is downloading a large file such as a video file, the eNodeB implementing the method 252 may determine that the file download may occur more efficiently if a second carrier is employed. In that case, the SCell is activated to provide the data to the UE device on carrier C2, along with the PCell and carrier C1. At step 265, carrier C2 is used to communicate data from the eNodeB 234 to the UE device 236. In the example, the downlink shared channel (DL-SCH) is used to communicate downlink data on the SCell. At step 266, responsive to receiving the downlink data, the SCell deactivation timer is reset. At step 267 and step 268, the eNodeB 234 and the UE device 236 operate in a carrier aggregation mode to convey data to the UE device 236. The operations of step 267 and step 268 generally operate simultaneously as the carriers are aggregated to provide either added throughput to the UE device 236 or to provide coverage extension for the UE device 236. At step 267, the downlink shared channel (DL-SCH) and the uplink shared channel (UL-SCH) of the PCell, carrier C1, are used for two-way communication of data on the PCell. At step 268, the downlink shared channel (DL-SCH) of the SCell, carrier C2 is used to communicate downlink data from the eNodeB 234 to the UE device 236. Up to now, the two-way and one-way configuration of a single UE in the above is explained with one data traffic session example. However, as shown in Paragraph [0099], the configuration in the above can be applied to two concurrent data traffic sessions: one is the data traffic session for voice (two-way) and the other is the data traffic session for large data (such as video) downloading (one-way). For example, the UE device reports that it is capable of 2x2 carrier aggregation. The UE device is initially attached to cell c1 (Carrier 1: C1). Cell c11 is collocated to cell c1. (Carrier 1:C1). Cell c2 (Carrier 2: C2) is adjacent to cell c1. The UE device is moving towards cell c2. The UE device is currently engaged in large data download such as video and also currently engaged in a voice call. The method 280 determines that the UE needs higher throughput to handle the data download but the UE device also needs to avoid dropping the call. As soon the UE device reports that it detects cell c2, then the network switches to carrier aggregation between cell c1 and cell c2 (Carrier 1 + Carrier 2). Based on this observation, it is clear that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session, where one-way data traffic session is independent from the two-way data traffic session and carries a different data stream that the two-way data traffic session.) Vivanco does not explicitly teach that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. Mchardy teaches that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. (Mchardy, in Fig. 1 and 2 and in Paragraphs [0059]-[0111], teaches that Fig. 1 shows the configuration of the concurrent two-way plus one-way traffic based on the inter-gNB CA with PCell (Primary Cell)-gNB and SCell (Secondary Cell)-gNB. As described in Fig. 1 and in Paragraphs [0070]-[0073] and [0077]-[0082], the PCell-gNB is responsible to schedule UL channels such as PUSCH as well as PUCCH for a communication device with separate resource pools, one per gNB, where UL channels are configured in PCell only. The DL slot-level scheduling decisions across the gNBs can be performed independently between PCell-gNB and SCell-gNB and UL scheduling is decoupled from any DL scheduling on SCell-gNBs. Thus, Fig 1 shows the concurrent the two-way plus one-way traffic session, the Primary Cell (PCell-gNB) schedules two-way traffic (UL and DL) and the Secondary Cell (SCell-gNB) schedules only one-way traffic (DL only). Further, in Paragraphs [0084]-[0092], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells (this description with Fig. 1 explains CA steering logic and operations). Existing approaches can be taken towards deciding on the data-split between the PCell-gNB 102 and the SCell-gNBs 106, where for data towards local serving cells, any intra-gNB data-transfer strategy can be employe, but Mchardy introduce the concept of Ext-MAC flow for data towards external serving cell. An Ext-MAC-flow 110 is defined with respect to each PCell-gNB 102 which forms the source end-point together with a destination end-point that constitutes an external SCell 106, and a MAC-QoS class associated with the flow. For each gNB, there will be as many Ext-MAC-flows as the number of external cells across all partner gNBs towards which this gNB has established carrier aggregation for one or more communication devices. The SCell-gNB 106, upon receiving the pipelined data, uses the QoS differentiation mechanism that it defines for each Ext-MAC-flow to prioritize this over local traffic 114 as well as over other Ext-MAC-flows. For each communication device 700 and towards a given SCell, when prioritized, SCell-gNB 106 creates a MAC PDU 116 (transport block) by multiplexing one or multiple of the Ext-MAC-flow packets 118 of that communication device 700, in sequence. Note, each Ext-MAC-flow packet is not segmented further in order to fit to the MAC PDU. SCell gNB 106 has full control over air interface link adaptation including MCS and rank selection. Thus, PCell and SCell create two independent MAC PDUs having different QoS-flows, respectively, in each cell. Based on Fig. 1 and the above explanation, the system of Mchardy has CA steering logic (mentioned as intra-inter node steering block 108) and using this logic, the PCell generates two independent traffic on PCell and SCell, respectively, with two different QoS-Flow by steering operation (Ext-MAC-flow method). Further detail explanation can be found in Paragraphs [0059]-[0111]. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 3, combination of Vivanco and Mchardy teaches the features defined in the claim 1, -refer to the indicated claim for reference(s). Vivanco further teaches that determining whether the concurrent two-way plus one-way data traffic session condition exists further comprises: (Vivanco, in Fig. 2D and in Paragraphs [0069], [0070], [0072], and [0085], teaches that when in the primary cell, normal data exchange between UE and eNodeB is performed with a two-way data session on the downlink and uplink, such in a voice call and UE request to download a large data file such as a video file, the amount of the buffered data exceeds a threshold. In this case, to perform a carrier aggregation, the secondary cell is activated and the secondary cell begins to the one-way data session (downlink only), along with PCell. This case is corresponding to the concurrent two-way plus one-way data traffic session condition. Further, in Fig. 2E and in Paragraph [0084] and [0085], Vivanco teaches that to perform a carrier aggregation, the eNodeB may collect information about requirements and status of UE. One of the requirements and status information is the traffic type such as voice call or a large data file like a video file since based on the traffic type, the condition of the traffic data session can be different. Therefore, it is clear that the concurrent two-way plus one-way data traffic session condition may occur, as shown in the above, and each traffic data session can be determined based on the traffic type.) However, Vivanco does not explicitly teaches that using, by the wireless network node, a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session. Further, Mchardy teaches using, by the wireless network node, a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session (Mchardy, in Fig. 1 and in Paragraphs [0016]-[0019] and [0084]-[0089], teaches that as shown in Fig. 1 and described in Paragraphs [0084]-[0089], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells. For this operation, the concept of Ext-MAC flow is introduced, based on MAC-QoS class associated with the flow. Namely, the intra or inter-node steering block 108 in Fig. 1 decides the two-way traffic or the one-way traffic, based on the MAC-QoS class (QoS indicators for the data traffics) associated with MAC-flow. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of using, by the wireless network node, a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 5, combination of Vivanco and Mchardy teaches the features defined in the claim 1, -refer to the indicated claim for reference(s). Vivanco further teaches that wherein the two-way data traffic session comprises a voice call or a video call (Vivanco, in Fig. 2E and in Paragraph [0088], teaches that at step 286, the method 280 includes collecting information about network topology, network design and network status, for example, if the UE device reports at step 284 being actively engaged in a voice call through a first eNodeB on a carrier C1, step 286 may include collecting information about neighboring eNodeB devices in the vicinity of the first eNodeB which may be handoff candidates for the UE device. Since the video call is also two-way data traffic, the two-way traffic session can comprise a video call, too. Therefore, it is clear that the first data traffic session comprises a voice call or a video call.). Regarding claim 7, combination of Vivanco and Mchardy teaches the features defined in the claim 1, -refer to the indicated claim for reference(s). Vivanco further teaches that wherein the p-cell uses a first base station and the s-cell uses a second base station that is not co-located with the first base station (Vivanco, in Fig. 2C and in Claim 13, teaches that a first cell (the primary cell) with a non-collocated second cell (the secondary cell) for carrier aggregation to improve link reliability by minimizing a likelihood of call-drop at cell edge while reducing battery consumption of the UE device. Therefore, it is clear that the p-cell uses a first base station and the s-cell uses a second base station that is not co-located with the first base station.). Regarding claim 8, Vivanco teaches a system comprising: one or more processors; and a computer-readable medium storing programming instructions for execution by the one or more processors, the programming instructions, upon execution by the one or more processors, causing the system to perform the following operations: (Vivanco, in Fig. 4 and in Paragraph [0109] and [0110], teaches that in Fig. 4, the computing environment 400 in the network element such as an access terminal, a base station or an access point can facilitate in whole or in part collecting information about capabilities and requirements of a user equipment device on a mobility network, collecting network information, and selecting and configuring carrier aggregation based on the capabilities and requirements of the user equipment. Program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, the methods in the art can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices. Therefore, it is clear that a system to provide CA over wireless network can be configured with processors that are operative on execution the instructions in computer-readable memories.) determining, by the wireless network node of a wireless network, that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session that is independent from the two-way data traffic session, wherein the one-way data traffic session carries a different data stream than the two-way data traffic session; (Vivanco, in Fig. 2D and 2E and in Paragraphs [0069]-[0070], [0072]-[0073], and [0099], teaches that in Fig. 2D and in Paragraphs [0069]-[0070] and [0072]-[0073], at step 261, normal data exchange occurs between the UE device 236 and the eNodeB 234. Data exchange is two-way, on the downlink and the uplink. In the example, a downlink shared channel (DL-SCH) is used to communicate downlink data. Similarly, on the uplink, an uplink shared channel (UL-SCH) is used to communicate uplink data. Data is exchanged using the primary cell or PCell, carrier C1. As data is exchanged, the data may be stored in a buffer and the amount of buffered data may be compared with a threshold. At step 270, carrier aggregation begins. In the example, the secondary cell (SCell) that was configured at step 257 is activated. In an example, if the amount of buffered data exceeds a threshold, the SCell is activated and a second carrier C2 associated with the second cell may begin communicating data. For example, if the UE device 236 is downloading a large file such as a video file, the eNodeB implementing the method 252 may determine that the file download may occur more efficiently if a second carrier is employed. In that case, the SCell is activated to provide the data to the UE device on carrier C2, along with the PCell and carrier C1. At step 265, carrier C2 is used to communicate data from the eNodeB 234 to the UE device 236. In the example, the downlink shared channel (DL-SCH) is used to communicate downlink data on the SCell. At step 266, responsive to receiving the downlink data, the SCell deactivation timer is reset. At step 267 and step 268, the eNodeB 234 and the UE device 236 operate in a carrier aggregation mode to convey data to the UE device 236. The operations of step 267 and step 268 generally operate simultaneously as the carriers are aggregated to provide either added throughput to the UE device 236 or to provide coverage extension for the UE device 236. At step 267, the downlink shared channel (DL-SCH) and the uplink shared channel (UL-SCH) of the PCell, carrier C1, are used for two-way communication of data on the PCell. At step 268, the downlink shared channel (DL-SCH) of the SCell, carrier C2 is used to communicate downlink data from the eNodeB 234 to the UE device 236. Up to now, the two-way and one-way configuration of a single UE in the above is explained with one data traffic session example. However, as shown in Paragraph [0099], the configuration in the above can be applied to two concurrent data traffic sessions: one is the data traffic session for voice (two-way) and the other is the data traffic session for large data (such as video) downloading (one-way). For example, the UE device reports that it is capable of 2x2 carrier aggregation. The UE device is initially attached to cell c1 (Carrier 1: C1). Cell c11 is collocated to cell c1. (Carrier 1:C1). Cell c2 (Carrier 2: C2) is adjacent to cell c1. The UE device is moving towards cell c2. The UE device is currently engaged in large data download such as video and also currently engaged in a voice call. The method 280 determines that the UE needs higher throughput to handle the data download but the UE device also needs to avoid dropping the call. As soon the UE device reports that it detects cell c2, then the network switches to carrier aggregation between cell c1 and cell c2 (Carrier 1 + Carrier 2). Based on this observation, it is clear that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session, where one-way data traffic session is independent from the two-way data traffic session and carries a different data stream than the two-way data traffic session.) Vivanco does not explicitly teach that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. Mchardy teaches that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. (Mchardy, in Fig. 1 and 2 and in Paragraphs [0059]-[0111], teaches that Fig. 1 shows the configuration of the concurrent two-way plus one-way traffic based on the inter-gNB CA with PCell (Primary Cell)-gNB and SCell (Secondary Cell)-gNB. As described in Fig. 1 and in Paragraphs [0070]-[0073] and [0077]-[0082], the PCell-gNB is responsible to schedule UL channels such as PUSCH as well as PUCCH for a communication device with separate resource pools, one per gNB, where UL channels are configured in PCell only. The DL slot-level scheduling decisions across the gNBs can be performed independently between PCell-gNB and SCell-gNB and UL scheduling is decoupled from any DL scheduling on SCell-gNBs. Thus, Fig 1 shows the concurrent the two-way plus one-way traffic session, the Primary Cell (PCell-gNB) schedules two-way traffic (UL and DL) and the Secondary Cell (SCell-gNB) schedules only one-way traffic (DL only). Further, in Paragraphs [0084]-[0092], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells (this description with Fig. 1 explains CA steering logic and operations). Existing approaches can be taken towards deciding on the data-split between the PCell-gNB 102 and the SCell-gNBs 106, where for data towards local serving cells, any intra-gNB data-transfer strategy can be employe, but Mchardy introduce the concept of Ext-MAC flow for data towards external serving cell. An Ext-MAC-flow 110 is defined with respect to each PCell-gNB 102 which forms the source end-point together with a destination end-point that constitutes an external SCell 106, and a MAC-QoS class associated with the flow. For each gNB, there will be as many Ext-MAC-flows as the number of external cells across all partner gNBs towards which this gNB has established carrier aggregation for one or more communication devices. The SCell-gNB 106, upon receiving the pipelined data, uses the QoS differentiation mechanism that it defines for each Ext-MAC-flow to prioritize this over local traffic 114 as well as over other Ext-MAC-flows. For each communication device 700 and towards a given SCell, when prioritized, SCell-gNB 106 creates a MAC PDU 116 (transport block) by multiplexing one or multiple of the Ext-MAC-flow packets 118 of that communication device 700, in sequence. Note, each Ext-MAC-flow packet is not segmented further in order to fit to the MAC PDU. SCell gNB 106 has full control over air interface link adaptation including MCS and rank selection. Thus, PCell and SCell create two independent MAC PDUs having different QoS-flows, respectively, in each cell. Based on Fig. 1 and the above explanation, the system of Mchardy has CA steering logic (mentioned as intra-inter node steering block 108) and using this logic, the PCell generates two independent traffic on PCell and SCell, respectively, with two different QoS-Flow by steering operation (Ext-MAC-flow method). Further detail explanation can be found in Paragraphs [0059]-[0111]. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 10, combination of Vivanco and Mchardy teaches the features defined in the claim 8, -refer to the indicated claim for reference(s). However, Vivanco does not explicitly teaches that using, by the wireless network node, a QoS indicator to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session. Further, Mchardy teaches using, by the wireless network node, a QoS indicator to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session (Mchardy, in Fig. 1 and in Paragraphs [0016]-[0019] and [0084]-[0089], teaches that as shown in Fig. 1 and described in Paragraphs [0084]-[0089], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells. For this operation, the concept of Ext-MAC flow is introduced, based on MAC-QoS class (QoS indicators for the data traffics) associated with the flow. Namely, the intra or inter-node steering block 108 in Fig. 1 decides the two-way traffic or the one-way traffic, based on the MAC-QoS class associated with MAC-flow. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of using, by the wireless network node, a QoS indicator to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 12, combination of Vivanco and Mchardy teaches the features defined in the claim 8, -refer to the indicated claim for reference(s). Vivanco further teaches that wherein the two-way data traffic session comprises a voice call or a video call (Vivanco, in Fig. 2E and in Paragraph [0088], teaches that at step 286, the method 280 includes collecting information about network topology, network design and network status, for example, if the UE device reports at step 284 being actively engaged in a voice call through a first eNodeB on a carrier C1, step 286 may include collecting information about neighboring eNodeB devices in the vicinity of the first eNodeB which may be handoff candidates for the UE device. Since the video call is also two-way data traffic, the two-way traffic session can comprise a video call, too. Therefore, it is clear that the first data traffic session comprises a voice call or a video call.). Regarding claim 14, combination of Vivanco and Mchardy teaches the features defined in the claim 8, -refer to the indicated claim for reference(s). Vivanco further teaches that wherein the p-cell uses a first base station and the s-cell uses a second base station that is not co-located with the first base station (Vivanco, in Fig. 2C and in Claim 13, teaches that a first cell (the primary cell) with a non-collocated second cell (the secondary cell) for carrier aggregation to improve link reliability by minimizing a likelihood of call-drop at cell edge while reducing battery consumption of the UE device. Therefore, it is clear that the p-cell uses a first base station and the s-cell uses a second base station that is not co-located with the first base station.). Regarding claim 15, Vivanco teaches one or more computer storage devices having programming instructions stored thereon, which, upon execution by one or more processors of a system, cause the system to perform the following operations: (Vivanco, in Fig. 4 and in Paragraph [0109] and [0110], teaches that in Fig. 4, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, the methods in the art can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices. Therefore, it is clear that a computer may execute or perform computer executable instructions stored in one or more computer storage devices.) determining, by the wireless network node of a wireless network, that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session that is independent from the two-way data traffic session, wherein the one-way data traffic session carries a different data stream that the two-way data traffic session; (Vivanco, in Fig. 2D and 2E and in Paragraphs [0069]-[0070], [0072]-[0073], and [0099], teaches that in Fig. 2D and in Paragraphs [0069]-[0070] and [0072]-[0073], at step 261, normal data exchange occurs between the UE device 236 and the eNodeB 234. Data exchange is two-way, on the downlink and the uplink. In the example, a downlink shared channel (DL-SCH) is used to communicate downlink data. Similarly, on the uplink, an uplink shared channel (UL-SCH) is used to communicate uplink data. Data is exchanged using the primary cell or PCell, carrier C1. As data is exchanged, the data may be stored in a buffer and the amount of buffered data may be compared with a threshold. At step 270, carrier aggregation begins. In the example, the secondary cell (SCell) that was configured at step 257 is activated. In an example, if the amount of buffered data exceeds a threshold, the SCell is activated and a second carrier C2 associated with the second cell may begin communicating data. For example, if the UE device 236 is downloading a large file such as a video file, the eNodeB implementing the method 252 may determine that the file download may occur more efficiently if a second carrier is employed. In that case, the SCell is activated to provide the data to the UE device on carrier C2, along with the PCell and carrier C1. At step 265, carrier C2 is used to communicate data from the eNodeB 234 to the UE device 236. In the example, the downlink shared channel (DL-SCH) is used to communicate downlink data on the SCell. At step 266, responsive to receiving the downlink data, the SCell deactivation timer is reset. At step 267 and step 268, the eNodeB 234 and the UE device 236 operate in a carrier aggregation mode to convey data to the UE device 236. The operations of step 267 and step 268 generally operate simultaneously as the carriers are aggregated to provide either added throughput to the UE device 236 or to provide coverage extension for the UE device 236. At step 267, the downlink shared channel (DL-SCH) and the uplink shared channel (UL-SCH) of the PCell, carrier C1, are used for two-way communication of data on the PCell. At step 268, the downlink shared channel (DL-SCH) of the SCell, carrier C2 is used to communicate downlink data from the eNodeB 234 to the UE device 236. Up to now, the two-way and one-way configuration of a single UE in the above is explained with one data traffic session example. However, as shown in Paragraph [0099], the configuration in the above can be applied to two concurrent data traffic sessions: one is the data traffic session for voice (two-way) and the other is the data traffic session for large data (such as video) downloading (one-way). For example, the UE device reports that it is capable of 2x2 carrier aggregation. The UE device is initially attached to cell c1 (Carrier 1: C1). Cell c11 is collocated to cell c1. (Carrier 1:C1). Cell c2 (Carrier 2: C2) is adjacent to cell c1. The UE device is moving towards cell c2. The UE device is currently engaged in large data download such as video and also currently engaged in a voice call. The method 280 determines that the UE needs higher throughput to handle the data download but the UE device also needs to avoid dropping the call. As soon the UE device reports that it detects cell c2, then the network switches to carrier aggregation between cell c1 and cell c2 (Carrier 1 + Carrier 2). Based on this observation, it is clear that two concurrent data traffic sessions of a single user equipment (UE) are associated with a concurrent two-way plus one-way data traffic session condition such that the two concurrent data traffic sessions include a two-way data traffic session and a one-way data traffic session, where one-way data traffic session is independent from the two-way data traffic session and carries a different data stream that the two-way data traffic session.) Vivanco does not explicitly teach that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. Mchardy teaches that wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells. (Mchardy, in Fig. 1 and 2 and in Paragraphs [0059]-[0111], teaches that Fig. 1 shows the configuration of the concurrent two-way plus one-way traffic based on the inter-gNB CA with PCell (Primary Cell)-gNB and SCell (Secondary Cell)-gNB. As described in Fig. 1 and in Paragraphs [0070]-[0073] and [0077]-[0082], the PCell-gNB is responsible to schedule UL channels such as PUSCH as well as PUCCH for a communication device with separate resource pools, one per gNB, where UL channels are configured in PCell only. The DL slot-level scheduling decisions across the gNBs can be performed independently between PCell-gNB and SCell-gNB and UL scheduling is decoupled from any DL scheduling on SCell-gNBs. Thus, Fig 1 shows the concurrent the two-way plus one-way traffic session, the Primary Cell (PCell-gNB) schedules two-way traffic (UL and DL) and the Secondary Cell (SCell-gNB) schedules only one-way traffic (DL only). Further, in Paragraphs [0084]-[0092], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells (this description with Fig. 1 explains CA steering logic and operations). Existing approaches can be taken towards deciding on the data-split between the PCell-gNB 102 and the SCell-gNBs 106, where for data towards local serving cells, any intra-gNB data-transfer strategy can be employe, but Mchardy introduce the concept of Ext-MAC flow for data towards external serving cell. An Ext-MAC-flow 110 is defined with respect to each PCell-gNB 102 which forms the source end-point together with a destination end-point that constitutes an external SCell 106, and a MAC-QoS class associated with the flow. For each gNB, there will be as many Ext-MAC-flows as the number of external cells across all partner gNBs towards which this gNB has established carrier aggregation for one or more communication devices. The SCell-gNB 106, upon receiving the pipelined data, uses the QoS differentiation mechanism that it defines for each Ext-MAC-flow to prioritize this over local traffic 114 as well as over other Ext-MAC-flows. For each communication device 700 and towards a given SCell, when prioritized, SCell-gNB 106 creates a MAC PDU 116 (transport block) by multiplexing one or multiple of the Ext-MAC-flow packets 118 of that communication device 700, in sequence. Note, each Ext-MAC-flow packet is not segmented further in order to fit to the MAC PDU. SCell gNB 106 has full control over air interface link adaptation including MCS and rank selection. Thus, PCell and SCell create two independent MAC PDUs having different QoS-flows, respectively, in each cell. Based on Fig. 1 and the above explanation, the system of Mchardy has CA steering logic (mentioned as intra-inter node steering block 108) and using this logic, the PCell generates two independent traffic on PCell and SCell, respectively, with two different QoS-Flow by steering operation (Ext-MAC-flow method). Further detail explanation can be found in Paragraphs [0059]-[0111]. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of wherein a quality of service (QoS) flow of the one-way data traffic session is independent from a QoS flow of the two-way data traffic session; and based on the concurrent two-way plus one-way data traffic session condition, performing, via carrier aggregation (CA) steering logic of the wireless network node, a CA steering operation to steer the one-way data traffic session to a secondary cell (s-cell) while retaining the two-way data traffic session on a primary cell (p-cell), wherein the QoS flow of the two-way data traffic session is communicated exclusively via a protocol data unit (PDU) session of the p-cell and the QoS flow of the one-way data traffic session is communicated exclusively via a PDU session of the s-cell after the CA steering operation, and wherein the CA steering logic of the wireless network node enables the wireless network node to steer the QoS flow of the one-way data traffic session and the QoS flow of the two way data traffic session to different cells of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 17, combination of Vivanco and Mchardy teaches the features defined in the claim 15, -refer to the indicated claim for reference(s). However, Vivanco does not explicitly teaches that using a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session. Further, Mchardy teaches using a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session (Mchardy, in Fig. 1 and in Paragraphs [0016]-[0019] and [0084]-[0089], teaches that as shown in Fig. 1 and described in Paragraphs [0084]-[0089], PCell-gNB 102 decides in intra vs inter-node steering 108 what proportion of RLC data needs to be sent over local serving cells and what proportion of RLC data needs to be sent over external serving cells. For this operation, the concept of Ext-MAC flow is introduced, based on MAC-QoS class associated with the flow. Namely, the intra or inter-node steering block 108 in Fig. 1 decides the two-way traffic or the one-way traffic, based on the MAC-QoS class (QoS indicators for the data traffics) associated with MAC-flow. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco and Mchardy to include the technique of using a QoS indicator to determine a traffic type to determine a traffic type of the QoS flow of the one-way data traffic session or the QoS flow of the two-way data traffic session of Mchardy in the system of Vivanco to provide a carrier aggregation method between a high-bandwidth/high-frequency carrier with a low-bandwidth/low frequency carrier to give network capacity gains by enabling either a higher net bandwidth or by enabling use of DL of the high-frequency beyond the point of UL coverage loss by moving the UL channels to the low-frequency carrier. (Mchardy, see Paragraph [0010]).). Regarding claim 19, combination of Vivanco and Mchardy teaches the features defined in the claim 15, -refer to the indicated claim for reference(s). Vivanco further teaches that wherein the two-way data traffic session comprises a voice call or a video call (Vivanco, in Fig. 2E and in Paragraph [0088], teaches that at step 286, the method 280 includes collecting information about network topology, network design and network status, for example, if the UE device reports at step 284 being actively engaged in a voice call through a first eNodeB on a carrier C1, step 286 may include collecting information about neighboring eNodeB devices in the vicinity of the first eNodeB which may be handoff candidates for the UE device. Since the video call is also two-way data traffic, the two-way traffic session can comprise a video call, too. Therefore, it is clear that the first data traffic session comprises a voice call or a video call.). Claims 2, 6, 9, 13, 16, and 20 are rejected under U.S.C. 103 as being unpatentable over Daniel Vivanco and et. al (USPub No: US 20220408411 A1, hereinafter “Vivanco”) in a view of Geoffrey Mchardy et. al (USPub No: US 20230370894 A1, hereinafter “Mchardy”) and further in a view of Henriksson, Daniel and et. al. (Int. Pub. No.: WO 2022271055 A1, hereinafter “Henriksson”). Regarding claim 2, combination of Vivanco and Mchardy teaches the features defined in the claim 1, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell. Henriksson teaches that selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. As shown in the above, if the concurrent two-way plus one-way data traffic session condition exists, the UE and the first and the second network nodes should support the carrier aggregation with multiple carriers and the first data session in the PCell may be steered to the SCell. However, based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the secondary cell profile (configuration) based on the received message can be selected or indicated for the steering unit not to steer the first data traffic unit to the S-Cell. Therefore, it is clear that selecting a S-Cell creation profile prevents steering the two-way data traffic session to the s-cell. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy and Henriksson to include the technique of selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Regarding claim 6, combination of Vivanco and Mchardy teaches the features defined in the claim 1, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that further comprising: during a hand-off of the UE, preventing steering of the two-way data traffic session to the s-cell. Henriksson teaches that further comprising: during a hand-off of the single UE, preventing steering, by the wireless network node, of the two-way data traffic session to the s-cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. Based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the steering unit does not steer the first data traffic unit to the SCell, since the carrier aggregation cannot be configured. Therefore, it is clear that during a hand-off of the UE, steering of the first data traffic session to the s-cell is prevented. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Henriksson to include the technique of further comprising: during a hand-off of the UE, preventing steering of the two-way data traffic session to the s-cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Regarding claim 9, combination of Vivanco and Mchardy teaches the features defined in the claim 8, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell. Henriksson teaches that selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. As shown in the above, if the concurrent two-way plus one-way data traffic session condition exists, the UE and the first and the second network nodes should support the carrier aggregation with multiple carriers and the first data session in the PCell may be steered to the SCell. However, based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the secondary cell profile (configuration) based on the received message can be selected or indicated for the steering unit not to steer the first data traffic unit to the SCell. Therefore, it is clear that when the concurrent two-way plus one-way data traffic session condition exists, selecting a SCell creation profile that prevents steering the two-way data traffic session to the s-cell. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Henriksson to include the technique of selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Regarding claim 13, combination of Vivanco and Mchardy teaches the features defined in the claim 8, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that wherein the programming instructions further cause the system to perform the following operation: during a hand-off of the single UE, prevent steering, by the wireless network node, of the two-way data traffic session to the s- cell. Henriksson teaches that wherein the programming instructions further cause the system to perform the following operation: during a hand-off of the single UE, prevent steering, by the wireless network node, of the two-way data traffic session to the s- cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. Based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the steering unit does not steer the first data traffic unit to the SCell, since the carrier aggregation cannot be configured. Therefore, it is clear that during a hand-off of the UE, steering of the first data traffic session to the s-cell is prevented. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Henriksson to include the technique of wherein the programming instructions further cause the system to perform the following operation: during a hand-off of the single UE, prevent steering, by the wireless network node, of the two-way data traffic session to the s- cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Regarding claim 16, combination of Vivanco and Mchardy teaches the features defined in the claim 15, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that selecting a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell. Henriksson teaches that selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. As shown in the above, if the concurrent two-way plus one-way data traffic session condition exists, the UE and the first and the second network nodes should support the carrier aggregation with multiple carriers and the first data session in the PCell may be steered to the SCell. However, based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the secondary cell profile (configuration) based on the received message can be selected or indicated for the steering unit not to steer the first data traffic unit to the SCell. Therefore, it is clear that when the concurrent two-way plus one-way data traffic session condition exists, selecting a SCell creation profile that prevents steering the two-way data traffic session to the s-cell. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Henriksson to include the technique of selecting, by the wireless network node, a first s-cell creation profile that prevents steering the two-way data traffic session to the s-cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Regarding claim 20, combination of Vivanco and Mchardy teaches the features defined in the claim 15, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that wherein the operations further comprise: during a hand-off of the single UE, preventing steering, by the wireless network node, of the two-way data traffic session to the s-cell. Henriksson teaches that wherein the instructions are further operative to: during a hand-off of the UE, prevent steering of the two-way data traffic session to the s- cell (Henriksson, in Fig. 4, 5, and 8 and in Page 15, Lines 27-32 and in Page 16, Lines 1-19, teaches that in Fig. 8, the first network node 111 for the primary cell (PCell) is configured by a determining unit 830 to determine whether or not to handover the UE 120 from the first cell 11 (PCell) to the second cell 12 (secondary cell (SCell)) for multi carrier connectivity towards the third cell 13 based on the indications in the received message. The multi carrier connectivity may be adapted to either Dual connectivity or carrier aggregation. The first network node 111 is configured by a determining unit 830 to determine a Primary Cell, PCell, for the UE 120 in the communication based on the indications in the received message from RCF (Radio Control Function) as shown in Fig. 5. The second network node in similar may be configured based on the received message from RCF as shown in Fig. 5. Based on the indications in the received message (with some reasons such as the UE capability or the cell configuration, etc), the determining unit decides to handover UE to the SCell and then, the SCell is to be a new PCell for the UE. In this case, the steering unit does not steer the first data traffic unit to the SCell, since the carrier aggregation cannot be configured. Therefore, it is clear that during a hand-off of the UE, steering of the two-way data traffic session to the s-cell is prevented. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Henriksson to include the technique of wherein the instructions are further operative to: during a hand-off of the UE, prevent steering of the two-way data traffic session to the s-cell of Henriksson in the system of combination of Vivanco and Mchardy to provide a data traffic steering method to improve the RAN (Radio Access Network) effect such as data rate, latency, and power consumption and to have benefits on OTT(over-the-top) service such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and extending battery lifetime (Henriksson, see Page 6, Lines 24-26 and Page 20, Lines 30-33).). Claims 4, 11, and 18 are rejected under U.S.C. 103 as being unpatentable over Daniel Vivanco and et. al (USPub No: US 20220408411 A1, hereinafter “Vivanco”) in a view of Geoffrey Mchardy et. al (USPub No: US 20230370894 A1, hereinafter “Mchardy”) and further in a view of Khirallah, Chadi and et. al. (Int. Pub No: WO 2019065617 A1, hereinafter “Khirallah”). Regarding claim 4, combination of Vivanco and Mchardy teaches the features defined in the claim 3, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. Khirallah further teaches that wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level (Khirallah, in Paragraphs [0006]-[0009], teaches that for 3GPP LTE networks, the concept of a QoS Class Identifier (QCI) was introduced as a mechanism to facilitate a class-based QoS architecture in which different types of bearer traffic are classified into different classes, each of which represents a respective QoS appropriate for that type of traffic. Each class is identified by a respective QCI. In LTE in which multiple applications may be running in a UE, the base station (eNB for LTE) has respective set of QoS parameters (including a QCI, an Allocation and Retention Priority (ARP), and other resource type (e.g. guaranteed bit rate (GBR) resource type or non-GBR resource type) dependent parameters for each enhanced radio access bearer (E-RAB) between the UE and the core network (serving gateway, S-GW). Accordingly, the QoS provided was at a radio bearer level of granularity. The QCI concept has been extended in 5G with a QCI (referred to as a 5G QoS Indicator (or '5QI')) being associated with each QoS flow (rather than each E-RAB). Like the LTE QCI, the 5G QCI (5QI) is a scalar that is used as a reference to a specific set of QoS characteristics (e.g. access node-specific parameters) that control the QoS forwarding treatment applied (e.g. the applied scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). Therefore, it is clear that the QoS indicator may be selected form the list consisting of a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Khirallah to include the technique of wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level of Khirallah in the system of combination of Vivanco and Mchardy to provide a communication system and associated apparatus and method to optimize the Data Radio Bearer (DRB) for packets with multiple different QoS flow characteristics, to achieve and to maintain the QoS requirement (Khirallah, see Paragraphs [0021]-[0024]).). Regarding claim 11, combination of Vivanco and Mchardy teaches the features defined in the claim 10, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. Khirallah further teaches that wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level (Khirallah, in Paragraphs [0006]-[0009], teaches that for 3GPP LTE networks, the concept of a QoS Class Identifier (QCI) was introduced as a mechanism to facilitate a class-based QoS architecture in which different types of bearer traffic are classified into different classes, each of which represents a respective QoS appropriate for that type of traffic. Each class is identified by a respective QCI. In LTE in which multiple applications may be running in a UE, the base station (eNB for LTE) has respective set of QoS parameters (including a QCI, an Allocation and Retention Priority (ARP), and other resource type (e.g. guaranteed bit rate (GBR) resource type or non-GBR resource type) dependent parameters for each enhanced radio access bearer (E-RAB) between the UE and the core network (serving gateway, S-GW). Accordingly, the QoS provided was at a radio bearer level of granularity. The QCI concept has been extended in 5G with a QCI (referred to as a 5G QoS Indicator (or '5QI')) being associated with each QoS flow (rather than each E-RAB). Like the LTE QCI, the 5G QCI (5QI) is a scalar that is used as a reference to a specific set of QoS characteristics (e.g. access node-specific parameters) that control the QoS forwarding treatment applied (e.g. the applied scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). Therefore, it is clear that the QoS indicator may be selected form the list consisting of a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Khirallah to include the technique of wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level of Khirallah in the system of combination of Vivanco and Mchardy to provide a communication system and associated apparatus and method to optimize the Data Radio Bearer (DRB) for packets with multiple different QoS flow characteristics, to achieve and to maintain the QoS requirement (Khirallah, see Paragraphs [0021]-[0024]).). Regarding claim 18, combination of Vivanco and Mchardy teaches the features defined in the claim 17, -refer to the indicated claim for reference(s). However, combination of Vivanco and Mchardy does not explicitly teach that wherein the QoS indicator comprises an indicator selected from the list consisting of:a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. Khirallah further teaches that wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level (Khirallah, in Paragraphs [0006]-[0009], teaches that for 3GPP LTE networks, the concept of a QoS Class Identifier (QCI) was introduced as a mechanism to facilitate a class-based QoS architecture in which different types of bearer traffic are classified into different classes, each of which represents a respective QoS appropriate for that type of traffic. Each class is identified by a respective QCI. In LTE in which multiple applications may be running in a UE, the base statin (eNB for LTE) has respective set of QoS parameters (including a QCI, an Allocation and Retention Priority (ARP), and other resource type (e.g. guaranteed bit rate (GBR) resource type or non-GBR resource type) dependent parameters for each enhanced radio access bearer (E-RAB) between the UE and the core network (serving gateway, S-GW). Accordingly, the QoS provided was at a radio bearer level of granularity. The QCI concept has been extended in 5G with a QCI (referred to as a 5G QoS Indicator (or '5QI')) being associated with each QoS flow (rather than each E-RAB). Like the LTE QCI, the 5G QCI (5QI) is a scalar that is used as a reference to a specific set of QoS characteristics (e.g. access node-specific parameters) that control the QoS forwarding treatment applied (e.g. the applied scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). Therefore, it is clear that the QoS indicator may be selected form the list consisting of a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level. It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Vivanco, Mchardy, and Khirallah to include the technique of wherein the QoS indicator comprises an indicator selected from the list consisting of: a QoS class identifier (QCI) value, a fifth generation (5G) QCI (5QI) value, and an allocation and retention priority (ARP) level of Khirallah in the system of combination of Vivanco and Mchardy to provide a communication system and associated apparatus and method to optimize the Data Radio Bearer (DRB) for packets with multiple different QoS flow characteristics, to achieve and to maintain the QoS requirement (Khirallah, see Paragraphs [0021]-[0024]).). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to JAEYOUNG KWAK whose telephone number is (703)756-1768. The examiner can normally be reached Monday-Friday 9 AM -5 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, Kevin Bates can be reached at 571-272-3980. 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. /JAEYOUNG KWAK/Examiner, Art Unit 2472 /KEVIN T BATES/Supervisory Patent Examiner, Art Unit 2472
Read full office action

Prosecution Timeline

Show 4 earlier events
Jul 14, 2025
Response Filed
Nov 03, 2025
Final Rejection mailed — §103
Nov 04, 2025
Interview Requested
Nov 17, 2025
Applicant Interview (Telephonic)
Nov 17, 2025
Examiner Interview Summary
Jan 30, 2026
Request for Continued Examination
Feb 10, 2026
Response after Non-Final Action
Apr 23, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12634750
ERROR PROTECTION OF DATA UNIT SERVICE FIELD IN WIRELESS LOCAL AREA NETWORK TRANSMISSIONS
3y 10m to grant Granted May 19, 2026
Patent 12634056
CODE BLOCK OPERATION FOR PHYSICAL UPLINK SHARED CHANNEL REPETITIONS WITH TRANSPORT BLOCK SCALING AND FREQUENCY HOPPING
3y 3m to grant Granted May 19, 2026
Patent 12628223
METHOD AND APPARATUS FOR POWER SAVING IN WIRELESS COMMUNICATION SYSTEM
3y 0m to grant Granted May 12, 2026
Patent 12563627
METHOD AND APPARATUS FOR HANDLING USER PLANE IN WIRELESS COMMUNICATION SYSTEM SUPPORTING MR-MC
3y 0m to grant Granted Feb 24, 2026
Patent 12563487
MANAGING FIXED WIRELESS ACCESS FOR EFFICIENT ENERGY USAGE
2y 11m to grant Granted Feb 24, 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
85%
Grant Probability
99%
With Interview (+28.6%)
3y 2m (~0m remaining)
Median Time to Grant
High
PTA Risk
Based on 13 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