Abstract:
The present disclosure relates to a communication method and system for converging a 5 th -generation (5G) communication system for supporting higher data rates beyond a 4 th -generation (4G) system with a technology for internet of things (IoT). The present disclosure may be applied to intelligent services based on 5G communication technology and IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. A system and a method for routing a data packet to a user equipment (UE) in a long term evolution-wireless local area network (LTE-WLAN) aggregation are provided. The system includes an evolved node B (eNB) with a packet data convergence protocol (PDCP) adaptation layer that adds a header to the data packet.

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
       [0001]    This application is a U.S. National Stage application under 35 U.S.C. §371 of an International application filed on Apr. 8, 2016 and assigned application number PCT/KR2016/003713, which claimed the benefit of an Indian patent application filed on Apr. 10, 2015 in the Indian Patent Office and assigned Serial number 1891/CHE/2015, and of an Indian patent application filed on Apr. 7, 2016 in the Indian Patent Office and assigned Serial number 1891/CHE/2015, the entire disclosure of each of which is hereby incorporated by reference. 
     
    
     TECHNICAL FIELD 
       [0002]    The present disclosure relates to a wireless communication. More particularly, the present disclosure relates to a mechanism for routing a data packet to a user equipment (UE) in a long term evolution-wireless local area network (LTE-WLAN) aggregation. 
       BACKGROUND 
       [0003]    To meet the demand for wireless data traffic having increased since deployment of 4th-generation (4G) communication systems, efforts have been made to develop an improved 5th-generation (5G) or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post long term evolution (LTE) System’. The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like. In the 5G system, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed. 
         [0004]    The internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the internet of things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The internet of everything (IoE), which is a combination of the IoT technology and the big data processing technology through connection with a cloud server, has emerged. As technology elements, such as “sensing technology”, “wired/wireless communication and network infrastructure”, “service interface technology”, and “security technology” have been demanded for IoT implementation, a sensor network, a machine-to-machine (M2M) communication, machine type communication (MTC), and so forth have been recently researched. Such an IoT environment may provide intelligent Internet technology services that generate a new value to human life by collecting and analyzing data generated among connected things. IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing information technology (IT) and various industrial applications. 
         [0005]    In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, MTC, and M2M communication may be implemented by beamforming, MIMO, and array antennas. Application of a cloud RAN as the above-described big data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology. 
         [0006]    Meanwhile, the third generation partnership project (3GPP) is working on an upcoming architecture where a LTE and a wireless local area network (WLAN) will be aggregated such that the LTE will control a transmission of packets over the WLAN. The WLAN access points (APs) will be hidden from a core network (CN) in the LTE; the associated evolved nodeB (eNB) will control the corresponding APs. In such an architecture where the LTE and the WLAN are aggregated such that the LTE controls the WLAN, one or more flows of one or more user equipment (UEs) associated with an LTE eNB can be either fully or partially diverted over the WLAN where the decision of routing the packets is determined by the eNB. In such the architecture, the way that the WLAN identifies the packets corresponding to the UE and flow of the UE is not yet addressed. This is of paramount importance because a receiver of the WLAN entity needs to route packets to the appropriate data plane entities of the associated UE. In the LTE, each flow (referred to as data radio bearer (DRB)) is handled by independent radio link control (RLC)/packet data convergence protocol (PDCP) entities, hence when the data packets are arriving at the receiver from the WLAN, it needs to be passed on to the correct data plane entity. 
         [0007]    The WLAN APs will be hidden from the core network, the associated LTE eNB will control the corresponding WLAN APs. The 3GPP/WLAN radio interworking Release-12 solution enhances CN-based WLAN offload by improving user quality of experience (QoE) and network utilization and providing more control to operators. These improvements can be further enhanced by the LTE-WLAN aggregation system, similar to enhancements already available from existing LTE carrier aggregation and dual connectivity features. The LTE-WLAN aggregation system provides the following advantages. The WLAN access network becomes transparent to the CN. This provides the operator unified control and management of both 3GPP and WLAN networks as opposed to separately managing the 3GPP and WLAN networks. The aggregation and tight integration at radio level allows for real-time channel and load aware radio resource management across the WLAN and the LTE to provide significant capacity and QoE improvements. 
         [0008]    The reliable LTE network can be used as a control and mobility anchor to provide the QoE improvements, minimize service interruption, and increase operator control. The WLAN-related CN signaling is eliminated. Thus results in reducing CN load in the LTE-WLAN aggregation system. 
         [0009]    The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present disclosure. 
       SUMMARY 
       [0010]    The benefits of long term evolution-wireless local area network (LTE-WLAN) aggregation system can be realized in both co-located and non-collocated deployments. For the collocated case, corresponding to the small cell deployment, the LTE evolved nodeB (eNB) and WLAN access point (AP)/access controller (AC) are physically integrated and connected via an internal interface. This scenario is similar to the LTE carrier aggregation. For the non-collocated case, the LTE eNB and the WLAN are connected via an external interface. This scenario is similar to the LTE dual connectivity. In both collocated and non-collocated cases, the WLAN link behaves as second cell/carrier for data while the control is managed by the eNB through a radio resource control (RRC) entity. 
         [0011]    However, existing mechanism fails to route a data packet to the user equipment (UE) in the LTE-WLAN aggregation system. 
         [0012]    Aspects of the present disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages descried below. Accordingly, an aspect of the present disclosure is to provide a method and system for routing a data packet to a UE in an LTE-WLAN aggregation. 
         [0013]    Another aspect of the present disclosure is to provide a method for receiving, by a packet data convergence protocol (PDCP) adaptation layer of an eNB, a data packet from a PDCP layer. 
         [0014]    Another aspect of the present disclosure is to provide a method for adding a header which includes at least one of bearer identification (ID), quality of service (QoS) and a radio network temporary identifier (RNTI) to WLAN ID mapping information to the data packet. 
         [0015]    Another aspect of the present disclosure is to provide a method for sending a data packet along with a header to a WLAN AP. 
         [0016]    In accordance with an aspect of the present disclosure, an apparatus for routing a data packet to a UE in an LTE-WLAN aggregation is provided. The apparatus includes an eNB having a PDCP adaptation layer configured to receive the data packet from a PDCP layer. The PDCP adaptation layer is configured to add a header to the data packet. The header includes at least one of bearer ID, QoS and an RNTI to WLAN ID mapping information to the data packet. The PDCP adaptation layer is configured to transmit the data packet along with the header to the WLAN AP. 
         [0017]    In accordance with another aspect of the present disclosure, a method for routing, by an eNB, a data packet to a UE in an LTE-WLAN aggregation is provided. The method includes receiving, by a PDCP adaptation layer of the eNB, the data packet from a PDCP layer of the eNB, adding, by the PDCP adaptation layer, a header which includes at least one of bearer ID, QoS and an RNTI to WLAN ID mapping information to the data packet, and transmitting, by the PDCP adaptation layer, the data packet with the header to the WLAN AP. 
         [0018]    In accordance with another aspect of the present disclosure, a method for routing, by a WLAN AP, a data packet to a UE in an LTE-WLAN aggregation is provided. The method includes identifying a media access control (MAC) address of a UE from a data packet, wherein the data packet is received from a PDCP adaptation layer of an eNB, generating a MAC header from the MAC address, and sending the data packet along with the MAC header to the UE. 
         [0019]    Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the present disclosure. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0020]    The above and other aspects, features, and advantages of certain embodiments of the present disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: 
           [0021]      FIG. 1  illustrates generally, among other things, a high level overview of a long term evolution-wireless local area network (LTE-WLAN) aggregation system for routing a data packet to a user equipment (UE) according to an embodiment of the present disclosure; 
           [0022]      FIG. 2  illustrates a layer level implementation of the LTE-WLAN aggregation system as shown in  FIG. 1  according to an embodiment of the present disclosure; 
           [0023]      FIG. 3A  is a flow diagram illustrating a method for routing a data packet to a UE by an evolved nodeB (eNB) in an LTE-WLAN aggregation system according to an embodiment of the present disclosure; 
           [0024]      FIG. 3B  is a flow diagram illustrating a method for routing a data packet to a UE by a WLAN access point (WLAN AP) in an LTE-WLAN aggregation system according to an embodiment of the present disclosure; 
           [0025]      FIGS. 4, 5, 6, 7, 8, 9, and 10  show sequence diagrams indicating various operations and procedures involved in routing a data packet to a UE in an LTE-WLAN aggregation system according to various embodiments of the present disclosure; 
           [0026]      FIG. 11  is a sequence diagram indicating various operations and procedures involved in establishing communication between an eNB and a WLAN AP using a UE specific tunnel identified (TEID) according to an embodiment of the present disclosure; 
           [0027]      FIG. 12  is a sequence diagram indicating various operations and procedures involved in establishing communication between an eNB and a WLAN AP using a UE and flow specific TEID according to an embodiment of the present disclosure; 
           [0028]      FIG. 13  is a sequence diagram indicating various operations and procedures involved for indicating a UE preference indication according to an embodiment of the present disclosure; 
           [0029]      FIG. 14  is a sequence diagram indicating various operations and procedures involved for a UE preference configuration but not indicated to an eNB according to an embodiment of the present disclosure; 
           [0030]      FIG. 15  is a schematic of packet format in which a WLAN AP distinguishes an upper layer according to an embodiment of the present disclosure; and 
           [0031]      FIG. 16  illustrates a computing environment implementing a mechanism for routing a data packet to a UE in a LTE-WLAN aggregation system according to an embodiment of the present disclosure. 
       
    
    
       [0032]    Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. 
       DETAILED DESCRIPTION 
       [0033]    The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. 
         [0034]    The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents. 
         [0035]    It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. 
         [0036]    The embodiments herein provide a long term evolution-wireless local area network (LTE-WLAN) aggregation system for routing a data packet to a user equipment (UE). The evolved node B (eNB) determines to route the data packet through a WLAN access point (WLAN AP) before sending the data packet to a packet data convergence protocol (PDCP) adaptation layer. The system includes an eNB having a PDCP adaptation layer configured to receive the data packet from a PDCP layer. The PDCP adaptation layer is configured to add a header to the data packet. The PDCP adaptation layer is configured to send the data packet with the header to the WLAN AP. 
         [0037]    In an embodiment, the header includes a bearer identification (ID). 
         [0038]    In an embodiment, the header includes quality of service (QoS) information. 
         [0039]    In an embodiment, the header includes radio network temporary identifier (RNTI) to WLAN ID mapping information. 
         [0040]    In an embodiment, the header includes a combination of bearer ID, QoS, and RNTI to WLAN ID mapping information. 
         [0041]    In an embodiment, the WLAN AP is configured to identify a media access control (MAC) address of the UE from the data packet. The WLAN AP is configured to generate a MAC header from the MAC address, and send the data packet along with the MAC header to the UE. 
         [0042]    In an embodiment, the UE includes a PDCP adaptation layer configured to identify data packet routed from the eNB based on the bearer ID. 
         [0043]    In an embodiment, the PDCP adaptation layer is configured to generate duplicates of an internet protocol (IP) header in the IP packet received from the PDCP layer as a PDCP payload prior to addition of the header. 
         [0044]    In an embodiment, the IP header includes a source IP address and a destination IP address. The PDCP adaptation layer is configured to generate duplicates of the IP header in the IP packet received from the PDCP layer where the IP header includes the source IP address and the destination IP address. 
         [0045]    In an embodiment, the WLAN AP is configured to identify the MAC address from the destination IP address. 
         [0046]    In an embodiment, the WLAN AP is configured to map the destination IP address to the MAC address of the UE. 
         [0047]    In an embodiment, the eNB is configured to share the MAC address of the UE and the destination IP address of the UE to the WLAN AP. 
         [0048]    In an embodiment, the UE is configured to directly share IP address of the UE to the WLAN AP. 
         [0049]    In an embodiment, the PDCP adaptation layer is configured to encrypt the data packet prior to generate duplicates of the source IP address and the destination IP address. The PDCP adaptation layer is configured to send the encrypted data packet to the WLAN AP. 
         [0050]    In an embodiment, the eNB is configured to establish a tunnel with the WLAN AP and the PDCP adaptation layer includes a UE ID along with the data packet. A tunnel ID is exchanged between the eNB and the WLAN AP. 
         [0051]    In an embodiment, the tunnel is established based on at least one of an IP address of the UE and the MAC address of the UE. The UE shares the IP address of the UE to the WLAN AP or the MAC address of the UE to the LTE eNB. 
         [0052]    In an embodiment, the WLAN AP is configured to identify the MAC address of the UE from the UE ID received in the tunnel ID. 
         [0053]    In an embodiment, the WLAN AP is configured to check the QoS and route the data packet to the UE based on the QoS. 
         [0054]    In an embodiment, the eNB determines to route the data packet through the WLAN AP based on at least one of support of aggregation capability information, aggregation feature enable information, aggregation feature disable information, and preference indication information received from the UE during registration. 
         [0055]    In an embodiment, the eNB is configured to send an aggregation command including identity of the WLAN AP to the UE. 
         [0056]    The embodiments herein provide a method for routing a data packet to a UE in a LTE-WLAN aggregation system. The method includes receiving, by a PDCP adaptation layer of an eNB, the data packet from a PDCP layer of the eNB. Further, the method includes adding, by the PDCP adaptation layer, a header which includes at least one of bearer ID, QoS and a RNTI to WLAN ID mapping information to the data packet. Further, the method includes sending, by the PDCP adaptation layer, the data packet with the header to the WLAN AP. 
         [0057]    The embodiments herein provide a method implemented in a WLAN AP. The method includes identifying a MAC address of a UE from a data packet. The data packet is received from a PDCP adaptation layer of an eNB. Further, the method includes generating a MAC header from the MAC address, and sending the data packet along with the MAC header to the UE. 
         [0058]    Referring now to the drawings and more particularly to  FIGS. 1, 2, 3A, 3B, and 4 to 16 , where similar reference characters denote corresponding features consistently throughout the figure, there are shown preferred embodiments. 
         [0059]      FIG. 1  illustrates generally, among other things, a high level overview of an LTE-WLAN aggregation system  100  for routing a data packet to a UE  106  according to an embodiment of the present disclosure. 
         [0060]    Referring to  FIG. 1 , the system  100  includes eNB  102 , a plurality of WLAN APs  104   a  and  104   b , a plurality of UEs  106   a - 106   d.    
         [0061]    In an embodiment, the WLAN AP  104   a  and the WLAN AP  104   b  is an operator AP. 
         [0062]    In an embodiment, the WLAN AP  104   a  is an operator AP and the WLAN AP  104   b  is a private AP. 
         [0063]    The eNB  102  may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or the like. 
         [0064]    The UE  106  can be, for example but not limited to, a cellular phone, a tablet, a smart phone, a laptop, a personal digital assistant (PDA), or the like. 
         [0065]    The eNB  102  is configured to add a header to the data packet. The header includes bearer ID, QoS and a RNTI to WLAN ID mapping information. 
         [0066]    In an embodiment, the eNB  102  is configured to generate duplicates of an IP header prior to add the header. 
         [0067]    In an embodiment, the IP header includes a source IP address and a destination IP address. The eNB  102  is configured to generate only duplicates of the source IP address and the destination IP address prior to add the header. 
         [0068]    In an embodiment, the eNB  102  is configured to encrypt the data packet prior to generate duplicates of the source IP address and the destination IP address. The eNB  102  is configured to send the encrypted data packet to the WLAN AP  104 . 
         [0069]    By adding the header into the data packet, the eNB  102  is configured to send the data packet along with the header to the WLAN AP  104 . 
         [0070]    After receiving the data packet along with the header from the eNB  102 , the WLAN AP  104  is configured to identify a MAC address of the UE  106  from the data packet. Further, the WLAN AP  104  is configured to generate a MAC header from the MAC address. After generating the MAC header, the WLAN AP  104  is configured to send the data packet along with the MAC header to the UE  106 . 
         [0071]    In an embodiment, the WLAN AP  104  is configured to identify the MAC address from the destination IP address. In an embodiment, the WLAN AP  104  is configured to map the destination IP address to the MAC address of the UE  106 . 
         [0072]    In an embodiment, the eNB  102  is configured to share the MAC address of the UE  106  and the destination IP address of the UE  106  to the WLAN AP  104 . In an embodiment, the UE  106  is configured to directly share IP address of the UE  106  to the WLAN AP  104 . 
         [0073]    In an embodiment, in order to establish the communication between the eNB  102  and the WLAN AP  104 , the eNB  102  is configured to establish a tunnel with the WLAN AP  104  using a UE ID. A tunnel ID is exchanged between the eNB  102  and the WLAN AP  104 . 
         [0074]    After receiving the data packet along with the MAC header from the WLAN AP  104 , the UE  106  is configured to identify data packet routed from the eNB  102  based on the bearer ID. 
         [0075]    In an embodiment, the eNB  102  differentiates the WLAN AP  104   a  and WLAN AP  104   b  based on IP address which are assigned by a LTE network. 
         [0076]    Although  FIG. 1  shows units of the system  100  but it is to be understood that other embodiments are not limited thereon. In other embodiments, the system  100  may include less or more number of WLAN APs and UEs. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the present disclosure. One or more units can be combined together to perform same or substantially similar function to route the data packet to the UE  106  in the LTE-WLAN aggregation. 
         [0077]      FIG. 2  illustrates a layer level implementation of the LTE-WLAN aggregation system  200  as shown in  FIG. 1  according to an embodiment of the present disclosure. 
         [0078]    Referring to  FIG. 2 , the LTE-WLAN aggregation system  200  includes the eNB  102 , the WLAN AP  104 , and the UE  106 . The eNB  102  includes a PDCP adaption layer  108 , an IP layer, a PDCP layer, a radio link control (RLC) layer, a MAC layer, and a physical (PHY) layer. The WLAN AP  104  includes a WLAN logical link control (LLC) layer, a WLAN MAC layer, and a WLAN PHY layer. The UE  106  includes a PDCP adaption layer  110 , and a WLAN entity. 
         [0079]    In an embodiment, if the eNB  102  determines to route the data packet through the WLAN AP  104 , a PDCP adaptation layer  108  in the eNB  102  is configured to receive the data packet from the PDCP layer. 
         [0080]    After receiving the data packet from the PDCP layer, the PDCP adaptation layer  108  is configured to add the header to the data packet. The header includes at least one of the bearer ID, the QoS and the RNTI to WLAN ID mapping information. 
         [0081]    In an embodiment, the PDCP adaptation layer  108  is configured to generate duplicates of the IP header received from the PDCP layer prior to add the header. In an embodiment, the IP header includes the source IP address and the destination IP address. The PDCP adaptation layer  108  is configured to generate duplicates of only the source IP address and the destination IP address. 
         [0082]    In an embodiment, the PDCP adaptation layer  108  is configured to encrypt the data packet prior to generate duplicates of the source IP address and the destination IP address. The PDCP adaptation layer  108  is configured to send the encrypted data packet to the WLAN AP  104 . 
         [0083]    After adding the header into the data packet, the PDCP adaptation layer  108  is configured to send the data packet along with the header to the WLAN AP  104 . Upon receiving the data packet along with the header from the eNB  102 , the WLAN AP  104  is configured to identify the MAC address of the UE  106  from the data packet. Further, the WLAN AP  104  is configured to generate the MAC header from the MAC address. After generating the MAC header, the WLAN AP  104  is configured to send the data packet along with the MAC header to the UE  106 . 
         [0084]      FIG. 3A  is a flow diagram illustrating a method  300   a  for routing the data packet to the UE  106  by the eNB  102  in the LTE-WLAN aggregation system  100  according to an embodiment of the present disclosure. 
         [0085]    Referring to  FIG. 3A , the operations  302   a  to  306   a  are executed by the PDCP adaptation layer  108  of the eNB  102 . Initially, the eNB  102  determines to route the data packet through the WLAN AP  104 . At operation  302   a , the method  300   a  includes receiving the data packet from the PDCP layer of the eNB  102 . At operation  304   a , the method  300   a  includes adding the header to the data packet. The header has the bearer ID, the QoS and the RNTI to WLAN ID mapping information. At operation  306   a , the method  300   a  includes sending the data packet with the header to the WLAN AP  104 . 
         [0086]    The various actions, acts, blocks, operations, or the like in the method  300   a  may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure. 
         [0087]      FIG. 3B  is a flow diagram illustrating a method  300   b  for routing the data packet to the UE  106  by the WLAN AP  104  in the LTE-WLAN aggregation system  100  according to an embodiment of the present disclosure. 
         [0088]    Referring to  FIG. 3B , the operations  302   b  to  306   b  are performed by the WLAN AP  104 . At operation  302   b , the method  300   b  includes identifying the MAC address of the UE  106  from the data packet. The data packet is received from the PDCP adaptation layer  108  of the eNB  102 . At operation  304   b , the method  300   b  includes generating the MAC header from the MAC address. At operation  306   b , the method  300   b  includes sending the data packet along with the MAC header to the UE  106 . 
         [0089]    The various actions, acts, blocks, operations, or the like in the method  300   b  may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure. 
         [0090]      FIGS. 4, 5, 6, 7, 8, 9, and 10  show a sequence diagram indicating various operations and procedures involved in routing the data packet to the UE  106  in the LTE-WLAN aggregation system  100  according to various embodiments of the present disclosure. 
         [0091]    Referring to  FIG. 4 , the PDCP layer sends at operation  402  the PDCP packet to the PDCP adaptation layer  108  without encryption and robust header compression (ROHC). In an embodiment, the PDCP adaptation layer  108  duplicates at operation  404  the IP header which is present in a PDCP packet and appends the duplicated header before an adaptation header. The PDCP adaptation layer  108  adds at operation  406  the header to the PDCP packet received from the PDCP layer. The header includes the bearer ID. Further, the PDCP adaptation layer  108  identifies the start of the IP header based on the size of a PDCP header. In an embodiment, the PDCP layer sends the size of the PDCP header to the PDCP adaptation layer  108  or the size can be pre-defined in advance. In an embodiment, if the PDCP header is variable then the PDCP adaptation layer  108  parses the PDCP header to identify the length field and accordingly computes the length of the PDCP header. Thus, the PDCP adaptation layer  108  computes the start of the IP header where the start of the IP header is at an offset with respect to the start of PDCP packet it received such that the offset is equal to the length of the PDCP header. The PDCP adaptation layer  108  duplicates the IP header based on the start of the offset of the IP header and the length of IP header. 
         [0092]    In an embodiment, the PDCP adaptation layer  108  adds IP header including the bearer ID to the IP packet. In an embodiment, the PDCP layer performs packet routing on receiving the IP packets from the upper layer (i.e., IP layer). Further, the eNB  102  sends at operation  408  the data packet to the WLAN AP  104 . 
         [0093]    After receiving the data packet from the eNB  102 , the WLAN AP  104  identifies at operation  410  the MAC address from the IP address. Further, the WLAN AP  104  generates at operation  412  the MAC header using the identified MAC address. Further, the WLAN AP  104  sends at operation  414  the data packet along with the MAC header to the UE  106 . 
         [0094]    The PDCP adaptation layer  108  forwards the data packets to the WLAN AP  104 . The WLAN AP  104  generates the MAC address based on the IP header (which is the first header in the packet that it receives from the PDCP adaptation layer  108 ) and further adds the MAC header with the MAC address in the MAC header. The WLAN AP  104  maintains a mapping of IP header to the MAC address. 
         [0095]    The UE  106  includes a WLAN entity which uncovers at operation  416  the MAC header using legacy WLAN MAC procedures and passes the data packets to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  removes at operation  418  the duplicated IP header and parses the adaptation header. Based on the bearer ID present in the adaptation header, the WLAN entity routes the data packet to the corresponding entity (for example: PDCP layer of LTE) at the UE  106 . The bearer ID corresponds to the PDCP flow between the eNB  102  and the UE  106 . 
         [0096]    Referring to  FIG. 5 , the PDCP layer sends at operation  502  the PDCP packet to the PDCP adaptation layer  108  without encryption and ROHC. The PDCP adaptation layer  108  duplicates at operation  504  only the source address and the destination address included in the IP header. The PDCP adaptation layer  108  adds at operation  506  the header including the bearer ID. The PDCP adaptation layer  108  sends at operation  508  the data packet along with the header to the WLAN AP  104 . Once the WLAN AP  104  receives the data packet along with the header from the eNB  102 , the WLAN AP  104  identifies at operation  510  the MAC address from the destination address included in the IP header and generates at operation  512  the MAC header using the identified MAC Address. The WLAN AP  104  sends at operation  514  the data packet along with the MAC header to the UE  106 . The UE  106  receives the data packet along with the MAC header. The WLAN entity in the UE  106  uncovers at operation  516  the MAC header and passes the data packet to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  included in the UE  106  removes at operation  518 ) the duplicate IP header and passes to the PDCP layer based on the bearer ID. 
         [0097]    Referring to  FIG. 6 , the PDCP layer sends at operation  602  the PDCP packet to the PDCP adaptation layer  108  without encryption and ROHC. The PDCP adaptation layer  108  duplicates at operation  604  only source address and the destination address included in the IP header. 
         [0098]    In an embodiment, the PDCP adaptation layer  108  performs encryption as per the PDCP encryption functionality where the parameters required for encryption will be shared by the PDCP layer to the PDCP adaptation layer  108 . The PDCP adaptation layer  108  excludes the appended duplicate IP header, the adaptation header and the PDCP header from the encryption. 
         [0099]    In an embodiment, eNB  102  sends the UE ID and MAC address mapping to the WLAN AP  104  prior to sending the data packet. In an example, the UE ID is an international mobile subscriber identity (IMSI)/international mobile equipment identity (IMEI). 
         [0100]    In an embodiment, the eNB  102  shares the UE ID and an association ID to the WLAN AP  104  so that the WLAN AP  104  generates the mapping table. 
         [0101]    Further, the PDCP adaptation layer  108  adds at operation  606  the header including the bearer ID. The PDCP adaptation layer  108  sends at operation  608  the data packet along with the header to the WLAN AP  104 . After receiving the data packet along with the header by the WLAN AP  104 , the WLAN AP  104  identifies at operation  610  the MAC address from the destination address included in the IP header and generates at operation  612  the MAC header using the identified MAC address. The WLAN AP  104  sends at operation  614  the data packet along with the MAC header to the UE  106 . The WLAN entity in the UE  106  receives the data packet along with the MAC header. The WLAN entity uncovers at operation  616  the MAC header and passes to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  removes at operation  618  the duplicate IP header and pass to the PDCP layer based on the bearer ID. 
         [0102]    Referring to  FIG. 7 , the PDCP layer performs packet routing on receiving the IP packets from the upper layer (i.e., IP layer). The PDCP layer determines to route the data packet via the WLAN AP  104  then duplicates at operation  702  IP header and appends the duplicated IP header before the PDCP header. Then it performs normal PDCP functionality like ROHC and encryption on a PDCP payload. The data packet includes the duplicated IP header, the PDCP header and the data packet is sent to the PDCP adaptation layer  108 . The PDCP adaptation layer  108  adds at operation  704  the adaptation header including the bearer ID in between the duplicated IP header and the PDCP header. 
         [0103]    The PDCP adaptation layer  108  forwards at operation  706  the data packet to the WLAN AP  104 . After receiving the data packet from the PDCP adaptation layer  108 , the WLAN AP  104  identifies at operation  708  the MAC address based on the IP header (which is the first header in the data packet that it receives from the PDCP adaptation layer  108 ) and further generates at operation  710  the MAC header with the appropriate MAC addresses in the MAC header. The WLAN AP  104  maintains the mapping of the IP header to the MAC address. The WLAN AP  104  sends at operation  712  the data packet to the UE  106 . The receiving WLAN entity at the UE  106  uncovers at operation  714  the MAC header using the legacy WLAN MAC procedures and then provides the data packets to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  removes at operation  716  the duplicated IP header and parses the adaptation header and based on the bearer ID present in the adaptation header routes the data packet to the appropriate entity (for example: PDCP layer of LTE) at the UE  106 . In an embodiment, the PDCP adaptation layer  110  parses and removes only the adaptation header and then sends the data packet to the PDCP layer. The PDCP layer removes the duplicated IP header and then continues its normal PDCP functionality. 
         [0104]    Referring to  FIG. 8 , if the PDCP layer determines to route the data packet via the WLAN AP  104 , the PDCP layer duplicates at operation  802  the IP header including only the source address and the destination address and then perform ROHC and encryption. In an embodiment, the PDCP layer copies only the source and destination portions of the IP header and appends before the PDCP header. The PDCP adaptation layer  108  adds the header in between the duplicated IP header and the PDCP header. The PDCP adaptation layer  108  needs to identify the length of the IP header which can be pre-specified or informed to it by the PDCP layer. 
         [0105]    In an embodiment, the PDCP adaptation layer  108  adds at operation  804  the header including the bearer ID. Further, the adaptation layer sends ( 806 ) the data packet along with the header to the WLAN AP  104 . 
         [0106]    Once the WLAN AP  104  receives the data packet along with the header, the WLAN AP  104  identifies at operation  808  the MAC address from the IP address and generates at operation  810  the MAC header using the identified MAC address. The WLAN AP  104  sends at operation  812  the data packet along with the MAC header to the UE  106 . The WLAN entity included in the UE  106  uncovers at operation  814  the MAC header and passes to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  removes at operation  816  the duplicate IP header and passes to the PDCP layer based on the bearer ID. 
         [0107]    Referring to  FIG. 9 , the PDCP layer performs the data packet routing on receiving the IP packets from the upper layer (i.e., IP layer). The PDCP layer sends at operation  902  the PDCP packet including the PDCP header to the PDCP adaptation layer  108 . The PDCP adaptation layer  108  exchanges at operation  904  the IP header and the PDCP header location in the data packet. Then the PDCP adaptation layer  108  adds at operation  906  the adaptation header in between the IP header and the PDCP header. 
         [0108]    Further, the PDCP adaptation layer  108  forwards at operation  908  the data packet to the WLAN AP  104 . After receiving data packet by the WLAN AP  104 , the WLAN AP  104  identifies at operation  910  the MAC address based on the IP header (which is in the first location of the data packet) and further generates at operation  912  the MAC header with the MAC addresses in the MAC header. It maintains the mapping of IP header to the MAC address. The WLAN AP  104  sends at operation  914  the data packet to the UE  106 . The receiving WLAN entity at the UE  106  uncovers at operation  916  the MAC header using the legacy WLAN MAC procedures and then provides the data packet to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  removes at operation  918  exchanged position of the IP header and the PDCP header and uncovers the adaptation header and then forwards the data packet to the PDCP layer at the UE  106 . 
         [0109]    Referring to  FIG. 10 , the PDCP sends at operation  1002  the PDCP packet to the PDCP adaptation layer  108  with encryption and ROHC from end of the IP header. Based on the receiving the PDCP packet, the PDCP adaptation layer  108  exchanges at operation  1004  the location of the IP header and the PDCP header. Further, the PDCP adaptation layer  108  adds at operation  1006  the header including the bearer ID. The PDCP adaptation layer  108  sends at operation  1008  the data packet along with the header to the WLAN AP  104 . 
         [0110]    After receiving the data packet along with the header by the WLAN AP  104 , the WLAN AP  104  identifies at operation  1010  the MAC address from the IP address and generates at operation  1012  the MAC header using the identified MAC address. Further, the WLAN AP sends at operation  1014  the data packet along with the MAC header to the UE  106 . The WLAN entity uncovers at operation  1016  the MAC header and passes to the PDCP adaptation layer  110 . The PDCP adaptation layer  110  exchanges at operation  1018  the location of IP header and the PDCP header. 
         [0111]      FIG. 11  is a sequence diagram indicating various operations and procedures involved in establishing communication between the eNB  102  and the WLAN AP  104  using a UE specific tunnel identified (TEID) according to an embodiment of the present disclosure. 
         [0112]    Referring to  FIG. 11 , the eNB  102  sends at operation  1102  a request to establish a general packet radio service (GPRS) tunneling protocol (GTP) tunnel with the WLAN AP  104 . The tunnel ID is exchanged at operation  1104  between the eNB  102  and the WLAN AP  104 . The PDCP adaptation layer  108  adds at operation  1106  the bearer ID and the UE ID. The PDCP adaptation layer  108  sends at operation  1108  the data packet with the header to the WLAN AP  104 . Once the WLAN AP  104  receives the data packet along with the header, the WLAN AP  104  identifies at operation  1110  the MAC address from the UEID included in the adaptation header and generates at operation  1112  the MAC header from the identified MAC address. The WLAN AP sends at operation  1114  the data packet along with the MAC header to the UE  106 . 
         [0113]    In an embodiment, once the eNB  102  determines to route partial data packets or full data packets to the UE  106  over the associated WLAN AP  104 , the eNB  102  establishes the GTP tunnel with the WLAN AP  104  where the TEID has one to one mapping with a UE identifier. 
         [0114]    For example, the UE ID can be a temporary mobile station identifier (TMSI), the IMSI, the IP address assigned to the UE  106 , association ID of the UE  106  with the WLAN AP  104  or any other UE identity that is used in a 3rd generation partnership project (3GPP) network. 
         [0115]    In an embodiment, the WLAN AP  104  maintains the mapping table of the UE ID and the MAC address which helps the WLAN AP  104  to identify corresponding UE when a data packet is received from the eNB  102 . 
         [0116]    In an embodiment, the UE  106  shares the MAC address to the eNB  102  and the eNB  102  shares with the WLAN AP  104  while establishing the tunnel. 
         [0117]    In an embodiment, the TEID is mapped to the MAC address of the UE  106 . The WLAN AP  104  on the receiving data packets from the eNB  102  identifies the UE  106  (among plurality of UEs) to which the data packets be routed. 
         [0118]    In an embodiment, the TEID can be mapped to other UE identities which in turn are mapped to the MAC address. 
         [0119]    In an embodiment, the UE  106  shares the association ID with the eNB  102  after associating with the WLAN AP  104 . The TEID can be mapped to association ID which the WLAN AP  104  initially generates a mapping table of association ID to MAC address of UEs. 
         [0120]    In an embodiment, the TEID is mapped directly or indirectly to the MAC address, the PDCP adaptation header includes the bearer ID which helps the WLAN entity to sends the data packets to the PDCP adaptation layer  110 . 
         [0121]    The eNB  102  establishes the tunnel with the associated WLAN APs  104  where the tunnel is identified by the TEID which is not mapped to the UE ID. The data packets for all the UEs which have to be routed via the associated WLAN AP  104  will be sent to the WLAN AP  104  on the single tunnel. 
         [0122]    In an embodiment, the adaptation header includes the UE ID which helps the WLAN AP  104  to identify the UE  106  and accordingly identify the corresponding MAC address of the UE  106 . 
         [0123]    In an embodiment, the adaptation header includes the MAC address of the UE  106  based on which the WLAN AP  104  generates the MAC header. In this scenario, the MAC address is reported by the UE  106  to the eNB  102 . In an embodiment, the adaptation header includes any other UE IDs which is then mapped by the WLAN AP  104  to the corresponding MAC address. In an embodiment, the eNB  102  informs MAC address and the UE ID that is to be used in the adaptation header to the WLAN AP  104  before the eNB  102  sends the data packets to the WLAN AP  104 . 
         [0124]    In an embodiment, the eNB  102  identifies the WLAN AP  104  based on IP addresses of the WLAN AP  104  which are assigned by a LTE network. 
         [0125]    In an embodiment, the WLAN AP  104  associates with the eNB  102  based on the IP address of the eNB  102 . 
         [0126]    In an embodiment, the eNB  102  identifies the WLAN AP  104  through the UE  106 . 
         [0127]    In an embodiment, the eNB  102  configures the UE  106  to report the result of scanning when both the eNB  102  and the WLAN AP  104  are in the vicinity to the UE  106 . 
         [0128]    Based on reports from the multiple UEs, the eNB  102  can build a list of WLAN APs which it can associate with for the LTE Wi-Fi aggregation. 
         [0129]      FIG. 12  is a sequence diagram various operations and procedures involved in establishing communication between the eNB  102  and the WLAN AP  104  using the UE and flow specific TEID according to an embodiment of the present disclosure. 
         [0130]    Referring to  FIG. 12 , in an embodiment, the eNB  102  sends at operation  1202  the request to establish the GTP tunnel with the WLAN AP  104 . The request includes the UE identifier (e.g., MAC address) and the bearer ID. The TEID provides at operation  1204  one to one mapping with the UE ID. The WLAN AP  104  generates at operation  1206  the mapping table of TEID to the MAC address. The PDCP adaptation layer  108  adds at operation  1208  the bearer ID. The PDCP adaptation layer  108  sends at operation  1210  the data packet along with the header to the WLAN AP  104 . 
         [0131]    In an embodiment, the WLAN AP  104  applies the QoS if the header from PDCP adaptation layer  108  includes the QoS. 
         [0132]    Further, the WLAN AP  104  identifies at operation  1212  the MAC address from the TEID. The WLAN AP  104  generates at operation  1214  the MAC header from identified MAC address and sends at operation  1216  the data packet along with the MAC header to the UE  106 . 
         [0133]    The eNB  102  establishes the GTP tunnel with the WLAN AP  104  where the mapping of TEID and the UE ID along with the bearer ID. 
         [0134]      FIG. 13  is a sequence diagram indicating various operations and procedures involved for indicating the UE preference indication (i.e., one time indication to the eNB  102 ) according to an embodiment of the present disclosure. 
         [0135]    Referring to  FIG. 13 , the UE preference indication can be provided based on an operator AP or a private AP. In an embodiment, the UE  106  checks at operation  1302  the support of LTE WLAN aggregation in the capability indication. The UE  106  sends at operation  1304  the capability indication to the eNB  102 . In an embodiment, the UE  106  checks at operation  1306  the indication whether aggregation feature is enabled or disabled by the user. The UE  106  sends at operation  1308  the aggregation enable information/aggregation disable information to the eNB  102 . In an embodiment, the UE  106  checks at operation  1310  the preference indication for the operator AP or the private AP. The UE  106  sends at operation  1312  preference indication to the eNB  102 . Based on the indication information, the eNB  102  determines at operation  1314  to use the aggregation. The eNB  102  determines at operation  1316  whether the UE  102  prefers the operator AP. If the UE  102  prefers the operator AP then the eNB  102  determines at operation  1318  to use the aggregation and sends the command based on the aggregation. If the UE  106  does not prefer the operator AP then, the eNB  102  does not send at operation  1320  the aggregation command. 
         [0136]    If UE preference is Operator AP: 
         [0137]    a) the eNB  102  sends WLAN aggregation add command (Scell Addition) 
         [0138]    b) the UE  106  performs association with indicated operator AP if the UE  106  not using the Wi-Fi (for the private WLAN AP) 
         [0139]    c) the UE  106  performs disassociation with the current private AP and performs association with the indicated operator AP, if the UE  106  uses the Wi-Fi (for the private WLAN AP) 
         [0140]    If UE preference is Private: 
         [0141]    Procedure A: 
         [0142]    1) If the Wi-Fi in use (for the private AP) then the eNB  102  does not send the aggregation command 
         [0143]    2) If Wi-Fi not in use (for the private AP) then the eNB  102  sends the aggregation command 
         [0144]    a) the eNB  102  detects the Wi-Fi usage based on “Wi-Fi Status Indication” which is sent by the UE  106  before the eNB  102  sends the aggregation command 
         [0145]    Procedure B: 
         [0146]    The eNB sends aggregation command irrespective of the Wi-Fi status:
       The UE  106  displays the command to the user via the UI   If the user agrees to perform the Wi-Fi aggregation then the UE  106  performs association with the indicated operator AP   If the Wi-Fi is in use then the UE  106  first performs dis-association       
 
         [0150]    Procedure C:
       If the Wi-Fi is in use then the eNB  102  sends the “Interest Indication”   The UE indicates the Wi-Fi Status to the eNB  102  after the UE  106  dis-associates with the AP   This may happen at a later time   This may also be a time limited behavior   UE sends the status if the Wi-Fi status becomes “not in use” within a configured time   This option can also be covered by the “Wi-Fi Status Indication” if these indications are sent every time Wi-Fi status changes (not only on the eNB request)   Alternatively, the eNB  102  can send the aggregation command again after some time       
 
         [0158]    If UE preference is selected list of Private APs 
         [0159]    a) If the Wi-Fi is in use with one of the APs in the list of “Prioritized Preferred Private APs then the eNB  102  does not sends the aggregation command 
         [0160]    (i) the eNB  102  detects the list of prioritized preferred APs 
         [0161]      FIG. 14  is a sequence diagram indicating various operations and procedures involved for the UE preference configuration but not indicated to the eNB  102  according to an embodiment of the present disclosure. 
         [0162]    Referring to  FIG. 14 , in an embodiment, the UE  106  checks at operation  1402  the support of LTE Wi-Fi aggregation in the capability indication. The UE  106  sends at operation  1404  the capability indication to the eNB  102 . In an embodiment, the UE  106  checks at operation  1406  the indication whether aggregation feature is enabled or disabled. The UE  106  sends at operation  1408  the aggregation enable information or the aggregation disable information) to the eNB  102 . In an embodiment, the UE  106  sends at operation  1410  the preference indication configured but not indicated to the eNB  102 . The eNB  102  determines at operation  1412  to use the aggregation. The eNB  102  sends at operation  1414  the aggregation command to the UE  106 . The UE  102  itself determines at operation  1416  prefer operator AP. If the UE prefers the operator AP then, the UE  106  associates at operation  1418  with the indicated AP. If the UE does not prefer the operator AP then, the UE does not associate at operation  1420  with the indicated AP.
       UE preference is configured based on the user selection via the UI       
 
         [0164]    It is not indicated to the eNB  102 
       the eNB  102  determines to configure the aggregation AP then it sends the aggregation command       
 
         [0166]    The UE  106  performs action based on the user configured UE preference for accepting or rejecting the command 
         [0167]    In an embodiment, the UE  106  can configure its preference of the private APs or the operator aggregation APs based on the user input. The UE  106  can indicate this preference to the eNB  102  in advance and the eNB  102  can accordingly determines to configure the aggregation AP. The eNB  102  can determine whether the Wi-Fi is in use or not at the UE  106 . The UE  106  can send this Wi-Fi status indication based on the request from the eNB  102  before the eNB  102  commands the UE  106  to configure the AP for aggregation. In an example, if the UE  106  has indicated its preference of operator aggregation APs then the eNB  102  can configure the aggregation AP without worrying about the Wi-Fi status at the UE  106 . The UE  106  will have to disassociate with it and associate with the indicated operator AP for the aggregation, if the UE  106  is connected to the private AP. 
         [0168]    In an embodiment, the UE  106  does not configure its preference of the private APs or operator aggregation APs but when the eNB  102  sends the command to aggregate indicated operator AP, then the UE  106  prompts the user to accept or reject the aggregation through the user interface. The UE  106  acts according to the user selection for accepting or rejecting the aggregation. 
         [0169]    The below table shows the UE preference indication. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
             
             
               
                 User preference 
                 eNB sends aggregation 
                 If Private AP &gt; operator 
               
               
                 configured and 
                 command based on user 
                 AP AND Wi-Fi Status is 
               
               
                 indicated to eNB 
                 preference and Wi-Fi 
                 in use then do not send 
               
               
                 102 
                 Status at UE 106 
                 Aggregation Command 
               
               
                   
                   
                 If Op AP &gt; Private AP 
               
               
                   
                   
                 then send Aggregation 
               
               
                   
                   
                 Command irrespective of 
               
               
                   
                   
                 Wi-Fi Status 
               
               
                 User Preference 
                 eNB sends Aggregation 
               
               
                 Configured but 
                 Command without 
               
               
                 NOT Indicated to 
                 considering user 
               
               
                 eNB 
                 preference or Wi-Fi 
               
               
                   
                 Status at UE 
               
               
                   
                 UE acts based on 
                 If Private AP &gt; Op AP 
               
               
                   
                 Configured User 
                 then reject the command 
               
               
                   
                 Preference 
                 If Op AP &gt; Private AP 
               
               
                   
                   
                 then accept the command 
               
               
                 User Preference 
                 eNB sends Aggregation 
               
               
                 NOT Configured in 
                 Command without 
               
               
                 advance 
                 considering user 
               
               
                   
                 preference or Wi-Fi 
               
               
                   
                 Status at UE 
               
               
                   
                 UE prompts user for 
               
               
                   
                 accepting/rejecting the 
               
               
                   
                 aggregation 
               
               
                   
                 UE acts based on user 
                 If user agrees then accept 
               
               
                   
                 input 
                 else reject the command 
               
               
                   
               
             
          
         
       
     
         [0170]      FIG. 15  is a schematic of data packet format in which a WLAN AP distinguishes the upper layer according to an embodiment of the present disclosure. 
         [0171]    Referring to  FIG. 15 , a new value of protocol ID field in a subnetwork access protocol (SNAP) extension header can be used to identify that the data packet is from the LTE. A reserved value of protocol ID can be used to identify the data packets from the LTE network. In an embodiment, the PDCP forms the data packet and sends to the PDCP adaptation layer  108 , if the PDCP determines to route the data packet via the WLAN AP  104 . The PDCP adaptation layer  108  generates the LLC/SNAP header with appropriate fields and sends the data packet to the AP. The AP on receiving the data packet can identify based on the SNAP header that the data packet is from the LTE and processes it accordingly in which, the WLAN AP  104  generates the MAC header based on the tunnel ID generated or based on the adaptation header if the MAC address or association ID is included in the adaptation header. 
         [0172]    In an embodiment, the encryption in the LTE network is not performed for the data packets which are to be routed via the WLAN. The eNB  102  can configure the WLAN to always perform encryption. The eNB  102  can also configure the encryption scheme to use among the ones available at the WLAN AP  104 . 
         [0173]    When the eNB  102  establishes the tunnel with the WLAN AP  104  for routing the packets to the UE  106 , where the TEID is one to one mapped to the UE ID, the eNB  102  also indicates the access category of the packets. In an embodiment, the eNB  102  can also indicate the parameters of the indicated access category for example, if video traffic is routed via the WLAN AP  104 , then the eNB  102  can indicate a CW value which the WLAN AP  104  should follow for the data. In addition, the PDCP adaptation layer  108  can form the traffic ID (TID) to select a user priority (UP) for prioritized QoS or a traffic specification (TSPEC) for the parameterized QoS. In an embodiment, the adaptation header includes the QoS access class so that the WLAN AP  104  can process the data packet based on the QoS. In an embodiment, the adaptation header includes the bearer ID and the WLAN AP  104  maps to the access class based on the tunnel establishment. 
         [0174]    In an embodiment, when the eNB  102  establishes the tunnel with the WLAN AP  104  for routing the packets to the UE  106  where the TEID is one to one mapped to the UE ID and the bearer ID, the eNB  102  also indicates the access category of the packets. The eNB  102  can also indicate the parameters of the indicated access category for example, if the video traffic is routed via the WLAN AP  104 , then the eNB  102  can indicate the CW value which the AP should follow for the data. 
         [0175]    Based on the QoS mapping from the 3GPP service or QCI to 15 802.11 QoS, the eNB  102  can instruct the UE  106  to send an add traffic stream (ADDTS) request frame to the WLAN AP  104 . The eNB  102  can provide the UE  106  with the set of parameters necessary to identify various kinds of PDU or incoming MAC service data unit (MSDU) that belong to the particular TS in a TCLAS element. In addition, the WLAN AP  104  forms the TSPEC element which includes parameters like service start time, minimum data rate, mean data rate and peak data rate or the like. The WLAN AP  104  responds with the ADDTS response frame based on the available resources. 
         [0176]    In an embodiment, the eNB  102  can instruct the WLAN AP  104  to include the upper layer protocol identification (U-PID) to indicate to the UE  106  that the data packet is from the PDCP. 
         [0177]      FIG. 16  illustrates a computing environment  1602  implementing a mechanism for routing the data packet to the UE  106  in the LTE-WLAN aggregation system  100  according to an embodiment of the present disclosure. 
         [0178]    Referring to  FIG. 16 , the computing environment  1602  comprises at least one processing unit  1608  (e.g. processor) that is equipped with a control unit  1604 , an arithmetic logic unit (ALU)  1606 , a memory  1610 , a storage unit  1612 , a plurality of networking devices  1616  and a plurality input output (I/O) devices  1614 . The processing unit  1608  is responsible for processing the instructions of the technique. The processing unit  1608  receives commands from the control unit  1604  in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU  1606 . 
         [0179]    The overall computing environment  1602  can be composed of multiple homogeneous or heterogeneous cores, multiple CPUs of different kinds, special media and other accelerators. The processing unit  1608  is responsible for processing the instructions of the technique. Further, the plurality of processing units  1604  may be located on a single chip or over multiple chips. 
         [0180]    The technique comprising of instructions and codes required for the implementation are stored in either the memory unit  1610  or the storage  1612  or both. At the time of execution, the instructions may be fetched from the corresponding memory  1610  or storage  1612 , and executed by the processing unit  1608 . 
         [0181]    In case of any hardware implementations various networking devices  1616  or external I/O devices  1614  may be connected to the computing environment  1602  to support the implementation through the networking unit and the I/O device unit. Further, a communication unit (not shown) is configured for communicating internally between internal units and with external devices via one or more networks. 
         [0182]    The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in  FIGS. 1, 2, 3A, 3B, and 4 to 16  include blocks, elements, actions, acts, operations, or the like which can be at least one of a hardware device, or a combination of hardware device and software module. 
         [0183]    The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. 
         [0184]    While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims their equivalents.