The present disclosure relates to wireless communications, and more specifically, relates to managing data networks on user equipments.
BACKGROUND
[0002] Recently, multiple techniques, such as load balancing, offloading, have been developed and deployed to improve user service quality or user experience while operating a mobile application. In the same context, some of the prior art references are given below:
[0003] A prior art reference "Multipath transmission control protocol-based multi-access traffic steering solution for 5G multimedia-centric network: Design and testbed system implementation" discloses that access traffic steering, switching, and splitting (ATSSS) is a traffic aggregation technology at the network level. It can easily expand throughput or provide redundancy under the common CN (Release 15) architecture that accommodates various types of ANs (e.g. 5G new radio (NR), Wi-Fi, satellite, broadband fixed). The ATSSS technology began to be standardized in Release 16.22 It aims to overcome the limitations of the MPTCP-based traffic aggregation function deployed outside the 3GPP network and to provide traffic aggregation more efficiently at the network level.
[0004] Another prior art reference "CN108353010B" relates to techniques for integration of wireless access and wired networks. One embodiment is a method, and comprises: receiving a bandwidth report ("BWR") at a termination element of a first network, wherein the BWR includes information regarding a data transmission opportunity of at least one endpoint data on a second network; scheduling a first network transmission opportunity for the at least one endpoint data using information derived from the received BWR; and receiving the at least one endpoint data from the first network forwarding device according to the scheduled first network transmission opportunity.
[0005] Another prior art reference "US9392515B2" teaches methods and systems splitting data in a wireless communications network. Data may be split to

use multiple base stations for transmission to user equipment, or may be split by user equipment for transmission to multiple base stations. In an embodiment, data splitting may be performed at the Packet Data Convergence Protocol (PDCP) layer. In an embodiment, data may be split at the Radio Link Control (RLC) layer. In an embodiment, data may be split at the Media Access Control (MAC) layer. In each of these embodiments, data may be split on user equipment and/or on a base station. In an embodiment, data may instead be split at the user plane, such as in a serving gateway.
[0006] Yet another prior art reference "CN103797888A" discloses systems, devices, and configurations to implement trusted connections within wireless networks and associated devices and systems are generally disclosed herein. In some examples, a wireless local area network (WLAN) may be attached to a 3 GPP evolved packet core (EPC) as a trusted access network, without use of an evolved packet data gateway (ePDG) and overhead from related tunneling and encryption. Information to create the trusted attachment between a mobile device and a WLAN may be exchanged using Access Network Query Protocol (ANQP) extensions defined by IEEE standard 802.11u-2011, or using other protocols or standards such as DHCP or EAP. A trusted WLAN container with defined data structure fields may be transferred in the ANQP elements to exchange information used in the establishment and operation of the trusted attachment.
[0007] Yet another prior art reference "US20140092742A1" discloses management apparatus and method to support wireless local area network (WLAN) offloading. A network management system (NMS) for WLAN offloading may include a network manager (NM); a first element manager (EM), coupled to the network manager, to communicate with the network manager and one or more WLANs; and a second EM, coupled to the NM, to communicate with the NM and one or more base stations of a cellular network. Coverage areas of at least one access point (AP) of the one or more WLANs are overlaid with at least one cell of the cellular network to support a WLAN offloading operation. Further, the NM is to activate the WLAN offloading operation based at least in part on at least one indicator received from the one or more WLANs.

[0008] While the prior arts provide various techniques to enhance the user experience like by switching between two network channels, however, there is a dearth of techniques that provide smooth and seamless transition between two network channels while improving the user experience and network utilization optimization. Therefore, there is a scope of improvement.
OBJECT OF THE DISCLOSURE
[0009] A principal object of the present disclosure is to manage data networks on a user equipment (UE).
[0010] Another object of the present disclosure is to enhance user experience by utilizing 3GPP (3rd Generation Partnership Project) network and Wi-Fi networks simultaneously.
[0011] Another object of the present disclosure is to utilize Access Traffic Steering, Switching and Splitting (ATSSS) technology and to optimize network utilization.
SUMMARY
[0012] Accordingly, a system and a method for managing a plurality of data networks on a user equipment (UE) are disclosed.
[0013] The method comprises configuring an application by one of a user, an operator and an app owner and receiving one or more rulesets on the UE from a network and utilizing an 3GPP (3rd Generation Partnership Project) network and a Wi-Fi channel on the UE simultaneously for data usage. Simultaneous utilization of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel comprises utilizing the 3GPP (3rd Generation Partnership Project) network by a first one or more UE applications and utilizing the Wi-Fi channel by a second one or more UE applications. The simultaneous utilization of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel occurs by access traffic steering, switching and splitting (ATSSS), wherein the network pushes the one or more rulesets into the UE that allows to control traffic to a network operator for a desired application based on security, criticality, and

priority, wherein steering includes packet-level switching and splitting through a multipath transmission control protocol (MP-TCP) and a flow-based data switching.
[0014] The simultaneous utilization and enabling the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel on the UE comprises performing authentication and key generation by the application, fetching the one or more rulesets by the application, enabling one or more UE applications based on a configured channel by the application and generating integrity protection policy for the one or more UE applications by the one or more rulesets based on an integrity protection technique included in the ATSSS. The enabling of the one or more UE applications by the application comprises performing an integrity protection by the application on one or more existing applications in the UE by using rules, traffic descriptor and access selection descriptor.
[0015] Further, the method includes configuring one of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel for the one or more UE applications on the UE, wherein the one or more rulesets associate the one or more UE applications with at least one of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel and switching of a UE application between the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel happens based on the one or more rulesets.
[0016] The method includes launching the one or more rulesets in the UE to provide selection of a channel for the one or more UE applications, where one UE application uses one channel at a time based on priority selection.
[0017] These and other aspects herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the invention herein without departing from the spirit thereof.

BRIEF DESCRIPTION OF FIGURES
[0018] The invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the drawings. The invention herein will be better understood from the following description with reference to the drawings, in which:
[0019] FIG. 1 illustrates a system for managing data networks on a user equipment (UE).
[0020] FIG. 2 illustrates various elements of the UE.
[0021] FIG. 3 and FIG. 4 illustrate example screens of the UE depicting registration process and applications using different data network channels respectively.
[0022] FIG. 5 illustrates a method for managing data networks on the UE.
DETAILED DESCRIPTION
[0023] In the following detailed description of the invention, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be obvious to a person skilled in the art that the invention may be practiced with or without these specific details. In other instances, well known methods, procedures and components have not been described in detail so as not to unnecessarily obscure aspects of the invention.
[0024] Furthermore, it will be clear that the invention is not limited to these alternatives only. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art, without parting from the scope of the invention.
[0025] The accompanying drawings are used to help easily understand various technical features and it should be understood that the alternatives presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein

to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.
[0026] Now simultaneous reference is made to FIG. 1 through FIG. 4, in which, FIG. 1 illustrates a system 100 for managing data/access networks on a user equipment (UE), FIG. 2 illustrates various elements of the UE, FIG. 3 and FIG. 4 illustrate example screens of the UE depicting registration process and applications using different data network channels respectively.
[0027] The system 100 may comprise the user equipment (UE) 102 connected to a network 108. The UE 102 may be a mobile phone, smart phone, laptop, desktop, for example. The network 108 may be a core network, for example 5G core network. The system 100 may manage a plurality of data networks on the UE 102 by simultaneous utilization of a first channel 104 and a second channel 106. The first channel 104 may be based on a 3GPP access network and the second channel 106 may be based on a non-3 GPP access network or vice-versa. In an example, the first channel 104 may be an 3GPP and the second channel 106 may be a Wi-Fi channel.
[0028] In order to simultaneously use and enable the first channel 104 and the second channel 106, the UE 102 may perform authentication and key generation using an application (data throughput unit 204 as shown in FIG. 2). The application 204 may be configured by a user, an operator, an app owner, for example. The application 204 may fetch one or more rulesets (or policies) from the network 108 (as shown in FIG. 3) that enables one or more UE applications (UE Application 1, UE Application 2.. UE Application n as shown in FIG. 2) 210 based on configured channel by performing integrity protection on one or more existing applications in the UE 102 by using rules, traffic descriptor, access selection descriptor, for example, as shown in Table 1 below. The one or more rulesets may generate integrity protection policy for the one or more UE applications based on an integrity protection algorithm included in ATSSS.
[0029] The UE 102 may simultaneously utilize the 3GPP (3rd Generation Partnership Project) network 104 and the Wi-Fi channel 106 for data usage by utilizing the ATSSS, where a first one or more UE applications may utilize the

3GPP (3rd Generation Partnership Project) network 104 and a second one or more UE applications may utilize the Wi-Fi channel 106. The system 100 may configure one of the 3GPP (3rd Generation Partnership Project) network 104 and the Wi-Fi channel 106 for the one or more UE applications on the UE 102, where one UE application can use only one channel at a time based on priority selection. The one or more UE applications may be configured by a user, an operator, an app owner, for example.
[0030] The UE 102 and the network 108 may be ATSSS enabled. The ATSSS stands for Access Traffic Steering, Switching and Splitting, which may be supported by the UE 102 and the network 108. The ATSSS feature/technique may be sustained over any access network such as untrusted and trusted non-3 GPP access networks, wireline 5G access networks, for example, as long as an MA-PDU (Multi-Access Protocol Data Unit) session can be established over such access network(s). Typically, the ATSSS technique enables the MA-PDU session that may exchange PDUs between the UE 102 and a data network by simultaneously using the first channel 104 and the second channel 106 and two independent N3/N9 tunnels between a user plane function (UPF) 110 and an access network or radio access network or gNB. The UPF 110 is a fundamental and vital component of the 5G core infrastructure enabling low-latency edge computing and terminates an N6 interface of a PDU session within the network 108. The N6 interface provides connectivity between the UPF 110 and other external or internal networks or service platforms, such as Internet, public cloud or private clouds. The N3 interface facilitates user data transfer from the access network to the UPF 110, making it possible to create both low and high-latency services and the N9 interface is an interface between two UPF's, for example, an Intermediate I-UPF and a UPF Session Anchor.
[0031] An MA-PDU connectivity service may be realized by establishing the MA-PDU session, i.e., a PDU session that may have user-plane resources on two access networks, which assumes both 3 GPP access and non-3 GPP access are allowed for an S-NSSAI (Single Network Slice Selection Assistance Information) of the PDU session. The PDU session may be a UE initiated PDU session, a UE

initiated PDU session handover between 3 GPP and non-3 GPP, a UE initiated PDU session handover from EPS (Evolved Packet System) to 5GS (5G System), a network triggered PDU session.
[0032] The UE 102 may request the MA-PDU session when the UE 102 is registered via any of the 3GPP and non-3GPP accesses. The MA-PDU session may be based on one of IPv4, IPv6, IPv4v6, and Ethernet. After the establishment of the MA-PDU session and when there are user-plane resources on both access networks, the UE 102 applies network-provided policy, i.e., ATSSS rulesets (also referred to as one or more rulesets) and considers local conditions like network interface availability, signal loss conditions, user preferences, for example, to decide on a distribution of uplink traffic across the two access networks. Similarly, the UPF anchor of the MA-PDU session applies network-provided policy like N4 rules and feedback information received from the UE 102 via the user-plane such as unavailability or availability of the access network to decide on a distribution of downlink traffic across the two N3/N9 tunnels and two access networks. When there are user-plane resources on only one access network, the UE 102 applies the ATSSS rulesets and considers local conditions for triggering the establishment or activation of the user plane resources over another access.
[0033] In short, the system 100 may be configured to push the one or more rulesets on the UE 102 from the network 108. Launching the one or more rulesets in the UE device 102 may provide selection of the channel for the one or more UE applications. The one or more rulesets may associate the one or more UE applications with at least one of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel, based on which, a UE application may be switched between the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel. Some example ATSSS rulesets are shown below in Table 1:
Table 1: Sample ATSSS rulesets

Information Name Details

Rule Precedence Determines the order in which the ATSSS rule is evaluated in the UE.
Traffic Descriptor Application Descriptor (list)

IP descriptors {list)
5-tuple: IP source and destination addresses and ports and protocol

Non-IP descriptors (list)
Destination of non-IP (Ethernet} traffic
Access Selection Descriptor Steering Mode Active Standby
Active = 3GPP | non-3GPP

Smallest Delay
(see 5.32.5 of 23.501 for Access Network Performance
Measurements)

Load-Balancing
3GPP% = Percentage
Non-3GPP%M00%-3GPP%

Priority-based
Priority Access = [ 3GPP | non-3GPP]

Steering Functionality MP-TCPorATSSS-LL
[0034] In LTE (Long Term Evolution), the capability to utilize both 3GPP and Non-3GPP access networks has been there from the early days of the wireless communications technology. As LTE matured, so too did the techniques available for manipulating how data should be split and transferred over each access network, particularly when both access types are available for use. 5G's ATSSS technique requires the 5G core network 108 for implementation, provides similar functionality to the aforementioned 4G steering techniques. In particular, ATSSS allows the service provider to configure ATSSS rulesets and push them to the UE 102 via the network 108. The ATSSS rulesets dictate how the UE 102 should utilize the 3 GPP and Non-3 GPP access networks it may have available, specifically with respect to sending uplink traffic. Conversely, for downlink traffic, the network 108 may provide the ATSSS rulesets to the UPF 110 which dictate which access network should be used for which traffic flow. In other

words, implementation of ATSSS allows the network 108 to push the one or more rulesets (policies) into the UE 102 that allows to control the traffic to network operator for desired applications based on security, criticality, and priority, where the steering functionality may include a packet-level switching and splitting through multipath transmission control protocol (MP-TCP) and flow-based data switching (ATSSS-LL). Packet-Level Switching is a method of grouping data into packets that are transmitted over a digital network. Packets are made of a header and a payload. Data in the header is used by networking hardware to direct the packet to its destination, where the payload is extracted and used by an operating system, application software, or higher layer protocols. Packet switching is the primary basis for data communications in computer networks worldwide. Packet-Level Split is something both eNB will have same bearer (bearer ID also same) and splits the single IP flow (single service packets) into two and forwards in the two bearers. Multi-Path TCP (MP-TCP) is an effort towards enabling the simultaneous use of several IP-addresses/interfaces by a modification of TCP that presents a regular TCP interface to applications, while in fact spreading data across several sub-flows. Flow-Based Data Switching is a cache-based forwarding mechanism that performs packet forwarding for the first packet in a flow, performs cache lookup on subsequent packets of the same flow and applies cached results without evaluating the input and output path. ATSSS-LL is meant to define a layer-2 Multi-Access mechanism between the UE 102 and the UPF 110 at the user plane of the network 108. In the case of Ethernet PDU, it is the only mechanism available in ATSSS, whereas if PDU is IP v4/v6, ATSSS-LL complements MP-TCP by managing the traffic which is not making use of MP-TCP.
[0035] Further, steering modes may be Active-Standby, Smallest Delay, Load Balancing and Priority Based.
[0036] In the Active-Standby mode, one of the two links/channels is marked as a master and the other as a slave, in which the traffic is sent via the master link unless the same becomes temporarily unavailable. In the Smallest Delay mode, the link which, at the moment of session initiation, shows the lowest

RTT is used. If the link becomes unavailable, then the other link will be used during the session. In the Load Balancing mode, a % of share between the two channels/links can be specified, for example 60% and 40%. If one of the two links/channels becomes unavailable, the balancing goes all in favour of the other link (100%)). In the Priority based mode, the traffic is sent initially only to the link marked with a higher priority, until it results congested. The traffic is steered to a low priority link/channel, if the high priority link/channel becomes unavailable.
[0037] Advantageously, the present disclosure results in cost saving as expanding Wi-Fi network can save huge cost compared to expanding the mobile spectrum. Further, the present disclosure facilitates improved data transmission rate, thereby improving user experience. The best example for this to restrict the data usage from certain applications where the user is in international roaming. Further, the present disclosure allows to control the traffic to a network operator for a desired application based on security, criticality and priority.
[0038] Although FIG. 1 shows various components of the system 100 but it is to be understood that other embodiments are not limited thereon. The system 100 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and do not limit the scope of the present disclosure. One or more components can be combined together to perform same or substantially similar function in the system 100.
[0039] Referring to FIG. 2, the UE 102 may comprise a transceiver 202, the data throughput unit 204, a storage unit 206, at least one processor or controller 208 and the one or more UE applications 210 (as shown in FIG. 4). However, the components of the UE 102 are not limited to the above-described example, and for example, the UE 102 may include more or fewer components than the illustrated components. Further, the labels or names of the components are used only for illustrative purpose and do not limit the scope of the present disclosure. One or more components can be combined together to perform same or substantially similar function in the UE 102.
[0040] The transceiver 202 may transmit and receive signals to and from a base station to enable the first channel 104 on the UE 102 and transmit and

receive signals to and from a router, for example, to enable the second channel 106.
[0041] The data throughput unit 204 is the application described in conjunction with FIG. 1. The user may register in the data throughput unit 204 by providing sufficient user information. The data throughput unit 204 may receive the one or more rulesets from the network 108 to enable simultaneous utilization of the first channel 104 and the second channel 106 for the one or more UE applications 210. Non-limiting examples of the one or more UE applications 210 are shown in FIG. 4 that utilizes different data network channels. That is, the first one or more UE applications utilize the 3GPP (3rd Generation Partnership Project) network 104 and the second one or more UE applications utilize the Wi-Fi channel 106.
[0042] The storage unit 206 may store programs and data necessary for the operation of the data throughput unit 204 and the one or more UE applications 210. In addition, the storage unit 206 may store control information or data included in signals transmitted and received by the UE 102. The storage unit 206 may be composed of a storage medium such as read only memory (ROM), random access memory (RAM), hard disk, compact disc ROM (CD-ROM), and digital versatile disc (DVD), or a combination of storage media. Also, there may be a plurality of storage units.
[0043] The controller 208 may control a series of processes so that the UE 102 can operate according to description described above. There may be a plurality of controllers that may perform a component control operation of the UE 102 by executing a program stored in the storage unit 206.
[0044] FIG. 5 illustrates a method for managing data networks on the UE 102. It may be noted that in order to explain the method steps of the flowchart 500, references will be made to the elements explained in FIG. 1 through FIG. 4.
[0045] At step 502, the method includes receiving the one or more rulesets on the UE 102 from the network 108.
[0046] At step 504, the method includes simultaneously utilizing the first channel 104 and the second channel 106 for data usage based on best network

availability, where the first channel 104 may be based on the 3GPP access network, such as the 3GPP (3rd Generation Partnership Project) network and the second channel 106 may be based on the non-3 GPP access network, such as the Wi-Fi channel or vice-versa.
[0047] It may be noted that the flowchart 500 is explained to have above stated process steps; however, those skilled in the art would appreciate that the flowchart 500 may have more/less number of process steps which may enable all the above stated implementations of the present disclosure.
[0048] The various actions act, blocks, steps, or the like in the flow chart and sequence diagrams may be performed in the order presented, in a different order or simultaneously. Further, in some implementations, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure.
[0049] The embodiments disclosed herein can be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.
[0050] It will be apparent to those skilled in the art that other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention. While the foregoing written description of the invention enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiment, method, and examples herein. The invention should therefore not be limited by the above-de scribed embodiment, method, and examples, but by all embodiments and methods within the scope of the invention. It is intended that the specification and examples be considered as exemplary, with the true scope of the invention being indicated by the claims.
[0051] The methods and processes described herein may have fewer or additional steps or states and the steps or states may be performed in a different order. Not all steps or states need to be reached. The methods and processes

described herein may be embodied in, and fully or partially automated via, software code modules executed by one or more general purpose computers. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all of the methods may alternatively be embodied in whole or in part in specialized computer hardware.
[0052] The results of the disclosed methods may be stored in any type of computer data repositories, such as relational databases and flat file systems that use volatile and/or non-volatile memory (e.g., magnetic disk storage, optical storage, EEPROM and/or solid-state RAM).
[0053] The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
[0054] Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. A general-purpose processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another

embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
[0055] The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.
[0056] Conditional language used herein, such as, among others, "can," "may," "might," "may," "e.g.," and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey those certain alternatives include, while other alternatives do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more alternatives or that one or more alternatives necessarily

include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular alternative. The terms "comprising," "including," "having," and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term "or" is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term "or" means one, some, or all of the elements in the list.
[0057] Disjunctive language such as the phrase "at least one of X, Y, Z," unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain alternatives require at least one of X, at least one of Y, or at least one of Z to each be present.
[0058] While the detailed description has shown, described, and pointed out novel features as applied to various alternatives, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the scope of the disclosure. As can be recognized, certain alternatives described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.

CLAIMS
We Claim:

1. A method for managing a plurality of data networks on a user equipment
(UE) (102), the method comprising:
simultaneously utilizing an 3GPP (3rd Generation Partnership Project) network (104) and a Wi-Fi channel (106) on the UE (102) for data usage.
2. The method as claimed in claim 1, wherein simultaneously utilizing the
3GPP (3rd Generation Partnership Project) network (104) and the Wi-Fi channel
(106) comprising:
utilizing the 3GPP (3rd Generation Partnership Project) network by a first one or more UE applications; and
utilizing the Wi-Fi channel (106) by a second one or more UE applications.
3. The method as claimed in claim 2 comprising simultaneous utilization of the 3GPP (3rd Generation Partnership Project) network (104) and the Wi-Fi channel (106) by access traffic steering, switching and splitting (ATSSS), wherein a network (108) pushes one or more rulesets into the UE (102) that allows to control traffic to a network operator for a desired application based on security, criticality, and priority, wherein steering includes packet-level switching and splitting through a multipath transmission control protocol (MP-TCP) and a flow-based data switching.
4. The method as claimed in claim 1 comprising configuring one of the 3GPP (3rd Generation Partnership Project) network and the Wi-Fi channel (106) for one or more UE applications (210) on the UE (102).

5. The method as claimed in claim 1 comprising receiving one or more rulesets on the UE (102) from a network (108), wherein the one or more rulesets associate one or more UE applications (210) with at least one of the 3GPP network (104) and the Wi-Fi channel (106).
6. The method as claimed in claim 5 comprising switching a UE application between the 3GPP network (104) and the Wi-Fi channel (106) based on the one or more rulesets.
7. The method as claimed in claim 1 comprising configuring an application (204) by one of a user, an operator and an app owner.
8. The method as claimed in claim 1, wherein launching one or more rulesets in the UE (102) provides selection of a channel for one or more UE applications (210), where one UE application uses one channel at a time based on priority selection.
9. The method as claimed in claim 1, wherein simultaneously utilizing and enabling the 3GPP network (104) and the Wi-Fi channel (106) on the UE (102), comprising:
performing, by an application (204), authentication and key generation;
fetching, by the application (204), one or more rulesets;
enabling, by the application (204), one or more UE applications (210) based on a configured channel; and
generating, by the one or more rulesets, integrity protection policy for the one or more UE applications (210) based on an integrity protection technique included in an ATSSS.

10. The method as claimed in claim 9, wherein enabling the one or more UE applications (210) by the application (204) comprising:
performing, by the application (204), integrity protection on one or
more existing applications in the UE (102) by using rules, traffic
descriptor and access selection descriptor.